Comment 35 for bug 948291

Hm, ok. So its more likely that grub2 either is more capable than I believe or gets presented a BIOS emulated device and all is magically ok for that stage. So we should not worry too much about that part.

The syslog is a bit confusing with respect of timing. It is probably normal because there is one point in time where messages from early boot are merged into what takes place after / is mounted. I think this is from about before dropping into busybox:

Mar 8 19:11:52 VPCSA dmraid-activate: ERROR: Cannot retrieve RAID set information for isw_cibcjijfgb_Volume0
Mar 8 19:11:52 dmraid-activate: last message repeated 2 times
Mar 8 19:11:52 VPCSA failsafe: Failsafe of 120 seconds reached.
Mar 8 19:11:52 VPCSA dmraid-activate: ERROR: Cannot retrieve RAID set information for isw_cibcjijfgb_Volume0
Mar 8 19:11:52 VPCSA laptop-mode: Laptop mode
Mar 8 19:11:52 VPCSA laptop-mode: disabled, not active

So for some reason reading the RAID meta-data fails. But I am not sure about the timing. It all seems to be going on at the same time. Just I am not sure this is right.
The dmraid script in scripts/init-premount seems to call "dmraid -r -c" and then dmraid-activate $dev for each of the devices printed. Maybe you could try that in the busybox to see whether this acts differently by the time to drop there. If that works too, then the question is why those failures happen in the normal boot...