WD Black NVME M2 disk is not starting; it shows raw data instead of a bootable system.
WD Black NVME M2 disk is not starting; it shows raw data instead of a bootable system.
Hello everyone! I’m dealing with an issue involving my operating system drive right now. My setup includes a motherboard from Asus Prime Z790-A, an NVME M.2 WD_Black sn770 OS, and Windows 11 Pro 22H2 (though I’m not sure if it’s 23H2). There’s an SSD and an HDD in the system. Recently, I’ve noticed frequent spikes in disk usage, which caused Windows to freeze for a few minutes. The logs indicated RAID I/O problems after those freezes. After a shutdown, I tried booting again but the BIOS couldn’t recognize the drive. It kept saying there was no bootable sector. I attempted to use an SSD from another old PC, and in Disk Management it showed up as RAW format with partitions labeled correctly, but I couldn’t access any data. I’m wondering if there’s a way to recover the file system or repurpose the NVME M2 drive as the system disk again. Any advice would be greatly appreciated!
, an SSD (Disk F
, and the OS disk. (Disk H: is just a USB in FAT32 for transferring captures.) The OS disk I was using was a WD Black M2 NVME SSD (SN770) from Disk G:. It seems to be dead now. I replaced it with a 120GB SSD that I installed with an old Windows version just to get a bootable system, at least. Disk G: isn't being recognized by the filesystem. Looking at the pictures below, can we try to recover data? I think it's possible to format and use it again... but I'm not really in the mood for that. T.T. I bought this drive about five months ago, not more. Is it really a bad drive? Of course, "any drive can fail at any time." But anyway... Wouldn't it be possible to fail it again? T.T. Using Partition Manager from Windows booted through the 120GB SSD shows that G: Drive (the failing NVME M.2 from WD) exists; the partition table is correct, and the data partition is in RAW format. Therefore, Windows can't access the data on the NVME drive, G: (though the system does recognize it), and CrystalDiskInfo isn't showing any SMART status.
The disk isn't working properly, so the crystal disk can't detect it. I'll share the captured images later... Sorry for the mix of languages; system just got a bit tricky. At the moment, in Disk Manager we see the drives listed. As mentioned, I have two HDDs (Disk E: & Disk D
, an SSD (Disk F
, and the OS disk. (Disk H: is just a USB in FAT32 for transferring captures.) The OS disk I was using was a WD Black M2 NVME SSD (SN770) from Disk G:. It seems to be dead now. I replaced it with a 120GB SSD that I installed with an old Windows version just to get a bootable system, at least. Disk G: isn't being recognized by the filesystem. Looking at the pictures below, can we try to recover data? I think it's possible to format and use it again... but I'm not really in the mood for that. T.T. I bought this drive about five months ago, not more. Is it really a bad drive? Of course, "any drive can fail at any time." But anyway... Wouldn't it be possible to fail it again? T.T. Using Partition Manager from Windows booted through the 120GB SSD shows that G: Drive (the failing NVME M.2 from WD) exists; the partition table is correct, and the data partition is in RAW format. Therefore, Windows can't access the data on the NVME drive, G: (though the system does recognize it), and CrystalDiskInfo isn't showing any SMART status.
While browsing other discussions... When a drive isn't recognized yet but is bootable, it means the data there is gone forever... ...I lost 2TB of information because of a faulty WD_Black NVME SSD M.2 (just five months old)? ...According to what’s shown, it’s likely still detected... and the Windows install there isn’t working and the files are in raw format... More details...: The bad WD_black M.2 NVME SSD is connected to the first M2 slot; the top one is on the ASUS Prime Z790-A WiFi adapter.
The latest picture indicates that CrystalDiskInfo isn't working properly. Disk G: in Windows Disk Management appears as seen before, with its partition table marked as correct—likely because the data partition is in RAW format. The images you mentioned show detection at the BIOS when removing the UEFI Windows USB and other attempts. Sometimes, if you disconnect the UEFI Windows USB and try booting from the old Windows installation on a 120GB SSD, it works. Thank you for your help; it means a lot.
I shared the Image of CrystalDiskInfo earlier, so it was already there. The latest pictures illustrate how BIOS recognizes it (as I believed you were asking about the BIOS version). These additions include a clear partition table visible in Windows Disk Management, while CrystalDiskInfo fails to read SMART data from the disk.