Gistolero
n00b
Joined: 05 Apr 2004
Posts: 2
|
 Posted: Sun May 23, 2004 10:23 am Post subject: Problems with initrd and ramdisk system |
 |
|
Hi,
I try to install a ramdisk system, without harddisks and without nfs mounts. But there are some problems:
- My client loads kernel and rootfs.gz from a dhcp/tftp-server.
- The kernel starts and extracts the rootfs.gz to /dev/rd/0.
- With /linuxrc I'm able to start a shell inside the ramdisk. "mount" shows that /proc and /dev are mounted and / is /dev/rd/0. All is fine!
Ok, now I want to start services and getty's with init. I type "exit" or "exec /sbin/init" and the error is:
| Code: |
VFS: Cannot open root device "rd/0" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
|
But inside the shell from /linuxrc I'm able to mount /dev/rd/0 at e.g. /mnt/.
man initrd says:
| Code: |
...
4. If the indicated normal root file system is also the initial root file-system (e.g. /dev/ram0 ) then the kernel skips to the last step for the usual boot sequence.
...
|
Thats what I want to do! My ramdisk is loaded and /sbin/init have to skip the mount root filesystem process. I don't know why init always tries to mount a new root filesystem.
Is there anybody out there, who can explain the initrd mechanism from kernel 2.6? I have read the http://lkml.org/lkml/2003/3/13/12 thread, but this procedure doesn't work for me.
system information:
| Code: |
master /tmp # cat /tftpboot/pxelinux.cfg/C0A801
DEFAULT bzImage_2.6.5-hardened-r3_20040519_124818
APPEND root=/dev/rd/0 init=/linuxrc initrd=rootfs.gz rw ip=dhcp
|
Thanks for your help,
Simon |
|
Kernel & Hardware
