[SOLVED] Boot Problems/Disk Problems/Reimage? Help

[joethejet]

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. The disks are Western Digital

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.

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

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?

 

[fzabkar]

Surely a full surface scan of the assembled RAID (mirror) will produce an error (and degrade the RAID) if there is a difference between the two RAID members at any sector? So I can't see the point of scanning each drive separately.

A full surface scan with a tool such as HDDScan will tell you if any sector is "slow", ie if it requires read retries.

 

[USAFRet]

This is specifically where a good backup regime comes in.

Determine the problematic physical drive (if any), replace it, recover the entire data set from last nights backup.

 

[joethejet]

Yes, you have definitely convinced me that I need a better backup system. I have a large enough NAS now that it should be feasible.

Will HDDScan work if I don't reboot? I know chkdsk wants me to restart and, at least at this point, I'm afraid to do so.

What I mean be breaking the Raid wasn't to scan, but to see if one has a hardward problem and the other doesn't If so, the machine should boot without trouble. If both disks are failing then it won't make any difference and if there is a corrupted file then it won't.

 

[joethejet]

Hey USAFRet,

If you don't mind me asking, what software do you use to make your incrementals? I don't think that native W7 will do that will it?

Thanks so much.

BTW, I did a HDDScan, full scan, but it didn't find any bad sectors, just some slow ones. Of course I was logged in at the time so I don't know if that had an impact or not

 

[USAFRet]

Hey USAFRet,

If you don't mind me asking, what software do you use to make your incrementals? I don't think that native W7 will do that will it?

Thanks so much.

BTW, I did a HDDScan, full scan, but it didn't find any bad sectors, just some slow ones. Of course I was logged in at the time so I don't know if that had an impact or not

Macrium Reflect.

What is your backup situation at home?

What is your backup situation at home? And if you don't do that, why not? Every single day, I read multiple threads here of "How do I get my stuff back?" or "That drive had 5 years of photos of my kids!!" Be it a dead drive, dropped phone, virus, accidental deletion, formatting the wrong...

forums.tomshardware.com