[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re: init problems



Emanoil Kotsev wrote:
Maria McKinley wrote:

I have a machine that I am attempting to boot over the network. I have
compiled a kernel for it, Debian Lenny Linux version 2.6.26, with nfs
file system and root file system support. For a complete rundown on how
I have created the setup, please see:

http://www.shadlen.org/~maria/pmwiki/Work/Gpxe


had another look and saw you have the no root squash option

I don't know anything about wraplinux. My server is on sarge and I booted
few clients with no problem, but I used custom initrd (and kernel).

I also don't understand (created image, and stuck it on a floppy). Did you
use the floppy to flash your network card's bios or to boot from?

I would just check the initrd file

cd /tmp
mkdir test
cd test
zcat /boot/<INITRD> | cpio -i -H newc

... do whatever you need to mount rw ...

find . ! -name "*~" | cpio -H newc --create | gzip -9 > /boot/<INITRD>

watch out - this will overwrite your initrd, so make backup

regards

hi there,

Thanks for the response. I am putting a gPXE image on a floppy, and booting from the floppy. From there it downloads the kernel with initrd, runs all of the way through the initrd file, and all of the way through /sbin/init as well, actually (but there are errors during init). Initrd is able to mount the root file system as read-only, which is what is suppose to happen. The problem is that init is not able to start statd, so cannot remount the root file directory according to fstab as a read-write mount. I thought at first that statd wasn't starting because portmap wasn't starting, but I downgraded portmap to 5-26 from etch, and now portmap will start, but statd still doesn't start. When I try to start statd from the command line, I get:

/var/run/rpc.statd.pid failed: Read-only file system.

Which seems really bizarre, as I need statd in order to mount the root file system as read-write. So if anyone knows a way to start statd temporarily without a pid until the root file system mounts read-write, that would probably solve my problem.


Reply to: