I’ve been running openSUSE 12.2 without any issues for a month and after loading security patches that came out the past couple of days while the machine will boot up past the Grub2 screen it keeps cycling through the "openSUSE with linux 3.4.6-2.10 desktop (normal or recovery mode) and gives me the following error message:
boot/vmlinux…
error: you need to load the kernel list
Unfortunately the white text on green is not the easiest thing to read at times, and then the screen keeps recycling.
This is probably “you need to load the kernel first”. It means that (script) attempts to load initrd before kernel was loaded. Most likely kernel does not exist, so it fails to load and next initrd statement fails with this error.
You can press “e” on menu entry and check which kernel name it has. It looks like during kernel update old kernel was removed but configuration not updated.
Which should, of course, not have been allowed to go native (as in Live Update).
I don’t mind doing command line entries (looking back to the days of CP/M) to fix a few minor things, but there are entirely too many “newbies” that grew up in a windows world that don’t have a clue.
Thanks caf4926, for the quick reply. Let’s hope this snafu doesn’t turn people off completely.
I booted the rescue disk, as you indicated, but when I issued the “Fdisk -|” command it did not display any of the information you was indicated at the …vd-rescue.html page. I’ve gone through those steps once before when grub2 was not working properly, so I’m familiar with it. The last time I had used the Fdisk command it had displayed the information, but this time it did not. Odd… any suggestions?
I booted the rescue disk, as indicated indicated in the instructions, but when I issued the “Fdisk -|” command it did not display any of the information indicated at the …vd-rescue.html page. I’ve gone through those steps once before when grub2 stopped working properly, so I’m familiar with it. The last time I had used the Fdisk command it had displayed similar information, but this time it did not. Odd… any suggestions?
caf4926: Update… Was able to run through the Fdisk -l, mount, chroot commands and reloaded the Grub2, however, once it rebooted it gave the same error message as before that it needed to load the kernl first. Any suggestion?
The fdisk info is just that, for info only. Advanced user will likely already know which partition is /
I always prefer to see it in front of me. Belt and Braces.
Your bootloader is most likely OK, you need to recreate its configuration. In addition to /dev mount /proc and /sys, mount /boot if it is on separate partition and rub grub2-mkconfig:
...
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount /dev/sdXXX /mnt/boot
chroot /mnt
/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
If you could paste here grub.cfg before you overwrite it and “ls -l /boot” output it could explain why you have this error.
Thanks to caf4926 and arvidjaar – My system is back up and running. With the additional commands provided by arvidjaar the configuration file was rewritten and everything seems to be working fine.
Fdisk -l command provided the following:
Disk /dev/sda: 300.1 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical: 512 bytes /
I/O size (minimum/optimal): 512 bytes /512
Disk identifier: 0xab4f2e46
Device Boot Start End Blocks ID System
/dev/sda1 2048 4208639 2103296 82 Linux swap / Solaris
/dev/sda2 * 4208640 46153727 20972544 83 Linux
/dev/sda3 46153728 151011327 52428800 83 Linux
/dev/sda4 151011328 586072063 217530368 83 Linux
Rescue: ~ #
For arvidjaar: Here is the output of the ls -l /boot command, however, I was not able to locate the grub.cfg file before it would have been overwritten.
Rescue: ~ # ls -l /boot the command provided the following: