I just ran zypper dup on my M3 install using the factory oss and non-oss repos and it no longer boots. All I see is a black screen with:
GRUB _
and I can’t type anything. I’m using Grub 2. Anyone know what the problem is or how to rescue this?
On 04/18/2012 11:26 AM, pilotgi wrote:
>
> I just ran zypper dup on my M3 install using the factory oss and non-oss
> repos and it no longer boots. All I see is a black screen with:
>
>
> Code:
> --------------------
> GRUB _
> --------------------
>
> and I can’t type anything. I’m using Grub 2. Anyone know what the
> problem is or how to rescue this?
It happened to me as well. To recover, download the M3 NET install CD for your
architecture, boot it, and select “Upgrade”, or use the DVD and upgrade from
there. Either one will reinstall GRUB. I tried all the tricks using a rescue
disk, but I never was able to reinstall GRUB by any other means.
I downloaded Net-x86_64-build 0332. I didn’t see an “Upgrade” option so I chose install. It stalled near the beginning. I forget exactly what it said but it was something that was 1 of 6 and it said 1 was 100% and then nothing else happened. I’m reinstalling from the KDE-Live CD now.
On 04/18/2012 05:26 PM, pilotgi wrote:
>
> I downloaded Net-x86_64-build 0332. I didn’t see an “Upgrade” option so
> I chose install. It stalled near the beginning. I forget exactly what it
> said but it was something that was 1 of 6 and it said 1 was 100% and
> then nothing else happened. I’m reinstalling from the KDE-Live CD now.
When you use NET, you need a network connection. Nearly everything is
downloaded. Are you sure nothing was happening? Sometimes the display goes to
100% early, but it is still downloading. Once all 6 parts are available, then
you will be asked if you want a “New Installation” or an “Upgrade”.
Larry, when I upgraded my openSUSE 12.2 M2 to M3 using zypper, it switched me to Grub Legacy. I had been playing with a menu.lst file and oddly, it came up and allowed me the one selection it included, which was valid, to run openSUSE 12.2 M3 . I then used grub2-install to reinstall grub2 and my old grub2 menu was still there. So, for some reason, doing a zypper up/dup in place upgrade is loading grub in place of grub2. This an issue worth posting as a problem report, but hard to reproduce again. What is your thoughts about this issue? By the way, a full install of M3 by DVD to a VirtualBox session had no such problem.
Thank You,
I don’t know if anything was downloading or not. I guess I got too impatient. I’m now running M3 again within VirtualBox from the live-cd install. I checked bugzilla for problems with grub2 but I didn’t see anything that resembled this problem. I’m wondering if I update from the factory repos again but deselect the update for grub2 if I’ll get the same result.
So, to show the problem can be produced over and over, you would want the exact setup that had the problem before. If you knew you got switched to grub legacy with no menu.lst file, you could boot from a LiveCD, chroot to the old setup and run Grub2 to reinstall and likely, your original upgraded openSUSE 12.2 would work OK.
Thank You,
What does “chroot to the old setup” mean?
chroot means to run command or interactive shell with special root directory. Imagine that you boot from a liveCD and the create a mount point for your openSUSE 12.2 M3 root / folder. You could open a terminal as root and do:
cd /
mkdir /M22Root
mount /dev/sdb2 (or what ever partition it is located at. Use fdisk -l to find out)
chroot /M22Root
/usr/sbin/grub2-install --force /dev/sdb2
This does not try to determine where grub2 was loaded, MBR or in the root / partition, but the latter is the default. The exact entries are a guess, but it would be something like this above.
Thank You,
I updated this evening from the factory repos using YaST instead of zypper dup. I locked grub and grub2 so they wouldn’t update. There were 2.5 GB of updates and when I rebooted everything worked fine. Even the boot-up chime is now working. The grub2 package is dated April 15 so I’m wondering if the next update will cause any problems.
Well as long as we are in the Milestone versions, anything is possible. I really never thought switching to grub2 would be easy and we just kept dodging the bullet each time before until the devs decided to push the grub2 button this time. Its just like when we switched over to systemd the last time. Its going to take some extra effort to get over this hump, for the better I hope.
Thank You,
So I’m back to this problem again. Is this a problem for anyone who updates the kernel and grub2, or is it just me?
Am I doing something wrong or is this just because 12.2 and grub2 are still experiencing growing pains?
On 05/26/2012 09:26 AM, pilotgi wrote:
>
> pilotgi;2456810 Wrote:
>> I just ran zypper dup on my M3 install using the factory oss and non-oss
>> repos and it no longer boots. All I see is a black screen with:
>>
>>>
> Code:
> --------------------
> > > GRUB _
> --------------------
>>>
>> and I can’t type anything. I’m using Grub 2. Anyone know what the
>> problem is or how to rescue this?
> So I’m back to this problem again. Is this a problem for anyone who
> updates the kernel and grub2, or is it just me?
>
> Am I doing something wrong or is this just because 12.2 and grub2 are
> still experiencing growing pains?
A factory dup is always a gamble, but it looks as if your grub2 installation
failed. Someone may know the magic incantation to reinstall grub2 from a rescue
disk. If not, I have a way to reinstall legacy grub. Boot a rescue disk such as
the 12.2 Live CD. Once that is running, open a terminal, and mount the /
partition in /mnt. Then run the following set of commands:
su -
grub
root (hd0,1)
setup (hd0,1) (hd0,1)
exit
dd if=/usr/lib/boot/master-boot-code of=/dev/sda bs=440 count=1
The above assumes the the boot disk is /dev/sda. If that is not true, then
adjust the “hd0” part. It also assumes that the active (boot) partition is
/dev/sda2. Adjust the number after the comma to be the partition number minus 1
if it differs. Be very careful with the dd command. Forgetting the “bs=” part
will destroy the partition table on your disk!!!
The above commands will install legacy grub, and as you were using grub2 before,
you will need to check /mnt/boot/grub/menu.lst to make certain it will boot your
kernel. Once you have rebooted, use YaST to reinstall grub2.
When I tried this, it said / and /root “is not a block device.” When I tried the dd command, no menu.lst file was created.
I read this thread but I did not understand much. I have opensuse 12.2 installed but when I updated using zypper dup it does boot in graphical interface anymore. I removed the nvidia installation but it did not help. Can anyone help me please? In addition, I don’t remember which packages were updated.
On 02/20/2013 07:26 AM, m aghtar wrote:
>
> I read this thread but I did not understand much. I have opensuse 12.2
> installed but when I updated using zypper dup it does boot in graphical
> interface anymore. I removed the nvidia installation but it did not
> help. Can anyone help me please? In addition, I don’t remember which
> packages were updated.
As has been the case since kernel 2.6.0, ALL external modules MUST be
rebuilt whenever the kernel is changed. You will need to rebuild the nVidia
driver, use nouveau, or be content with the framebuffer driver nv.