--- Comment From ye...@us.ibm.com 2015-08-18 17:35 EDT---
(In reply to comment #11)
> Hi Yuechang,
>
> (In reply to comment #7)
> > This problem was first seen on last Friday, and it is a regression bug.
>
> On which version(s) did this work?
>
> Thanks
> (In reply to comment #11)
> > Manually booting from item 7 shows that this is the multipath disk we
> > installed Ubuntu on. I think this device (or both 7 and 9), should be set as
> > the 1st boot device.
>
> So, bootloader installation is OK.
> The point is setting the LPAR bootlist on PowerVM environments.
(In reply to comment #12)
> Yuechang / Wen,
>
> Does this occur on non-multipath installations?
I tried to recreate this problem (Multipath disk is not automatically
set as 1st boot device after installation) this morning, and I have
tried reinstall Ubuntu on multipath and VSCSI disks, but I didn't see it
again. I believe the problem has been fixed with the new daily updated
kernel. However, I saw Bug 124708 in the installation with Crocodile
adapters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486022
Title:
ISST-LTE: Multipath disk is not automatically set as 1st boot device
after installation (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1486022/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
