Kernal Panic Help....

[Twinkle]

Hi..


Just started me Linux debian install everything went cool .. I booted a couple of times with no problem ... Until I booted into Win XP then tried to boot into debian and I started getting this error msg:

EXT3-fs: group descriptors corrupted
pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernal panic: Attempted to kill init!

Here where it hangs and wont reboot or do anything...


I installed debian from the 2 DVDs I downloaded...
I am a newbie who is willing to learn ..

Will apprecaite ur help....

Twinkle...

[cyclister]

Do you overclock?
If answer are yes to that question the answer are quite easy, lower your temprature in your computer's chassi/box.Had some hick ups with kernel panic and them was all to heat, at least ubuntu on this rig want to have maximum 39 celcius.

If that's not the issue here then my answer are incorect but lower the temp are a nice thing to a stable system, a system with high temp will suffer some minor hick ups and in windows you get more often "stuck".

Cpu core have AS5 cold paste and a nice heatsinker the more it can lower the temp the better, cu are a nice metal that often heatsinks's has here more heavier then alu but suck in more heat.Watercooling are almost best beacuse you get it cold chill and less sound ok wapo's and co but they do not take the gpu core.

A nice dimension on the heatsink and you can throw away your fan for a more stable cpu clock freqens and less sound, also on your gfx card they generate a lot of heat.Then a couple of fans in the box with low speed so your heatsinks have something to work with, you do install a fan controller for reducing power to the fans power to the fans that was quite funny, not.

Now isent at least the temprature a problem any more for your linux rig

[Twinkle]

Hi ..

After I have been a happy user of linux for a couple of days .. I booted again into XP and then tried to boot again into debain and started getting the same Kernel panic again ???

EXT3-fs: group descriptors corrupted !

Will apprecaite any help..

I am not overclocking my machine, double checked the bios is not set to overclock.. I fixed the problem the first time by re installing debian...
I dont want to reinstall every time?!!!
Logged into XP and then into debian normally with no probs until today !!! Why now? Agian !!

[engineuity]

As root:
fdisk -l /dev/hda
(or whatever disk debian is installed on)
Check your linux partitions to make sure that they are type 83 "Linux"
If they arent, you need to change them to that type...the partition may need to be reformatted depending on the type, so be prepared for another reinstall


Edit:
You can also use a live-cd (or the install cd) to run fsck on the partitions.

Start either the live-cd or install cd:
For the live-cd just pop up a shell
For the install cd, hit escape once you get to the partitioning section. Then scroll down to execute a shell

From there run:
fsck /dev/hda1
Make sure you run that on all of your linux partitions. I dont know if it will affect a windows partition, but I would try to avoid that.

[Twinkle]

I checked fdisk and they were all 83 linux partitions..

I ended running fsck.ext3 which seemed to have fixed the problem for now .. I am not sure what is causing it to crash after running windows??

[junkman4547]

Just curious Twinkle, how do you boot into different OS?

I my case, I have Debian installed on the Master harddrive and Win2000 on the Slave drive. I would changed the BIOS to boot different OSs. Now if Debian is on Slave harddrive, I get the Kernel panic like you.

[Twinkle]

I have set my system as dual boot .. I have grub run from the main disk with a choice of which OS to boot from..
I have set grub when I ran Debian setup and according to debian installation manual instructions...



Back to my main problem ,,, It happened again ..
Kernel Panic due to corrupted descriptors after running Win XP all day !!!! Why is Win XP causing me a problem everytime I run it ?

[engineuity]

i believe junkman was giving you an explanation...that it may be because your debian os is on a slave drive

[Twinkle]

Both drives are running masters on SATA1 and SATA2 !!! I think thats the way I have them ?!
Am starting to suspect that the drive is faulty or something?!