Win 7, WD blue 500 GB HD, can no longer boot

AnPeter90

Distinguished
Jan 16, 2017
4
0
18,510
Hi,

I run a desktop on Win 7, with 2 HD in a mirror configuration. Recently, one HD stopped working. I have replaced the broken HD with a new WD Caviar “Blue” 500 GB, reestablished the RAID; everything seemed to be ok. Until about 3 weeks ago, the replaced HD stopped working. I have replaced the failed HD, but it would not integrate into the system. The running HD started having problems on startup; however, I could get the PC working. From my local service center there was no real help to fix the issue. Finally, the PC would not startup anymore. So, all the desktop options are no longer available.


I have tried booting from the Win 7 System Repair Disk; all these attempts did not get me anywhere. I have gone many times through the System Recovery Options without success.


I have also tried booting from the Win 7 OEM systems disk. This did not solve the problem; however, the System Recovery Options showed that Windows sits now on D: \.


During these attempts I got 2 error messages:


· RecEnv.exe – Corrupt file (The file or directory E:\$Mft is corrupt and unreadable. Please run the Chkdsk utility). I did run Chkdsk as recommended; however, this did not solve the problem. During the rerun of the System Recovery Options another error message was displayed:


· RegSvr32 (The module “fverecover.dll” may not [be] compatible with the version of Windows you are running. Check if the module is compatible with an x86 (32 bit) or x64 (64 bit) version of regsvr32.exe.

Due to the nature of the problem, I could check the compatibility of the “fverecover.dll”.
I have done DISKPART > list volume. The check came up with:
· Volume 0, C, System Rese, NFTS, Partition 100 MB, Healthy
· Volume 1, D, NFTS Partition 37 GB Healthy
· Volume 2 E Removable 0B No Media
· Volume 3 F Removable 0B No Media



I have read about the option from upgrading Win 7 from the OEM Systems disk; however, this option is not for me, as I cannot access the desktop environment.


I have made a completely new installation of Win 7 on a Seagate HD, just to verify that Motherboard and other peripherals are working properly, which they do.


The not bootable HD is spinning and after starting up, the sounds are completely normal. Most likely, the HD is ok.


I would like to run Win 7 from the currently not functioning WD HD to retrieve some data that are only on that HD. All other data are on a separate backup disk.


Any suggestion how to successfully tackle the problem?
 
Solution
Whenever you run a RAID array of any degree, it's advised to use identical(even down to the capacity's) HDD's irrespective of the RAID numbering. If you can install your OS via the bootable media on a stand alone HDD then it's quite possible that you're lacking the necessary drivers during installation of your RAID 1 array. Might I ask what your full system's specs are inclusive of the purpose of the RAID array? It's possible that a different approach might help solve your problems.

On another note, I've found that WD drives tend to be a slightly overpriced and tend to be the ones with higher failure rates. Second note, your installation being corrupt is what lead you to this arena...are you sure your installer isn't corrupt?

Lutfij

Titan
Moderator
Whenever you run a RAID array of any degree, it's advised to use identical(even down to the capacity's) HDD's irrespective of the RAID numbering. If you can install your OS via the bootable media on a stand alone HDD then it's quite possible that you're lacking the necessary drivers during installation of your RAID 1 array. Might I ask what your full system's specs are inclusive of the purpose of the RAID array? It's possible that a different approach might help solve your problems.

On another note, I've found that WD drives tend to be a slightly overpriced and tend to be the ones with higher failure rates. Second note, your installation being corrupt is what lead you to this arena...are you sure your installer isn't corrupt?
 
Solution