[BusyBox] Kernel panic: VFS: unable to mount root fs on 01:01
Craig Skinner
craig at openpost.org
Fri Jun 3 11:30:11 UTC 2005
Wim Vinckier wrote:
> Are you sure you have the correct filesystem driver? You're not using
> cramfs or something like that on your initrd?
minix for the initrd which it seems to mount:
> VFS: mounted root (minix filesystem).
maybe /sbin/init can't be found/run????
# ls -lh /mnt/
total 6.0K
drwxr-xr-x 2 root root 480 May 18 21:56 bin
drwxr-xr-x 2 root root 2.0K May 29 00:08 dev
drwxr-xr-x 4 root root 128 May 20 01:58 mnt
drwxr-xr-x 2 root root 64 Jun 2 14:18 proc
drwxr-xr-x 2 root root 224 May 29 00:07 sbin
# ls -lh /mnt/sbin
total 5.0K
-rwxr-x--- 1 root root 709 May 28 23:17 init
lrwxrwxrwx 1 craski craski 14 Jun 2 14:18 pivot_root -> ../bin/busybox
# cat /mnt/sbin/init
#!/bin/sh
export PATH=/sbin:/bin
mount -nt proc proc proc
echo "$0: started, sleeping 5 secs for USB storage initialisation."
sleep 5
echo "$0: woke up, mounting /dev/sda1"
mount -t auto -o ro /dev/sda1 /mnt/device
echo "$0: extracting root file system..."
zcat /mnt/device/invrcrg/root.gz > /dev/ram0
echo "$0: unmounting /dev/sda1..."
umount /mnt/device
echo "$0: mounting /dev/ram0"
mount /dev/ram0 /mnt/root
cd /mnt/root
echo "$0: pivoting into root file system..."
pivot_root . mnt
chroot . sbin/init <dev/console >dev/console 2>&1
#pivot_root failed!
echo "Bummer, unable to pivot root from flash to ram"
# ls -lh /mnt/bin
total 79K
lrwxrwxrwx 1 craski craski 17 Jun 2 14:18 [ -> ../../bin/busybox
-rwxr-xr-x 1 craski craski 66K Jun 1 20:55 busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 echo -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 false -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 gunzip -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 lash -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 mount -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 sh -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 sleep -> busybox
lrwxrwxrwx 1 craski craski 17 Jun 2 14:18 test -> ../../bin/busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 true -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 umount -> busybox
lrwxrwxrwx 1 craski craski 7 Jun 2 14:18 zcat -> busybox
camira:/home/craski-shell_86# ls -lh /mnt/dev
total 1.0K
crw------- 1 root tty 5, 1 May 18 21:10 console
brw-rw---- 1 root disk 3, 0 May 12 12:15 hda
brw-rw---- 1 root disk 3, 1 May 12 12:15 hda1
brw-rw---- 1 root disk 3, 2 May 12 12:15 hda2
brw-rw---- 1 root disk 3, 3 May 12 12:15 hda3
brw-rw---- 1 root disk 3, 4 May 12 12:15 hda4
brw-rw---- 1 root disk 3, 64 May 12 12:15 hdb
brw-rw---- 1 root disk 3, 65 May 12 12:15 hdb1
brw-rw---- 1 root disk 3, 66 May 12 12:15 hdb2
brw-rw---- 1 root disk 3, 67 May 12 12:15 hdb3
brw-rw---- 1 root disk 3, 68 May 12 12:15 hdb4
brw-rw---- 1 root disk 22, 0 May 12 12:15 hdc
brw-rw---- 1 root disk 22, 1 May 12 12:15 hdc1
brw-rw---- 1 root disk 22, 2 May 12 12:15 hdc2
brw-rw---- 1 root disk 22, 3 May 12 12:15 hdc3
brw-rw---- 1 root disk 22, 4 May 12 12:15 hdc4
brw-rw---- 1 root disk 22, 64 May 12 12:15 hdd
brw-rw---- 1 root disk 22, 65 May 12 12:15 hdd1
brw-rw---- 1 root disk 22, 66 May 12 12:15 hdd2
brw-rw---- 1 root disk 22, 67 May 12 12:15 hdd3
brw-rw---- 1 root disk 22, 68 May 12 12:15 hdd4
crw-rw-rw- 1 root root 1, 3 May 12 12:15 null
lrwxrwxrwx 1 root root 4 Jun 2 14:18 ram -> ram1
brw-rw---- 1 root disk 1, 0 May 12 12:15 ram0
brw-rw---- 1 root disk 1, 1 May 12 12:15 ram1
brw-rw---- 1 root disk 1, 2 May 12 12:15 ram2
brw-rw---- 1 root disk 1, 3 May 12 12:15 ram3
brw-rw---- 1 root disk 1, 4 May 12 12:15 ram4
brw-rw---- 1 root disk 1, 5 May 12 12:15 ram5
brw-rw---- 1 root disk 1, 6 May 12 12:15 ram6
brw-rw---- 1 root disk 1, 7 May 12 12:15 ram7
brw-rw---- 1 root disk 1, 8 May 12 12:15 ram8
brw-rw---- 1 root disk 1, 9 May 12 12:15 ram9
brw-rw---- 1 root disk 8, 0 May 12 12:15 sda
brw-rw---- 1 root disk 8, 1 May 12 12:15 sda1
brw-rw---- 1 root disk 8, 2 May 12 12:15 sda2
brw-rw---- 1 root disk 8, 3 May 12 12:15 sda3
brw-rw---- 1 root disk 8, 4 May 12 12:15 sda4
brw-rw---- 1 root disk 8, 16 May 12 12:15 sdb
brw-rw---- 1 root disk 8, 17 May 12 12:15 sdb1
brw-rw---- 1 root disk 8, 18 May 12 12:15 sdb2
brw-rw---- 1 root disk 8, 19 May 12 12:15 sdb3
brw-rw---- 1 root disk 8, 20 May 12 12:15 sdb4
brw-rw---- 1 root disk 8, 32 May 12 12:15 sdc
brw-rw---- 1 root disk 8, 33 May 12 12:15 sdc1
brw-rw---- 1 root disk 8, 34 May 12 12:15 sdc2
brw-rw---- 1 root disk 8, 35 May 12 12:15 sdc3
brw-rw---- 1 root disk 8, 36 May 12 12:15 sdc4
brw-rw---- 1 root disk 8, 48 May 12 12:15 sdd
brw-rw---- 1 root disk 8, 49 May 12 12:15 sdd1
brw-rw---- 1 root disk 8, 50 May 12 12:15 sdd2
brw-rw---- 1 root disk 8, 51 May 12 12:15 sdd3
brw-rw---- 1 root disk 8, 52 May 12 12:15 sdd4
crw-rw---- 1 root dialout 4, 64 May 12 12:16 ttyS0
crw-rw---- 1 root dialout 4, 65 May 12 12:16 ttyS1
crw-rw---- 1 root dialout 4, 66 May 12 12:16 ttyS2
crw-rw---- 1 root dialout 4, 67 May 12 12:16 ttyS3
crw-rw---- 1 root dialout 4, 68 May 12 12:16 ttyS4
crw-rw-rw- 1 root root 1, 5 May 12 12:15 zero
> wim.
>
>>>
>>>RAMDISK: Compressed image found at block 0
>>>Freeing initrd memory: 41k freed
>>>VFS: mounted root (minix filesystem).
>>>FAT: bogus logical sector size 25708
>>>UMSDOS: msdos_read_super failed, mount aborted.
>>>FAT: bogus logical sector size 25708
>>>FAT: bogus logical sector size 25708
>>>Kernel panic: VFS: unable to mount root fs on 01:01
>>
>>My experiance has been that initrd often ends up in /dev/ram0 (aka 100
>>or 01:00). Your output seems like it is looking for it in /dev/ram1.
>>
>>David Daney.
Nope, it is specified as ram1 in the syslinux.cfg file (I want to use
ram0 for a piviot_root from a USB pen drive):
$ cat /mnt/floppy/syslinux.cfg
serial 0 57600
display syslinux.txt
default linux
label linux
kernel linux
append root=/dev/ram1 initrd=initrd.gz console=ttyS0,57600n
Is this legal/doable/ok?
Craig Skinner.
More information about the busybox
mailing list