Comment 8 for bug 1671605

Just noticed I didn't wrote anywhere that MAAS installs to sdf. It creates
MBR.

Selecting other disks as boot creates GPT and makes system unbootable.

pon, 13. ožu 2017. 23:23 Ante Karamatić <email address hidden> je
napisao:

> Andres
>
> If you reread again, you'll notice that MAAS installs to sdf (BIOS boots
> from sda), and selecting anything else is impossible because MAAS decides
> to use GPT, instead of MBR.
>
> Problem doesn't exist on 2.1. This is a regression.
>
> pon, 13. ožu 2017. 22:50 Andres Rodriguez <email address hidden> je
> napisao:
>
> @Ante,
>
> As stated before, it sounds that the 'Boot' device selected on the BIOS
> vs the first disk identified by the OS are different. In other words:
>
> 1. The OS identifies hdX as sda, which is /not/ set as the boot device in
> the BIOS.
> 2. The BIOS has hdY as the boot device, identified as sd[b...x].
>
> So, while MAAS installs in 'sda', the BIOS attempts to boot from
> 'sd[b...x]'. For that, you can select in MAAS which device is the *boot*
> device.
>
> Ante, in the UI, can you please select the 'Boot' option to a different
> disk other than 'sda'. That being the disk where the BIOS is booting
> from!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671605
>
> Title:
> Unbootable system after installation
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1671605/+subscriptions
>
> --
> Ante Karamatić
> <email address hidden>
> Canonical
>
--
Ante Karamatić
<email address hidden>
Canonical