[Bug 804065] New: zypper up installed grub2, then reboot FAILED after next kernel upgrade

older
[Bug 820382] New: Interface wwan0...

bugzilla_noreply＠novell.com

15 Feb 2013 15 Feb '13

18:33

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c0 Summary: zypper up installed grub2, then reboot FAILED after next kernel upgrade Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: VMWare OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: archie@dellroad.org QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20100101 Firefox/18.0 I have an openSUSE 12.2 VMWare virtual system that has been working fine since 2012-10-25. Every so often, I do a "zypper up" to get the latest updates. Occasionally these updates include new kernels. When that happens, I do a reboot and things come back to life normally. After the most recent "zypper up" I got a kernel-default update from 3.4.11-2.16 to 3.4.28-2.20, and then rebooted as I normally would. After rebooting, the system would not boot! If I were just a "normal" user :) I would have been really stuck! But even though I happen to know how to edit a grub config, this is still a huge problem because this virtual machine is half-way across the country and I don't have remote console access to it. So I have to instruct a non-Linux person on how to fix the problem using the boot screen remotely via email. This is a major pain, not to mention the long downtime it causes. It turns out grub2 (?) was still looking for 3.4.11-2.16 instead of 3.4.28-2.20. After getting the system to boot by manually editing the boot script, I started to investigate. Here are the facts: 1. Somehow my system has both grub and grub2 installed. Is this normal?? $ rpm -qa|grep grub grub2-2.00-1.23.1.x86_64 grub-0.97-185.1.2.x86_64 2. The directory /boot/grub still exists, but there is no /boot/grub/menu.lst 3. /boot/grub2/grub.cfg still had "3.4.11-2.16" in it everywhere. 4. I inspected /var/log/zypp/history and last(1) to reconstruct the sequence of events. Here they are: 2012-12-19 reboot with 3.4.11-2.16 2013-01-10 reboot with 3.4.11-2.16 2013-01-24 grub2-2.00-1.23.1.x86_64.rpm installed ok 2013-01-24 reboot with 3.4.11-2.16 2013-01-30 reboot with 3.4.11-2.16 2013-02-14 kernel-default-3.4.28-2.20.1 installed ok 2013-02-14 reboot with 3.4.28-2.20 *** FAILS *** It is unknown to me whether the grub2 install on 2013-01-24 was the first install of grub2, or just an upgrade of it. 5. Not sure if this is related, but every time certain RPMs are updated (kernel-default, udev, etc.) I always get this warning: Perl-Bootloader: 2012-10-30 16:42:10 ERROR: Core::ReadFiles: Failed to open /boot/grub/menu.lst I've gotten used to it. Obviously, this error message can be explained by the fact that /boot/grub/menu.lst doesn't exist on this system. Reproducible: Always Steps to Reproduce: I have not tried to reproduce this problem. See description for how it happened. Actual Results: System does not boot after kernel upgrade. Expected Results: System boots after kernel upgrade. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

15 Feb 15 Feb

18:45

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c1 --- Comment #1 from Archie Cobbs 2013-02-15 18:45:36 UTC --- A little more information which may (or may not) be helpful. Copy of terminal session with kernel upgrade (note 'xxxx' RPM contains customer Java application, not relevant to this issue). --------------------- CUT HERE ------------------ $ zypper -v up Verbosity: 1 Initializing Target Checking whether to refresh metadata for XXX developer repository Checking whether to refresh metadata for XXX production repository Loading repository data... Reading installed packages... Force resolution: No The following packages are going to be upgraded: cron 4.2-37.5.1 -> 4.2-37.9.1 cronie 1.4.8-37.5.1 -> 1.4.8-37.9.1 kernel-default 3.4.11-2.16.1 -> 3.4.28-2.20.1 xxxx 1.0.2317-1.suse12.2 -> 1.0.2325-1.suse12.2 4 packages to upgrade. Overall download size: 70.0 MiB. After the operation, additional 85.9 KiB will be used. Continue? [y/n/?] (y): committing Installing: xxxx-1.0.2325-1.suse12.2 .............................................................................................................................................................................[done] Installing: cron-4.2-37.9.1 ......................................................................................................................................................................................[done] Installing: kernel-default-3.4.28-2.20.1 .........................................................................................................................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.4.28-2.20-default Initrd image: /boot/initrd-3.4.28-2.20-default KMS drivers: vmwgfx Root device: /dev/sda1 (mounted on / as ext3) modprobe: Module hid_generic not found. WARNING: no dependencies for kernel module 'hid-generic' found. Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw drm ttm vmwgfx scsi_transport_spi mptbase mptscsih mptspi usb-common usbcore pcmcia_core pcmcia mmc_core ssb ohci-hcd uhci-hcd ehci-hcd xhci-hcd usbhid hid-logitech-dj Features: acpi kms plymouth block usb resume.userspace resume.kernel Perl-Bootloader: 2013-02-14 16:47:43 ERROR: Core::ReadFiles: Failed to open /boot/grub/menu.lst Installing: cronie-1.4.8-37.9.1 ..................................................................................................................................................................................[done] Additional rpm output: setting /etc/crontab to root:root 0644. (wrong permissions 0600) setting /usr/bin/crontab to root:trusted 4755. (wrong permissions 4750) redirecting to systemctl committingCommitResult (total 4, done 4, error 0, skipped 0, updateMessages 0) Checking for running processes using deleted libraries... There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. $ sync $ reboot Broadcast message from archie@XXX.com on pts/0 (Thu, 14 Feb 2013 16:48:02 -0600): The system is going down for reboot NOW! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

18:57

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c2 Andrey Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #2 from Andrey Borzenkov 2013-02-15 18:57:37 UTC --- What is bootloader type? linux-9drg:~ # grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub2" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:30

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c3 --- Comment #3 from Archie Cobbs 2013-02-15 19:30:43 UTC --- $ grep LOADER /etc/sysconfig/bootloader LOADER_TYPE="grub" LOADER_LOCATION="mbr" Hmm....! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19:51

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c4 --- Comment #4 from Archie Cobbs 2013-02-15 19:51:30 UTC --- Also, somebody please tell me what I need to do to make my hand-edits to /boot/grub2/grub.cfg permanent, if anything. Changes made were: sed -r 's/3\.4\.11-2\.16/3.4.28-2.20/g' Do I need to do anything else? With grub it was not necessary; I don't know if grub2 is different. Probably not. Just checking. I want it to boot properly next time without all the hassle I went through last time :-) Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:46

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c5 --- Comment #5 from Archie Cobbs 2013-02-15 20:46:30 UTC --- A little more information.... The original image was built using SuSE Studio. I still have it lying around. I also realize I have another similar VMWare image running locally that has the same problem, except that it has not had its kernel upgraded yet so the problem hasn't occurred yet. In other words, on this local VMWare image: $ rpm -q kernel-default kernel-default-3.4.11-2.16.1.x86_64 $ rpm -qa|grep grub grub2-2.00-1.19.1.x86_64 grub-0.97-185.1.2.x86_64 $ grep LOAD /etc/sysconfig/bootloader LOADER_TYPE="grub" LOADER_LOCATION="mbr" $ ls -l /boot/grub/menu.lst /bin/ls: cannot access /boot/grub/menu.lst: No such file or directory So it seems that maybe SuSE Studio is causing this problem... ? The image was built in SuSE Studio on 10-15-2012. I've give an URL to it but SuSE Studio login is currently broken. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:44

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c6 --- Comment #6 from Archie Cobbs 2013-02-15 22:44:48 UTC --- Further update (see below): It turns out that the grub2 upgrade did not cause the problem. The system was actually built in this broken state by SUSE Studio. Copying email from opensuse-factory mailing list... --------------- CUT HERE ---------------- On Fri, Feb 15, 2013 at 2:29 PM, Yamaban wrote:

...

...
The bug is https://bugzilla.novell.com/show_bug.cgi?id=804065

Short-list for repair:

You wish to use Grub2:

1. uninstall 'grub' (rpm -e grub)

Done.

...

2. edit file: /etc/sysconfig/bootloader line LOADER_TYPE to LOADER_TYPE="grub2"

Done.

...

3. to make sure edit /boot/grub2/grub.cfg to match your kernel.

Done.

...

4. call "/sbin/update-bootloader --refresh" to make sure the config is active.

Fails with: Perl-Bootloader: 2013-02-15 16:35:48 ERROR: Core::ReadFiles: Failed to open /boot/grub2/device.map Can't use an undefined value as a HASH reference at /usr/lib/perl5/vendor_perl/5.16.0/Bootloader/Core/GRUB2.pm line 1105. The file /boot/grub2/device.map does in fact not exist on this system.

...

Just why the install of grub2 killed /boot/grub/menu.lst, but did not change LOADER_TYPE is a mystery to me.

It turns out that the grub2 upgrade did not cause the problem. The system was actually built in this broken state by SUSE Studio. I have the original image (as downloaded from SUSE Studio) lying around and am able to reproduce the problem in VMWare on my laptop and can see that it has /etc/sysconfig/bootloader configured wrong. I vaguely remember a bootloader selection in SUSE Studio but don't remember what I put there (if I could login to SUSE Studio I would examine how I had configured the virtual machine image, but SUSE Studio login is completely broken ATM...). Perhaps there is something about VMWare image builds that violates assumptions of the grub2 install? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23:16

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c7 --- Comment #7 from Archie Cobbs 2013-02-15 23:16:48 UTC --- I created the /boot/grub2/device.map file and now I get this: $ /sbin/update-bootloader --refresh Perl-Bootloader: 2013-02-15 17:15:38 ERROR: Core::ReadFiles: Failed to open /etc/default/grub_installdevice Can't use an undefined value as a HASH reference at /usr/lib/perl5/vendor_perl/5.16.0/Bootloader/Core/GRUB2.pm line 1105. The file /etc/default/grub_installdevice does not exist on this system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16 Feb 16 Feb

06:51

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c8 --- Comment #8 from Andrey Borzenkov 2013-02-16 06:51:15 UTC --- What happens when you use YaST2 to set bootloader to GRUB2? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:19

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c9 --- Comment #9 from Archie Cobbs 2013-02-16 20:19:42 UTC ---

...

What happens when you use YaST2 to set bootloader to GRUB2?

I reset the VMWare image and started over, then ran yast2. It showed GRUB (not GRUB2) as the boot loader. I changed that to GRUB2. After doing so, /etc/sysconfig/bootloader contained LOADER_TYPE="grub2" Then I rebooted. It booted OK with grub2, but the previous green themed boot screen was gone, and a simple black boot screen appeared instead. After that, I upgraded the kernel and rebooted and it booted OK with the new kernel. So this is all consistent with the original, root problem being that SUSE Studio produced an image that had LOADER_TYPE="grub" in /etc/sysconfig/bootloader, but no /boot/grub/menu.lst and GRUB2 actually installed on the (virtual) disk. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19 Feb 19 Feb

13:07

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com AssignedTo|jsrain@suse.com |mchang@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:02

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c10 --- Comment #10 from Archie Cobbs 2013-02-19 17:02:51 UTC --- FYI, SUSE Studio is back up now. The VMWare image that I built there is configured to have "grub2" installed on it as one of the selected packages. So something must be wrong with how grub2 gets installed when building VMWare images via SUSE Studio. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Feb 25 Feb

09:25

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c11 --- Comment #11 from Michael Chang 2013-02-25 09:25:26 UTC --- (In reply to comment #9)

...

...
What happens when you use YaST2 to set bootloader to GRUB2?

...

Then I rebooted. It booted OK with grub2, but the previous green themed boot screen was gone, and a simple black boot screen appeared instead.

FYI. This should have been addressed and fixed in bnc#775778. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

4 Mar 4 Mar

09:39

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c12 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |shshyukriev@suse.com InfoProvider| |shshyukriev@suse.com --- Comment #12 from Michael Chang 2013-03-04 09:39:36 UTC --- Hi Shyukri, Do you know any suse studio folks can help to check this? It seems that the vmware image built with grub2 have wrong sysconfig settings (LOADER_TYPE=grub). Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:08

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c13 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ms@suse.com --- Comment #13 from Marcus Schaefer 2013-03-04 11:08:16 UTC ---

...

From the image building site when kiwi builds the 12.2 image there is no code which adds LOADER_TYPE if grub2 is set as bootloader. the function setupBootLoaderGrub2() callled by kiwi only creates the config in /etc/default/grub and no LOADER_TYPE

thus something else might have added it: a) Studio config scripts ? b) The image used grub before and was switched to grub2 somehow c) some package installs/updates /etc/sysconfig/bootloader and prefers grub over grub2 after all it's hard to guess what happened -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:19

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c14 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|shshyukriev@suse.com | Resolution| |FIXED --- Comment #14 from Marcus Schaefer 2013-03-04 11:18:59 UTC --- kiwi now writes the value correctly I submitted a new 12.2 containment (v5.03.65) closing -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

19 Apr 19 Apr

18:01

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c15 Archie Cobbs changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Bootloader |Bootloader Resolution|FIXED | AssignedTo|mchang@suse.com |jsrain@suse.com Product|openSUSE 12.2 |openSUSE 12.3 OS/Version|openSUSE 12.2 |openSUSE 12.3 --- Comment #15 from Archie Cobbs 2013-04-19 18:00:59 UTC --- This problem still occurs and can be easily reproduced as follows: 1. Create a totally stock openSUSE 12.3 "Server" system on susestudio.com 2. Notice that by default "grub2", but not "grub", is shown under "Software" 3. Build and download a VMWare image 4. Boot the image in VMWare 5. Login as root 6. Notice BOTH grub and grub2 are installed (via "rpm -qa | grep grub"); however, /etc/sysconfig/bootloader is now properly configured with LOADER_TYPE="grub2" (this was not the case previously) 6. Run these commands to install a new kernel: $ zypper ar http://download.opensuse.org/repositories/Kernel:/openSUSE-12.3/standard/Ker... $ zypper ref $ zypper -v up kernel-default 6. Notice several errors spit out by zypper during kernel upgrade. 7. Restart system and discover that it can no longer be booted. So there are three problems here: *** PROBLEM #1 *** Even if you select only "grub" OR only "grub2" in under "Software" in susestudio.com, you always get BOTH of them for some reason. I can't tell if this is a problem with susestudio, kiwi, or openSUSE. *** PROBLEM #2 *** The following files are missing from the generated image, and this causes the kernel upgrade to fail: /boot/grub2/device.map /etc/default/grub_installdevice The errors that you see because of this are: The following NEW package is going to be installed: kernel-default 3.7.10-13.1 1 new package to install. Overall download size: 38.4 MiB. After the operation, additional 153.8 MiB will be used. Continue? [y/n/?] (y): committing Retrieving package kernel-default-3.7.10-13.1.x86_64 (1/1), 38.4 MiB (153.8 MiB unpacked) Retrieving: kernel-default-3.7.10-13.1.x86_64.rpm ................................................................................................................................................................[done (879.6 KiB/s)] (1/1) Installing: kernel-default-3.7.10-13.1 ...................................................................................................................................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.7.10-13-default Initrd image: /boot/initrd-3.7.10-13-default KMS drivers: vmwgfx Root device: /dev/sda1 (mounted on / as ext3) Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_rdac scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw drm ttm vmwgfx scsi_transport_spi mptbase mptscsih mptspi usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd usbhid hid-logitech-dj hid-generic Features: acpi kms plymouth block usb resume.userspace resume.kernel Perl-Bootloader: 2013-04-19 12:05:00 <3> pbl-9571.2 FileIO::ReadFile.85: Error: Failed to open /boot/grub2/device.map: No such file or directory Perl-Bootloader: 2013-04-19 12:05:00 <3> pbl-9571.2 FileIO::ReadFile.85: Error: Failed to open /etc/default/grub_installdevice: No such file or directory Perl-Bootloader: 2013-04-19 12:05:00 <3> pbl-9571.2 Core::GRUB2::GrubDev2UnixDev.127: Error: did not find a match for hd0 in the device map Perl-Bootloader: 2013-04-19 12:05:00 <3> pbl-9571.2 FileIO::ReadFile.85: Error: Failed to open /etc/default/grub_installdevice: No such file or directory To fix this requires the following manual steps: 1. /boot/grub2/device.map must be created containing "hd(0) /dev/sda" 2. /etc/default/grub_installdevice must be created containing "/dev/sda" *** PROBLEM #3 *** If you reboot after encountering problem #2, your system will not boot because the GRUB2 configuration is screwed up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Apr 25 Apr

09:34

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c18 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |jsrain@suse.com --- Comment #18 from Michael Chang 2013-04-25 09:34:43 UTC --- Hi, I have fixed that perl bootloader did not have to explicitly require device.map. obs://home:michael-chang:bnc804065/perl-Bootloader It invokes grub2-probe to get the mappings of grub device and os device instead of reading /boot/grub2/device.map. If there's /boot/grub2/device.map, grub2-probe will honer it (overrides it's internal mapping), so we won't loose anything (hopefully). I think one thing left to do is to write the install device to /etc/default/grub_installdevice. It has to be kiwi or other means that decides it. I will submit the patch after testing, and need someone to take care the install device. Jiri do you know who should is better to do that? thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Sep 5 Sep

08:57

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c19 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|jsrain@suse.com | --- Comment #19 from Jiri Srain 2013-09-05 08:57:31 UTC --- I think that it still should be perl-Bootloader who writes the settings, incl. the boot device. I think that here the problem was more related to the switch of bootloader via plain zypper up - without all options being migrated. kiwi (or YaST) is only involved in the initial installation (or, in case of YaST, when you reconfigure bootloader via the module). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:45

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c20 --- Comment #20 from Archie Cobbs 2013-09-05 17:45:32 UTC ---

...

kiwi (or YaST) is only involved in the initial installation (or, in case of YaST, when you reconfigure bootloader via the module).

Yes but please see "PROBLEM #1" Step #6 .. kiwi installs BOTH grub and grub2 at the same time. This mistake seems to set up this whole problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Sep 25 Sep

12:14

New subject: [Bug 804065] zypper up installed grub2, then reboot FAILED after next kernel upgrade

https://bugzilla.novell.com/show_bug.cgi?id=804065 https://bugzilla.novell.com/show_bug.cgi?id=804065#c Alberto Planas Dominguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

3874

Age (days ago)

4096

Last active (days ago)

List overview

Download

20 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 804065] New: zypper up installed grub2, then reboot FAILED after next kernel upgrade

tags

participants (1)