- May 19, 2011
- 19,679
- 13,537
- 136
The computer normally runs WinXP. C drive is a bit mangled. I can't correct it either via XP's recovery console (booting off CD) with the command CHKDSK /P (error: "The volume appears to have one or more unrecoverable problems")
I also can't correct it by connecting it to my machine and running CHKDSK DRIVELETTER: /r (it says something like 'encountered an unwriteable sector').
SeaTools for DOS on a long test gives the drive a completely clean bill of health.
Ideally I'd like to be able to correct the file system problem and have things back to normal, or at least be able to run a data backup in case the most recently backup isn't up-to-date enough.
Formatting the drive and reinstalling XP obviously remains an option.
The file system is NTFS. It doesn't take either system long to throw the respective error.
Admittedly I am not sure about trusting SeaTools on this occasion. The drive has two partitions, the first one initially was readable until the drive stopped responding during a copy to a second disk and I had to switch the drive off. The drive then did the same thing with the second partition in approximately the same amount of time but the second partition is still readable.
I also can't correct it by connecting it to my machine and running CHKDSK DRIVELETTER: /r (it says something like 'encountered an unwriteable sector').
SeaTools for DOS on a long test gives the drive a completely clean bill of health.
Ideally I'd like to be able to correct the file system problem and have things back to normal, or at least be able to run a data backup in case the most recently backup isn't up-to-date enough.
Formatting the drive and reinstalling XP obviously remains an option.
The file system is NTFS. It doesn't take either system long to throw the respective error.
Admittedly I am not sure about trusting SeaTools on this occasion. The drive has two partitions, the first one initially was readable until the drive stopped responding during a copy to a second disk and I had to switch the drive off. The drive then did the same thing with the second partition in approximately the same amount of time but the second partition is still readable.
Last edited: