RAID 0 prevents host from doing full-registration

[george1421]

What raid card did you try this on? Unless the drivers are built into the kernel or included dynamically in the root fs, the kernel will be ignorant of the array.

[Wayne Workman]

@george1421 I don’t even know what it is, I’ve had them for years. it’s a PCI RAID card, supports SATA1, has four ports on it.

I’m not terribly concerned about it - right now I’m trying to get the ‘exit to hdd’ feature to work…

[Wayne Workman]

fdisk -l lists

/dev/sda
/dev/sdb

then it gets very interesting… check it out…

it next lists
/dev/mapper/sil_cbbhdgafcffd

Now… the fun part… next two entries are…

/dev/mapper/sil_cbbhdgafcffd1
/dev/mapper/sil_cbbhdgafcffd2

and the one with 1 is marked as boot in the next entry… and the sizes of 1 and 2 are correct (combined /dev/sda and /dev/sdb in RAID 0 )

I don’t have the HDD space (at the moment) to test if that works or not…

[george1421]

Whats going on here is the kernel is seeing the individual disks and not the raid controller. You can’t boot to /dev/sda since that is only half of your data (i.e. half a raid 0 array). So I can understand why its failing.

When you boot the computers isn’t there a banner or such that is displayed during post to show what raid card is installed?

[Sebastian Roth]

@Wayne-Workman Still interested in getting this done?

[Tom Elliott]

Should this really be considered a bug? While I do realize that it is unexpected, most consumer grade motherboards only do a software level raid on the “raid controller”. Linux see’s, usually, this as individual disks even if the “volume” is setup.

[Tom Elliott]

To add on, that basically means there’s nothing I can do directly. Until consumer motherboard raid controllers actually represent the “raid volume” as a single volume rather than presenting the OS with the disks directly, this isn’t really a bug that I can fix.

With all of that, we added the mdraid=true kernel argument passing that should be able to look at the disks that are setup in a raid and combine them as a separate /dev/md0 device.

[Wayne Workman]

@Tom-Elliott I think the biggest problem that it presents is the inability to register the host. I haven’t tried this in a great while though, maybe things are better now? I’ll try here in a bit.

[Tom Elliott]

@Wayne-Workman but why is it unable to register the host?

It finds the disk fine, from what I can tell right?

[Tom Elliott]

This, for now, is the only unresolved bug, any timeframe for when we can know any type of info regarding the status?

[Tom Elliott]

Bump? Do you still want to try to do this – as it is being considered a bug.

[Wayne Workman]

@Tom-Elliott I’m on r7410 at home currently, I just deleted this host and tried to network boot and do a full registration. It worked fine lol.

However all it saw was sda when I do have sdb there as well. They are still configured as RAID 0. I’ve learned a little more about this particular RAID card because of one of George’s posts. It’s a hybrid card. It doesn’t actually present one singular drive to the OS, it presents two. But it does have it’s own POST and BIOS menu, and can create volumes and delete them, restore volumes and such… The card is like 6 bucks on ebay - and for what I do with it, it’s a great card. I’ve bought 3 of them lol.