Replacing Hard Drive?

Hi Guys,


Ok, currently I have a raid (1) disk array and it's having some problems, at least I believe it's a disk problem as when I do a scandisk, it can't repair a system file. I would think that raid (two duplicate hard drives) would repair this, but apparently not.



Currently, I don't dare shutdown my computer and I never know if it will successfully boot up again. The last time I spent two days trying to fix the problem and then, suddenly, it booted after no apparent change was made.



Because I'm having problems, I made an image of my computer and put it on my NAS.



In any case, I'm thinking my best plan is to either break the raid and reinstall my image there, or get a new hard drive and install it there.


I plan to upgrade the computer to Windows 10 in January.



Any thoughts on which direction I should take above and whether this approach is advisable at all. I suppose my problems could be memory or motherboard related also?


Thanks in advance for your help.


Joe

First step is to nake sure which disk is failing if indeend it is if you goto dick makers website they have a tool specific for their drive to test it. Is this a hardware raid or software

There are two disks so I assume that's hardware Raid.



They are WD1001FAES-74W6A0 drives.

Hardware raid 1 (disk mirroring) is just about useless. You are better off splitting into a system disk and a backup disk, and using a tool such as Macrium Reflect / AOMEI to image the system disk to the backup disk at reasonable intervals (eg full image once a month, incrementals every couple of days).


This can protect you against other failures besides a disk failure (like a virus infection or system disk corruption) which in a mirrored system will happily trash both disks.

Ok, so, given where I am at, should I break the raid 1? Would that fix the system problem I'm having?


Essentially I'm looking for advice on how to get my current system more stable.



Thanks.

Most of the RAID arrays are built under BIOS.
There are many kinds of RAID arrays. Standard RAID levels - Wikipedia
With two disks it can be
- RAID 1 (mirror). One is a copy of the other and you can disassemble the array without loosing data.
- RAID 0 (striping). Data is sent across two or more disks, if you disassemble the array you will loose ALL data.

It's very important to know if you have RAID 0 or RAID 1 before you do anything.

Don't you have a IRST icon near the clock (Intel rapid storage)? If you open it it will say if you have RAID 0 or RAID 1

It's Raid 1.



My plan is sort of like this:
1. Get the W7 box stable so it will boot. I assume I'm having a hard drive problem, not memory or MoBo because it will boot sometimes and sometimes not. Also when I do a scandisk, it tells me there is a dll that cannot be repaired.

2. To do this, either break the raid and figure out which disk is bad, or get a new disk and install the image that I made onto it.
3. Upgrade to W10
4. Take an image of W10 and, when I get a new computer, install it there so I don't have to reinstall all my programs and data.


Does this plan make any sense at all?


Oh, btw, when it doesn't boot, I'm getting These error codes


problem signature 01: 6.1.7600.16385
problem signature 02: 6.1.7600.16385
problem signature 03: unknown
problem signature 04: 176
problem signature 05: AutoFailover
problem signature 06: AutoFailover

problem signature 07: NoRootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Do a System File Check (sfc)
Open a CMD window as administrator and type:
sfc /scannow

If you have IRST icon near the clock, the best way to break the array is using it.

Once it is out of the array, use the WD tool to test the disk. A complete test can take many hours, so do it overnight.
Data Lifeguard Diagnostic

Ok, so I have the Intel Rapid Storage Tech (IRST I just figured out!) What options do I pick to break the raid and, what is it going to do to the disk that is no longer "raided"? Does it format it, or do I have two duplicate disks?


Do I need to make a new image?



The IRST says I have 126 verification errors. Is that a concern? I am running a verify and repair now.



My sfc found corrupt files but was unable to fix some of them. I have attached a zip of the cbs.log file. The relevant error is, I believe:
Cannot repair member file [l:30{15}]"NlsData001d.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2019-12-22 19:06:16, Info CSI 000001e5 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-naturallanguage6_31bf3856ad364e35_6.1.7601.17514_none_fc00d9a9415b5f6e\NlsData001d.dll do not match actual file [l:30{15}]"NlsData001d.dll" :
Found: {l:32 b:Q8CxPCVQlH0AfLGqSvOyeoCJBU/Us+RO1LIoDEVJk1c=} Expected: {l:32 b:gBoyLEE0r/NuzCOp1co/dEPck6LIOBY1UrMUEf532BM=}

I used to have RAID 0 and after backing up the files I used IRST to disassemble the RAID. Once you disassemble the RAID 1 you should end with two equal disks.