- Apr 14, 2011
- 12
- 0
- 18,520
My drive seems to be stuck in some sort of RAID. It works as just a single volume in RAID so I can still use the drive in the end but...
This is a fairly new Crucial NVMe (Used as a Storage drive, this is not my boot drive) that worked as a normal drive but upon troubleshooting other issues, bios got flipped to NVMe Raid mode. Ever since then, I cannot get Windows to see the drive unless it's in an Array, even after deleting the Array from the bios in RaidXpert2. I've deleted the partition, formatted the drive, re-created the array, then red-eleted it. I've attempted to switch it to MBR then GPT. I've tried booting with the storage and even boot drive as Legacy and UEFI. When the drive was new and first set up, it showed as the name of the drive in Device manager. When it first went into the Array, it would show in my device as AMD-RAID with the name of the drive, now in the array it won't even give the drive name, just calls it the name of the Array. When it's not being detected, it's not in the Device manager or the windows boot manager. When the Array is turned on with the drive in the Bios, it will not show the drive under NVMe in the bios options but when it's deleted from the Array it does, so it's like Xpert2 is actually deleting the array. There's nothing important on the drive, so if it requires wiping it's good to go.
In case it's important to anybody, the reason I turned it to NVMe RAID mode was because I was getting intermittent "Hangups" with massive DPC latency (took me a long time to just figure that out, because it wasn't getting picked up sometimes with Latencymon) spikes that lasted half a second each every now and again. I spent probably the course of 48 hours over a few weeks trying to fix this and was trying everything at that point. That was corrected by changing the AMD Sata Controller driver to also run as Standard SATA AHCI Controller in the device manager.
Windows 10 64 bit Pro
Gigabyte AB350 Gaming Rev 1, F25 Bios (was working outside of the array on this version at some point)
Ryzen 1600
My boot drive is a Crucial 240m500SSD1, but the drive stuck in Raid is a Crucial CT500p1SSD8.
This is a fairly new Crucial NVMe (Used as a Storage drive, this is not my boot drive) that worked as a normal drive but upon troubleshooting other issues, bios got flipped to NVMe Raid mode. Ever since then, I cannot get Windows to see the drive unless it's in an Array, even after deleting the Array from the bios in RaidXpert2. I've deleted the partition, formatted the drive, re-created the array, then red-eleted it. I've attempted to switch it to MBR then GPT. I've tried booting with the storage and even boot drive as Legacy and UEFI. When the drive was new and first set up, it showed as the name of the drive in Device manager. When it first went into the Array, it would show in my device as AMD-RAID with the name of the drive, now in the array it won't even give the drive name, just calls it the name of the Array. When it's not being detected, it's not in the Device manager or the windows boot manager. When the Array is turned on with the drive in the Bios, it will not show the drive under NVMe in the bios options but when it's deleted from the Array it does, so it's like Xpert2 is actually deleting the array. There's nothing important on the drive, so if it requires wiping it's good to go.
In case it's important to anybody, the reason I turned it to NVMe RAID mode was because I was getting intermittent "Hangups" with massive DPC latency (took me a long time to just figure that out, because it wasn't getting picked up sometimes with Latencymon) spikes that lasted half a second each every now and again. I spent probably the course of 48 hours over a few weeks trying to fix this and was trying everything at that point. That was corrected by changing the AMD Sata Controller driver to also run as Standard SATA AHCI Controller in the device manager.
Windows 10 64 bit Pro
Gigabyte AB350 Gaming Rev 1, F25 Bios (was working outside of the array on this version at some point)
Ryzen 1600
My boot drive is a Crucial 240m500SSD1, but the drive stuck in Raid is a Crucial CT500p1SSD8.
Facebook
Twitter
Instagram