I do have a drive issue potential failure. Drive its a Samsung MVMe 2TB. The drive went all of a sudden in readme only mode, so I cannot use it. The system at boot prompts me failure is imminent and advise to backup the data and replace the drive. I have tried DISKPART from command prompt as admin to put the disk back online with no success. Tried chkdsk command with no luck also. Any help much appreciated.
I suggest you backup ASAP and look to get it replaced (hopefully) under warranty.
This isn’t really the right forum for addressing a hardware failure. Suggest you go the manufacturer and see if they have a forum.
Why not just do as you are advised? Backup and replace. It’s not like you can repaid a NVMe drive.
Recuva? R studio? maybe a shot… found this. https://www.youtube-nocookie.com/embed/W_4k_DJaJAg ![]()
If you have any drive tools already installed that can access SMART disk info check for the ‘Available Spare’ attribute, if this is in a warning state then the drive needs replacing as any spare blocks have almost been consumed.
What’s the error that you’re seeing? If you can get the SMART status, that would be even better.
Backup and replace. Today.
Thank you all for your thoughts!
And maybe think about your cooling system if that might be a contributor to the failure - (or maybe the NVme card is ancient?)
A final step you can try before replacing it is to remove it, clean the contacts and re-seat it. It’s a long shot but worth the try if it turns out to just be a faulty contact.
Sadly you have almost run out of spare blocks for the NVMe drive to use when it detects bad sectors, this needs replacing ASAP. Out of curiosity, how old is the drive and was the drive nearly full when you were using it - this can shorten the life of a solid state drive.
It`s a Samsung 970 Pro, 2TB, 7 years old now. Drive was in good use but not overly used, various games on in, DCS etc. Used also as a home for MSFS swap file, some storage, bits and bobs, etc ![]()
Edited, as I meant pagefiles, rather than the MSFS swapfile.
rolling cache actually ![]()

