Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
Just a comment: Today I wanted to install a new host (the first since one or two months), however I ended up with the same dracut error... It seems that now nfs is needed at the begin of the NFSROOT entry in nfsroot.conf, to get dracut to recognize the fai-server NFSROOT=*nfs:*phkup26:/srv/fai/nfsroot (instead of NFSROOT=phkup26:/srv/fai/nfsroot ) After this small change it works again without problems, but I wonder now: Was there a change in fai-chboot? (Did former versions eventually add the nfs: automatically to the nfsroot when creating the tftp-file?) Or maybe was there a change in nfs or dracut? Regards René On 04/03/2014 10:57 AM, ARNAUDOV Krasimir wrote: Ok I solved the problem. It was not the Network, FAI did not know where the NFS server is. I have made the following changes so that FAI works: - in PXE config file root=nfs:fai-server:/srv/fai/nfsroot (default is root=/srv/fai/nfsroot) - /srv/fai/nfsroot/etc/fai/fai.conf was not copied from /etc/fai/fai.conf and I configured it with the path to the config space Now everything works:) Regards Krasimir Arnaudov -Original Message- From: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] On Behalf Of ARNAUDOV Krasimir Sent: Donnerstag, 03. April 2014 08:37 To: Thomas Lange; FAI Mailing Subject: RE: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot Meanwhile I have updated - FAI 4.1.1 kernel /linux-image-3.13-0.bpo.1-amd64 I have deleted nfsroot and I have started fai-setup again. Now there is no problem with NFS... but something with network configuration/dhcp is not working. Starting dhcp for interface eth0 dhcp: PREINIT eth0 up dhcp: BOND setting eth0 No carrier detected no LINK FS-Cache: loaded FS-Cache: Netfs 'nfs' registered for caching Key typ dns_resolver registered NFS: Registering the the id_resolver key tape Key type id_resolver registered Key type id_legacy registered Random: nonblocking pool is initialized And nothing happens There is link - earlier message: e1000e: eth0 NIC Link is up 100 Mbps Full Duplex, Flow control None Regards Krasimir Arnaudov
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
On Fri, 25 Apr 2014 09:13:35 +0200, René Bleisch accou...@climate.unibe.ch said: It seems that now nfs is needed at the begin of the NFSROOT entry in nfsroot.conf, to get dracut to recognize the fai-server NFSROOT=nfs:phkup26:/srv/fai/nfsroot(instead of NFSROOT=phkup26:/srv/fai/nfsroot ) Which FAI and dracut version are you using? I have this in my nfsroot.conf: NFSROOT=/srv/fai/nfsroot I'm sure, I never had a host name in this line. IIRC NFSROOT should not be used for specifying the nfsroot kernel command line parameter. man dracut.cmdline says: .. root=/dev/nfs nfsroot= is deprecated. Now you should use root=. I have root=123.45.67.8:/srv/fai/nfsroot in my pxelinux.cfg files. Was there a change in fai-chboot? (Did former versions eventually add the nfs: automatically to the nfsroot when creating the tftp-file?) Yes, there was a change in FAI 4.1. -- regards Thomas
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
Versions:
fai 4.1
dracut ? (where can I find this out?)
I think I remember the problem now:
Last year, when I set up the new wheezy-FAI-server, I first set
NFSROOT=/srv/fai/nfsroot in nfsroot.conf (as in the
make_fai_nfs_root.conf file in my old fai 3.4.7 server) .
However, tftp/dracut then tried to mount the nfsroot from the
dhcp-server :-( (not on the same machine...*)
I just tried a test installation with NFSROOT=/srv/fai/nfsroot and
indeed the installation stops with
mount.nfs: access denied by server while mounting
130.92.143.225:/srv/fai/nfsroot
Indeed, 130.92.143.225 is the dhcp-server machine, and in the syslog of
this machine I find
Apr 25 13:10:57 kuppacific rpc.mountd[1658]: refused mount request from
kuphalmahera.unibe.ch for /srv/fai/nfsroot (/): no export entry
(kuphalmahera.unibe.ch is the host to install)
If I put NFSROOT=phkup26:/srv/fai/nfsroot it worked until ~one month
ago, but now I had to put
NFSROOT=nfs:phkup26:/srv/fai/nfsroot into nfsroot.conf to get it to
work again.
PS: If I'm right, fai-chboot just takes the NFSROOT variable from
nfsroot.conf to create the nfsroot kernel command line parameter entry
(I invoke it with /usr/sbin/fai-chboot -IFv -u
nfs://phkup26/srv/fai/config hostname)
Regards
René
* Since years I have a dhcp-server for our network on a special machine.
In the dhcpd.conf I just declared a special group for the FAI-hosts:
---
group {
server-name kuppacific.unibe.ch;
next-server phkup26;
use-host-decl-names on;
filename fai/pxelinux.0;
...
This worked for years with the old FAI-server
On 04/25/2014 10:57 AM, Thomas Lange wrote:
On Fri, 25 Apr 2014 09:13:35 +0200, René Bleisch accou...@climate.unibe.ch
said:
It seems that now nfs is needed at the begin of the NFSROOT entry in
nfsroot.conf, to get dracut to recognize the fai-server
NFSROOT=nfs:phkup26:/srv/fai/nfsroot(instead of
NFSROOT=phkup26:/srv/fai/nfsroot )
Which FAI and dracut version are you using?
I have this in my nfsroot.conf:
NFSROOT=/srv/fai/nfsroot
I'm sure, I never had a host name in this line.
IIRC NFSROOT should not be used for specifying the nfsroot kernel
command line parameter. man dracut.cmdline says: .. root=/dev/nfs
nfsroot= is deprecated. Now you should use root=.
I have root=123.45.67.8:/srv/fai/nfsroot in my pxelinux.cfg files.
Was there a change in fai-chboot? (Did former versions eventually add the
nfs: automatically to the nfsroot when creating the tftp-file?)
Yes, there was a change in FAI 4.1.
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
On Fri, 25 Apr 2014 13:38:47 +0200, René Bleisch accou...@climate.unibe.ch said: dracut ? (where can I find this out?) It's in /var/log/fai/fai-make-nfsroot.log at the end. However, tftp/dracut then tried to mount the nfsroot from the dhcp-server :-( (not on the same machine...*) Oh, you hit this bug in dracut: bugs.debian.org/731244 My proposal is to use NFSROOT=/srv/fai/nfsroot in nfsroot.conf and fai-chboot -u nfs://IP of phkup26/srv/fai/config This works nicely for me. -- regards Thomas
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
Thanks for the informations - dracut: I have version 020-2 I tried your suggestion with NFSROOT=/srv/fai/nfsroot and fai-chboot -u nfs://IP of phkup26/srv/fai/config, but I still tried to mount the nfsroot from the dhcp-server. For me it really only works with NFSROOT=nfs:phkup26:/srv/fai/nfsroot (resp. root=nfs:phkup26:/srv/fai/nfsroot in the tftp-file), -hence I will stay with this until maybe the dracut guys fix the bug Regards René On 04/25/2014 01:49 PM, Thomas Lange wrote: On Fri, 25 Apr 2014 13:38:47 +0200, René Bleischaccou...@climate.unibe.ch said: dracut ? (where can I find this out?) It's in /var/log/fai/fai-make-nfsroot.log at the end. However, tftp/dracut then tried to mount the nfsroot from the dhcp-server :-( (not on the same machine...*) Oh, you hit this bug in dracut: bugs.debian.org/731244 My proposal is to use NFSROOT=/srv/fai/nfsroot in nfsroot.conf and fai-chboot -u nfs://IP of phkup26/srv/fai/config This works nicely for me.
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
On Fri, 25 Apr 2014 14:08:07 +0200, René Bleisch accou...@climate.unibe.ch said: - dracut: I have version 020-2 I use dracut 036-1 which is also available in the fai-project package repository. -- regards Thomas
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
On 4/25/2014 07:38, René Bleisch wrote: I just tried a test installation with NFSROOT=/srv/fai/nfsroot and indeed the installation stops with mount.nfs: access denied by server while mounting 130.92.143.225:/srv/fai/nfsroot I have a similar issue and fixed by placing the following in /etc/fai/fai.conf: FAI_CONFIG_SRC=nfs://yourservername/serverIP/srv/fai/config Cheers!
RE: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
Meanwhile I have updated - FAI 4.1.1 kernel /linux-image-3.13-0.bpo.1-amd64 I have deleted nfsroot and I have started fai-setup again. Now there is no problem with NFS... but something with network configuration/dhcp is not working. Starting dhcp for interface eth0 dhcp: PREINIT eth0 up dhcp: BOND setting eth0 No carrier detected no LINK FS-Cache: loaded FS-Cache: Netfs 'nfs' registered for caching Key typ dns_resolver registered NFS: Registering the the id_resolver key tape Key type id_resolver registered Key type id_legacy registered Random: nonblocking pool is initialized And nothing happens There is link - earlier message: e1000e: eth0 NIC Link is up 100 Mbps Full Duplex, Flow control None Regards Krasimir Arnaudov
RE: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
Ok I solved the problem. It was not the Network, FAI did not know where the NFS server is. I have made the following changes so that FAI works: - in PXE config file root=nfs:fai-server:/srv/fai/nfsroot (default is root=/srv/fai/nfsroot) - /srv/fai/nfsroot/etc/fai/fai.conf was not copied from /etc/fai/fai.conf and I configured it with the path to the config space Now everything works:) Regards Krasimir Arnaudov -Original Message- From: linux-fai [mailto:linux-fai-boun...@uni-koeln.de] On Behalf Of ARNAUDOV Krasimir Sent: Donnerstag, 03. April 2014 08:37 To: Thomas Lange; FAI Mailing Subject: RE: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot Meanwhile I have updated - FAI 4.1.1 kernel /linux-image-3.13-0.bpo.1-amd64 I have deleted nfsroot and I have started fai-setup again. Now there is no problem with NFS... but something with network configuration/dhcp is not working. Starting dhcp for interface eth0 dhcp: PREINIT eth0 up dhcp: BOND setting eth0 No carrier detected no LINK FS-Cache: loaded FS-Cache: Netfs 'nfs' registered for caching Key typ dns_resolver registered NFS: Registering the the id_resolver key tape Key type id_resolver registered Key type id_legacy registered Random: nonblocking pool is initialized And nothing happens There is link - earlier message: e1000e: eth0 NIC Link is up 100 Mbps Full Duplex, Flow control None Regards Krasimir Arnaudov
Re: linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot
On Wed, 2 Apr 2014 15:56:45 +0200, ARNAUDOV Krasimir krasimir.arnau...@thalesgroup.com said: I have biuld nfsroot today with kernel linux-image-3.12-0.bpo.1-amd64 - no errors everything fine. When I boot I receive dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot Missing NFS module? How does the complete kernel command line looks like? Do you use fai-chboot for creating the pxelinux.cfg file? -- regards Thomas
