testing fai4 on wheezy
Michał Dwużnik
michal.dwuznik at gmail.com
Wed Dec 11 18:18:30 CET 2013
On Wed, Dec 11, 2013 at 10:59 AM, Thomas Lange
<lange at informatik.uni-koeln.de> wrote:
>>>>>> On Wed, 11 Dec 2013 02:29:08 +0100, Michał Dwużnik <michal.dwuznik at gmail.com> said:
>
> > NFSROOT:dracut-network live-boot- live-boot-initramfs-tools-
> You are using dracut inside the nfsroot. That's fine.
>
> I guess you are running into this problem:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731244
>
you nailed it.
> With dracut you can specify the root device as follows:
> root=nfs:[<server-ip>:]<root-dir>[:_<nfs-options>_]
>
Thank you, there's a big step forward:
append initrd=initrd.img-3.2.0-4-amd64 ip=dhcp root=/dev/nfs
nfsroot=nfs://172.20.50.50/srv/fai/nfsroot aufs FAI_ACTION=install
seems to cure the forementioned problem,
yielding the problem below :>
>
> If this works but you get a kernel panic later, you might hit the
> problem that the client tries to mount via NFSv4. Here's a workaround
> for that:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676883#10
>
nfsvers=3 helps,
dracut: Mounted filesystem 172.20.50.50:/srv/fai/nsroot
can't open /etc/fstab No such files or directory
So, I'm back on nfsroot error level, thank you.
...And after a few changes in nfsroot/etc/fai/fai.conf My test client
is installing.
Thank you again
>
> P.S.: Please do NOT cite all previous mails in your response. That's
> not needed.
Sorry for that.
Regards
Michal
More information about the linux-fai
mailing list