[Bug 1415918] Re: ISST-LTE: Ubuntu15.04: Boot loader installation is failing
Mathieu Trudel-Lapierre
mathieu.tl at gmail.com
Wed Feb 18 23:25:56 UTC 2015
Well, that issue appears to be caused by stale data on the disk, and
that's probably something like that pre-existing PReP partitions aren't
being handled properly.
Could you try to just manually wipe /dev/sdX1 (replacing X with whatever
device you choose to install on), using 'dd if=/dev/zero of=/dev/sdX1',
see if just this is sufficient to let the installer complete
successfully?
I still don't know why this might be happening, but I've also built a
version of grub-installer in my PPA that ignores the failure to wipe a
PReP partition and carries on with the installation:
https://launchpad.net/~mathieu-tl/+archive/ubuntu/installer-
dev/+packages. That package will need to be installed manually before
the installer reaches the point where it would install the bootloader.
I'm still waiting to get access to a proper LPAR to do better testing on
this, so as soon as that is available I'll update here and do my own
testing as well to try and reproduce the issue here.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1415918
Title:
ISST-LTE: Ubuntu15.04: Boot loader installation is failing
Status in grub-installer package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Sowmya G. Parvathi <sowparva at in.ibm.com> - 2015-01-23 04:26:08 ==
I am trying to install ubuntu 15.04 in one of the lpar, most of the file sets will be installed but boot loader installation is failing with below error:
??????????????????? [!] Continue without boot loader ????????????????????
? ?
? No boot loader installed ?
? No boot loader has been installed, either because you chose not to or ?
? because your specific architecture doesn't support a boot loader yet. ?
? ?
? You will need to boot manually with the /boot/vmlinux kernel on ?
? partition /dev/sda2 and root=/dev/sda2 quiet passed as a kernel ?
? argument. ?
? ?
? <Continue> ?
? ?
?????????????????????????????????????????????????????????????????????????
And I have choosen single path disks for installation.
Please let me know for more information.
Contact: sowparva at in.ibm.com
== Comment: #4 - Sowmya G. Parvathi <sowparva at in.ibm.com> - 2015-01-23
12:01:12 ==
For disk selection, i choose "Use Entire Disk" option:
?????????????????????????? [!!] Partition disks ???????????????????????????
? ?
? The installer can guide you through partitioning a disk (using ?
? different standard schemes) or, if you prefer, you can do it ?
? manually. With guided partitioning you will still have a chance later ?
? to review and customise the results. ?
? ?
? If you choose guided partitioning for an entire disk, you will next ?
? be asked which disk should be used. ?
? ?
? Partitioning method: ?
? ?
? Guided - resize SCSI3 (0,1,4), partition #1 (sdj) and use freed s ?
? Guided - resize SCSI3 (0,1,5), partition #1 (sdk) and use freed s ? ?
? Guided - use entire disk ?
? Guided - use the largest continuous free space ? ?
? Guided - use entire disk and set up LVM ?
? ?
? <Go Back> ?
? ?
???????????????????????????????????????????????????????????????????????????
Next, i choose a disk from the list and proceed with installation.
I also observed, when boot loader installation was not successful, i
tried the same again from the Main menu and installation was
successful.
The scenario u mentioned might be true: the installer may just think
that no bootloader has been selected. So it could be a problem with
the installer dialogs, that you were not prompted for this but should
have been.
== Comment: #5 - David Heller <hellerda at us.ibm.com> - 2015-01-23 14:42:18 ==
Hmm. It could be confused about which disk to install the boatloader to... or perhaps it installed the OS to a disk other than sda and for some reason, only knows to install the bootloader to sda... or some variation of that theme. I.e. it's confused by multiple disks in the system.
Is it possible to install to a system with only one disk online, as a
sanity check?
In either case I think you will have to provide some log information
to be sure. At the point it fails, can you please "execute a shell"
from within the installer, and search the latter part of
/var/log/syslog for pertinent errors; or attach the file here
== Comment: #6 - Sowmya G. Parvathi <sowparva at in.ibm.com> - 2015-01-28 06:26:37 ==
I tried installation on two lpars.
1. On one lpar with multiple disks, boot loader installation is
failing.
logs: /var/log/syslog
Jan 28 09:48:44 grub-installer: info: Identified partition label for /dev/sda2: gpt
Jan 28 09:48:44 kernel: [ 4184.838418] sdd: sdd1 sdd2 sdd3
Jan 28 09:48:44 kernel: [ 4184.847047] sde: sde1 sde2 sde3
Jan 28 09:48:44 kernel: [ 4184.858556] sdf: sdf1 sdf2 sdf3
Jan 28 09:48:44 kernel: [ 4184.867589] sdg: sdg1 sdg2 sdg3
Jan 28 09:48:44 kernel: [ 4184.876261] sdh: sdh1 sdh2 sdh3
Jan 28 09:48:44 kernel: [ 4184.884164] sdi: sdi1 sdi2 sdi3
Jan 28 09:48:44 kernel: [ 4184.892658] sdj: sdj1 sdj2 sdj3
Jan 28 09:48:45 kernel: [ 4185.148993] sdd: sdd1 sdd2 sdd3
Jan 28 09:48:45 kernel: [ 4185.217318] sde: sde1 sde2 sde3
Jan 28 09:48:45 kernel: [ 4185.489753] sdh: sdh1 sdh2 sdh3
Jan 28 09:48:45 grub-installer: info: Wiping PReP partition
Jan 28 09:48:45 grub-installer: dd: invalid number ''
Jan 28 09:48:45 main-menu[352]: (process:9397): File descriptor 3 (pipe:[2083]) leaked on lvdisplay invocation. Parent PID 10145: /bin/sh
Jan 28 09:48:45 main-menu[352]: (process:9397): File descriptor 4 (/dev/hvc0) leaked on lvdisplay invocation. Parent PID 10145: /bin/sh
Jan 28 09:48:45 main-menu[352]: (process:9397): File descriptor 5 (/dev/hvc0) leaked on lvdisplay invocation. Parent PID 10145: /bin/sh
Jan 28 09:48:45 main-menu[352]: (process:9397): File descriptor 6 (/dev/hvc0) leaked on lvdisplay invocation. Parent PID 10145: /bin/sh
Jan 28 09:48:45 main-menu[352]: (process:9397): Volume group "sda" not found
Jan 28 09:48:45 main-menu[352]: (process:9397): Skipping volume group sda
Jan 28 09:48:45 main-menu[352]: (process:9397): blockdev: can't open '': No such file or directory
Jan 28 09:48:45 main-menu[352]: WARNING **: Configuring 'grub-installer' failed with error code 1
Jan 28 09:48:45 main-menu[352]: WARNING **: Menu item 'grub-installer' failed.
Jan 28 09:49:26 main-menu[352]: INFO: Modifying debconf priority limit from 'high' to 'medium'
Jan 28 09:49:26 debconf: Setting debconf/priority to medium
Jan 28 09:50:07 main-menu[352]: INFO: Menu item 'di-utils-shell' selected
2. On lpar with one disk, installation is successful, but in installer "Main Menu" i still get option, "Continue without bootloader":
??????????????????? [!] Continue without boot loader ????????????????????
? ?
? No boot loader installed ?
? No boot loader has been installed, either because you chose not to or ?
? because your specific architecture doesn't support a boot loader yet. ?
? ?
? You will need to boot manually with the /boot/vmlinux kernel on ?
? partition /dev/sda2 and root=/dev/sda2 quiet passed as a kernel ?
? argument. ?
? ?
? <Continue> ?
? ?
?????????????????????????????????????????????????????????????????????????
== Comment: #8 - David Heller <hellerda at us.ibm.com> - 2015-01-28 20:10:43 ==
I don't see any major errors in syslog before it failed. There are a
few "couldn't mount" errors early on but I'm guessing that's part of
the disk detection. What looks odd though, is that grub seems to be
looking at /dev/sda2:
Jan 28 09:48:44 grub-installer: info: Identified partition label for /dev/sda2: gpt
Jan 28 09:48:45 grub-installer: info: Wiping PReP partition
Jan 28 09:48:45 grub-installer: dd: invalid number ''
And it probably should be looking at /dev/sda1 instead:
root at pole2lp2:~# parted -l
Model: IBM 2810XIV (scsi)
Disk /dev/sda: 34.4GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 8389kB 7340kB prep
2 8389kB 32.9GB 32.9GB ext4
3 32.9GB 34.4GB 1460MB linux-swap(v1)
In fact, it's actually /dev/sdf that has the root partition here:
root at pole2lp2:~# mount | grep sd
/dev/sdf2 on / type ext4 (rw,errors=remount-ro)
But this drive is partitioned the same way: the prep partition is the
1st partition:
Model: IBM 2810XIV (scsi)
Disk /dev/sdf: 34.4GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 8389kB 7340kB prep
2 8389kB 32.9GB 32.9GB ext4
3 32.9GB 34.4GB 1460MB linux-swap(v1)
So, it kind of looks like it's having trouble finding the correct
partition to install to.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1415918/+subscriptions
More information about the foundations-bugs
mailing list