Re: dracut "mount.nfs: Connection timed out"

2019-04-30 Diskussionsfäden Thomas Lange
> On Tue, 30 Apr 2019 17:28:51 +0200, Daniel Haensse > said: > It seems like there is still the old issue, if the dhcp server is > different from the fai server, I had to > prepend the ip in /srv/tftp/fai/pxelinux.cfg/XYZ file > root=192.168.10.2:/srv/fai/nfsroot Yes,

dracut "mount.nfs: Connection timed out"

2019-04-30 Diskussionsfäden Daniel Haensse
It seems like there is still the old issue, if the dhcp server is different from the fai server, I had to prepend the ip in /srv/tftp/fai/pxelinux.cfg/XYZ file root=192.168.10.2:/srv/fai/nfsroot hostname did not work

Re: dracut mount.nfs: Connection timed out

2013-06-07 Diskussionsfäden Toomas Tamm
On Fri, 2013-06-07 at 09:51 +0200, Clément LAGRANGE wrote: Hello, I had to specify the NFS server by IP for the root to mount... No idea why though. I can second that. With wheezy, I had to explicitly specify nfsroot=XXX.XXX.XXX.XXX:/wrk/fai/nfsroot64 while earlier, just

Re: dracut mount.nfs: Connection timed out

2013-06-07 Diskussionsfäden Toomas Tamm
On Fri, 2013-06-07 at 11:46 +0300, Toomas Tamm wrote: On Fri, 2013-06-07 at 09:51 +0200, Clément LAGRANGE wrote: Hello, I had to specify the NFS server by IP for the root to mount... No idea why though. I can second that. With wheezy, I had to explicitly specify

Re: dracut mount.nfs: Connection timed out

2013-06-07 Diskussionsfäden Toomas Tamm
On Fri, 2013-06-07 at 11:56 +0300, Toomas Tamm wrote: TFTP server. In squeeze, however, it (dracut) defaults to the DHCP server's IP address. In my setup, the DHCP server is separate from the TFTP+FAI server, so specifying an explicit IP address became necessary. Correction: the latter

Re: dracut mount.nfs: Connection timed out

2013-06-07 Diskussionsfäden Russ Allbery
Toomas Tamm tt-...@kky.ttu.ee writes: On Fri, 2013-06-07 at 11:56 +0300, Toomas Tamm wrote: TFTP server. In squeeze, however, it (dracut) defaults to the DHCP server's IP address. In my setup, the DHCP server is separate from the TFTP+FAI server, so specifying an explicit IP address became

Re: dracut mount.nfs: Connection timed out

2013-06-07 Diskussionsfäden Toomas Tamm
On Fri, 2013-06-07 at 02:33 -0700, Russ Allbery wrote: Oh! I'll try that tomorrow. But it's supposed to default to next-server from the DHCP reply; I assume that's no longer happening? Well, I did not do any extensive debugging. I just wanted to get FAI to boot. Thus when it refused to mount

Re: dracut mount.nfs: Connection timed out

2013-06-07 Diskussionsfäden Russ Allbery
Russ Allbery r...@debian.org writes: Toomas Tamm tt-...@kky.ttu.ee writes: On Fri, 2013-06-07 at 11:56 +0300, Toomas Tamm wrote: TFTP server. In squeeze, however, it (dracut) defaults to the DHCP server's IP address. In my setup, the DHCP server is separate from the TFTP+FAI server, so

dracut mount.nfs: Connection timed out

2013-06-06 Diskussionsfäden Russ Allbery
Hello folks, I'm updating our FAI build environment to wheezy and trying to get the first systems to build, and I'm running into trouble with mounting the NFS root from the build server. I'm using dracut (rather than live-boot) since that seems to be the new, preferred option, but it's failing

Re: dracut mount.nfs: Connection timed out

2013-06-06 Diskussionsfäden Thomas Lange
On Thu, 06 Jun 2013 13:40:37 -0700, Russ Allbery r...@debian.org said: The error I get is: mount.nfs: Connection timed out dracut Warning: Could not boot. append initrd=initrd.img-3.2.0-4-amd64 ip=dhcp root=nfs:/srv/fai/wheezy-amd64 aufs