Bugzilla – Bug 759224
Milestone 4 stops at GRUB
Last modified: 2012-04-26 14:50:37 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 I used zypper dup and got Milestone 4. On a reboot the following happens ---------------------------------- Booting from local disk... GRUB ---------------------------------- That's as far as it gets. Only the Milestone 2 DVD will boot to rescue, Milestone 3 will allow update or install but not rescue. grub2 was OK around 14:00 Wednesday after a zypper dup and it was still Milestone 3. rpm -qi grub2 says it was installed on 20th. April. I have another x86_64 system I upgraded and "grub2-mkconfig -o /boot/grub2/grub.cfg" works but I am reluctant to try rebooting that. Reproducible: Always Steps to Reproduce: 1. zypper dup to Milestone 4 2. Reboot 3. Actual Results: See Details above. Expected Results: Should bring up grub2 menu.
Assuming this is about GRUB2. Michael, I guess you can better ask for the right information to help resolve this issue.
@Jiri, Thanks. I just figured out why. The problem is that when grub2 package updates the core.img file relocates to elsewhere in file system. Unfortunately grub2-install seems not triggered in the process thus grub2's boot.img (stage1) still use stale block-list trying to load core.img (stage2). @Sid, I'll try resolve it asap .. meanwhile would it be possible to recover your system ? Sorry for the inconvenience.
how about my bug I opened from 12.1, that has the same "GRUB " hanging there after the kernel update from last week? 12.1 doesnt have grub2, still it was the first situation I came across such a defect on opensuse recently https://bugzilla.novell.com/show_bug.cgi?id=758570 thanks for helping.
@andreas, Sorry this one should dup with 758570 .. *** This bug has been marked as a duplicate of bug 758570 ***
(In reply to comment #2) > @Jiri, > > Thanks. > > I just figured out why. The problem is that when grub2 package updates the > core.img file relocates to elsewhere in file system. Unfortunately > grub2-install seems not triggered in the process thus grub2's boot.img (stage1) > still use stale block-list trying to load core.img (stage2). > > @Sid, > > I'll try resolve it asap .. meanwhile would it be possible to recover your > system ? > > Sorry for the inconvenience. I booted from a 12.2 Milestone 2 DVD into rescue, the Milestone 3 DVD fails rescue. I mounted /dev/sda1 as /mnt chroot /mnt grub2-install complained it couldn't find / (as I remember). Booted 12.2 Milestone 3 DVD and chose install --> upgrade, included factory repos. It's up and running as Milestone 3. It's backed off some of the changes, e.g gcc is now back at 4.6.3 whereas it was 4.7.0 previously. Awaiting your fix before doing zypper dup again.
(In reply to comment #5) > (In reply to comment #2) > > @Jiri, > > > > Thanks. > > > > I just figured out why. The problem is that when grub2 package updates the > > core.img file relocates to elsewhere in file system. Unfortunately > > grub2-install seems not triggered in the process thus grub2's boot.img (stage1) > > still use stale block-list trying to load core.img (stage2). > > > > @Sid, > > > > I'll try resolve it asap .. meanwhile would it be possible to recover your > > system ? > > > > Sorry for the inconvenience. > > I booted from a 12.2 Milestone 2 DVD into rescue, the Milestone 3 DVD fails > rescue. > I mounted /dev/sda1 as /mnt > chroot /mnt > grub2-install complained it couldn't find / (as I remember). I think the error was mostly due to empty /dev and /sys, Try the commands (I also reply it in factory ML) 1. Boot to rescue system 2. mount /dev/sda1 /mnt (suppose /dev/sda1 is your / partition) 3. mount --bind /dev /mnt/dev 4. mount --bind /sys /mnt/sys 5. mount --bind /proc /mnt/proc 6. chroot /mnt 7. /usr/sbin/grub2-install --force --skip-fs-probe /dev/sda1 (ASSUME you want to install to /dev/sda1) Hope this works for you. > > Booted 12.2 Milestone 3 DVD and chose install --> upgrade, included factory > repos. > It's up and running as Milestone 3. > > It's backed off some of the changes, e.g gcc is now back at 4.6.3 whereas it > was 4.7.0 previously. > > Awaiting your fix before doing zypper dup again. I'm trying hard on it. Thanks.
OK, I started another zypper dup. When that is finished I'll try the grub2 commands.
This time I ran "grub2-mkconfig -o /boot/grub2/grub.cfg" before rebooting and it booted Milestone 4. I wanted to check that out as I have another box that's already at Milestone 4 and I wanted to see if it was safe to reboot having ran grub2-mkconfig on it.