Hi all. So I've been using 4 drives in RAID 10, a fifth standalone drive and an SSD boot drive. One of the cables must've been jiggled or something because one of the RAID drives disappeared, and on the next reboot chose my standalone HDD to rebuild the array. I stopped it and didn't let it boot to Windows. Disconnected the entire array, kept the lone drive in.
And so I'm faced with this situation:
When I uninstall the virtual disk driver and try rescanning it just reinstalls the virtual disk driver. Crystaldiskinfo doesn't detect the drive at all. RST software doesn't detect the drive at all.
Of course the first thing I tried was connecting it via USB adapter: the drive is recognised with all data intact and everything works normally. While this is a great temporary solution, it's not ideal. Really need normal functionality back.
Motherboard is an IX hero, drive is a newish (~3 months) Toshiba P300 HDWD130UZSVA.
Thanks all
Next day edit: Nothing I've tried has helped so far. Backups are fine, but no luck actually getting my PC to detect the drive.
It's starting to get very tedious.
Tried initializing it, but I got this message.
Used different ports, different cables but it still won't be seen by the BIOS/OS. I still have no idea why it appears as a virtual disk in SATA, or why it operates perfectly fine via USB.
And so I'm faced with this situation:
When I uninstall the virtual disk driver and try rescanning it just reinstalls the virtual disk driver. Crystaldiskinfo doesn't detect the drive at all. RST software doesn't detect the drive at all.
Of course the first thing I tried was connecting it via USB adapter: the drive is recognised with all data intact and everything works normally. While this is a great temporary solution, it's not ideal. Really need normal functionality back.
Motherboard is an IX hero, drive is a newish (~3 months) Toshiba P300 HDWD130UZSVA.
Thanks all
Next day edit: Nothing I've tried has helped so far. Backups are fine, but no luck actually getting my PC to detect the drive.
It's starting to get very tedious.
Tried initializing it, but I got this message.
Used different ports, different cables but it still won't be seen by the BIOS/OS. I still have no idea why it appears as a virtual disk in SATA, or why it operates perfectly fine via USB.
Facebook
Twitter
Instagram