[I have survived a] Kernel Panic ! ! !

[Archie]

Now, I am eager for the new ISO! A couple of hours ago, I wanted to reboot but the shutdown hanged (left it for a bit but ...) so Power Off and Power On. Bad move. One bootup, I get a kernel panic of a different sort. I did a search on the forum, Googled a bit but none of the suggested fix seemed to work.

The error is as follow:

Code: [Select]

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)
I found suggestions such as # fsck -f /dev/sda5, # redo-mbr, # touch /forcefsck and none of these worked.

The error continues...

Code: [Select]

Pid: 1, comm: swapper Not tainted 2.6.38.6-pclos.bfs #1
Call Trace:
[c0439113] ? panic=0x66/0x161
[c05dfc3f] ? mount_block_root+0x1c0/0x259
[c02067dc] ? sys_mkmod+0x2c/0x30
[c05dfe50] ? prepare_namespace+0x14e/0x192
[c01f7de5] ? sys_access+0x25/0x30
[c05df9bc] ? kernel_init+0x198/0x1a7
[c05df824] ? kernel_init+0x0/0x1a7
[c01043fe] ? kernel_thread_helper+0x6/0x10
[code]

:)  I like to be thorough. In addition, I also noticed that in one of the reboots after an attempted fix, there was an additional info after the Pid line.
[code]Input: AlpsPS/ALPS GlidePoint as devices/platform/i8042/serio1/input/input2then the Call Trace.

Frankly, I cannot make out what all those meant, except the touchpad that is working on the LiveUSB (I am alternating the use of Zen Mini and e17 )

Here are the outputs of query commands:

Code: [Select]

[root@localhost archie]# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1bd271dd

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     2040254     1020096   82  Linux swap / Solaris
/dev/sda2         2040255    33479459    15719602+   5  Extended
/dev/sda4        33479460   234436544   100478542+  83  Linux
/dev/sda5         2040318    23229989    10594836   83  Linux
/dev/sda6        23230053    33479459     5124703+  83  Linux

Disk /dev/sdb: 1992 MB, 1992294400 bytes
62 heads, 62 sectors/track, 1012 cylinders, total 3891200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00023db9

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          62     3890127     1945033   83  Linux
[root@localhost archie]#[root@localhost archie]# umount /dev/sda5
[root@localhost archie]# fsck -f /dev/sda5
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
PCLinuxOS: 202501/662256 files (0.2% non-contiguous), 1501805/2648709 blocks
[root@localhost archie]#
/dev/sdb1 is a LiveUSB I am using to fix this machine. I am also unable to boot to another kernel because I have removed (another bad move) the other kernels and have only the aforementioned left.

I have also forgotten how to chroot to my borked install so I could possibly installed another kernel, fix the GRUB and boot with the newly installed kernel. Then reinstall 2.6.38-6 and cross my fingers.

Anyone? Old-Pollack?[/code][/code]

[Archie]

I am thrilled because this hasn´t happened in years, and proves without a doubt that PCLinuxOS is as stable as it gets. I hope I do get to learn something new with this experience.

The last kernel panic I had, I just rebooted to another kernel, reinstalled the broken kernel and FIXED! I guess I have to read some chrooting. I´ve completely forgotten that process.

I wonder when the next ISO would be released or will I be booting on a LiveUSB for a while?

[menotu]

Now, I am eager for the new ISO!

Crikey Archie!!! have ya resorted to breaking things in the hope a new ISO will magically appear.   

[Archie]

Now, I am eager for the new ISO!

Crikey Archie!!! have ya resorted to breaking things in the hope a new ISO will magically appear.   

Timely coincident, isn't it? Purported accident? I'm trying to make up my mind. Challenging quiz? I'm working on it. Shouldn't you be??     

[AS]

Now, I am eager for the new ISO! A couple of hours ago, I wanted to reboot but the shutdown hanged (left it for a bit but ...) so Power Off and Power On. Bad move. One bootup, I get a kernel panic of a different sort. I did a search on the forum, Googled a bit but none of the suggested fix seemed to work.

The error is as follow:

Code: [Select]

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)
I found suggestions such as # fsck -f /dev/sda5, # redo-mbr, # touch /forcefsck and none of these worked.

Hello Archie,

the meaning of the error message should be related to the initrd image,  but the cause should be searched.
1) boot from a live system and run fsck -f for every linux partition: /dev/sda4, /dev/sda5, /dev/sda6
2) you should know exactly what  is in each of the 3 partitions, it's not bad if you share the info with us.
3) identify exactly where is installed your system, mount the '/' partition somewhere, and please post the content of /somewhere/boot/grub/menu.lst

the above instructions, should simplify the next steps ... 

to chroot, mount your '/' filesystem somewhere, and then: chroot /somewhere /bin/bash

AS

[Old-Polack]

Archie:

What were the messages for the last 5-10 lines before the panic line you quoted. Those are the ones that give us clues.

From the liveCD, logged in as root, in a terminal;

[root@localhost ~]# mkdir /here                   <Enter>

[root@localhost ~]# mount /dev/sda5 /here                     <Enter>

[root@localhost ~]# mount -o bind /proc /here/proc           <Enter>

[root@localhost ~]# mount -o bind /sys /here/sys           <Enter>

[root@localhost ~]# chroot /here          <Enter>

To get online from within the chroot;

[root@localhost /]# service network start           <Enter>

From there you should be able to run apt-get to install the kernel or your choice. You might want to check /boot/grub/menu.lst to see if it got corrupted somehow, and also check the vmlinuz and initrd.img links in /boot, to see what they are linked to;

[root@localhost /]# ls -l /boot |grep vm               <Enter>

[root@localhost /]# ls -l /boot |grep init               <Enter>

[Archie]

Hey, thanks guys. I've installed 2.6.38.7 and I'm crossing my fingers as I reboot. Whatever happens, thanks!

[Archie]

Hmmm rebooting on 2.6.38.7 didn't go well, and I remembered why I stuck to 2.6.38.6 so I removed it and reinstalled 2.6.33.7, and will reboot shortly.

Here's what I have done so far: (It's kinda long)

@as

Code: [Select]

[archie@localhost ~]$ df
Filesystem            Size  Used Avail Use% Mounted on
/dev/root             998M   16K  998M   1% /
/dev/sda5              10G  5.6G  3.9G  60% /media/PCLinuxOS
/dev/sda6             4.9G  171M  4.4G   4% /media/WWW
/dev/sda4              95G   79G   16G  84% /media/Archie
[archie@localhost ~]$ su
Password:
[root@localhost archie]# umount -a
umount: /: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[root@localhost archie]# df
Filesystem            Size  Used Avail Use% Mounted on
/dev/root             998M   12K  998M   1% /
[root@localhost archie]# fsck -f /dev/sda5
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
PCLinuxOS: 202501/662256 files (0.2% non-contiguous), 1501805/2648709 blocks
[root@localhost archie]# fsck -f /dev/sda6
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes

Pass 4: Checking reference counts
Pass 5: Checking group summary information

WWW: ***** FILE SYSTEM WAS MODIFIED *****
WWW: 2073/320640 files (0.0% non-contiguous), 63792/1281175 blocks
[root@localhost archie]# fsck -f /dev/sda4
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes

Pass 4: Checking reference counts
Pass 5: Checking group summary information

Archie: ***** FILE SYSTEM WAS MODIFIED *****
Archie: 126886/12566528 files (8.9% non-contiguous), 21093984/25119635 blocks
[root@localhost archie]#
What next, Master Yoda?


@O-P

Code: [Select]

[archie@localhost ~]$ su
Password:
[root@localhost archie]# mkdir /home/my_vaio
[root@localhost archie]# mount /dev/sda5 /home/my_vaio/
[root@localhost archie]# ls -la /home/my_vaio/
total 260
drwxr-xr-x  23 root   root     4096 May 30 14:19 ./
drwxr-xr-x   1 root   root     4096 May 30 22:42 ../
-rw-r--r--   1 root   root        0 May 30 10:00 .autofsck
drwxr-xr-x   2 root   root     4096 May 25 17:29 bin/
drwxr-xr-x   3 root   root     4096 May 30 10:00 boot/
drwxr-xr-x   2 root   root     4096 May 20 01:37 .config/
drwxr-xr-x  24 root   root   135168 Jan 14 21:55 dev/
drwxr-xr-x 140 root   root    12288 May 30 18:01 etc/
drwxr-xr-x   2 root   root     4096 Jan 14 21:55 home/
drwxr-xr-x   2 root   root     4096 Jan 15 02:10 initrd/
drwxr-xr-x  17 root   root    12288 May 25 17:29 lib/
drwx------   2 root   root    16384 Jan 14 21:54 lost+found/
drwxrwxr-x   2 root   root     4096 May 30 18:01 media/
drwxr-xr-x   3 root   root     4096 Apr 20 16:37 mnt/
dr-xr-xr-x   2 root   root     4096 Feb 27 14:24 net/
drwxr-xr-x   9 root   root     4096 Apr 11 04:37 opt/
drwxr-xr-x   2 root   root     4096 Jan 14 21:55 proc/
drwxr-xr-x  42 root   root     4096 May 30 18:48 root/
drwxr-xr-x   2 root   root    12288 May 20 12:35 sbin/
drwxr-xr-x   2 root   root     4096 Jul 12  2010 srv/
drwxr-xr-x   2 root   root     4096 Jan 14 21:55 sys/
drwxrwxrwt  62 archie vboxsf   4096 May 30 19:08 tmp/
drwxr-xr-x  14 root   root     4096 May 18 19:42 usr/
drwxr-xr-x  20 root   root     4096 Apr 23 13:58 var/
[root@localhost archie]# mount -o bind /proc /home/my_vaio/proc
[root@localhost archie]# chroot /home/my_vaio/
[root@localhost /]# service network start
Bringing up loopback interface:                                 [  OK  ]
Configuring wireless regulatory domain                          [  OK  ]
Bringing up interface eth0:  Device eth0 does not seem to be present, delaying initialization.
                                                                [FAILED]
Bringing up interface eth1:                                     [  OK  ]
Bringing up interface wlan0:  Device wlan0 does not seem to be present, delaying initialization.
                                                                [FAILED]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
[root@localhost /]# ifconfig
eth1      Link encap:Ethernet  HWaddr 00:1A:80:1B:1D:27  
          inet addr:192.168.XXX.XXX  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21a:80ff:fe1b:1d27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6011 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5927 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5692644 (5.4 MiB)  TX bytes:650237 (634.9 KiB)
          Interrupt:16

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:240 (240.0 b)  TX bytes:240 (240.0 b)

[root@localhost /]# ls -l /boot | grep vm
lrwxrwxrwx 1 root   root        27 May 11 11:02 vmlinuz -> vmlinuz-2.6.38.6-pclos1.bfs
-rw-r--r-- 1 root   root   2330528 May 10 15:28 vmlinuz-2.6.38.6-pclos1.bfs
[root@localhost /]# ls -l /boot | grep init
-rw------- 1 root   root         0 May 30 09:59 initrd-2.6.38.6-pclos1.bfs.img
lrwxrwxrwx 1 root   root        30 May 11 11:02 initrd.img -> initrd-2.6.38.6-pclos1.bfs.img
[root@localhost /]#
Here's where I removed 2.6.38.7 BFS and installed 2.6.33.7 BFS. I mounted my local repo and ...

Code: [Select]

[root@localhost RPMS.updates]# cp -v kernel*2.6.33.7-pclos6.bfs* /home/my_vaio/media/
`kernel-2.6.33.7-pclos6.bfs-1-1pclos2010.i586.rpm' -> `/home/my_vaio/media/kernel-2.6.33.7-pclos6.bfs-1-1pclos2010.i586.rpm'
`kernel-devel-2.6.33.7-pclos6.bfs-1-1pclos2010.i586.rpm' -> `/home/my_vaio/media/kernel-devel-2.6.33.7-pclos6.bfs-1-1pclos2010.i586.rpm'
[root@localhost RPMS.updates]#
... back to the chroot environment:

Code: [Select]

[root@localhost /]# mount
/dev/sda5 on / type ext4 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw)
/dev/sda4 on /home type ext3 (rw)
/dev/sda6 on /var/www type ext4 (rw,noatime)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/sdb2 on /media/Archie type ext3 (rw,nosuid,nodev,uhelper=hal)
/dev/sdb1 on /media/PCLinuxOS type ext3 (rw,nosuid,nodev,uhelper=hal)
/dev/sdc1 on /media/PCLinuxOS type ext3 (rw,nosuid,nodev,uhelper=hal)
[root@localhost /]# cd /media
[root@localhost media]# ls
kernel-2.6.33.7-pclos6.bfs-1-1pclos2010.i586.rpm
kernel-devel-2.6.33.7-pclos6.bfs-1-1pclos2010.i586.rpm
[root@localhost media]# rpm -ivh *
error: failed to stat /dev/pts: No such file or directory
Preparing...                ########################################### [100%]
   1:kernel-2.6.33.7-pclos6.########################################### [ 50%]
INTERNAL ERROR: hd0 has no mapping in device.map (when translating (hd0,4))
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/bootloader.pm:1610
bootloader::grub2dev_and_file() called from /usr/lib/libDrakX/bootloader.pm:1619
bootloader::grub2dev() called from /usr/lib/libDrakX/bootloader.pm:245
bootloader::_may_fix_grub2dev() called from /usr/lib/libDrakX/bootloader.pm:220
bootloader::read_grub() called from /usr/lib/libDrakX/bootloader.pm:174
bootloader::read() called from /usr/sbin/bootloader-config:64
   2:kernel-devel-2.6.33.7-p########################################### [100%]
[root@localhost media]#

Note the INTERNAL ERROR. At this point, I issued grub > and went by the usual find, geometry, root and setup.

Code: [Select]

[root@localhost media]# grub
Probing devices to guess BIOS drives. This may take a long time.
[root@localhost media]# nano /boot/grub/men
menu.lst      menu.lst.old  
[root@localhost media]# nano /boot/grub/menu.lst
[root@localhost media]#
And to simplify things, I only have 1 stanza that I changed to to the correct vmlinuz and initrd.

Code: [Select]

title PCLinuxOS
kernel (hd0,4)/boot/vmlinuz-2.6.33.7-pclos6.bfs BOOT_IMAGE=PCLinuxOS root=UUID=$
initrd (hd0,4)/boot/initrd-2.6.33.7-pclos6.bfs.img

Code: [Select]

[root@localhost media]# ls -l /boot
total 8232
-rw-rw-r-- 1 root   root       440 May 20 16:14 boot.backup.sda
lrwxrwxrwx 1 root   root        26 May 30 10:00 config -> config-2.6.38.6-pclos1.bfs
-rw-r--r-- 1 root   root    112837 Oct 21  2010 config-2.6.33.7-pclos6.bfs
-rw-r--r-- 1 root   root    126423 May 10 15:28 config-2.6.38.6-pclos1.bfs
-rw-r--r-- 1 archie archie  531968 May 30 07:07 gfxmenu
drwxr-xr-x 2 root   root      4096 May 30 23:10 grub/
-rw------- 1 root   root         0 May 30 09:59 initrd-2.6.38.6-pclos1.bfs.img
lrwxrwxrwx 1 root   root        30 May 30 23:10 initrd.img -> initrd-2.6.38.7-pclos1.bfs.img
lrwxrwxrwx 1 root   root        34 Apr 24 09:11 kernel.h -> /boot/kernel.h-2.6.38.3-pclos1.bfs
-rw-r--r-- 1 root   root      1493 Apr  5 20:57 kernel.h-2.6.38.2-pclos1
-rw-r--r-- 1 root   root      1493 Apr 23 20:32 kernel.h-2.6.38.2-pclos1.bfs
-rw-r--r-- 1 root   root      1493 Apr 24 09:11 kernel.h-2.6.38.3-pclos1.bfs
-rw-r--r-- 1 root   root    254766 Nov  5  2006 message-graphic
lrwxrwxrwx 1 root   root        30 May 12 08:04 System.map -> System.map-2.6.38.6-pclos1.bfs
-rw-r--r-- 1 root   root   1410936 Oct 21  2010 System.map-2.6.33.7-pclos6.bfs
-rw-r--r-- 1 root   root   1565140 May 10 15:28 System.map-2.6.38.6-pclos1.bfs
-rw-rw-r-- 1 root   root       256 May  7 15:03 us.klt
lrwxrwxrwx 1 root   root        27 May 30 23:10 vmlinuz -> vmlinuz-2.6.38.7-pclos1.bfs
-rw-r--r-- 1 root   root   2059312 Oct 21  2010 vmlinuz-2.6.33.7-pclos6.bfs
-rw-r--r-- 1 root   root   2330528 May 10 15:28 vmlinuz-2.6.38.6-pclos1.bfs
[root@localhost media]#

Going for a reboot now. Two fingers crossed.

[Neal ManBear]

Fingers crossed for you, Archie.

[Archie]

Rebooted with 2.6.33.7 and the fingers didn't help at all. Still stuck.

chroot probably wasn't the way. Any other ideas, guys and smart gals?

[Old-Polack]

Rebooted with 2.6.33.7 and the fingers didn't help at all. Still stuck.

chroot probably wasn't the way. Any other ideas, guys and smart gals?

I'm still trying to wrap my head around why you didn't just use apt-get install kernel-2.6.33.7-pclos6.bfs-1-1pclos2010?

[Archie]

Rebooted with 2.6.33.7 and the fingers didn't help at all. Still stuck.

chroot probably wasn't the way. Any other ideas, guys and smart gals?

I'm still trying to wrap my head around why you didn't just use apt-get install kernel-2.6.33.7-pclos6.bfs-1-1pclos2010?

I guess I could try that instead of rpm -ivh. Is there any particular difference between the two type of package installation? I knew the kernel would also need the devel package so I got that as well.

Going back to chroot to try apt-get and will report back.

[Old-Polack]

Rebooted with 2.6.33.7 and the fingers didn't help at all. Still stuck.

chroot probably wasn't the way. Any other ideas, guys and smart gals?

I'm still trying to wrap my head around why you didn't just use apt-get install kernel-2.6.33.7-pclos6.bfs-1-1pclos2010?

I guess I could try that instead of rpm -ivh. Is there any particular difference between the two type of package installation? I knew the kernel would also need the devel package so I got that as well.

Going back to chroot to try apt-get and will report back.

Last time you didn't do this;

[root@localhost ~]# mount -o bind /sys /here/sys           <Enter>

I don't know if that contributed to the problem or not, but I do it, and have added kernels and done full apt-get dist-upgrade processes without a hitch, even when the upgrade included a full KDE version upgrade.

[Archie]

Thank you, Old-Pollack for your valuable advice. You allowed me, like a naughty little boy, to play a bit on the sand and eat some. But you have to put your hands on your hips and ask, "Did that taste well for you?"

Actually, I must have missed that on my copy paste. A little confession, my first chroot (where I learnt) was from the brown distro but that had been years ago.

I # rpm -e and # apt-get install, and I'm back on my HD install! I'm gonna cry (again like a naughty little boy) because I didn't play long enough on the murky sand... but can I have a badge that says, "I survived a kernel panic?" Thank you.

Another strong reason why PCLinuxOS is solid as a ROCK!

[Old-Polack]

Thank you, Old-Pollack for your valuable advice. You allowed me, like a naughty little boy, to play a bit on the sand and eat some. But you have to put your hands on your hips and ask, "Did that taste well for you?"

Actually, I must have missed that on my copy paste. A little confession, my first chroot (where I learnt) was from the brown distro but that had been years ago.

I # rpm -e and # apt-get install, and I'm back on my HD install! I'm gonna cry (again like a naughty little boy) because I didn't play long enough on the murky sand... but can I have a badge that says, "I survived a kernel panic?" Thank you.

Another strong reason why PCLinuxOS is solid as a ROCK!

Don't chew the lumps!  We have cats hereabouts.