> If there were something wrong the MBR or the labels, I wouldn't be able > to boot the kernel from raid0a.
Not really: the bootloader finds the kernel from one disk or the other (should be able to boot from both). It does not boot from raid0a as it does not know about it. Good enough partitioning for the system to boot-up without raid does not necessarily mean it complies with a valid and booting-capable Raidframe setup. > Since then I booted that box with Seatools. Both disks passed the long > test. dmesg doesn't contain "can't read blk ..." errors. I notice sometimes > delays in writes and an associated unwelcome "thunk" from the disks, so > I will shelve this as unprovable disk hardware issue (unsatisfactory). I would start over without the EFI partition.
