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.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx



Relevant Pages

  • Re: Mini-ITX, LinuxBios and DOC
    ... >program a bootloader which initialises the motherboards regsiters, loads the ... >kernel and then can load an initrd from the doc. ... Besides the quicker boot, it doesn't buy much for your application, does it? ... >the root file system. ...
    (comp.os.linux.embedded)
  • Re: waiting for root file system
    ... It was a sata disk in an external enclosure connected with USB, now it is in the same enclosure but conneceted with SATA cable. ... After 'waiting for root file system' and the 5 minute wait, initrd drops ...
    (Debian-User)
  • Re: Unable to boot with LVM mount on USB drive (Fedora 10)
    ... BTW for those that may have influence, would it be unreasonable to expect the default initrd to include usb-storage? ... The current approach is to build initramfs images that are tailored to a specific system - only the modules actually required to get the root file system going are included by default. ...
    (Fedora)
  • Re: Mini-ITX, LinuxBios and DOC
    ... program a bootloader which initialises the motherboards regsiters, loads the ... kernel and then can load an initrd from the doc. ... I will use a moduleless kernel but i wanted to have my application in the ... the root file system. ...
    (comp.os.linux.embedded)
  • Re: RFC: root mount enhancement (round 2)
    ... new devices to appear that contain the root file system before giving ... the next mount directrives. ... medium and software images are ISO images stored in it. ...
    (freebsd-arch)