On 15.10.2014 16:25, Dinar Valeev wrote:

I've seen similar on Power, but I have grub2-mkconfig problem.

http://bugzilla.opensuse.org/show_bug.cgi?id=901180

If you scroll down the error message, what's the actual failure?

That's the problem with screenshots: scrolling doesn't help :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 2014-10-15 at 16:25 +0200, Dinar Valeev wrote:

I've seen similar on Power, but I have grub2-mkconfig problem.

http://bugzilla.opensuse.org/show_bug.cgi?id=901180

If you scroll down the error message, what's the actual failure?

The perks of an automated testing system making screenshots: you can't scroll on the screenshot. But openQA publishes nicely the y2logs.tar.bz: https://openqa.opensuse.org/tests/27344/file/y2logs.tar.bz2 -- Dimstar / Dominique Leuenberger -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Yeah. Seems the same issue: 2014-10-15 03:16:06 <1> pbl-0473.2 Core::UpdateBootloader.1607: rename /boot/grub2/grub.cfg.new -> /boot/grub2/grub.cfg 2014-10-15 03:16:07 <3> pbl-0473.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg' failed with exit code 1, output: <<<<<<<<<<<<<<<< Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt

...

...

...

...

...

>>>>>>>>>>

On Wed, Oct 15, 2014 at 4:35 PM, Dimstar / Dominique Leuenberger wrote:

On Wed, 2014-10-15 at 16:25 +0200, Dinar Valeev wrote:

...

I've seen similar on Power, but I have grub2-mkconfig problem.

http://bugzilla.opensuse.org/show_bug.cgi?id=901180

If you scroll down the error message, what's the actual failure?

Looking into y2log, the error message would be:

`Heading ("An error occurred during initrd creation."), `RichText (`opt (`plainText), "Creating initrd: /boot/initrd-3.16.4-1.g7a8842b-desktop Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.4-1.g7a8842b-desktop 3.16.4-1.g7a8842b-desktop *** Including module: bash *** *** Including module: warpclock *** *** Including module: i18n *** *** Including module: convertfs *** *** Including module: ifcfg *** *** Including module: drm *** *** Including module: plymouth *** *** Including module: btrfs *** *** Including module: kernel-modules *** Omitting driver i2o_scsi *** Including module: qemu *** *** Including module: qemu-net *** *** Including module: resume *** *** Including module: rootfs-block *** *** Including module: terminfo *** *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules Skipping udev rule: 80-drivers-modprobe.rules *** Including module: systemd *** *** Including module: usrmount *** *** Including module: base *** *** Including module: fs-lib *** *** Including module: shutdown *** *** Including module: suse *** *** Including modules done *** *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** *** Resolving executable dependencies done*** *** Hardlinking files *** *** Hardlinking files done *** *** Stripping files *** *** Stripping files done *** *** Generating early-microcode cpio image *** *** Store current command line parameters *** Stored kernel commandline: resume=UUID=652ed60b-67b7-4a9b-8f19-8f2aa19169ce root=UUID=f6d3e7af-495c-46a5-b455-d6ab232e6083 rootflags=rw,relatime,space_cache rootfstype=btrfs *** Creating image file *** *** Creating image file done *** Update bootloader... Perl-Bootloader: 2014-10-15 03:16:06 <3> pbl-0473.2 FileIO::ReadFile.85: Error: Failed to open /boot/grub2/grub.cfg: No such file or directory Perl-Bootloader: 2014-10-15 03:16:07 <3> pbl-0473.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg' failed with exit code 1, output: <<<<<<<<<<<<<<<< Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt

...

...

...

...

...

>>>>>>>>>>> Updating bootloader failed "), `ButtonBox (`PushButton (`id (`ok_help), `opt (`default, `okButton), "&OK")))

-- Dimstar / Dominique Leuenberger

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Oct 15, 2014 at 08:29:40PM +0400, Andrei Borzenkov wrote:

В Wed, 15 Oct 2014 16:41:47 +0200 Dinar Valeev пишет:

...

Yeah. Seems the same issue: 2014-10-15 03:16:06 <1> pbl-0473.2 Core::UpdateBootloader.1607: rename /boot/grub2/grub.cfg.new -> /boot/grub2/grub.cfg 2014-10-15 03:16:07 <3> pbl-0473.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg' failed with exit code 1, output: <<<<<<<<<<<<<<<< Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt

...

...

...

...

>>>>>>>>>>>>

On Wed, Oct 15, 2014 at 4:35 PM, Dimstar / Dominique Leuenberger wrote:

...

On Wed, 2014-10-15 at 16:25 +0200, Dinar Valeev wrote:

...

I've seen similar on Power, but I have grub2-mkconfig problem.

http://bugzilla.opensuse.org/show_bug.cgi?id=901180

If you scroll down the error message, what's the actual failure?

Looking into y2log, the error message would be:

`Heading ("An error occurred during initrd creation."), `RichText (`opt (`plainText), "Creating initrd: /boot/initrd-3.16.4-1.g7a8842b-desktop Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.16.4-1.g7a8842b-desktop 3.16.4-1.g7a8842b-desktop *** Including module: bash *** *** Including module: warpclock *** *** Including module: i18n *** *** Including module: convertfs *** *** Including module: ifcfg *** *** Including module: drm *** *** Including module: plymouth *** *** Including module: btrfs *** *** Including module: kernel-modules *** Omitting driver i2o_scsi *** Including module: qemu *** *** Including module: qemu-net *** *** Including module: resume *** *** Including module: rootfs-block *** *** Including module: terminfo *** *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules Skipping udev rule: 80-drivers-modprobe.rules *** Including module: systemd *** *** Including module: usrmount *** *** Including module: base *** *** Including module: fs-lib *** *** Including module: shutdown *** *** Including module: suse *** *** Including modules done *** *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** *** Resolving executable dependencies done*** *** Hardlinking files *** *** Hardlinking files done *** *** Stripping files *** *** Stripping files done *** *** Generating early-microcode cpio image *** *** Store current command line parameters *** Stored kernel commandline: resume=UUID=652ed60b-67b7-4a9b-8f19-8f2aa19169ce root=UUID=f6d3e7af-495c-46a5-b455-d6ab232e6083 rootflags=rw,relatime,space_cache rootfstype=btrfs *** Creating image file *** *** Creating image file done *** Update bootloader... Perl-Bootloader: 2014-10-15 03:16:06 <3> pbl-0473.2 FileIO::ReadFile.85: Error: Failed to open /boot/grub2/grub.cfg: No such file or directory Perl-Bootloader: 2014-10-15 03:16:07 <3> pbl-0473.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg' failed with exit code 1, output:

Please check /etc/default/grub, GRUB_CMDLINE_LINUX_*. There were multiple reports that it contains string similar to

GRUB_CMDLINE_LINUX_DEFAULT="... elevator=`missing ..."

Which makes shell very unhappy.

From the log Dimstar provided.

GRUB_CMDLINE_LINUX_DEFAULT=" video=1024x768-16 plymouth.ignore-serial-consoles console=ttyS0 console=tty resume=/dev/vda1 splash=silent quiet showopts vga=791" It looks unlikely a /etc/default/grub issue. regards, Michael

...

...

<<<<<<<<<<<<<<<< Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt

...

...

...

>>>>>>>>>>>>> Updating bootloader failed "), `ButtonBox (`PushButton (`id (`ok_help), `opt (`default, `okButton), "&OK")))

-- Dimstar / Dominique Leuenberger

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 15/10/14 a las #4, Dimstar / Dominique Leuenberger escribió:

Perl-Bootloader: 2014-10-15 03:16:06 <3> pbl-0473.2 FileIO::ReadFile.85: Error: Failed to open /boot/grub2/grub.cfg: No such file or directory Perl-Bootloader: 2014-10-15 03:16:07 <3> pbl-0473.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg' failed with exit code 1, output: <<<<<<<<<<<<<<<< Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt

Oook.. nothing to do with plymouth or dracut itself. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В 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

Le 18/10/2014 16:34, Dale Ritchey a écrit :

On 10/15/2014 10:19 AM, Stephan Kulow wrote:

...

Hi,

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.

As the only test not affected is minimal installation, my naive guess would be plymouth problem. So if someone wants to debug it: you can download the test ISO from the test - I'll be in 13.2 if you need me.

Greetings, Stephan

My observationebooted Running in virtual box initrd is created when the kernel is installed so rerunning a boot script at the end of the installation seems to be redundant. I manually removed /mnt/etc/grub.d/00_tuned during the install and was able to get a good /etc/grub2/grub.cfg i successfully rebooted into openSUSE

The bug is knew. It has been fixed with the new version of tuned actually in Factory. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org