PXE nfs problems

nomorewindows · 2024-11-17 05:15:25

While I have used PXE diskless workstation off and on, it seems like it no longer recognizes mount.nfs when running from a pxe boot.

Have been using dnsmasq. Switched back to tftpd, dhcpd4, & nfs-utils. I can mount nfs from a disk running machine with no problems.

It tries to boot from /dev/nfs even if I don't include root=/dev/nfs. If I try to mount the nfs from the rootfs shell, it still won't mount. I can get

mount.nfs: Either use '-o nolock' to keep locks local or start statd.
mount.nfs: rpc.statd is not running but is required for remote locking.

Still doesn't mount nfs. This hasn't been a problem before.

I also tried using an older arch32 pxe installation that of course 32bit is no longer supported by arch linux that hasn't been touched being no longer maintained. Still the same behaviour.

Latest nfs-utils is back on Oct 20. Maybe the culprit?

NFS over TCP is not available from x.x.x.x

Last edited by nomorewindows (2024-11-17 05:59:11)

seth · 2024-11-17 08:32:09

NFS over TCP is not available from x.x.x.x

nmap x.x.x.x

https://serverfault.com/questions/37717 … to-use-nfs
Maybe it only run UDP on 2049 ?

mount.nfs: Either use '-o nolock' to keep locks local…

Did you? What happens then?

nomorewindows · 2024-11-17 20:20:27

seth wrote:

NFS over TCP is not available from x.x.x.x
nmap x.x.x.x
https://serverfault.com/questions/37717 … to-use-nfs
Maybe it only run UDP on 2049 ?
mount.nfs: Either use '-o nolock' to keep locks local…
Did you? What happens then?

Yeah it said access rejected. It's kind of weird that I could mount it from another station, but not pxe nfs.

rpcbind was open, but not nfs. Maybe somewhere in there I had nfs-server stopped, and once I restarted it, it worked again. Nfs-utils was running saying it was providing nfs server and client, but it wasn't open for nfs server port.

Not sure how it started as the server was rebooted after power outage.

Looks like maybe I have it, but not exactly sure where it started.

seth · 2024-11-17 21:02:54

Maybe somewhere in there I had nfs-server stopped, and once I restarted it, it worked again.

For clarification, the PXE boot now works again?
Maybe the service wa still running but the daemon itself died? Can you inspect the logs/coredumps on the server?

nomorewindows · 2024-11-17 22:30:19

seth wrote:

Maybe somewhere in there I had nfs-server stopped, and once I restarted it, it worked again.
For clarification, the PXE boot now works again?
Maybe the service wa still running but the daemon itself died? Can you inspect the logs/coredumps on the server?

Was able to boot pxe shortly ago.

Just searching journalctl for NFS shows hardly anything for NFS.

Strangely something went weird with my ssh, wouldn't assign a PTY, but restarting it cleared that up.

Apparently,

mount: unknown filesystem nfs

is indicating that the NFS server was unavailable or going weird.

Last edited by nomorewindows (2024-11-17 22:32:05)

seth · 2024-11-17 22:50:32

It primarly indicates a lack of nfs-utils which provides mount.nfs*

nomorewindows · Yesterday 02:50:55

Looks like I had to reboot to get sshd working again, but for now it looks like PXE is working.

Arch Linux

#1 2024-11-17 05:15:25

PXE nfs problems

#2 2024-11-17 08:32:09

Re: PXE nfs problems

#3 2024-11-17 20:20:27

Re: PXE nfs problems

#4 2024-11-17 21:02:54

Re: PXE nfs problems

#5 2024-11-17 22:30:19

Re: PXE nfs problems

#6 2024-11-17 22:50:32

Re: PXE nfs problems

#7 Yesterday 02:50:55

Re: PXE nfs problems

Board footer