Kernel panic: VFS: Unable to mount root fs on 01:00

Using applications, configuring, problems
Post Reply
Message
Author
User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

Kernel panic: VFS: Unable to mount root fs on 01:00

#1 Post by rarsa »

I was a virgin on the 'asking' side of the forum until now. This must have an easy explanation.

I'm trying to put additional files in a remastered puppy image.

I'm doing some experiments here, so I'd like to understand what's happening. I'd like to understand the error. Also welcome are suggestions on how to add files to the puppy iso. outside the compresed file systems.

I am getting a kernel error with a remastered Puppy. Here is what I did (including details that don't appear to be relevant) I'm bolding what I did out of the ordinary:

- I'm working on a laptop that only has NTFS
- I unzipped pup001.zip, renamed to pupdata and resized the file to 1.25 GB
- Booted the pupy 1.0.5 chubby cd with option 3
- Did not select a partition. Working 100% in RAM.

- Mounted the pupdata file to /root/data
- Started the PCCC script
- Selected /root/data as my working partition
- Accepted all the defaults. I did not modify the package list.
- When it asks to modify the isolinux.cfg, I copied the usr_devx.sfs and pup001.zip to /root/data/puppy-unleashed/isolinux-builds
- I continued without modifying isolinux.cfg
- The script created the ISO
- I burned the iso in a different computer using K3B with verification so I know that it's burned correctly.
- I boot on the laptop (both by using option 1 and option 3) and I get the following error (here are the last few lines)

Code: Select all

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 0k freed
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount abourted
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
Kernel panic: VFS: Unable to mount root fs on 01:00
Any idea?

Guest

#2 Post by Guest »

You have to pass the kernel parameter of ramdisk_size=your ramdisk size

I think the Puppy kernel is compiled with an initial ramdisk size of 11280K or there abouts. By the kernel messages your ramdisk size is larger.

When I made my custom iso I bumped the initrd up to 16MB and had to provide an argument of ramdisk_size=16384 for correct booting.

User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#3 Post by rarsa »

Now it's clear, Thank you.

The PCCC script sets the parameters for the standard 1.0.5 not for Chubby. I cannot test it right now, but I will as soon as I get home.

Post Reply