Hello,
I've been running for some time now a setup where I have a tftp/dhcp/nfs-server and a diskless mediaplayer (stock Intel setup) on a local network. The mediaplayer has done a PXE-boot from the server and everything has been smooth. Both the server as well as the mediaplayer have been running FC5 with the 2.6.17-1.2187 kernel. The tftpboot-stuff has been created/managed with the system-config-netboot program.
However the more recent kernels have had a number of problems, some still unsolved.
For starters, the newer kernels require that I define ramdisk_blocksize=1024 as an additional boot-parameter.
At the moment I can get the FC5 mediabox to boot up with the new kernel, but it now is unable to mount a number of directories, such as /var/lock and /var/run, as readwrite. This of course wreaks havoc on the whole functionality. The said directories are mentioned in the snapshot/files-file, so there is something else broken in the whole setup.
I also set up a basic FC6-installation to be booted from the server, but using that installation to boot the mediaplayer fails at a separate error. It complains that the /tftpboot/boot/mediaplayerfc6/root is not mountable, although I can NFS-mount this fine from another workstation in the same local network. Creating the FC6 setup on the server with the system-config-netboot does not give any errors.
Neither case gives off any errors in the server logs (messages/dmesg/secure).
I'm a bit stumped at this point so I would really appreciate if anyone could give a hint where to look for next or whether I have missed something obvious.
Poltsi
On Sat, 2007-01-20 at 20:50 +0200, Paul-Erik Törrönen wrote:
I also set up a basic FC6-installation to be booted from the server, but using that installation to boot the mediaplayer fails at a separate error. It complains that the /tftpboot/boot/mediaplayerfc6/root is not mountable, although I can NFS-mount this fine from another workstation in the same local network. Creating the FC6 setup on the server with the system-config-netboot does not give any errors.
Neither case gives off any errors in the server logs (messages/dmesg/secure).
I'm a bit stumped at this point so I would really appreciate if anyone could give a hint where to look for next or whether I have missed something obvious.
Here is the specific error for the FC6 boot (manually written from screen):
Mounting root filesystem: /tftpboot/boot/mediaboxfc6/root from: 192.168.1.1 mount: wrong fs type, bad option, bad superblock on 192.168.1.1:/tftpboot/boot/mediaboxfc6/root, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so
ERROR! Failed to mount the root directory via NFS! Possible reasons include...
Kernel panic - not syncing: Attempted to kill init!
I've googled for the various lines of this error message, but have not found anything in relation to PXE/netboot which would be of any use.
Looking with the tcpdump (with the options '-X -v -s 1500'), I can't see anything out of the ordinary, the address and path of the mount is given correctly (as in the error above).
Out of desparation I also converted the whole NFS share on the server to NFSv4 but that gave the same results as above.
Poltsi
On 1/21/07, Paul-Erik Törrönen poltsi@777-team.org wrote:
On Sat, 2007-01-20 at 20:50 +0200, Paul-Erik Törrönen wrote:
I also set up a basic FC6-installation to be booted from the server, but using that installation to boot the mediaplayer fails at a separate error. It complains that the /tftpboot/boot/mediaplayerfc6/root is not mountable, although I can NFS-mount this fine from another workstation in the same local network. Creating the FC6 setup on the server with the system-config-netboot does not give any errors.
Neither case gives off any errors in the server logs (messages/dmesg/secure).
I'm a bit stumped at this point so I would really appreciate if anyone could give a hint where to look for next or whether I have missed something obvious.
Here is the specific error for the FC6 boot (manually written from screen):
Mounting root filesystem: /tftpboot/boot/mediaboxfc6/root from: 192.168.1.1 mount: wrong fs type, bad option, bad superblock on 192.168.1.1:/tftpboot/boot/mediaboxfc6/root, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so
ERROR! Failed to mount the root directory via NFS! Possible reasons include...
Kernel panic - not syncing: Attempted to kill init!
I've googled for the various lines of this error message, but have not found anything in relation to PXE/netboot which would be of any use.
Looking with the tcpdump (with the options '-X -v -s 1500'), I can't see anything out of the ordinary, the address and path of the mount is given correctly (as in the error above).
I'm getting the same error, with a diskless install of fc6 setup by system-config-netboot. But I don't see anything in the server log indicating that a mount request is being made (or in the tcpdump output), so I suspect there's a problem with the nfs client. When I have more time I'm going to unpack the initrd.img and switch debugging on in disklessrc to try and work out whats going wrong.
Chris
I bumped into the same problem with FC6, mount fails for no obvious reason. Has anyone investigated this further?
I haven't been able to find any other info about this problem.
- Timo
I solved this. You need to unpack initrd.img and add the file mount.nfs to it. Then it works okay.
rcuban2006 wrote:
I solved this. You need to unpack initrd.img and add the file mount.nfs to it. Then it works okay.
Alternatively, if you have or can make a vfat partition, put the .iso file there and the update works fine. The problem has been resolved and is fixed for F7T2 BTW
Scott
Kind of a NUB here. How exactly do you unpack the initrd.img? Right now I'm getting the message;
Mount, bad fs type, bad option, bad superblock on 192.168.1.110:/client_image/root, missing codepage or other error In some cases useful ifo is found in syslog - try dmesg | tail or so
ERROR. Failed to mount the root directory via NFS! Possible reasons include (.yadda yadda yadda)
Anyway.. the directory is available via NFS, and the above suggestion looks like it might resolve my problem, but how do I implement it? The initrd.img APPEARS to be a GZ file and I can unpack it, I get a 19MB binary file... help!
OK, I mounted the initrd.img and added mount.nfs to it. Now I get yet another error. I googled for it and found only 5 hits, none of them relevant..
mount: mount to NFS server '192.168.1.110' failed: RPC Error: Program not registered.
Anyone shed any light on this one?? Is it because of how the mount.nfs was added to the initrd.img? I just dragged it to the mounted directory and then unmounted it. Should have paceded it into the unzipped image. I then re gsipped the file and dropped it into the subdir under tftpboot from whence it came.
Got it all workng. FC6 diskless boot from CentOS 4.4.
On Mon, 2007-03-19 at 16:02 +0800, Ed Greshko wrote:
SABBAS wrote:
Got it all workng. FC6 diskless boot from CentOS 4.4.
Not bad. You seem to have got it all working and sent 3 mails in less than a minute. I think you've managed a new record. :-)
What? You haven't figured it out yet? It's a corollary to Murphy's Law. You will figure out the solution to the problem approximately 5 seconds after sending your bitch message about how it's broken. So you send in a message knowing that the sooner you bitch, the sooner it will dawn on you. Works for me 9 falls out of 10.
Another corollary is that you will respond up to someone else's bitch message with a metoo and it will cross paths in the ether with the solution to both of your messages (just happened to me on devel).
:-)
Mike
-
"Paul-Erik Törrönen" -
Chris Rouch -
Ed Greshko -
Michael H. Warfield -
Oldman -
potat0