https://bugzilla.novell.com/show_bug.cgi?id=653081
https://bugzilla.novell.com/show_bug.cgi?id=653081#c17
Jeff Mahoney changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEEDINFO
InfoProvider| |nothereforever@hotmail.com
--- Comment #17 from Jeff Mahoney 2012-03-28 14:09:44 EDT ---
Yeah, RAID controllers typically warn of losing all your data but they usually
don't. It's a "just in case something happens, you should be prepared" kind of
warning.
The dirty little secret about these "RAID" controllers is that that they don't
actually do anything other than have a bit of nvram, some basic firmware that
can write some metadata to the disks, and *sometimes* may have something basic
like an xor accelerator that is nearly always slower than the subsequent
generation of CPU doing it itself.
The main reason they're "RAID" controllers rather than a regular controller
with a software raid front-end is so that generic ATA/AHCI drivers don't claim
them as separate disks. For Windows, I suppose the driver probably claims the
disk, reads the metadata and sets up software raid. I don't know for sure.
For Linux, dmraid claims the devices after reading the metadata off the disks.
I'm not a dmraid expert but I expect that the 'dmraid -x' will also remove the
metadata from the disks without having to involve the firmware. That's also why
when you moved it to a different type of controller, it still came up.
I'm having trouble parsing the situation you're in now. Did going through the
RAID controller firmware succeed in un-RAIDing your disks?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.