C:\Windows\System32\Config\System

[Freehold Fred]

...error and hangs at that point. Suggests 1st 'r' repair (sic)..

IBM
40GB HD looks like originally put into service 4-1/2 yrs ago.

Went to recovery console:

Fixboot --- no change.
Chkdsk/r --- took an inordinate amount of time. I wasn't watching for the first few minutes, but then all of a sudden it seemed to crawl when it hit 50% and ~1/2 hr. later got to 60%. I left while it was cooking. 3 hrs. later, client reports that it apparently completed with no other reported errors.

I am going back tomorrow to do a Restore Image thingy from the hidden partition, BUT I am suspicious about the health of the drive.

What do you think? I know that chkdsk /r recovers bad sectors. What should I be looking for? Where is the log and will I see recovered files file0001.chk, etc?

Or since HD is probably beyond the end of its use, just replace it. BUT how do I get the legitimate system off of the hidden partition and on to the new drive?

[Seth]

Hi Fred.

Blown config files coupled with a hanging chkdsk is a classic symptom of a hard drive failing. It's likely that the chkdsk /r will maintain the drive long enough for you to do something about it. BTW-The chkdsk log is found in the Event Viewer>Applications>Winlogon. At the very least the log will list minor inconsistancies...these are normal. Pretty much anything other than that, such as bad sectors or errors in the Master File Table is bad news (replace the drive).

If the system doesn't boot, I recommend going back to the Recovery Console and running BOOTCFG /REBUILD. Failing that, run a repair install. Slave the new drive and run full error checking on it. Now download the trial version of Acronis Migrate Easy. (http://www.acronis.com/homecomputing/products/migrateeasy/) It will create a bit for bit copy of the data on the failing drive, onto the new drive. When completed, boot to the new drive and run quick error checking (Checks and repairs system files). That should do it.

[Seth]

Clarification to my previous post:

All new hard drives should have full error checking run on them before an OS is installed, or in Fred's case, a direct copy is installed. The reason for this is because it's not uncommon to find a new drive with bad sectors. These bad sectors are merely a byproduct of the manufacturing processs, and are not normally indicative of a bad drive. Yet, continuous bad sectors are indicitave of such. The chkdsk can be skipped if you choose a full format when you install Windows, as the full format will automatically run a chkdsk /r.

The reason for the quick error checking (system file check) on the drive after the data and OS have been written to it, is to repair OS file errors that may be copied over to the new drive from the failing one. This is unlikely since the chkdsk /r on the old drive would have corrected this, but this step is fast and a valuable one to take.

[golfmore]

Does the /r repair the bad sectors, or just mark them to not be used? Thanks.

[Seth]

No, chkdsk /r does not repair bad sectors. When a bad sector is encountered, XP recovers the data from it, flags the bad sector as unusable, then moves the data to a different location. The sector is not repairable as the damage is usually a slight scratch or "thin spot" on the platter.

It's possible that XP won't be able to recover all the data in the bad sector. However, I've yet to see that happen as XP repeatedly reads the sector in order to properly recover the file.

[mylanta]

While it could be hard drive, the more obvious is registry corruption, go here Fred:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545

[Seth]

While it could be hard drive, the more obvious is registry corruption, go here Fred:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545

I disagree.

The above may get XP to boot, however the hanging chkdsk /r indicates a failing hard drive. As such, it is far more likely that the file corruption was caused by the failing hard drive.

[Freehold Fred]

As it turns out, there WERE errors reported and CHKDSK found and fixed them. I had my client reboot today and she is fully operational. We have the okay to replace the HD, nevertheless.

Seth is correct: the data is copied to good 'spare' sectors and the bad sectors are marked bad.

Seth, I like the idea of checking a virgin HD.

'bootcfg /rebuild,' I believe, fixes the boot.ini only, but from my experience a different error would have appeared than the one I got. I also have used 'Fixmbr' from Recovery Console. These are usual remedies after a foobar restore or something you know you just did or as we say ..."It seemed like a good idea at the time...."

Rich, I did saw all kinds of remedies on the Inet regarding the error: bad registry, bad memory, and bad HD. In almost all cases of registry problems, what I read was that ONE of the hives was either too large or corrupt. The remedy in fixing the registry from the RECOVERY CONSOLE is tedious and the fix in many cases was reported as temporary and had to be redone periodically ARGHH!!!

It looks like I guessed right with a hardware failure this time. Sometimes, you win and sometimes you loose.

To all, thanks for the feedback.

[Seth]

'bootcfg /rebuild,' I believe, fixes the boot.ini only, but from my experience a different error would have appeared than the one I got.

Rich, I did saw all kinds of remedies on the Inet regarding the error: bad registry, bad memory, and bad HD. In almost all cases of registry problems, what I read was that ONE of the hives was either too large or corrupt. The remedy in fixing the registry from the RECOVERY CONSOLE is tedious and the fix in many cases was reported as temporary and had to be redone periodically ARGHH!!!

It looks like I guessed right with a hardware failure this time. Sometimes, you win and sometimes you loose.

To all, thanks for the feedback.

Correct on the bootcfg /rebuild.

The remedies are reported as temporary as it usually indicates a failing drive. I would run chkdsk once a week for 3 weeks to see if further bad sectors show up. If they do, the system is facing emminent drive failure. If not, I would keep an eye on it by running chkdsk once a month. (Which is something that should be done on all systems anyway). If the bios has Smart drive monitoring, I would enable it if it isn't already.

Glad it's up and running!

[Freehold Fred]

Seth,

The old drive will be official history tomorrow. Thanks for making me aware of Acronis Easy Migrating. Was a snap. New drive is ready to be swap in place tomorrow.

As I mentioned on PalTalk tonight, I had somewhat of a moral dilemma. Since this was probably a one-time download for this client and the next and the next, I felt guilty downloading the trial version w/o purchasing the product. They do keep track of emails, but ya never run out of those throw aways.

I intend to build the price of the s/w into my repair fee and pass it on via a purchase to Acronis. I own Acronis True Image 9 and have previously bought Acronis for clients, so I intend to continue to support this company with $$$.

Does anyone else play by the rules:grouphug:?

Correct on the bootcfg /rebuild.

The remedies are reported as temporary as it usually indicates a failing drive. I would run chkdsk once a week for 3 weeks to see if further bad sectors show up. If they do, the system is facing emminent drive failure. If not, I would keep an eye on it by running chkdsk once a month. (Which is something that should be done on all systems anyway). If the bios has Smart drive monitoring, I would enable it if it isn't already.

Glad it's up and running!

[mylanta]

Fred obviously I was a part of that chat on Paltalk, though few here were there, and I agree with you that we have a need to pay for what we use so I think it is a good idea to buy the program and bill the client, and after all that is something you may well use again.
Though out of curiosity is there some reason you did not use "clone disk" from Acronis 9 in "Manage disks" section to move contents of drive from one drive to the other? Much like Drive Image used to have "Drive Coy" as a stand alone tool but also was part of the Drive Image program. You could do that with the program or the Rescue Disk.

[Dan18960]

I agree with Rich. If you are looking at future business with a client, the use of software is going to be continual, and you purchased it to solve THEIR problem - the client pays (both for labor, product, AND a portion of R&D time). I don't bill my clients for the total time I spend "learning" about a solution but I do bill them a portion of that time. The next client will benefit from my research by immediately solving their issue(s).

Where the remain portion of the R&D time comes in is that IF I can resolve the next issue in less than an hour - the client is still billed the minimum hour. I get reimbursed for my previous R&D time, the client benefits from that investment, and the original client didn't foot the entire bill.

If you train your clients in the manner that they will be billed a minimum 1 hour AND that they are benefitting from a previous R&D required to solve their problem - they usually don't have an issue with that. IF they are a business owner at least.

[Freehold Fred]

To be honest, Rich, I thought that Disk Clone from my rescue CD was disabled and that only Restore was possible. I never did look at it. I did not want to load my legitimate copy of Acronis 9 on client's machine. I also feel now, in hindsight, that Easy Migrating is much faster.


Though out of curiosity is there some reason you did not use "clone disk" from Acronis 9 in "Manage disks" section to move contents of drive from one drive to the other? Much like Drive Image used to have "Drive Coy" as a stand alone tool but also was part of the Drive Image program. You could do that with the program or the Rescue Disk.

[Freehold Fred]

Dan,

I agree. Much of what we do is really 'thinking' and being 'resourceful.' How true it is that the next guy/gal benefits!That is probably why we cringe at scripted support teams by you-know-whos.

I too charge for research, but at a lower rate and capped it at some point --- also not to embarrass myself that it takes so long ;).

I agree with Rich. If you are looking at future business with a client, the use of software is going to be continual, and you purchased it to solve THEIR problem - the client pays (both for labor, product, AND a portion of R&D time). I don't bill my clients for the total time I spend "learning" about a solution but I do bill them a portion of that time. The next client will benefit from my research by immediately solving their issue(s).