Comment 31 for bug 948291

Paul, ah ok, so the RAID setup is just a JBOD one (basically glueing together the individual parts of the SSD). That explains the boot messages (because the partition table was created over the length of the RAID). And just a word of warning: at least in my experience grub in the past had no concept of RAID setups. So it was essential to have at least /boot on a partition that is accessible natively. In your case this just might about work since the first partition covers the whole first disk. But it also continues after and I am not sure that the files in /boot always will remain in the areas of the first disk. Must admit that grub2 may be more capable than I think. This limitations are from a bit back in time. But at least being cautious here cannot go wrong. ;)

But for the current problem: the simplest way to gather output in such cases is by using a usb stick which you can mount in the busybox shell and then redirect output there.

The rename error is weird. Even more since your later ls shows the node is correctly named. About the vgchange command. I think that was just an incorrect assumption from my side. I was just assuming you would be using lvm volumes on top of the RAID (which I was guessing to be in some other mode like striping, mirror or raid5). But it looks like Volume0p1 could just be your / and Volume0p5 be your swap partition (note "dmsetup ls" is another nice way to list currently available device mapper volumes). So maybe you were just about there and exit would have completed the boot.

If that works the next step would be to have --debug on the grub command line which enables debugging output of the upstart system. That should show up in /var/log/boot.log and/or /var/log/syslog. Maybe that will show what is going wrong. Oh, in the busybox, maybe have a look at scripts/init-premount, there should be a dmraid file.