Suse 10.1 doesn't start anymore.: help!
Hello, I have been running for months Suse 10.1 on a pc without any problem. Yesterday, all of a sudden, it stopped working. What happens is that I arrive to the Grub screen where I can choose between Suse 10.1 and Suse/failsafe mode. If I select the first, or let the timeout expire, the screen goes black in about one second and nothing happens anymore. I have to press the reset button to restart. if I select the failsafe mode, it goes almost immediately to character mode and freezes after printing "Kernel panic" and something else which unfortunately I had no possibility to write down. If I boot the Knoppix 4.02 CD, it starts and works just fine, mounts my hard disk, my files are still there... everything OK. My _feeling_ is that the MBR and/or the /root partition were corrupted in some way. What I'd like to ask is: 1) how could it have happened (that is, excluding hw faults) 2) what else could it be 3) What is the most efficient way to fix it (it's been a long time since I had to do similar things, and I'd really appreciate some pointers to go in the right direction from the beginning, without false starts... with only Knoppix 5.01 CD (not dvd) and the suse install CDs without Net access :-( (I can just ask a friend to download and burn to CD other stuff for me until this is fixed...) The PC: Asus A8N-VM Motherboard with AMD Athlon 64 X2 3800, 4GB RAM Any help is welcome!! TIA, Marco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-10-18 at 14:38 +0200, Marco Fioretti wrote:
if I select the failsafe mode, it goes almost immediately to character mode and freezes after printing "Kernel panic" and something else which unfortunately I had no possibility to write down.
You can use the install CD/DVD to first try to boot the installed system (the option is there somewhere), or start the rescue system, which will examine several things. My guess would be a bad kernel update (there was one not too long ago). If you saw the wording "kernel panic" then the MBR and grub are probably correct. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFNiYItTMYHG2NR9URAnMGAJkBhqVzIlJ4PyUYTfC5AWk5hNmHFgCeOi5u uUbbH9bMwIcwiaoDMVGCaBs= =xhFK -----END PGP SIGNATURE-----
On 06/10/18 14:38 (GMT+0200) Marco Fioretti apparently typed:
I have been running for months Suse 10.1 on a pc without any problem. Yesterday, all of a sudden, it stopped working. What happens is that I arrive to the Grub screen where I can choose between Suse 10.1 and Suse/failsafe mode.
If I select the first, or let the timeout expire, the screen goes black in about one second and nothing happens anymore. I have to press the reset button to restart.
if I select the failsafe mode, it goes almost immediately to character mode and freezes after printing "Kernel panic" and something else which unfortunately I had no possibility to write down.
If I boot the Knoppix 4.02 CD, it starts and works just fine, mounts my hard disk, my files are still there... everything OK.
My _feeling_ is that the MBR and/or the /root partition were corrupted in some way. What I'd like to ask is:
1) how could it have happened (that is, excluding hw faults)
I've run into something like that lately, getting an immediate CRC error and/or "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)". I think in my case some sector(s) holding initrd or the kernel were weak. I replaced the HD. Try running several passes of badblocks on the partition holding yours to see if your problem might too be the HD. -- "The Lord is my strength and my shield; my heart trusts in him, and I am helped." Psalm 28:7 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/
On Wednesday 18 October 2006 14:38, Marco Fioretti wrote:
I have been running for months Suse 10.1 on a pc without any problem. Yesterday, all of a sudden, it stopped working. What happens is that I arrive to the Grub screen where I can choose between Suse 10.1 and Suse/failsafe mode.
If I select the first, or let the timeout expire, the screen goes black in about one second and nothing happens anymore. I have to press the reset button to restart.
if I select the failsafe mode, it goes almost immediately to character mode and freezes after printing "Kernel panic" and something else which unfortunately I had no possibility to write down.
Yes, there's lots of technical data after that. But usually near the words "kernel panic" (maybe the line above or below) is a short reason for the panic, e.g. "unable to mount rootfs" or so. Cheers, Leen
participants (4)
-
Carlos E. R.
-
Felix Miata
-
Leendert Meyer
-
Marco Fioretti