[Bug 848826] New: upgrade 12.3 -> 13.1 RC2 hangs on boot
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c0 Summary: upgrade 12.3 -> 13.1 RC2 hangs on boot Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Upgrade Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: axel.braun@gmx.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I did a new installation of 12.3 in Virutalbox, SUSE Base system with LXDE and all patches applied. Changed the 4 repos from 12.3 to 13.1 run in a terminal zypper dup -dl and afterwards zypper dup -l Installation itself went fine. After closing the terminal, system did not shut down properly and had to be switched off. On restart the system hangs at boot and just displays GRUB Second attempt, after upgrading I did not close the terminal window, but entered a shutdown -r now ..result was the same Reproducible: Always Steps to Reproduce: 1.see above 2. 3. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |ma@suse.com |ovo.novell.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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |snwint@suse.com |ovo.novell.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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c2 Mario Knothe <mario_knothe@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mario_knothe@web.de --- Comment #2 from Mario Knothe <mario_knothe@web.de> 2013-11-12 18:08:28 UTC --- I think it is the same problem how bug 848973: the entry in grub.cfg is faulty. Can you repair it from a livesystem, the new 13.1 should boot. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|snwint@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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c3 --- Comment #3 from Axel Braun <axel.braun@gmx.de> 2013-11-13 08:45:40 UTC --- (In reply to comment #2)
I think it is the same problem how bug 848973: the entry in grub.cfg is faulty.
Hmmmm...scrolled through the grub.cfg , and wish the old grub1 style back. Anyway, could not spot the point where there might be something wrong...
Can you repair it from a livesystem, the new 13.1 should boot.
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c4 --- Comment #4 from Michael Chang <mchang@suse.com> 2013-11-13 11:35:04 UTC --- Hi Axel, What's the file system used for your /boot ? You bootloader is installed to partition or MBR ? Anyway if you see only 'GRUB' that means second stage core.img not loaded due to it's block has changed and your MBR or partition boot record using a wrong block. Try mount your root partition in rescue mode and provide the logs under /var/log/YaST2. Besides you can try this commands in rescue mode to bring your back. Suppose that your root partition is /dev/sda1 mount /dev/sda1 /mnt mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev chroot /mnt update-bootloader --reinit || update-bootloader --refresh -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c5 --- Comment #5 from Axel Braun <axel.braun@gmx.de> 2013-11-13 15:41:27 UTC --- (In reply to comment #4)
What's the file system used for your /boot ?
ext4
You bootloader is installed to partition or MBR ? Anyway if you see only 'GRUB' that means second stage core.img not loaded due to it's block has changed and your MBR or partition boot record using a wrong block.
Try mount your root partition in rescue mode and provide the logs under /var/log/YaST2.
will attach them
Besides you can try this commands in rescue mode to bring your back. Suppose that your root partition is /dev/sda1
mount /dev/sda1 /mnt mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev chroot /mnt update-bootloader --reinit || update-bootloader --refresh
That fails with the error message disk 'hd0,2' not found The boot partition is on /dev/sda2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c6 --- Comment #6 from Axel Braun <axel.braun@gmx.de> 2013-11-13 15:43:10 UTC --- Created an attachment (id=567295) --> (http://bugzilla.novell.com/attachment.cgi?id=567295) YaST2-logs logs as requested -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c7 --- Comment #7 from Axel Braun <axel.braun@gmx.de> 2013-11-13 15:46:39 UTC --- root partition, of course I did not change the location of the boot loader - it was defaulted from the installation of 12.3 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c8 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |axel.braun@gmx.de --- Comment #8 from Michael Chang <mchang@suse.com> 2013-11-14 05:38:53 UTC --- I see the same error in your log. 2013-11-05 18:17:35 <1> pbl-6120.2 Core::RunCommand.1641: run /usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "(hd0,2)"
/var/log/YaST2/y2log_bootloader 2>&1 - ret 256 + output: /usr/sbin/grub2-bios-setup: error: disk `hd0,2' not found.
2013-11-05 18:17:35 <3> pbl-6120.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "(hd0,2)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: error: disk `hd0,2' not found.
Did your /boot/grub2/device.map exists ? A successful grub2-install needs this file like this. 2013-11-04 19:23:54 <1> pbl-3626.2 FileIO::ReadFile.82: /boot/grub2/device.map = <<<<<<<<<<<<<<<< (hd0) /dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4
>>>>>>>>>>
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c9 --- Comment #9 from Michael Chang <mchang@suse.com> 2013-11-14 05:41:38 UTC --- Try this again to rescue your system or not ? mount /dev/sda1 /mnt mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev chroot /mnt echo '(hd0) /dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4' > /boot/grub2/device.map update-bootloader --reinit || update-bootloader --refresh -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c10 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|axel.braun@gmx.de | --- Comment #10 from Axel Braun <axel.braun@gmx.de> 2013-11-14 09:19:06 UTC --- the file /boot/grub2/device.map exists with exactly the same content I tried to rescue the system as described in comment 4 and 9, but the result remains the same: Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "(hd0,2)"
/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: error: disk `hd0,2' not found.
I wonder why it looks at 'hd0,2'. fdisk -l just shows /dev/sda1 : Linux swap /dev/sda2: Linux hd 0,2 would be /dev/sda3, no? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c11 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |axel.braun@gmx.de --- Comment #11 from Michael Chang <mchang@suse.com> 2013-11-14 10:55:56 UTC --- (In reply to comment #10)
hd 0,2 would be /dev/sda3, no?
Grub2 device syntax is one based for partition. http://www.gnu.org/software/grub/manual/grub.html#Device-syntax Would you change your /etc/default/grub_installdevice to this content and test again ? /dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4-part2 activate generic_mbr In 13.1, new installation doesn't use grub device name as installation device as it requires device.map which causes trouble many times. It uses by-id device name like above as grub2-install supports it very well. Since you're upgrading from 12.3, grub device is kept in used and it seems a regression in 13.1 grub2 version causes the trouble. I cannot go deep in it now as I'm away from my test machines. Please try above test and if it works for you, use it and it's not a workaround. I'll back to this topic probably next week. Please let me know if it works or not. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c12 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|axel.braun@gmx.de | --- Comment #12 from Axel Braun <axel.braun@gmx.de> 2013-11-14 11:23:20 UTC --- (In reply to comment #11)
Would you change your /etc/default/grub_installdevice to this content and test again ?
/dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4-part2 activate generic_mbr
done. ran update-bootloader --reinit || update-bootloader --refresh with error message: /usr/sbin/grub2-probe: error: cannot find a GRUB drive for /dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4-part2. Check your device.map. device.map contains (hd0) /dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c13 --- Comment #13 from Michael Chang <mchang@suse.com> 2013-11-15 07:16:10 UTC --- Weird. What if you replace update-bootloader --reinit || update-bootloader --refresh with this ? /usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe /dev/disk/by-id/ata-VBOX_HARDDISK_VB54378b33-5a4cf5d4-part2 and /usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe /dev/sda2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c14 --- Comment #14 from Axel Braun <axel.braun@gmx.de> 2013-11-15 08:39:32 UTC --- That did not help either, but pointed to the root cause of the problem: The upgrade test was performed on a cloned virtual machine - this gets obviously a new Harddisk-ID: localhost:/home/test # dir /dev/disk/by-id/ata-VBOX_HARDDISK* lrwxrwxrwx 1 root root 9 15. Nov 09:00 /dev/disk/by-id/ata-VBOX_HARDDISK_VBf6f1c11c-f08fc8bb -> ../../sda lrwxrwxrwx 1 root root 10 15. Nov 09:00 /dev/disk/by-id/ata-VBOX_HARDDISK_VBf6f1c11c-f08fc8bb-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 15. Nov 09:00 /dev/disk/by-id/ata-VBOX_HARDDISK_VBf6f1c11c-f08fc8bb-part2 -> ../../sda2 After assigning this ID to device.map the reinstallation works. Only strange thing is that it complained about something with ext2 file system - although ext 4 is used. I will close this bug as invalid Thanks for your patience and your help! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=848826 https://bugzilla.novell.com/show_bug.cgi?id=848826#c15 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #15 from Axel Braun <axel.braun@gmx.de> 2013-11-15 08:40:25 UTC --- closed as per prior comment -- 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.
participants (1)
-
bugzilla_noreply＠novell.com