1

Topic: Unable to mount root

I have a TFTP server set up to serve GParted to a VirtualBox client for testing, but when I boot the guest, it dowloads the TFTP image, boots, and stops with:

List of all partitions:
No filesystems could mount root, tried:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(9,1)

My pxelinux.cfg says:

label GParted Live
MENU LABEL GParted Live
kernel linux
append initrd=initrd1.img boot=live union=aufs noswap noprompt vga=788 fetch=http://<serverip>/filesystem.squashfs

My guess is something isn't going right with the fetch bit, but I can't scroll back in the VM output, and it goes too fast to see what's going on. The TFTP and HTTP server are on the same machine, and I've confirmed doing an HTTP get on the squashfs file works. Anyone have a suggestion what's wrong? Thanks!

2

Re: Unable to mount root

Hello pratfall,

My pxelinux.cfg says:

label GParted Live
MENU LABEL GParted Live
kernel linux
append initrd=initrd1.img boot=live union=aufs noswap noprompt vga=788 fetch=http://<serverip>/filesystem.squashfs

AFAIK, kernel should be "vmlinuz1", not "linux".

Regards
cmdr

3

Re: Unable to mount root

I got pxelinux.0 from Debian Etch, and it expects the kernel to be in a file called linux, not vmlinuz1. If I change the line in pxelinux.cfg/default, nothing changes. If I rename linux to vmlinuz1, I get:

"Could not find kernel image: linux"

Is there gparted-specific pxelinux.0 I should use? Nothing was supplied in the file I downloaded.

Thanks!

4

Re: Unable to mount root

Hello pratfall,

where are files "linux", "vmlinuz1", "initrd1.img" stored ?

You might need a (relative) path to kernel and filesystem image ...

... or you try this :

If I rename linux to vmlinuz1, I get: ...

The other way round : rename "linux" to "old_linux", copy "vmlinuz1"  and probably "initrd1.img" to the location where "(old_)linux" resides and rename "vmlinuz1" to "linux". Then try again.

http://www.debian-administration.org/articles/478 wrote:

The files which are used for booting are stored beneath the TFTP root directory and thus accessible to booting clients.

Regards
cmdr