Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 11-29-2006, 06:27 PM   #1
LQ Newbie
Registered: Nov 2006
Location: Canada
Distribution: Debian (Sarge)
Posts: 3

Rep: Reputation: 0
Debian will not boot after unknown event

I will start with this question in the newbie section.

I have, what I thought, was a stable install of Debian. Up until tonight all was well.
Here are specs first:

Dual P3 550 running the stable 2.6.8-SMP 686 kernel on Sarge.

A few weeks ago I installed VMware sucessfully. I had an XP vm running as well as a DOS 6.22 vm. The catalyst for this event, I think, is my desire to have sound in the DOS vm.

To this point the machine has not had a sound card. With an uptime around 80 days, I turned off the PC and installed a Creative CT4810 (Esonique). Turning the PC back on everything went seemingly according to plan.

Upon booting to the bash prompt (this machine does not run X) I typed lspci | grep audio to ensure Debian saw the card. It returned details about a CT4810 and something akin to a memory address. I thought all was well.

I fired up vmware server console on my Windows machine to begin my DOS vm adventures, but I could not connect. I then loaded the web interface (vmware-mui) from Windows and all looked ok. I started the DOS vm and quite strangely the whole Debian PC restarted.

Now, each time Debian boots 1 of 2 things happens:

1) The boot process hangs permanently "Checking quotas..." (which is immediately preceded by "Mounting local file systems..."

2) The boot process hangs briefly at the same place... but then spits out a variety of things
Call Trace:
... all with too much for me to type here right now.
<0> Kernel panic: fatal exception in interrupt
In interrupt handler - not syncing

I have removed the sound card and the booting remains the same... I only have the 1 kernel to boot with as I removed the default 2.4.x kernel that is installed initially by the Debian installer.

I would like to know if there is a way for for me to salvage this install, without having to install on a new drive, mount this one and then bring everything over.
Old 11-29-2006, 06:37 PM   #2
LQ Newbie
Registered: Nov 2006
Location: Canada
Distribution: Debian (Sarge)
Posts: 3

Original Poster
Rep: Reputation: 0


I guess after so many mounts of a filesystem fsck is forced to run...

So it ran, prompted me to login and remount the drive as rw. I did this and ran fsck again. It found some things and I answered 'Y' to all questions... and then dumped me back to the same interrupt error.

But.. now when I reboot it hangs much earlier:

chroot: cannot run command '/sbin/init': No such file or directory
Kernel panic: Attempted to kill init!

My guess at this point is that the kernel, as well as other files are corrupt on the hard drive.

I have the Debian net-installer CD. Is there a way to copy the 2.4.x kernel files to the drive and then I can edit GRUB to load the different kernel? Am I destined to reinstall on a new drive and bring over what I can from this one?

Old 11-29-2006, 07:16 PM   #3
Senior Member
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 -current
Posts: 2,300

Rep: Reputation: 90
Use a LiveCD or other Linux bootable CD to boot up your system and then run fsck on the drive.
Old 11-29-2006, 08:42 PM   #4
LQ Newbie
Registered: Nov 2006
Location: Canada
Distribution: Debian (Sarge)
Posts: 3

Original Poster
Rep: Reputation: 0

Thanks for the reply.

I have discovered that 1 stick of RAM seems to have been the cause all along. Until I removed the problematic 64mb stick I couldn't boot into any live CD or alternate OS on this machine

I ended up doing something similar to your suggestion...

I installed a base Debian install on a spare hard drive. Then I mounted the original, problem drive. The entire contents of /sbin was gone. The folder was empty. Something must have been screwed up when it ran fsck and had the bad stick of RAM in it. I copied all files from /sbin on the good install to the /sbin on the other drive and prayed.

Everything started seemingly normally. I am aware there are some symlinks which did not get copied but I will deal with that as needed. At least it will boot now and all init scripts and services seem to run properly.

Thanks again.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Unknown machine mode while installing gcc 2.6.3 on a P4 PC running Debian 3.1 bigwab Linux - Software 3 12-17-2010 08:34 AM
Very strange boot event in FC5 BobNutfield Fedora 7 03-26-2006 02:46 PM
Debian 3.1 kernel upgrade to 2.6.8-16sarge1 causes CUPS to fail-unknown-parallel0 joespam Debian 2 01-10-2006 11:17 AM
Debian-sid: filesystem unknown parition type solferino Debian 1 09-03-2004 09:09 AM
Unknown hanging during boot up EgosZ Fedora 2 09-03-2004 07:27 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 02:35 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration