|Format!! Well, THAT could be the very obvious thing I haven't done - Because I don't want to break the RAID array in case I lose all data (as it warns - and I don't even know if just changing the SATA configuration in BIOS away from RAID will effectively break the array - or whether Ctlr+i is where that mistake happens)....I haven't dared fiddle and have been unable to check the disk on its own at all on any channel. I don't know what status it is in but I hoped I could use the WD tool from in Windows, but that wasn't seeing it either.|
I'm relatively new to this RAID and SATA lark and it's just been making me very wary.
Anyway, I bit the bullet and reactivated Marvell (I don't know if this is the best route)
and tried using Disk Management - and this time was met with a 'please initialise
drive' message. However, it failed due to an "device i/o error". I tried my WD tool and what freaks me here is that it shows an IDE (disk1) drive of 3913987GB "not available" - sometimes it is 0GB and not available.
I don't have any IDE controllers so I am a bit cautious of this discrepancy. However, it also shows a zero byte IDE drive2 "not available". (Surely these should read disk 0 & 1 not 1&2?)
On the non Marvel setup, Windows still refuses to see it at all But the RAID screen sees it as non RAID.
So, all in all, it is a bit daunting and problematic to do anything without further
exploration. I was expecting to hook up and go.