Kernel panic after hard reboot and fsck

07-05-2010

Registered User

1,713, 295

Join Date: Feb 2010

Last Activity: 26 April 2017, 8:59 AM EDT

Location: istanbul

Posts: 1,713

Thanks Given: 4

Thanked 295 Times in 286 Posts

Code:

# export PATH=$PATH:/usr/bin:/usr/sbin:/bin:/sbin:/usr/bin

Code:

# mkinitrd -f -v --with=megaraid /boot/initrd-2.6.9-5.EL_new.img  $(uname -r)

edit like this and change the "default" line

Code:

 
# cat /boot/grub/grub.conf
default=1
....
....
title Red Hat Enterprise Linux Server New initrd-2.6.9-5.EL_new.img (2.6.9-5.EL_new)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-5.EL ro 
        initrd /initrd-2.6.9-5.EL_new.img

reboot
let see you what happened

Last edited by ygemici; 07-05-2010 at 11:37 AM..

ygemici

View Public Profile for ygemici

Find all posts by ygemici

07-06-2010

Registered User

11, 0

Join Date: Jul 2010

Last Activity: 12 August 2010, 8:45 AM EDT

Posts: 11

Thanks Given: 0

Thanked 0 Times in 0 Posts

[mod] Broken Links to Images Removed {/mod]

Also I have tried to change in my fstab LABEL to /dev/sdaX, but OS loading ending with this:

---------- Post updated at 12:49 AM ---------- Previous update was at 12:21 AM ----------

Quote:

Originally Posted by ygemici

Code:

# export PATH=$PATH:/usr/bin:/usr/sbin:/bin:/sbin:/usr/bin

Code:

# mkinitrd -f -v --with=megaraid /boot/initrd-2.6.9-5.EL_new.img  $(uname -r)

edit like this and change the "default" line

Code:

 
# cat /boot/grub/grub.conf
default=1
....
....
title Red Hat Enterprise Linux Server New initrd-2.6.9-5.EL_new.img (2.6.9-5.EL_new)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-5.EL ro 
        initrd /initrd-2.6.9-5.EL_new.img

reboot
let see you what happened

Thank you!

I have performed rebuild initrd with

Code:

mkinitrd -f -v --with=megaraid_mm  --with=megaraid_mbox /boot/initrd-2.6.9-5.EL_new.img 2.6.9-5.EL

because in /etc/modprobe.conf

Code:

alias scsi_hostadapter megaraid_mbox

but after reboot I have the same screen 404 - File or directory not found.

---------- Post updated at 02:14 AM ---------- Previous update was at 12:49 AM ----------

last dmesg available here

---------- Post updated at 09:10 AM ---------- Previous update was at 02:14 AM ----------

The problem was in a disabled RAID in BIOS. After reboot now I have screens:

and after fsck:

Last edited by nikkadim; 07-06-2010 at 08:57 AM..

nikkadim

View Public Profile for nikkadim

Find all posts by nikkadim

07-06-2010

Registered User

4,996, 477

Join Date: Dec 2003

Last Activity: 12 June 2016, 11:03 PM EDT

Location: /dev/ph

Posts: 4,996

Thanks Given: 73

Thanked 477 Times in 439 Posts

Looks like grub cannot find your initramfs after you fsck'ed the root filesystem - it is probably in lost+found. The previous "RAMDISK: Ran out of compressed data" message in your screenshot was a clue that there was something wrong with it anyway. You should rebuild it.

fpmurphy

View Public Profile for fpmurphy

Find all posts by fpmurphy

07-06-2010

Registered User

1,713, 295

Join Date: Feb 2010

Last Activity: 26 April 2017, 8:59 AM EDT

Location: istanbul

Posts: 1,713

Thanks Given: 4

Thanked 295 Times in 286 Posts

can you write the output ?

Code:

 # cat /etc/grub.conf

ygemici

View Public Profile for ygemici

Find all posts by ygemici

07-07-2010

Registered User

11, 0

Join Date: Jul 2010

Last Activity: 12 August 2010, 8:45 AM EDT

Posts: 11

Thanks Given: 0

Thanked 0 Times in 0 Posts

in grub.conf

It turned out that it was necessary to add the path /boot/ for kernel and initrd.

Now system going to boot and stoped here:

and after fsck -t ext2 /dev/sda1 -y

nikkadim

View Public Profile for nikkadim

Find all posts by nikkadim

07-07-2010

Registered User

1,713, 295

Join Date: Feb 2010

Last Activity: 26 April 2017, 8:59 AM EDT

Location: istanbul

Posts: 1,713

Thanks Given: 4

Thanked 295 Times in 286 Posts

Reboot and boot system for single user mode then run fsck

ygemici

View Public Profile for ygemici

Find all posts by ygemici

07-07-2010

Registered User

11, 0

Join Date: Jul 2010

Last Activity: 12 August 2010, 8:45 AM EDT

Posts: 11

Thanks Given: 0

Thanked 0 Times in 0 Posts

Quote:

Originally Posted by ygemici

Reboot and boot system for single user mode then run fsck

Yes, I have tried this but on next boot system again makes me checking filesystem..

and after pause:

Last edited by nikkadim; 07-07-2010 at 09:29 AM..

nikkadim

View Public Profile for nikkadim

Find all posts by nikkadim

Red Hat

Kernel panic after hard reboot and fsck

10 More Discussions You Might Find Interesting

1. Solaris

Df reporting double size of du after fsck & reboot

Discussion started by: lcoreyl

2. Solaris

fsck entire hard drive?

Discussion started by: orange47

3. HP-UX

Reboot After Panic

Discussion started by: Kozmo

4. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

Discussion started by: dave043

5. AIX

Is fsck executed during reboot for AIX?

Discussion started by: cteoh88

6. Solaris

different between soft reboot and hard reboot

Discussion started by: seelan3

7. UNIX for Advanced & Expert Users

reboot after panic hp-ux 11o

Discussion started by: shoultsc

8. Linux

kernel panic

Discussion started by: Davide71

9. UNIX for Advanced & Expert Users

Reboot after Panic

Discussion started by: nikk

10. UNIX for Dummies Questions & Answers

kernel panic

Discussion started by: pgas