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

Toggle sidebar Toggle sidebar
J

joethejet

Distinguished
Oct 14, 2009
33
0
18,530
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?
 
Solution
F
I would backup your data to another drive, but be prepared for file corruption.

The $BITMAP is an NTFS metafile which keeps a record of free and in-use clusters. AIUI, if this gets messed up, then there is the potential for cross-linking. That's where two or more files think that they own the same cluster.

The Index errors relate to the $MFT (master file table). This metafile consists of records which store the name and properties of each file.

For example, there is a problem with file #26431. In DMDE you can see the properties of this file by examining its $MFT record. To do this, launch DMDE and select your target disk. Then double-click your NTFS volume, select Editor -> File Record, and key in your file number.
Sort by date Sort by votes
Can you replace the damaged system file?

What does Scandisk say about the system file?

Can you retrieve the SMART data from each drive? You may need a tool such as smartctl (Linux) which can see the HDD behind the RAID controller.
 
Last edited:
Upvote 0 Downvote
fzabkar said:
Can you replace the damaged system file?

What does Scandisk say about the system file?

Can you retrieve the SMART data from each drive? You may need a tool such as smartctl (Linux) which can see the HDD behind the RAID controller.
Click to expand...
I tried to replace the dll, but scandisk still didn't like it.

My sfc found corrupt files but was unable to fix some of them. I have a zip of the cbs.log file, but I'm not sure how to upload it here. Either way, 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=}

As for the the disks: They are WD1001FAES-74W6A0 drives. I'm not sure what other "smart" information you need. I have the IRST.
 
Upvote 0 Downvote
For your original #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. "

That is unlikely to work.
Moving a physical drive, or clone, or image to new hardware often fails.
 
Upvote 0 Downvote
joethejet said:
So, I'm sort of hosed here then? Any advice on how to correct the corrupt file? Is it possible?
Click to expand...
The question is...is it a bad physical drive, or a bad file.

A bad physical drive should be fixable in the RAID 1 by simply replacing the drive in question, and let the array rebuild itself.

A bad file, that is uncorrectable via what you've already tried...more problematic.
 
Upvote 0 Downvote
Obviously I'm trying to avoid reinstalling everything else. Sounds like that may not be in the cards. That's a LOT of stuff to reinstall.

So, if I break the Raid and, perhaps, only one of the disks are bad, then, possibly, that's the same as replacing a drive and reinstablishing the Raid. Right? I just wouldn't have a raid array, I would have two big disks.

But, if the file is really hosed, even if the disk is good, I'm not going to make much progress? How come if I downloaded a new dll, sfc still says the file is corrupt? Are there any other steps I can take?

I guess I could try to upgrade to W10 and if it doesn't work, I can go back to a new install. At that point, I would probably just buy a new computer.
 
Upvote 0 Downvote
Buying a whole new PC because of a single corrupt file, or a bad drive is a pretty big stretch.
You'd still have to reinstall all of your applications anyway.

Firstly, back up ALL your personal files. Doc/Music/Video/whatever else you do.
Some other physical drive or location.

Then try an inplace Upgrade to Win 10. That may fix the issue.
If it works, great.
If it fails, the system is no more broken than it is now.

But take this as a warning to always have a known good backup. Preferably of the whole system.
RAID 1 is not that.
 
Upvote 0 Downvote
First off, thanks so much for all your help. It is greatly appreciated!

Yes, I thought that Raid 1 would protect me in the event of a disk failure, but maybe not a corrupt spot on my disk.

I have an image of my computer. Do I need a full backup too?

The computer is 8 1/2 years old so I guess I'm thinking if I have to reinstall everything, I may as well invest in new hardware at the same time. My goal is to save all that time in reinstalls ( not to mention things just don't working due to licensing and finding the install keys).

Seems like it might be worth breaking the raid first to see if I have a bad drive? Since they will both be boot disks, I guess I can try each in turn?

Of course, if I can't get either to boot, then that will make it hard to upgrade to W10 in place. It's very weird to me that sometimes it boots and other times it doesn't.

Any ideas on this question: How come if I downloaded a new dll, sfc still says the file is corrupt? Are there any other steps I can take?
 
Upvote 0 Downvote
IIUC, SFC checks the integrity of each system file by comparing it against an original list of file properties. If a DLL is subsequently upgraded, then SFC flags a mismatch error. ICBW, though.

AISI, the original file had a version of 6.1.7600.16385, but is now reporting a version of 6.1.7601.17514.

https://dllworld.org/nlsdata001d-dll/

According to the following web site, 6.1.7601 corresponds to Windows 7, Service Pack 1.

https://gaijin.at/en/infos/windows-version-numbers

Therefore, I believe that the "error" is a red herring and is nothing to be concerned about.

As for SMART, look for reallocated, pending or uncorrectable sectors.
 
Upvote 0 Downvote
Uh, Ok. So, if that's probably not an issue, THEN, I likely have a hard disk that is being flaky?

In that case, would breaking the raid and trying each disk individually identify if this is the case?

Oh, and what about this: I have an image of my computer. Do I need a full backup too?
 
Upvote 0 Downvote
joethejet said:
Uh, Ok. So, if that's probably not an issue, THEN, I likely have a hard disk that is being flaky?

In that case, would breaking the raid and trying each disk individually identify if this is the case?

Oh, and what about this: I have an image of my computer. Do I need a full backup too?
Click to expand...
An "image", with what tool?
A full drive image will contain whatever corrupt or incorrect files it was made with.

For the drives...breaking the RAID may be as simple as simply disconnecting one of them.
That is the purpose behind the RAID 1. A drive fails, the system can limp along with the other one.
It will report as a degraded array, but it will work.
 
Upvote 0 Downvote
An image is a complete, sector by sector, backup. You can clone this image onto a new drive, or you can mount the image and recover individual files from it.

For example, 7-Zip is just one tool that can mount a disc image.

https://www.7-zip.org/

I would first examine each drive with smartctl (without breaking the RAID). Alternatively, try GSmartControl (Windows).

https://gsmartcontrol.sourceforge.io/home/index.php/Downloads
 
Upvote 0 Downvote
I used the Windows 7 tool to create the image.

From what you guys said, I probably don't have a corrupt file?

Yes, it would be simpler to just unhook one drive and see if it boots OK. Won't totally tell me, but I can "limp along" for awhile and see if the flakiness goes away.

So, I think you're telling me that if I have an image, I do not need a full backup?

is smartctl better than Data Lifeguard Diagnostic for Windows? I have already downloaded that.
 
Upvote 0 Downvote
Data LifeGuard won't tell you if your drive has reallocated, pending or uncorrectable sectors. It also won't see each individual drive behind a RAID controller. Its only useful feature, IMHO, is that it provides the necessary proof for an RMA.

If you break the RAID and run with it, Windows will make changes which obviously won't be replicated in the other RAID member. Therefore you won't be able to simply re-RAID the drives without a complete rebuild.

Also, some RAIDs place their RAID metadata at the beginning of the drive, which means that these hidden areas will be exposed to the OS when the RAID is broken. Normally the OS expects to find a partition table in sector 0, not RAID metadata, so you may find that the individual drive does not boot.
 
Upvote 0 Downvote
"I plan to upgrade the computer to Windows 10 in January. "

Personally, I would just do a full OS install, and reinstall of everything else.
Forget the RAID, forget trying to 'fix' this array...start over with a clean OS install.

And institute a comprehensive backup plan, so that you won't see this again. RAID or no RAID.
 
Upvote 0 Downvote
fzabkar said:
Data LifeGuard won't tell you if your drive has reallocated, pending or uncorrectable sectors. It also won't see each individual drive behind a RAID controller. Its only useful feature, IMHO, is that it provides the necessary proof for an RMA.

If you break the RAID and run with it, Windows will make changes which obviously won't be replicated in the other RAID member. Therefore you won't be able to simply re-RAID the drives without a complete rebuild.

Also, some RAIDs place their RAID metadata at the beginning of the drive, which means that these hidden areas will be exposed to the OS when the RAID is broken. Normally the OS expects to find a partition table in sector 0, not RAID metadata, so you may find that the individual drive does not boot.
Click to expand...

So, you're thinking if I use smartctl I'll know whether one of my disks is bad?

Yes, if I run with one disk, I would be expecting to have to resynch.

I'm using whatever Raid that came with a Dell computer.
 
Upvote 0 Downvote
"I plan to upgrade the computer to Windows 10 in January. "

Personally, I would just do a full OS install, and reinstall of everything else.
Forget the RAID, forget trying to 'fix' this array...start over with a clean OS install.

And institute a comprehensive backup plan, so that you won't see this again. RAID or no RAID.
Click to expand...

Well, if I just upgrade my W7 box to W10, I shouldn't have to reinstall everything right? Big difference in the amount of time required.

I will likely never raid again. Seems worthless.

A comprehensive backup plan wouldn't solve this problem unless I was also making images. The problem isn't that I can't get to my files, I can, the problem is that the computer is flaky when it boots. Sometimes it does, sometimes it doesn't.

If I break the raid, will I have to reboot?
 
Upvote 0 Downvote
"A comprehensive backup plan wouldn't solve this problem unless I was also making images. "

Well, yes, that is sort of the whole point. And 'images' don't need to be, nor should they be, full drive images all the time.
A Full image, then a series of Incremental or Differential images is what is needed.

In my system currently, I could recover any of the individual drives, including the OS drive, from any date in the last month or so.
I had to do exactly that last year this time for one of my secondary drives.
SSD died suddenly, 960GB Sandisk with 605GB data on it.
Put in a new drive, click click...all 605GB recovered exactly as it was at 4AM that morning when it ran its nightly Incremental.

Read here:

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 forums.tomshardware.com
(my procedure has altered a little since then, but the same basic concept)
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom