I’ve updated the kernel of OpenSUSE 11.3 just recently via autoupdate, and now every time I try to boot, I get a kernel panic just after md scans for RAID:
VFS: Cannot open root device "disk/by-label/Root" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.34.7-0.5-desktop #1
I checked if the label is still there and it is, and I’ve also tried setting the root option to /dev/sda5 (which is the root partition), and it still fails with "Cannot open root device “sda5"”. Any idea what’s causing that and how to fix it, if it’s at all possible?
If your kernel is corrupted and you did not maintain more than one kernel version, you may need to reload, but only install a kernel, leaving everything else, by doing an in place upgrade. Here is a guide for this method.
Picasa Web Albums - carl fletcher - DVD Kernel Fix
If you get your system running, I would suggest you ask on how to maintain more than one kernel version, for future updates so you can drop back to a former working kernel.
Thank You,
I had the same issue after letting OpenSUSE 11.3 perform an automatic update from the repository. I was running the 64-bit version, so I wasn’t sure if it was specific to that kernel or anything else in my system. After several re-installs, then trying the 32-bit 11.3 (with the same results), I was about ready to give up. As a last resort, I updated the BIOS from my Intel D945GTP motherboard to the latest release (2009/11). After that, not another problem! All my updates have been smooth and the system is finally stable and working for me. For the few Linux desktops I’ve installed over the last few years, it seems getting the BIOS up-to-date is a ‘gotcha’ I never seem to remember, but it always resolves my general installation issues.
Bill
On 12/16/2010 09:06 AM, bvalaski wrote:
>
> I had the same issue after letting OpenSUSE 11.3 perform an automatic
> update from the repository. I was running the 64-bit version, so I
> wasn’t sure if it was specific to that kernel or anything else in my
> system. After several re-installs, then trying the 32-bit 11.3 (with
> the same results), I was about ready to give up. As a last resort, I
> updated the BIOS from my Intel D945GTP motherboard to the latest release
> (2009/11). After that, not another problem! All my updates have been
> smooth and the system is finally stable and working for me. For the few
> Linux desktops I’ve installed over the last few years, it seems getting
> the BIOS up-to-date is a ‘gotcha’ I never seem to remember, but it
> always resolves my general installation issues.
Buggy BIOS code is a real problem. When it fails to report the hardware
correctly, what is an OS to do? Panic seems a reasonable response.