- Oct 29, 2009
- 116
- 5
- 18,595
Apparently there is a known issue with this: https://www.tomshardware.com/news/chkdsk-windows-10-command-breaking-ssds
And of course I need to be able to run that command; sometimes filesystems get messed up and need to be fixed, and sometimes one needs to check while diagnosing issues. Such as yesterday when trying to figure out why a backup to a HDD was failing.
And "CHKDSK /f" 'broke' my SSD.
By which I mean that it wasn't recognized by Windows (it showed as "Local Disk"). This 'broken' SSD was NOT the system drive, it's 'just' a data drive. Every time I boot Windows I got the message
"Scanning and repairing drive F: 100% complete"
This started when I ran "CHKDSK /f" on restart for both this SSD and the HDD. Event Viewer shows a Wininit entry for (the "CHKDSK /f" for) the HDD, but no Event entry is appearing for this SSD F: "CHKDSK /f".
The day before I had updated the SSD firmware and ran a Diagnostic scan (which it passed AOK; and it still does now, I tried it again) with Samsung Magician. The SSD worked perfectly until I ran the "CHKDSK /f" on it.
Samsung SSD 980 Pro 2TB NVMe
ASUS ROG Crosshair VIII Dark Hero
Windows 10.0.19042 Pro 64-bit 20H2
The steps there seem to relate to a system drive so I don't know what to do to run CHKDSK on a non-system drive.
Thankfully, I unbroke the SSD by restoring a backup from the night before. But as I said one needs to be able to run "CHKDSK /f" on my drives. Unsurprisingly, no reply on the Microsoft forum..
Does anyone please know how to resolve this knows potential issue with running CHKDSK on an SSD on Windows 10?
And of course I need to be able to run that command; sometimes filesystems get messed up and need to be fixed, and sometimes one needs to check while diagnosing issues. Such as yesterday when trying to figure out why a backup to a HDD was failing.
And "CHKDSK /f" 'broke' my SSD.
By which I mean that it wasn't recognized by Windows (it showed as "Local Disk"). This 'broken' SSD was NOT the system drive, it's 'just' a data drive. Every time I boot Windows I got the message
"Scanning and repairing drive F: 100% complete"
This started when I ran "CHKDSK /f" on restart for both this SSD and the HDD. Event Viewer shows a Wininit entry for (the "CHKDSK /f" for) the HDD, but no Event entry is appearing for this SSD F: "CHKDSK /f".
The day before I had updated the SSD firmware and ran a Diagnostic scan (which it passed AOK; and it still does now, I tried it again) with Samsung Magician. The SSD worked perfectly until I ran the "CHKDSK /f" on it.
Samsung SSD 980 Pro 2TB NVMe
ASUS ROG Crosshair VIII Dark Hero
Windows 10.0.19042 Pro 64-bit 20H2
The steps there seem to relate to a system drive so I don't know what to do to run CHKDSK on a non-system drive.
Thankfully, I unbroke the SSD by restoring a backup from the night before. But as I said one needs to be able to run "CHKDSK /f" on my drives. Unsurprisingly, no reply on the Microsoft forum..
Does anyone please know how to resolve this knows potential issue with running CHKDSK on an SSD on Windows 10?
Facebook
Twitter
Instagram