Comment 11 for bug 1566399
Revision history for this message
| Alexander Gordeev (a-gordeev) wrote | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
On the screenshot you can see only high level disk roles, for example: such as 'base system' or 'storage' .
These disk roles don't reflect to the actual low-level partitioning scheme and don't expose such details as partitions. Any partition for service needs (such as uefi system partition or even special 'bios_grub' partition) is not visible from UI perspective.
So, from UI point of view, it's true that those disks are unallocated. There're no high level roles has been assigned to any of them.
But, they did contain partitions for service needs (such as BIOS_GRUB and UEFI partition).
There's no /boot partition on /dev/vdc and /dev/vdb. The first partition is BIOS_GRUB and the second is for UEFI.
Even if volume manager asked to create /boot on MD raid, fuel-agent refused to do that and created only one plain partition named under /dev/vda3 for /boot.
The reason why fuel-agent created service partitions on them is that volume-manager from nailgun provided the default partitioning scheme which assumes that /boot partition is spread across all disks on MD raid. That's all.