linux-image-3.12-0.bpo.1-amd64 dracut: FATAL: Don`t know how to handle root=/srv/fai/nfsroot

[ARNAUDOV Krasimir]

Hello,
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?

FAI Version 4.1

P.S. Sorry Thomas for the spam I have just hit reply

Regards
Krasimir Arnaudov

-----Original Message-----
From: linux-fai [mailto:linux-fai-bounces at uni-koeln.de] On Behalf Of Thomas Lange
Sent: Mittwoch, 02. April 2014 15:38
To: FAI Mailing
Subject: newer kernel packages for FAI when using wheezy

If you have recent hardware, the default kernel from Debian stable may not work. In the past we proposed to use the grml kernel with FAI for newer hardware. Now, I've also put the backports kernel packages from wheezy into the FAI project package repository. You can select from these kernel packages, when building the nfsroot and when installing your clients:

linux-image-3.12-0.bpo.1-amd64
linux-image-3.13-0.bpo.1-amd64
linux-image-3.13-0.bpo.1-486
linux-image-3.12-0.bpo.1-486


More infos at: http://wiki.fai-project.org/wiki/Grml_Kernel
--
regards Thomas

[Thomas Lange]

Post by ARNAUDOV Krasimir
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

[ARNAUDOV Krasimir]

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

[ARNAUDOV Krasimir]

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-bounces at 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

[René Bleisch]

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?

Post by ARNAUDOV Krasimir
Ok I solved the problem.
It was not the Network, FAI did not know where the NFS server is.
- 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-bounces at 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 ....
e1000e: eth0 NIC Link is up 100 Mbps Full Duplex, Flow control None
Regards
Krasimir Arnaudov

-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20140425/d25af12c/attachment.html>

[Thomas Lange]

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.

[René Bleisch]

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

Post by Thomas Lange

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?
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.

-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20140425/aaa4a68f/attachment.html>

[Thomas Lange]

Post by René Bleisch
dracut ? (where can I find this out?)

It's in /var/log/fai/fai-make-nfsroot.log at the end.

Post by René Bleisch
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.

[René Bleisch]

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?

Post by Thomas Lange

Post by René Bleisch
dracut ? (where can I find this out?)

It's in /var/log/fai/fai-make-nfsroot.log at the end.

Post by René Bleisch
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.

-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20140425/2c56e7ed/attachment.html>

[Thomas Lange]

Post by René Bleisch
- dracut: I have version 020-2

I use dracut 036-1 which is also available in the fai-project package repository.

[n43w79]

Post by René Bleisch
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!