Replacing Hard Drive, Windows 2000

[shamrin]

I have a customer with an IBM ThinkCentre desktop running some software that controls medical equipment. After fixing about a dozen popped capacitors, I found that his hard drive was failing. The old HDD required some repairs with HDD Regenerator in order to get an image which I eventually got. However, the machine now fails about half-way through the Windows 2000 Welcome screen with a 0x07B (inaccessible boot drive) BSOD.

The computer is a Pentium 4 so it's "of a certain age" and I'm wondering if either the hardware, BIOS or Windows 2000 are somehow incompatible with the new HDD. The new one is a SATAII but that's supposed to be backward compatible. Does anyone have any thoughts on this?

 

[phaZed]

Try to Run an sfc /scannow on the new drive.. may be corruption issues from the Regen/transfer.

Personally, it seemed notorious for 2000 and previous to have BSODs after ANY major hardware changes.

Edit:
What's safe mode doing?

 

[red12049]

I have a customer with an IBM ThinkCentre desktop running some software that controls medical equipment. After fixing about a dozen popped capacitors, I found that his hard drive was failing. The old HDD required some repairs with HDD Regenerator in order to get an image which I eventually got. However, the machine now fails about half-way through the Windows 2000 Welcome screen with a 0x07B (inaccessible boot drive) BSOD.

The computer is a Pentium 4 so it's "of a certain age" and I'm wondering if either the hardware, BIOS or Windows 2000 are somehow incompatible with the new HDD. The new one is a SATAII but that's supposed to be backward compatible. Does anyone have any thoughts on this?

May need a repair install, or perhaps this may apply: http://techpatterns.com/forums/about260.html

Let us know how you make out.

Rick

 

[YeOldeStonecat]

I'm guessing the cloning didn't go well.....the source was probably a bit dirty. I've cloned hundreds and hundreds of Win2K boxes...they cloned fine.

 

[shamrin]

What's safe mode doing?

Same BSOD part way through the boot

May need a repair install, or perhaps this may apply: http://techpatterns.com/forums/about260.html

Let us know how you make out.

Rick

Hmm, that's interesting. I forgot about the 137MB limit issue in some machines. This motherboard has a SATA port though...I can't imagine it has that restriction but will look into that and the link. Customer took machine with old hard drive last night (they need it for operations this week). I'll have it back next weekend to try and fix the HDD issue, will document solution (if I find one) then.

I'm guessing the cloning didn't go well.....the source was probably a bit dirty. I've cloned hundreds and hundreds of Win2K boxes...they cloned fine.

Well, the source WAS a bit dirty, but it boots the machine and the new drive does not so I suspect it's something about the drive.

OH wait....Did I mention that the drive was formatted as FAT? I don't know if it's FAT16 or FAT32 but I'll bet if it's FAT16 that won't handle a 500GB drive.

 

[red12049]

Same BSOD part way through the boot



Hmm, that's interesting. I forgot about the 137MB limit issue in some machines. This motherboard has a SATA port though...I can't imagine it has that restriction but will look into that and the link. Customer took machine with old hard drive last night (they need it for operations this week). I'll have it back next weekend to try and fix the HDD issue, will document solution (if I find one) then.



Well, the source WAS a bit dirty, but it boots the machine and the new drive does not so I suspect it's something about the drive.

OH wait....Did I mention that the drive was formatted as FAT? I don't know if it's FAT16 or FAT32 but I'll bet if it's FAT16 that won't handle a 500GB drive.

Neither will FAT32. If you have the cloned drive, what format is it?

Rick

 

[shamrin]

Neither will FAT32. If you have the cloned drive, what format is it?

Rick

Well, the image says that it's FAT32 (which apparently is theoretically able to go to 2TB but is twitchy on Windows 2000). Maybe I'll try creating a volume of the same size as the original disk rather than expanding the partition to take up the whole drive.

 

[YeOldeStonecat]

Well, the image says that it's FAT32 (which apparently is theoretically able to go to 2TB but is twitchy on Windows 2000). Maybe I'll try creating a volume of the same size as the original disk rather than expanding the partition to take up the whole drive.

The cloning software would handle that for you automatically.

 

[Galdorf]

What i do if they need an old os to support old software but the hardware is outdated and failing is i make an image if image is dirty i run a repair and make sure all critical data is there.
I build a new machine with windows 7 then take the repaired image and run it through vmware i have tried this over 100 times and works great i retire the old machine and toss it.
The software i use for imaging creates an image that is compatible with vm virtual machine just mount it and go.
That way they have best of both worlds not to mention you can set up a task to backup the image every day.

 

[synack2]

Inaccesible Boot Device

You need a disk driver. First go into the bios and make sure the SATA ports are set to emulate a Native IDE device or ATA not AHCI.

Next you have changed chipsets so that is where you are having your issue.

If you have access to the old hardware (it still works), or you can at least get the new hardware to boot in safe mode then, bring it up and refer to this:

http://support.microsoft.com/kb/314082

This will enable the standard ATA compatible disk controller in the registry then make a new backup and try again.

Second if the old hardware is gone, dead, onfire, etc.

Here is how I fixed it in the past... Get Falcons 4.5 UBCD. Facebook falcon UBCD and torrent it. Now reference this to fix the driver on the new hard drive. http://www.drivesnapshot.de/en/hardware.htm

Even though you didn't use snapshot to make the image these switches here will enable all the standard drivers or allow you to get the driver for the motherboard's chipset and insert it vial the .inf and .sys files, into the current hard drive that you have resored it to. This has Saved my A$$ many a times.

Third if it was a Dell did you backup the dell diag/restore partition as well. IF not you can use the fixdellmbr utility on the Falcon UBCD.

 

[tempusfugit]

Swapping a hard drive shouldn't require new drivers nor will it change the chipset.

I think bad clone is probably the right direction.