Comment # 6 on bug 1161331 from Ancor Gonzalez Sosa

(In reply to Ancor Gonzalez Sosa from comment #3)
> 
> So my question is: do my explanations fit your expectations about how the
> proposal should work on top of "virtual disks"?

Setting the needinfo on Shivani Changela and Nanda Kishore again, for them to
reply to my questions about expectations and booting from software RAIDs.

Talking about expectations, let me clarify two points.

First, in the logs attached by Shivani Changela I can see these systems use EFI
to boot. So everytime I say "partition of type bios_boot" in comment#3 I should
had actually said "an ESP (EFI) partition". All other considerations stay
exactly as they are.

That being said, in the mentioned logs uploaded by Shivani Changela I can see
this:

A disk "/dev/sda" with a total size of 220 GiB and GPT partition table
  It contains a single "/dev/sda1" partition of 100 GiB

A disk "/dev/sdb" with a total size of 910 GiB and GPT partition table
  It contains no partitions

A disk "/dev/sdc" with a total size of 440 GiB and GPT partition table
  It contains a single "/dev/sdc1" partition of 100 GiB

A disk "/dev/sdd" fully empty (not even partition table) 

A software RAID1 called "/dev/md/VirtualDisk01" formed by sda1 and sdc1
  It contains a GPT partition table with:
    - An ESP (EFI) partition
    - Two Linux partitions formatted with XFS
    - A swap partition

According to what I explained in comment#3, we (the YaST Team) wouldn't expect
such system to be able to boot, since there is no ESP partition allocated in
any real disk. The only ESP partition is inside a software RAID that is backed
by partitions.

So my question here is: does such system boot? So far, we had no evidence of
S130/S140 controllers being able to boot from a software RAID if the needed
partitions were not present in real physical disks. If you can prove that
works, we would need to reconsider how the proposal works in those cases.