This probably an improper use of a trim command which may have deleted/corrupted a required file system database file.
#HOW TO RUN A DISK CHECK SOLID STATE DRIVE UPDATE#
The recent problem is a bug introduced by an update that probably added or changed a repair feature. There is a chance data corruption or loss could be caused by faulty hardware, but most storage these days are good at hiding this from the OS and transparently fixing things in the background (spare sector/nand relocation). The command is used to correct file system errors that could happen if the disk was not uncounted properly (system crash or unexpected power outage). In normal usage there is nothing wrong with using ChkDsk. The article and previous comments are not correct. If you can’t or don’t want to, consider tools from diskpart or diskinternals which can also offer a variety of options which won’t cause excess wear and tear or straight out render the disk unusable.Īlso, drop the defragmenter and step away from it for the love of all that is good! If you do find yourself with an SSD with a bad file system your best choice is to visit the manufacturer’s site and grab their proprietary tools which will help you get your disk back without the damage CHKDSK can do. In theory you may be able to repair the damage by running the command again in offline mode, but it should be the last time you do so.
The research which was done on the bug, which The Register covers here, shows that the bug is not specifically CHKDSK but what the /f parameter calls, which causes a corrupted file 9 and an error in the BITMAP attribute of the Master File Table.
The issue, caused by KB4586853 and KB4592438 has been resolved and you will no longer destroy the NTFS file system on your SATA SSD … but you still should not do it! There are more than a few people who discovered the hard way that CHKDSK is not a good thing to SSDs the hard way, thanks to a recent Microsoft Update which rendered SSDs unbootable if CHKDSK /F was run. Yes They Fixed The CHKDSK Bug, But Don’t Do It!
0 kommentar(er)
