My laptop hard drive (spinner) has a bad block but CHKDSK doesn’t map it out. After every restart there are 6 more message in the System Event Log:
The device, \Device\Hardisk0\Dr0, has a bad block.
Source: disk
Event ID: 7
Another symptom: Macrium Reflect throws this error message when I run a Full Image backup :
Saving Partition – Windows (C:)
-> Backup aborted! – Unable to read from disk – Error Code 23 – Data error (cyclic redundancy check).
That’s the problem, here is the System Info:
Acer Aspire V5 (8-ish years old )
Windows 8.1 Pro (with Stardock Start8)
RAM 8 GB
Disk Drive: ST1000LM024
If someone brought this old laptop to me to repair, I would recommend that they buy a new laptop. But I like Windows 8.1 because I can control when to install Windows Updates and with Start8 I have an easy Start menu and I don’t have to deal with the stupid Windows 8 program list.
I use the laptop at home for Outlook 2013, browsing with Vivaldi and Brave, guitar lessons, and oh yeah, Quickbooks 2011 for my little bitty business (almost retired.)
I have tried:
Chkdsk /f
Chkdsk /r
Chkdsk /f /r
Chkdsk /spotfix
Chkdsk /offlinescanandfix
These commands all require a reboot and seem to be running normally, but none of them provide any Wininit records in the Application Event Log like chkdsk always used to do, so I’m wondering if chkdsk is failing and just restarting the system or if there is a problem with the event log file.
But I am getting some info from:
Chkdsk /scan
which runs online. That puts a Chkdsk Event ID 26226 in the Application Event Log that says:
The type of the file system is NTFS.
Volume label is Windows.
Stage 1: Examining basic file system structure …
849664 file records processed. File verification completed.
23012 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage …
1019240 index entries processed. Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
Stage 3: Examining security descriptors …
Security descriptor verification completed.
84789 data files processed.
CHKDSK is verifying Usn Journal…
38538400 USN bytes processed.
Usn Journal verification completed.
Read failure with status 0xc000009c at offset 0xba252000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xba25c000 for 0x1000 bytes.
Windows has scanned the file system and found no problems.
No further action is required.
965825535 KB total disk space.
300737148 KB in 664128 files.
413028 KB in 84790 indexes.
48 KB in bad sectors.
987207 KB in use by the system.
65536 KB occupied by the log file.
663688104 KB available on disk.
4096 bytes in each allocation unit.
241456383 total allocation units on disk.
165922026 allocation units available on disk.
———————————————————————-
Stage 1: Examining basic file system structure …
Stage 2: Examining file name linkage …
Stage 3: Examining security descriptors …
Replacing bad clusters in logfile.
Adding 1 bad clusters to the Bad Clusters File.
I find those last two lines interesting. And yes, the number of KB in use by the system has slowly been creeping up, so I realize that the drive will fail soon.
So, I have moved almost everything from this old laptop to a newer Win10 machine. But I would like to clone the failing drive and swap in an SSD just because I want to see if I can do it. I realize that opening the chassis to swap the drive might be a Pandora’s box, but I’m up for giving it a go. I’ve done similar things before.
I found a hint that running chkdsk from the Windows Repair Environment might produce different results so I ran chkdsk c: /f /r from WRE. An interesting observation… When I run chkdsk from a command prompt in Windows and then reboot, the only status I get is progress up to 11% and then swirling dots for hours. However, from the Command Prompt in the WRE, I get complete progress status including such info as:
Stage 4: Looking for bad clusters in user file data …
…
Stage 5: Looking for bad, free clusters …
Along with an ETA that is constantly updated.
When it finished the last 4 lines said:
Free space verification is complete.
Correcting errors in the Master File Table (MFT) mirror.
An unspecified error occurred (6e7466733686b2e 138c).
Failed to transfer logged messages to the event log with status 50.
So yeah, as always, there were no chkdsk messages in the event log. But, as with every restart there were 6 more of the “bad block” messages.
I’m wondering what incantation of chkdsk to run that will force chkdsk to actually work.
Or would it be better to run SeaTools or SpinRite?