01-10-2006, 07:23 AM
Join Date: Jan 2006
I have run into a problem even though I routinely copy my boot drive to a backup drive using Western Digital (WD) Data Lifeguard. My system HDD is a WD 80 GB with 2 partitions. Always ran well. The backup drive is another WD 80 GB with 2 partitions (slightly different size than the system HDD).
After performing some MSoft "critical" patches and updating to Office SR3 I ran into many problems. So I pulled out my old backup and inserted the HDD into my system as the master drive with the old master now set as slave. All jumpers were correct. The system booted up to the configuration just before the MSoft updates. All seemed rosy.
I used the WD Data Lifeguard tool to "set up" the slave as a new boot device and copy the data from the current master to this new slave. It took a while and when finished I disconnected the master (the backup drive) and reinstalled the original drive. When I tried to boot I got an error "the following file is missing or corrupt c:\windows\system32\config\system".
Here's the real kicker. I put the backup drive back into the system by itself. It started to boot and gave the exact same error. In case you're wondering I did make sure that I didn't mix the drives up. One has a large #1 marked on top and the other has #2. Also, the difference in partition sizes and the fact that WD DLG won't let you "set up" your current c:drive pretty much makes the swaps fool proof. It worked in the past without issue.
On one drive I used a W98 boot disk to run fdisk/mbr. Now that disk gives a black screen when it is installed in the system. Strangely, if I boot using the W98 boot disk, I can see all the files on the hard drive. I tried fdisk again to set the active partition and it said "data could not be written to drive". Also, when booting the drive shows as 10 GB but fdisk shows the partition sizes as correct with the total drive size as 10GB.
The other drive that still gives "the missing or corrupt file" error also seems to have all the data files in place. One time and only one time in the middle of a dozen reboot attemps, the drive booted up as normal when I chose "last known good configuration". After that I am still getting the file error. Running Win2K setup, Repair installed a lot of stuff (seemed like a new install) but the problem persists after rebooting.
So there are 2 problems:
1. Drive that has missing/corrupt file.
2. Drive that gives black screen
Any suggestions would be grately appreciated.