Mailinglist Archive: opensuse (3217 mails)

< Previous Next >
Re: [SLE] Kernel Panic VFS Unable to mount root [NEW ERROR]
  • From: wmeler <wmeler@xxxxxxxxxxxxx>
  • Date: Mon, 1 Mar 2004 01:55:24 -0500 (GMT-05:00)
  • Message-id: <11632839.1078124124558.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
If you formatted, you may not have written over the bootloader. I'm nearly positive the VFS error was related to the bootloader being confused. And unless you WIPE (not format) the drive, grub or lilo could easily be causing you problems.

If you need help wiping the drive, let me know. Formatting only erases the partitions usually (or sometimes just the beginnings and ends of the partitions). The bootloader is usually NOT one of the partitions to be erased.

-----Original Message-----
From: Hartmut Meyer <hartmut.meyer@xxxxxx>
Sent: Feb 28, 2004 2:00 PM
To: suse-linux-e@xxxxxxxx
Subject: Re: [SLE] Kernel Panic VFS Unable to mount root [NEW ERROR]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am Samstag, 28. Februar 2004 19:26 schrieb edoc:

> Booted from the SuSE 9 Pro CD 1 and started a new Installation in
> Safe Mode.
>
> Now I have a lovely new error message, much more creative than
> the old one:
>
> "Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler -- not syncing."
>
> Gobbledygook to me ... can someone translate, please?

This could be a pointer to a hardware flaw (most likely defective RAM).

You're not doing any overclocking or the like?

My advise would be to let metest86 ("memory test" boot option from the 1st
SUSE CD) run over night and see if it reports any errors.


Greetings from Bremen
hartmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAQOVXZopYnYJxam4RAvghAJ9BDwgmhgRgEBpJf84jjCK8CpGZzgCfWlWT
HvDuPKQo2S0iKfowUae+ZIQ=
=DBIy
-----END PGP SIGNATURE-----

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx




Cheers,
wmeler

< Previous Next >
This Thread