В Thu, 16 Oct 2014 12:40:27 -0500
Neil Rickert
On Wed, 15 Oct 2014 16:19:51 +0200 Stephan Kulow
wrote: https://openqa.opensuse.org/tests/27344/modules/livecdreboot/steps/1 is just one out of many tests that fail at the moment because the initrd can't be created.
I downloaded the iso, and then installed.
I ran into the same problems.
It did look as if the "initrd" had been created, but I couldn't boot it.
Since the bootloader install failed, I ran "grub2-mkconfig" on another instance of opensuse, and that added a boot entry for the new install. However booting stops progressing at some early stage. So I'll guess that the "initrd" is defective.
I then booted the install media in rescue mode, mounted the installed system, including "--bind" mounts for "/dev", "/proc" and "/sys". I then did a chroot, to see what I could accomplish.
"mkinitrd" ran, and seemed to build the "initrd", but failed on updating grub.cfg.
I tried installing grub2:
----- cut here ----- Rescue:/ # grub2-install /dev/sdc Installing for i386-pc platform. grub2-install: warning: Attempting to install GRUB to a disk with multiple partition labels. This is not supported yet.. grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. grub2-install: error: will not proceed with blocklists. ----- end cut -----
I'm not sure what that's about. I don't understand the "multiple partition labels" message.
this means one of a) there are multiple valid partition headers. It explicitly excludes valid GPT with protective MBR and possibly GPT sync MBR (not checked but there is support for it) b) there are both partition header and valid filesystem superblock on the same disk. c) there are both LDM (Windows dynamic disk) header and valid filesystem superblock. "Label" here means partition label, like MBR or GPT. Creating filesystem on /dev/sdc could well leave MBR intact.
I did have a label on "/dev/sdc1" (which was "/boot"), but that was a file system label, not a partition label. I had thought that partition labels were GPT thingies, and I was not using GPT. Removing that file system label did not help.
In any case, I repeated the "grub2-install", but with a "--force" option. That appeared to succeed.
Yes, it then tries to avoid embedding and using blocklists if allowed.
I ran "grub2-mkconfig -o /boot/grub2/grub.cfg" and that seemed to succeed. However, the resulting "grub.cfg" file does not contain any "linux" lines. So it failed to find the bootable system.
And then there was the output of "blkid":
----- cut here ----- Rescue:/ # blkid /dev/block/254:2: UUID="e13065c0-25a2-484a-89eb-2a8dd64e7f8b" TYPE="ext4" /dev/block/254:0: UUID="EPHvyn-pdQ7-wVSz-JjPx-1Ty6-BDDw-24PuvW" TYPE="LVM2_member" /dev/block/8:33: UUID="57e28164-ffdc-4008-96bc-f23d2423621f" TYPE="ext2" PARTUUI D="00015448-01" /dev/disk/by-id/scsi-SWDC_WD80_0JB-00ETA0_152D20337A0C-part2: UUID="dff2b7fd-b57 b-4b3b-b8f7-d3f5c0173c19" TYPE="crypto_LUKS" PARTUUID="00015448-02" /dev/sda1: UUID="b515b78a-427f-4552-80f6-1736ea04a98a" TYPE="ext2" PTTYPE="dos" PARTUUID="b52d54b1-01" /dev/sda2: LABEL="Recovery" UUID="CC70378A703779F2" TYPE="ntfs" PARTUUID="b52d54 b1-02" /dev/sda3: LABEL="OS" UUID="AC7C4EC27C4E86D4" TYPE="ntfs" PARTUUID="b52d54b1-03" /dev/sda5: UUID="04aa1807-4efc-4f12-b718-7ef326d1bddc" TYPE="ext2" PTTYPE="dos" PARTUUID="b52d54b1-05" /dev/sda6: LABEL="DATA" UUID="B6FCCF7FFCCF37FF" TYPE="ntfs" PARTUUID="b52d54b1-0 6" /dev/sda7: UUID="35ff5b61-9a76-4ed7-a437-61b2f4abd224" TYPE="crypto_LUKS" PARTUU ID="b52d54b1-07" /dev/sda8: UUID="489cebb5-0bb5-42fd-8a64-21ebb3ddf756" TYPE="ext4" PARTUUID="b52d54b1-08" /dev/sda9: UUID="d571dbe7-c17a-415d-a147-262eb7ff978a" TYPE="crypto_LUKS" PARTUUID="b52d54b1-09" /dev/sda10: UUID="45554160-a8a7-497d-b88f-1ee08766a498" TYPE="crypto_LUKS" PARTUUID="b52d54b1-0a" /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/loop2: TYPE="squashfs" /dev/loop3: TYPE="squashfs" /dev/loop4: TYPE="squashfs" /dev/sdb1: SEC_TYPE="msdos" UUID="BF70-F44B" TYPE="vfat" PARTUUID="3473465c-01" /dev/sdb2: UUID="2014-10-14-21-00-23-00" LABEL="openSUSE-Factory-DVD-x86_640001" TYPE="iso9660" PARTUUID="3473465c-02" /dev/mapper/wd80-home: UUID="9f908a1b-691d-4f65-a1a9-91c7ef51acd4" TYPE="ext4" /dev/mapper/wd80-swap: UUID="c5b36853-73c2-4177-9511-7360d971e595" TYPE="swap" ----- end cut -----
Yes, I did install in an encrypted LVM on an external drive.
The external drive was "/dev/sdc". There are no obvious entries for that in the "blkid" output. However, "/dev/block/8:33" does appear to have the data for "/dev/sdc1".
Notice that most of the "blkid" lines have a PARTUUID entry. Again, I thought that only applied to GPT disks, and none of the disks involved are GPT.
That I do not know. Oh, looks like recent util-linux adds blkid_partition_gen_uuid that synthesizes PARTUUID ... at least for msdos style.
My best guess is that some other software has changed and is producing output that is confusing grub2-install, dracut, grub2-mkconfig and perhaps others.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org