Bug 800326

Summary: Instalation hangs on grub2 with the error code 32512
Product: [openSUSE] openSUSE Tumbleweed Reporter: Martin Caj <mcaj>
Component: BootloaderAssignee: Michael Chang <mchang>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: jdd, jsrain, ncutler, snwint
Version: 13.1 Beta 1   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: IS&T Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Y2logs from the installation.
full /var/log/YaST2 as requested

Description Martin Caj 2013-01-24 14:23:41 UTC
Created attachment 521790 [details]
Y2logs from the installation.

Hi 

We tried to install OpenSUSE 12.3 Beta 1 on two bare metal x86_64 machines.
In both cases, the Y2 installation process hung at grub2 package. The fallowing error messages appeared on the console one: 

"Perl-Bootloader: 2013-01-24 15:01:23 <3> yast-8395.1 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-set-default '0' >/var/log/Yast2/y2log_bootloader 2>&1' failed with code 32512 and output: sh: /usr/sbin/grub2-set-default: No such file or directory
@lymouthd: ply-event-loop.c:631: ply_event_loop_add_source: Assertion 'status == 0' failed."

On the first machine we have tried two time with the same results. On the second machine was it just once and after we rebooted it it worked.

In the attachment there are Y2 log files.

Martin
Comment 1 Nathan Cutler 2013-01-24 14:35:36 UTC
On the machine where the installation failed twice, in the "Actions performed:" frame it says:

...
Downloading gptfdisk (download size 155.8 kB)
Installing gptfdisk-0.8.5-1.6.x86_64.rpm (installed size 584.5 kB)
Downloading grub (download size 330.5 kB0
Installing grub-0.97-187.2.x86_64.rpm (installed size 1.38 MB)
Additional rpm output:
0+1 records in
0+1 records out
102058 bytes (102 kB) copies, 0.000187885 s, 543 MB/s


Downloading grub2 (download size 1.65 MB)
Installing grub2-2.00-18.1.x86_64.rpm (installed size 10.00 MB)

This particular machine used to have openSUSE 12.2 on it. We're running a new installation, not an update. Seems strange that it installs both grub (0.97) and grub2 (2.00) ???
Comment 2 Jean-Daniel Dodin 2013-01-28 09:35:42 UTC
looks same as mine https://bugzilla.novell.com/show_bug.cgi?id=800744
Comment 3 Jiri Srain 2013-01-28 09:45:25 UTC
Steffen, Michael, can you clarify this workflow? Why does GRUB2 in its script call perl-Bootloader at all?
Comment 4 Michael Chang 2013-01-29 04:53:04 UTC
The grub2-set-default error shouldn't be the cause. There should have some other reasons(clues) that we have to find out ..

Although it's a bug, but shouldn't lead to such serious consequence. 

My guts feeling is that some other packages triggers mkinitrd or such which calls update-bootloader and at that time grub2 haven't been installed .. That why that error would be logged but should be harmless.

By judging from the log, that error appeared at 15:01:23 but installation stopped  at 15:02:45 ...
Comment 5 Michael Chang 2013-01-29 06:15:29 UTC
Hi Martin,

Could you provide me the full /var/log/YaST2? Or the perl-BL-standalone-log ..? 

Thanks.
Comment 6 Michael Chang 2013-01-29 07:06:17 UTC
Also /var/log/messages please? Thanks.
Comment 7 Michael Chang 2013-01-29 08:48:03 UTC
Hi Martin,

From the log you're try LVM based installation? If that's true then you probably hit by bnc#798604.

Could you please help to check your ps output has LVM2_member like this one ?? 

http://bugzillafiles.novell.org/attachment.cgi?id=520328
Comment 8 Nathan Cutler 2013-01-29 13:56:53 UTC
Created attachment 522446 [details]
full /var/log/YaST2 as requested

Here is the full /var/log/YaST2 requested by Michael Chang in Comment #5
Comment 9 Nathan Cutler 2013-01-29 13:59:26 UTC
(In reply to comment #6)
> Also /var/log/messages please? Thanks.

/var/log/messages is a symlink to /mounts/mp_0000/var/log/messages and there's nothing in it.

mount -l says (inter alia):

/dev/loop2 on /mounts/mp_0000 type squashfs (ro,relatime)
Comment 10 Nathan Cutler 2013-01-29 14:05:31 UTC
(In reply to comment #7)
> From the log you're try LVM based installation? If that's true then you
> probably hit by bnc#798604.

Yes, LVM.

> Could you please help to check your ps output has LVM2_member like this one ?? 
> 
> http://bugzillafiles.novell.org/attachment.cgi?id=520328

Not quite the same. Here's the output from "ps ax | grep LVM":

 6359 tty1     D+     0:00 mount -o ro -t LVM2_member /dev/sda2 /var/lib/os-prober/mount
 6361 ?        S      0:01 /etc/nothing -q -- LVM2_member

From the correspondence on bnc#798604 it would appear that we have indeed been hit by this bug.
Comment 11 Michael Chang 2013-02-06 08:05:36 UTC
Ok I set to dup of bnc#798604. Reopen if you still encounter the problem from next milestone release.

Thanks.

*** This bug has been marked as a duplicate of bug 798604 ***