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

[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é


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