Skip to contentSkip to conversation

Booting from USB with initrd

DISCUSSION gabriel 4 participants 4 messages Apr 15, 2005 – Apr 16, 2005

lore
Share & tools
lore

gabriel

author
#0 lore raw

Hi Im trying to boot an encrypted file system using an initrd on a USB. I use syslinux for the actual boot process as I couldnt get Grub to boot of it for some reason. This is the .cfg

default vmlinuz
timeout 100
prompt 1
label linux
kernel vmlinuz
append initrd=/initrd.gz root=/dev/ram0 rootfstype=minix init=/linuxrc

As far as I can tell this should load the initrd but that never happens. Everything seems to boot fine. Syslinux loads the kernel and I get to the point where initrd should be mounted only to get this error.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

followed by the USB information and stop.
<5> Vendor SWISSBIT Mode: Victorinox 2.0 Rev 2.00 Type Direct-Access ANSI SCSI Revision: 02 SCSI device sdb: 1022720 512 byte hdwr sectors (524mb)
sdb: Write Protect is off
sdb: asuming driver cache: write-through

I have support for minix, vfat, ext2 and ext3 in the kernel. I have recompiled the kernel
like 20 times to test different things. So what Im thinking is that the USB device doesn't
get realized before syslinux tries to load it?

Oh I do have the ramdisk in the kernel and everything.

#1 lore raw
Quoted 10 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

gabriel <[email protected]> writes:

Hi Im trying to boot an encrypted file system using an initrd on a USB. I use syslinux for the actual boot process as I couldnt get Grub to boot of it for some reason. This is the .cfg

...
...
...

Quoted 7 lines
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

followed by the USB information and stop.
<5> Vendor SWISSBIT Mode: Victorinox 2.0 Rev 2.00 Type Direct-Access ANSI SCSI Revision: 02 SCSI device sdb: 1022720 512 byte hdwr sectors (524mb)
sdb: Write Protect is off
sdb: asuming driver cache: write-through

If this is the model of your disk, the USB device has been detected properly, or at least it shows up. Are the contents encrypted you said? Can you post a more complete log?

Signature · 1 line
Inaky
#2 lore raw
In reply to gabriel
Quoted 1 line · gabriel
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

Hi Gabriel!

It looks like initrd.gz could not be mounted. The unknown-block(1,0) is /dev/ram0 (and has normally initrd attached to it) as specified on kernel command line.

Do you use an initrd or an initramfs? Is the kernel compiled with initrd support? Is the ramdisk size big enough to hold your initrd?

regards

#3 lore raw
In reply to gabriel
Quoted 4 lines · gabriel

Hi Im trying to boot an encrypted file system using an initrd on a USB. I use syslinux for the actual boot process as I couldnt get Grub to boot of it for some reason. This is the .cfg

append initrd=/initrd.gz root=/dev/ram0 rootfstype=minix init=/linuxrc

I don't think syslinux digs the "/" in the initrd filename. Did you try it with initrd=initrd.gz?

Eric