If BIOS detects the drive but Windows doesn’t, the issue is likely with how the drive is set up or recognized by the operating system. The drive might be unallocated, not initialized, or using a corrupted file system that Windows can’t read. In some cases, the necessary drivers may be missing or outdated, preventing proper detection. It’s also possible that the drive is hidden or marked as offline in Disk Management. To fix this, open Disk Management to check the drive’s status. From there, you can initialize the drive, assign a drive letter, or format it if necessary.
The RAID 10 array on your MSI PRO X670 motherboard became inaccessible after a single drive failed. Even though three drives are still online, the system doesn’t detect the array or show any partitions, not even after loading the correct AMD RAID drivers.
This could be due to RAID metadata corruption, a bad connection to the failed drive, or BIOS changes. Do not rebuild or initialize the array — that can wipe the data.
Start by checking the physical connection of the removed drive. Reseat cables or swap ports. Then enter the AMD RAID BIOS (RAIDXpert2) and check if the array can be imported or viewed without initializing.
If that fails, try using a Linux live USB with mdadm or dmraid to assemble and access the array. If Linux doesn’t detect it, use RAID recovery software like Stellar Data Recovery Technician, R-Studio or UFS Explorer to scan and recover the data.
Once the data is safe, replace the failed drive and rebuild the array. For future reliability, consider using software RAID or a dedicated RAID card instead of motherboard-based RAID.
Viewing 4 replies - 181 through 184 (of 184 total)
It’s safe to disable or delete the FTDI device if you don’t use it. If you do, it will stop working until reinstalled.