Re: Kernel panic on upgrade from 2.4.18 to 2.6.17-2
John wrote:
> Hi list,
>
> After an apt-get install linux-image 2.6.17-2 I get the following:
>
> "VFS Cannot open root device "hda2" or unknown-block (0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing VFS Unable to mount root fs on
> unknown-block (0,0)
> <0> Press Stop-A (L1-A) to return to boot prom."
>
> The silo.conf is:
>
> partition=1
> root=/dev/hda2
> timeout=100
> image=1/vmlinuz
> label=linux
> read-only
>
> As the partitioning hasn't changed I'm at a loss to understand why
> this error is occurring especially as when I change the vmlinuz link
> back to the old kernel everything 'just works'.
>
> Boot prom acknowledges the kernel as 2.6.17-2 on the way through.
>
> I've copied the /, /boot, df and fstab output below in case its
> relevant.
>
> TIA
>
> John
>
> ~# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda2 36G 2.0G 32G 6% /
> /dev/hda1 92M 9.5M 77M 11% /boot
>
> ~# cat /etc/fstab
> # /etc/fstab: static file system information.
> #
> # <file system> <mount point> <type> <options>
> <dump> <pass>
> /dev/hda2 / ext3
> defaults,errors=remount-ro 0 1
> /dev/hda4 none swap sw
> 0 0
> proc /proc proc defaults
> 0 0
> /dev/fd0 /floppy auto user,noauto
> 0 0
> /dev/cdrom /cdrom iso9660 ro,user,noauto
> 0 0
> /dev/hda1 /boot ext3 defaults
> 0 2
>
> /# ls -la
> total 873
> drwxr-xr-x 22 root root 4096 Dec 6 12:17 .
> drwxr-xr-x 22 root root 4096 Dec 6 12:17 ..
> -rw------- 1 root root 5 Dec 6 12:15 .bash_history
> drwxr-xr-x 2 root root 4096 Nov 21 20:28 bin
> drwxr-xr-x 3 root root 1024 Dec 6 12:13 boot
> drwxr-xr-x 2 root root 4096 Apr 15 2004 cdrom
> -rw------- 1 root root 2629632 Dec 6 12:18 core
> -rw------- 1 root root 2629632 Dec 6 11:53 core.old
> drwxr-xr-x 6 root root 20480 Dec 6 12:17 dev
> drwxr-xr-x 74 root root 4096 Dec 6 12:17 etc
> drwxr-xr-x 2 root root 4096 Apr 15 2004 floppy
> drwxrwsr-x 4 root staff 4096 Aug 9 11:46 home
> drwxr-xr-x 2 root root 4096 Apr 15 2004 initrd
> lrwxrwxrwx 1 root root 32 Dec 6 11:59 initrd.img ->
> boot/initrd.img-2.6.17-2-sparc64
> drwxr-xr-x 11 root root 4096 Nov 19 16:28 lib
> drwxr-xr-x 2 root root 4096 Nov 15 21:44 lib64
> drwx------ 2 root root 16384 Dec 5 16:10 lost+found
> drwxr-xr-x 2 root root 4096 Feb 9 2002 mnt
> drwxr-xr-x 2 root root 4096 Apr 15 2004 opt
> dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
> drwxr-xr-x 6 root root 4096 Nov 30 15:10 root
> drwxr-xr-x 2 root root 4096 Nov 21 20:28 sbin
> drwxr-xr-x 2 root root 4096 May 11 2005 sys
> drwxrwxrwt 5 root root 4096 Dec 6 12:17 tmp
> drwxr-xr-x 16 root root 4096 Feb 9 2002 usr
> drwxr-xr-x 15 root root 4096 Jul 25 2005 var
> lrwxrwxrwx 1 root root 25 Dec 5 16:10 vmlinuz -> boot/vmlinuz-
> 2.4.18-sun4u
> lrwxrwxrwx 1 root root 29 Dec 6 11:59 vmlinuz-old ->
> boot/vmlinuz-2.6.17-2-sparc64
>
> /boot# ls -la
> total 5560
> drwxr-xr-x 3 root root 1024 Dec 6 12:13 .
> drwxr-xr-x 22 root root 4096 Dec 6 12:17 ..
> -rw-r--r-- 1 root root 837500 Sep 14 07:35
> System.map-2.6.17-2-sparc64
> lrwxrwxrwx 1 root root 1 Dec 5 17:38 boot -> .
> -rw-r--r-- 1 root root 40131 Sep 14 01:40 config-2.6.17-2-sparc64
> lrwxrwxrwx 1 root root 1 Dec 5 17:38 etc -> .
> -rw-r--r-- 1 root root 1024 Oct 28 13:49 fd.b
> -rw-r--r-- 1 root root 512 Oct 28 13:49 first.b
> -rw-r--r-- 1 root root 1024 Oct 28 13:49 generic.b
> -rw-r--r-- 1 root root 692 Oct 28 13:49 ieee32.b
> -rw-r--r-- 1 root root 1795763 Dec 6 11:59
> initrd.img-2.6.17-2-sparc64
> -rw-r--r-- 1 root root 6936 Oct 28 13:49 isofs.b
> drwx------ 2 root root 12288 Dec 5 16:10 lost+found
> -rw-r--r-- 1 root root 7680 Dec 5 16:14 old.b
> -rw-r--r-- 1 root root 63488 Dec 6 12:15 second.b
> -rw-r--r-- 1 root root 77 Dec 5 17:38 silo.conf
> -rw-r--r-- 1 root root 60871 Oct 28 13:49 silotftp.b
> -rw-r--r-- 1 root root 512 Oct 28 13:49 ultra.b
> lrwxrwxrwx 1 root root 20 Dec 5 16:15 vmlinuz ->
> vmlinuz-2.4.18-sun4u
> -rw-r--r-- 1 root root 1379575 Dec 5 16:10 vmlinuz-2.4.18-sun4u
> -rw-r--r-- 1 root root 1443003 Sep 14 07:35 vmlinuz-2.6.17-2-sparc64
> lrwxrwxrwx 1 root root 24 Dec 6 12:01 vmlinuz-old ->
> vmlinuz-2.6.17-2-sparc64
John,
I had the same problem last weekend with a Linux-PC. My mistake: I
compiled the filesystem as module
( <M> instead of <*>). After correcting this mistake the OS booted as
expected.
HTH
Friedhelm
Reply to: