The file system structure on the disk is corrupt and unusable. - Seems Unfixable.

[Ciber]

A couple of weeks ago I got home and my girlfriend told me my PC was acting up. She turned it on earlier and it wouldn't boot, just got a blank screen so she soft restarted and then there was a message about a missing file, so she turned it off and left it. So, I turned it on and it boots fine, but after a while there is a blue screen and this keeps happening, I keep getting BSOD. After checking a few things like temps and not finding anything obviously wrong, I decide I'll try to save what files I can in case it is install windows time. While I'm saving files ready to burn to DVD it blue-screens again and then when I restart the PC drive is automatically checked by windows and lots of files are found and fixed. It seems to me that the blue-screen error interrupted a big write to the drive and screwed things up. So, much later, after looking at various things I try reinstalling the motherboard drivers and this seems to work, I've not had a lockup or blue-screen since. However now that drive seems very slow to access sometimes and every time I boot the PC, windows XP checks the file system. I've run all kinds of checking the drive for errors (the full at boot-up five step one included), chkdsk /r, chkdsk /x etc. It occurred to me to check the even log and I keep getting these errors:

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 08/11/2008
Time: 21:06:15
User: N/A
Computer: JKDESKTOP
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume D:.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 02 00 4e 00 ......N.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 32 00 00 c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

When I do the things that windows help suggests, such as chkdsk /r d:, nothing works.

When I check it does tell me that ntfs is dirty but not how or why:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jake>chkntfs d:
The type of the file system is NTFS.
D: is dirty. You may use the /C option to schedule chkdsk for
this drive.

C:\Documents and Settings\Jake>

I'm not sure how to proceed apart from saving the data and wiping the drive. My guess is a file that cannot be fixed by chkdsk is corrupted, maybe the pagefile. I don't really want to format the drive if there is an easier way. Hope someone can advise me.

[GoNz0]

you can delete the pagefile from safe mode to rule that out, if that doesnt work (you have to show hidden and operating system files to find it in c:\) then i suggest a repair install so you dont lose anything.

if you do a repair install i would use another pc to make a sp3 xp disk

[smargh]

Back up the data immediately. Replace/clone the hard drive. If you want to be sure, use Speedfan and do the online diagnostics. Reallocated sectors == bad.

Also check the voltages that the power supply is putting out.

Job done.

[Ciber]

I did the speedfan online diagnostics and no realloacted sectors were shown. I'm thinking the hardware itself is fine.

[Ciber]

Well I moved the pagefile to another drive and now that drive is no longer showing as 'dirty'. It seems I need to replace the sata cable after looking up this event log error:

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 13/11/2008
Time: 20:02:20
User: N/A
Computer: JKDESKTOP
Description:
The driver detected a controller error on \Device\Harddisk1\D.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 0b 00 04 c0 .......À
0010: 01 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 0e 1c 07 02 00 00 00 ........
0028: ae 3a 01 00 00 00 00 00 ®:......
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
0038: 40 00 00 84 02 00 00 00 @..„....
0040: a5 20 0a 12 42 03 00 40 ¥ ..B..@
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 00 00 00 e0 52 2b 8a ....àR+Š
0058: 00 00 00 00 d0 22 29 88 ....Ð")ˆ
0060: 58 41 d2 b9 07 8e 03 01 XAÒ¹.Ž..
0068: 28 00 01 03 8e 07 00 00 (...Ž...
0070: 40 00 00 00 00 00 00 00 @.......
0078: f0 00 04 00 00 00 00 0b ð.......
0080: 00 00 00 00 08 03 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

Details
Product: Windows Operating System
ID: 11
Source: Disk
Version: 5.2.3790.1830
Message: Disk - The driver has detected a controller or cable error.

Explanation
This event indicates that I/O failures have occurred on the volume.

Cause
Possible causes include:

A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).


User Action
Do one or more of the following:

Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure).
Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure.
Restart the computer.
Contact Microsoft Customer Service and Support.



Version: 5.2
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.

Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.


User Action
Replace the cable.

I'll be swapping the sata cable for another later, as I've tried reseating the cables already.

[GoNz0]

make sure NCQ is disabled for the drives m8

go to device manager and find the disk, then go to its properties, it should be hiding in the IDE ATA section

NCQ can cause the error you listed

[peterb]

and do check the SATA cable - I had one where the connector housing had cracked - the drive was recognised as present, but it was unwriteable - luckily it was part of a RAID 1 array, so nothing lost - but it took a while to diagnose - and not until after I replaced the drive - and still had errors.

[jamin]

While you are checking the cable mate, give the connector contacts on the drive and motherboard a clean with a cotton bud dipped in some acetone (nail varnish remover) or isopropyl alcohol to remove any crud. But keep the solvents off the plastic!

[Ciber]

Well after swapping the SATA cable all seems well. Fingers crossed.

[peterb]

While you are checking the cable mate, give the connector contacts on the drive and motherboard a clean with a cotton bud dipped in some acetone (nail varnish remover) or isopropyl alcohol to remove any crud. But keep the solvents off the plastic!

Don't use nail varnish remover - the amount of acetone it contains is minimal, and it has other stuff in it (designed for nails) that won't help the contacts. Acetone is also a very aggressive plastic solvent.

Only ever use IPA to degrease the contacts.

[Will404]

Why not boot of the xp CD, hit R and then type in chkdsk /r

The error (in the first post) is probably due to the fact that it cannot repear files that are running. This way works 9 times out of 10.

Hope it helps - will

[Ciber]

It seems I must have damaged the cable when fitting my new graphics card. The cable looks fine, but the wires inside must be damged. I have heard that SATA cables can be fragile! I've had no errors in the event log since and CHKNTFS shows the file system as clean.

[Ciber]

It has started doing it again. Might have to try disabling ncq next. The thing is I have 2 of the same model drive and only one is doing it. I can't understand why a drive would start needing ncq off after 18 months or more of being fine.

make sure NCQ is disabled for the drives m8

go to device manager and find the disk, then go to its properties, it should be hiding in the IDE ATA section

NCQ can cause the error you listed

No IDE ATA section. Oddly for a SATA drive it has an 'SCSI properties' tab in the device properties though.

[GoNz0]

try that for the ncq

[Ciber]

In 'SCSI Properties' there are tick boxes for 'Disable tagged queuing' and 'Disable synchronous transfers' only.

[jamin]

If the fault cleared when you changed the cable, but has now come back. Maybe it is a connector or dirt. Is there any tension/weight on the cable/connector in your system? Have you cleaned the connectors with IPA? Do they seem loose?