Should a 357GB Image take 24+ hours to create?

For me it is because that method (deleting the checksum values from the registry) is foolproof, whilst removing the controller and rebooting will not always fix the problem. To each his own I guess. I know many people don't like editing the registry, although they wind up doing the same by proxy.

 

Would having a tape drive conected cause this to slow things down even if it is not in use.

 

Only if it is on an IDE channel and its presence is causing the other device on the channel to use a slower speed than it is capable of.

If you think this is a problem remove all devices from IDE other than your hard-drives and see what you get. To be certain you might uninstall the controller or do the registry hack trick to make things are as best as they can be.

What model is your motherboard, maybe googling it will show what it is capable of?

If you are UDMA controller challenged you could consider adding a Promise Ultra UDMA card. This would only be a benefit if your drives also will run at UDMA 5 or 6.

 

Update Re: Should a 357GB Image take 24+ hours to create?

Finally got some new drives to save my image to, and it took about 6.5 hours so I think I'm doing alot better thanks for the help.

 

Re: Update Re: Should a 357GB Image take 24+ hours to create?

Are you using the same USB ports?

If so, then I expect the problem was that your former drives had a USB-IDE bridge that did not support USB 2. If so, you could get a newer drive enclosure and move the drive to the new enclosure.

 

I never used the USB port. Actually I am not sure what all new hardware was put into the server. Someone else changed that out over night and I just went to testing.

 

Re: Update Re: Should a 357GB Image take 24+ hours to create?

If your image tib files are still around 205GB then you probably are in the range of expected performance for your machine. You are around 525 MB/min.

Glad you got some significant improvement.