<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
I just ran into problems when I tried to install a xenial client
with my new xenial-config.<br>
The installation got stuck due to a read-only filesystem - similar
to Erwanns (11.2.2016 "NFSROOT mounted on /") and Dirks case (
27.5.2016 "no writeable /tmp on PXE-Boot...").<br>
<br>
As in Erwanns case, it seems to be due to the missing "aufs" option
in the PXE-file.<br>
But I wonder, why the aufs option is missing in my tftp-config - it
is not added when I execute fai-chboot.<br>
If I manually add the "aufs" option to the PXE-file, everything
works as expected.<br>
<br>
In the FAI-changelog, I found the following entry for fai 5.1:<br>
"fai-chboot: automatic test if aufs or overlayfs is needed"<br>
<br>
I suspect, that in my case fai-chboot somehow decides that aufs is
not required<br>
=> how does "fai-chboot" make its decision on using aufs or
overlayfs (based on which conditions)?<br>
=> is there a command line option or fai.conf/nfsroot.conf option
to enforce fai-chboot to use aufs? *<br>
<br>
* I know, I could use a PXE-template file as I already do it in my
jessie/wheezy FAI - but I rather would avoid this in this case<br>
<br>
Regards<br>
René<br>
<br>
------------------<br>
My fai-chboot command:<br>
<font size="-1">/usr/sbin/fai-chboot -C /etc/fai_xenial -IFv -k
LOGREMOTEDIR=/var/log/fai_ubuntu -u
nfs://phkup26/srv/fai/config_xenial kupmolucca<br>
</font><br>
the resulting PXE-file:<br>
---<br>
<font size="-1">default fai-generated<br>
<br>
label fai-generated<br>
kernel vmlinuz-3.16.0-4-amd64<br>
append initrd=initrd.img-3.16.0-4-amd64 ip=dhcp
root=nfs:phkup26:/srv/fai/nfsroot
LOGREMOTEDIR=/var/log/fai_ubuntu FAI_FLAGS=verbose,sshd,createvt
FAI_CONFIG_SRC=nfs://phkup26/srv/fai/config_xenial
FAI_ACTION=install hostname=kupmolucca<br>
</font>---<br>
<br>
</body>
</html>