Re: early stage rpcbind failure

My fault! I usually apply few little patches to fai-chboot one of which modifies the $nfsroot perl variable. That patch always worked over the past few years but now it breaks the 'aufs' check with fai 5.1.2. I fixed that too so no -k option is now needed. MG ~ Matteo

Re: early stage rpcbind failure

> On Mon, 5 Sep 2016 13:49:52 +, Guglielmi Matteo > said: > 'aufs' option fixes the problem! > fai-chboot -k aufs -IBv hostname Great. fai-chboot should detect automatically if aufs or overlayfs (option rootovl) is used inside the nfsroot and then

Re: early stage rpcbind failure

> On Mon, 5 Sep 2016 13:00:42 +, Guglielmi Matteo > said: > 2) there is no /run/rpcbind/ folder (see 1st > error message I get). What I have in the > /run folder related to rpcbind are the following > two files: > /run/rpcbind.lock

Re: early stage rpcbind failure

On top of that I also see that the install client mounts the root '/' with the 'ro' option and I'm not able to create any additional file or folder anywhere on it. This is wrong, right? MG ~ Matteo Guglielmi EPFL SB-IT / CM 1 617 STATION 8 CH-1015 LAUSANNE

Re: early stage rpcbind failure

Just tried but it did not solve the problem. Despite that, connecting a console to the install node and wait for the installation to fail I could in fact confirm that: 1) nfsroot is mounted with nfs version 3 2) there is no /run/rpcbind/ folder (see 1st error message I get). What I have in the

Re: early stage rpcbind failure

> On Sun, 4 Sep 2016 23:01:25 +, Guglielmi Matteo > said: > I've also rebuilt the nfsroot several times in order to create > new initrd files without luck. You can try the nfsroot from http://fai-project.org/download/misc/. call fai-make-nfsroot -av