After update from 8.4 to 9.0 NFS doesn't work

P

p-user

Member
Jan 26, 2024
67
4
8
Hi Fiona,

I've got a tiny proxmox cluster, two N100/N150 32GB nodes, with an extra one as a pbs, same specs (except 16GB).
The pbs is an extra quorum device to make up for the three node cluster.
For cluster storage I use an NFS server, which worked fine for version 8.4.
After the update the pbs storage came up fine, but not the nfs share, on both nodes.

Here's my storage.cfg:
root@pve1:/etc/pve# cat storage.cfg
dir: local
disable
path /var/lib/vz
content iso,vztmpl,backup
shared 0

lvmthin: local-lvm
disable
thinpool data
vgname pve
content images,rootdir

dir: Storage
path /mnt/pve/Storage
content import,snippets,iso,rootdir,vztmpl,images
nodes pve2
prune-backups keep-all=1
shared 0

pbs: Backup_General
datastore PBSStorage
server pbs.pauw.local
content backup
fingerprint ######################################
namespace Backup
prune-backups keep-all=1
username root@pam

pbs: Backup_Mail
datastore PBSStorage
server pbs.pauw.local
content backup
fingerprint ######################################
namespace MailBackup
prune-backups keep-all=1
username root@pam

nfs: Storage_NFS
export /mnt/user/nfs
path /mnt/pve/Storage_NFS
server nfs.pauw.local
content images,iso
nodes pve2,pve1
preallocation metadata
prune-backups keep-all=1

root@pve1:/etc/pve# showmount -e nfs.pauw.local
Export list for nfs.pauw.local:
/mnt/user/nfs 192.168.2.*

Here are the settings:
1754494477111.png
These settings haven't changed.
And here are the last bits of the /var/log/syslog on one of the nodes:
2025-08-06T17:31:40.346419+02:00 pve1 pvedaemon[24999]: mount error: exit code 32
2025-08-06T17:31:43.572887+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:31:49.430577+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:31:53.585853+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:31:59.891675+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:32:03.599348+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:32:09.381852+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:32:13.612597+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:32:20.097216+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:32:23.625870+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:32:29.583974+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:32:33.639030+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:32:40.077188+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:32:43.652503+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:32:49.567686+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:32:53.665460+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:32:59.027332+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:33:03.678988+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:33:09.515679+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:33:13.693012+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:33:20.136445+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:33:23.706329+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:33:29.499493+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:33:33.719479+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:33:39.212533+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:33:43.732868+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:33:49.701220+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:33:53.745871+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:33:59.064411+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:34:03.758995+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:34:09.811517+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:34:13.771930+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:34:19.274108+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:34:23.785331+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:34:29.634605+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:34:33.798431+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:34:39.378052+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:34:43.811844+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:34:49.740474+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:34:53.824880+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:34:59.329388+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:35:03.838031+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:35:09.819183+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:35:13.851237+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:35:19.437252+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:35:23.864735+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:35:29.926698+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:35:33.877564+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:35:39.415107+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:35:40.104395+02:00 pve1 systemd[1]: Started session-16.scope - Session 16 of User root.
2025-08-06T17:35:43.890755+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
2025-08-06T17:35:49.902984+02:00 pve1 pvestatd[1312]: mount error: exit code 32

I have never configured anything for the firewall.

As a bonus, another problem cropt up. I restored a VM from the pbs to local storage and tried to start it and got this:

TASK ERROR: KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS.

Which puzzeled me, as nothing was changed in the BIOS of the nodes.
 
p-user said:
root@pve1:/etc/pve# showmount -e nfs.pauw.local
Export list for nfs.pauw.local:
/mnt/user/nfs 192.168.2.*
Click to expand...
Okay, so listing the shares works at least, that's a start.

p-user said:
2025-08-06T17:31:49.430577+02:00 pve1 pvestatd[1312]: mount error: exit code 32
2025-08-06T17:31:53.585853+02:00 pve1 pve-firewall[1307]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Click to expand...
It's unfortunate that there's not more details. Could you try mounting the share manually mount -t nfs nfs.pauw.local:/mnt/user/nfs /mnt/pve/Storage_NFS? What does pvesm status say?

p-user said:
I have never configured anything for the firewall.

As a bonus, another problem cropt up. I restored a VM from the pbs to local storage and tried to start it and got this:

TASK ERROR: KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS.

Which puzzeled me, as nothing was changed in the BIOS of the nodes.
Click to expand...
This also sounds very strange. Could you share the full journal for the current boot, i.e. journalctl -b > /tmp/boot.txt?
 
Hi Fiona,
thanks for your help. I'm at work right now, but will report this evening, i.e. in about six hours.
Let's hope it is an easy fix.
Regards,
Albert
 
Same for me !! Unable to start any VM

mount -vvv -t nfs truenas.denis.prive:/mnt/POOL-ZFS01/DS-V /ZZ1
mount.nfs: failed to prepare mount: No such device


lsmod | grep -i nfs
> nothing

pvesm status
storage 'nfs_lv_vm' is not online
mount.nfs: failed to prepare mount: No such device
mount error: exit code 32
mount.nfs: failed to prepare mount: No such device
mount error: exit code 32
Name Type Status Total Used Available %
local dir active 28461108 5653796 21336236 19.86%
lv_vm dir active 1269650848 1017445124 194237168 80.14%
nfs_lv_vm nfs inactive 0 0 0 0.00%
nfs_truenas_backups nfs inactive 0 0 0 0.00%
nfs_x_images_iso nfs inactive 0 0 0 0.00%


journalctl -b | grep -i nfs
Aug 07 09:46:59 r740-1 systemd[1]: Mounting proc-fs-nfsd.mount - NFSD configuration filesystem...
Aug 07 09:46:59 r740-1 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a
Aug 07 09:46:59 r740-1 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'.
Aug 07 09:46:59 r740-1 systemd[1]: Failed to mount proc-fs-nfsd.mount - NFSD configuration filesystem.
Aug 07 09:46:59 r740-1 systemd[1]: Dependency failed for nfs-server.service - NFS server and services.
Aug 07 09:46:59 r740-1 systemd[1]: Dependency failed for nfs-mountd.service - NFS Mount Daemon.
Aug 07 09:46:59 r740-1 systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start failed with result 'dependency'.
Aug 07 09:46:59 r740-1 systemd[1]: Dependency failed for nfs-idmapd.service - NFSv4 ID-name mapping service.
Aug 07 09:46:59 r740-1 systemd[1]: nfs-idmapd.service: Job nfs-idmapd.service/start failed with result 'dependency'.
Aug 07 09:46:59 r740-1 systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.
Aug 07 09:46:59 r740-1 systemd[1]: Dependency failed for nfsdcld.service - NFSv4 Client Tracking Daemon.
Aug 07 09:46:59 r740-1 systemd[1]: nfsdcld.service: Job nfsdcld.service/start failed with result 'dependency'.
Aug 07 09:46:59 r740-1 mount[990]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'.

systemctl restart nfs-kernel-server
journalctl -xe
 A start job for unit rpc-gssd.service has finished with a failure.
░░
░░ The job identifier is 1418 and the job result is dependency.
Aug 07 10:28:28 r740-1 systemd[1]: rpc-gssd.service: Job rpc-gssd.service/start failed with result 'dependency'.
Aug 07 10:28:28 r740-1 systemd[1]: rpc_pipefs.target: Job rpc_pipefs.target/start failed with result 'dependency'.
Aug 07 10:28:28 r740-1 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An n/a= process belonging to unit proc-fs-nfsd.mount has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 32.
Aug 07 10:28:28 r740-1 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'.
Aug 07 10:28:28 r740-1 systemd[1]: Failed to mount proc-fs-nfsd.mount - NFSD configuration filesystem.
░░ Subject: A start job for unit proc-fs-nfsd.mount has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit proc-fs-nfsd.mount has finished with a failure.
░░
░░ The job identifier is 1406 and the job result is failed.
Aug 07 10:28:28 r740-1 systemd[1]: Dependency failed for nfs-server.service - NFS server and services.
░░ Subject: A start job for unit nfs-server.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit nfs-server.service has finished with a failure.
░░
░░ The job identifier is 1281 and the job result is dependency.
Aug 07 10:28:28 r740-1 systemd[1]: Dependency failed for nfs-mountd.service - NFS Mount Daemon.
░░ Subject: A start job for unit nfs-mountd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit nfs-mountd.service has finished with a failure.
░░
░░ The job identifier is 1407 and the job result is dependency.
Aug 07 10:28:28 r740-1 systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start failed with result 'dependency'.
Aug 07 10:28:28 r740-1 systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.
Aug 07 10:28:35 r740-1 pvestatd[1765]: storage 'nfs_lv_vm' is not online
Aug 07 10:28:35 r740-1 pvestatd[1765]: mount error: exit code 32
Aug 07 10:28:35 r740-1 pvestatd[1765]: mount error: exit code 32
Aug 07 10:28:35 r740-1 pve-firewall[1764]: status update error: iptables_restore_cmdlist: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
 
Last edited:
More infos:

systemctl restart nfs-server
journalctl -xe
...
The unit run-rpc_pipefs.mount has entered the 'failed' state with result 'exit-code'.
Aug 07 10:48:15 r740-1 systemd[1]: Failed to mount run-rpc_pipefs.mount - RPC Pipe File System.
░░ Subject: A start job for unit run-rpc_pipefs.mount has failed
 
Hi,
@titou10 are you running your NFS server on the same node as the client? Otherwise, you shouldn't need the nfs-server package and service there.
 
Creating a new NFS storage at the console fails with
create storage failed: storage 'xxx' is not online (500)

Editing an NFS storage with the goal to disable it fails with:
update storage failed: no such option 'maxfiles' (500)

'maxfile' can not be found in any file under /etc/pve...

Totally stuck here
 
fiona said:
Hi,
@titou10 are you running your NFS server on the same node as the client? Otherwise, you shouldn't need the nfs-server package and service there.
Click to expand...
Yes. Worked fine with 8.x version. did not changed anything after v9 upgrade
But also the NFS client is broken, see previous post with tentative to create new NFS storage to another NFS server
 
Last edited:
titou10 said:
Creating a new NFS storage at the console fails with
create storage failed: storage 'xxx' is not online (500)
Click to expand...
If the NFS server is not running, this is no surprise. Please share the full log from the current boot: journalctl -b /tmp/boot.txt
titou10 said:
Editing an NFS storage with the goal to disable it fails with:
update storage failed: no such option 'maxfiles' (500)

'maxfile' can not be found in any file under /etc/pve...
Click to expand...
Regarding the maxfiles parameter, this has been deprecated long ago and is dropped in Proxmox VE 9. The pve8to9 checker script would tell you and this is also noted in the breaking changes. Remove the setting and use prune-backups keep-all=1 if you had set maxfiles to 0 or prune-backups keep-last=N if you had maxfiles set to non-zero N.
 
fiona said:
The pve8to9 checker script would tell you and this is also noted in the breaking changes.
Click to expand...

Nope, setting prune-backups keep-all=1 in storage.cfg. solved the "edit storage" console issue, not the create of new NFS storage to external nfs server

'boot.txt' attached. in there you can find this that may be related to the problem
systemd[1]: Starting of proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point unsupported
 

Attachments

Last edited:
Hi Fiona,
here are my replies:

root@pve2:~# mount -t nfs nfs.pauw.local/mnt/usr/nfs /mnt/pve/Storage_NFS
mount.nfs: failed to prepare mount: No such device

FYI, The last 1000s of lines of boot.txt is just a repetition about firewalld

Regards,
Albert
 

Attachments

@p-user and @fiona I solved it for my own problem
The only warning I had from pve8to9 was that i should install the "Intel-microcode" package
WARN: The matching CPU microcode package 'intel-microcode' could not be found! Consider installing it to receive the latest security and bug fixes for your CPU.

I install it and now NFS works !! (and many other things)

To install it, add the "non-free-firmware" repo to /etc/apt/sources.list.d/debian.sources,

Types: deb
URIs: https://deb.debian.org/debian/
Suites: trixie
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

or if you use old style /etc/apt/sources.list :
deb-src http://deb.debian.org/debian trixie-updates main contrib non-free non-free-firmware

Then "apt update && apt install intel-microcode", reboot and youou.it works
Now "lsmod" shows way more modules loaded...

It also solved the problem with KVM when the microcode is not installed:
KVM virtualisation configured, but not available. Either disable in VM configuration or enable in BIOS
..and cpu=host does not work

Now this also works

@fiona IMHO the warning about "intel-microcode" missing is misleading. It is a blocker in my case, it should be shown a such, ie blocker

lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) Silver 4214 CPU @ 2.20GHz
 
Last edited:
  • Like
Reactions: brianj2k and waltar
That's great, thank you so much. I will try it tomorrow. I already had taken one of the nodes out of the cluster for a clean install, but hadnt got round that bit yet. If this works then I have to find a way to add it back into the cluster, using the same hostname.

FYI I had no warning regarding missing intel microcode in the pve8to9 script. I had a warning that I had two vms running, so I stopped them and pve8to9 was all green.

If it works you are a life saver.

Regards Albert
 
p-user said:
If it works you are a life saver.
Click to expand...
yw. finger crossed.
Before installing the intel-microcode package, lsmod what showing about 20 modules. now there are 118, including the nfs, nfsd, netfs, nfsv4...modules that were not there
In my case the intel-microcode package is required. I do not see a direct relationship with the NFS features/services/share not working except that the required modules where not loaded by the kernel probably because the MB (Dell Poweredge R740 in my case) was not detected
 
We'll see, my specs are more modest. It's a GMKtec G3 plus with 32GB memory and 1 TB nvme drive and Intel N150 processor. Works great though (if it works).
 
Well, unfortunately, it didn't work. I actually had the correct debian.sources already set up, including non-free-firmware:

root@pve2:~# cat /etc/apt/sources.list.d/debian.sources
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://ftp.nl.debian.org/debian/
Suites: trixie
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://ftp.nl.debian.org/debian/
Suites: trixie-updates
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://security.debian.org/
Suites: trixie-security
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

And the modules now installed:

root@pve2:~# lsmod
Module Size Used by
btrfs 1978368 0
blake2b_generic 24576 0
xor 20480 1 btrfs
raid6_pq 122880 1 btrfs
usbhid 69632 0
hid 253952 1 usbhid
dm_thin_pool 90112 1
dm_persistent_data 114688 1 dm_thin_pool
dm_bio_prison 24576 1 dm_thin_pool
dm_bufio 53248 1 dm_persistent_data
nvme 61440 1
i2c_i801 36864 0
nvme_core 212992 2 nvme
i2c_mux 16384 1 i2c_i801
xhci_pci 24576 0
spi_intel_pci 12288 0
igc 192512 0
nvme_auth 24576 1 nvme_core
spi_intel 32768 1 spi_intel_pci
i2c_smbus 20480 1 i2c_i801
sdhci_pci 98304 0
intel_lpss_pci 28672 0
sdhci_uhs2 28672 1 sdhci_pci
ahci 49152 5
sdhci 94208 2 sdhci_uhs2,sdhci_pci
libahci 53248 1 ahci
intel_lpss 12288 1 intel_lpss_pci
cqhci 40960 1 sdhci_pci
xhci_hcd 376832 1 xhci_pci
idma64 20480 0
video 77824 0
wmi 28672 1 video
pinctrl_alderlake 32768 0
 
Here some status info from the pve storage manager:

root@pve2:~# pvesm scan nfs nfs.pauw.local
/mnt/user/nfs 192.168.2.*


root@pve2:~# pvesm status
mount.nfs: failed to prepare mount: No such device
mount error: exit code 32
Name Type Status Total Used Available %
Backup_General pbs active 942923136 329542016 613381120 34.95%
Backup_Mail pbs active 942923136 329542016 613381120 34.95%
Storage dir active 960302804 205549252 705899092 21.40%
Storage_NFS nfs inactive 0 0 0 0.00%
local dir disabled 0 0 0 N/A
local-lvm lvmthin disabled 0 0 0 N/A
 
In my case "Suites" is "trixie" not "trixie-security" for "non-free-firmnware" and "URIs: https://deb.debian.org/debian/" in debian.sources. check my previous post
In fact all URI are different

My debian.source:

Types: deb
URIs: http://ftp.ca.debian.org/debian/
Suites: trixie
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://ftp.ca.debian.org/debian/
Suites: trixie-updates
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/
Suites: trixie-security
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: https://deb.debian.org/debian/
Suites: trixie
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Not sure who's right there as some but not all use mirror sites ("ca" "vs "nl")


is package "intel-microcode" installed? if not, after correcting debian .sources. apt update && apt upgrade -y && apt install intel-microcode then reboot
 
Last edited:
p-user said:
boot.txt
Click to expand...
Regarding firewall/network, it seems like you might be missing a module/packages for openvswitch or have left-over configuration?

The root cause for your NFS client not working might be the failed RPC files system mount. Don't know why that could be from the top of my head and I'll have to run for the weekend, but you should continue investigating there.

See:
Code: 
Aug 06 12:02:24 pve2 systemd[1]: Mounting run-rpc_pipefs.mount - RPC Pipe File System...
Aug 06 12:02:24 pve2 mount[943]: mount: /run/rpc_pipefs: unknown filesystem type 'rpc_pipefs'.
Aug 06 12:02:24 pve2 mount[943]:        dmesg(1) may have more information after failed mount system call.
Aug 06 12:02:24 pve2 systemd[1]: run-rpc_pipefs.mount: Mount process exited, code=exited, status=32/n/a
Aug 06 12:02:24 pve2 systemd[1]: run-rpc_pipefs.mount: Failed with result 'exit-code'.
Aug 06 12:02:24 pve2 systemd[1]: Failed to mount run-rpc_pipefs.mount - RPC Pipe File System.
Aug 06 12:02:24 pve2 systemd[1]: Dependency failed for rpc_pipefs.target.
Aug 06 12:02:24 pve2 systemd[1]: Dependency failed for rpc-gssd.service - RPC security service for NFS client and server.
Aug 06 12:02:24 pve2 systemd[1]: rpc-gssd.service: Job rpc-gssd.service/start failed with result 'dependency'.
Aug 06 12:02:24 pve2 systemd[1]: Dependency failed for nfs-blkmap.service - pNFS block layout mapping daemon.
Aug 06 12:02:24 pve2 systemd[1]: nfs-blkmap.service: Job nfs-blkmap.service/start failed with result 'dependency'.
Aug 06 12:02:24 pve2 systemd[1]: rpc_pipefs.target: Job rpc_pipefs.target/start failed with result 'dependency'.
Aug 06 12:02:24 pve2 systemd[1]: Reached target nfs-client.target - NFS client services.
Aug 06 12:02:24 pve2 networking[871]: warning: Vnet3: post-up cmd 'iptables -t nat -A POSTROUTING -s '192.168.3.0/24' -o vmbr0 -j SNAT --to-source 192.168.2.241' failed: returned 3 (modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.14.8-2-pve
Aug 06 12:02:24 pve2 networking[871]: iptables v1.8.11 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Aug 06 12:02:24 pve2 networking[871]: Perhaps iptables or your kernel needs to be upgraded.
Aug 06 12:02:24 pve2 networking[871]: )
Aug 06 12:02:24 pve2 /usr/sbin/ifup[871]: warning: Vnet3: post-up cmd 'iptables -t nat -A POSTROUTING -s '192.168.3.0/24' -o vmbr0 -j SNAT --to-source 192.168.2.241' failed: returned 3 (modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.14.8-2-pve
                                          iptables v1.8.11 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
                                          Perhaps iptables or your kernel needs to be upgraded.
                                          )
Aug 06 12:02:24 pve2 networking[871]: warning: Vnet3: post-up cmd 'iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1' failed: returned 3 (modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.14.8-2-pve
Aug 06 12:02:24 pve2 networking[871]: iptables v1.8.11 (legacy): can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
Aug 06 12:02:24 pve2 networking[871]: Perhaps iptables or your kernel needs to be upgraded.
Aug 06 12:02:24 pve2 networking[871]: )
Aug 06 12:02:24 pve2 /usr/sbin/ifup[871]: warning: Vnet3: post-up cmd 'iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1' failed: returned 3 (modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.14.8-2-pve
                                          iptables v1.8.11 (legacy): can't initialize iptables table `raw': Table does not exist (do you need to insmod?)
                                          Perhaps iptables or your kernel needs to be upgraded.
                                          )
Aug 06 12:02:25 pve2 systemd[1]: ovs-vswitchd.service: Scheduled restart job, restart counter is at 3.
Aug 06 12:02:25 pve2 systemd[1]: Starting ovs-vswitchd.service - Open vSwitch Forwarding Unit...
Aug 06 12:02:25 pve2 (ovs-ctl)[982]: ovs-vswitchd.service: Referenced but unset environment variable evaluates to an empty string: OVS_CTL_OPTS
Aug 06 12:02:25 pve2 ovs-ctl[1022]: modprobe: FATAL: Module openvswitch not found in directory /lib/modules/6.14.8-2-pve
 
titou10 said:
In my case "Suites" is "trixie" not "trixie-security" for "non-free-firmnware" and "URIs: https://deb.debian.org/debian/" in debian.sources. check my previous post
In fact all URI are different

My debian.source:

Types: deb
URIs: http://ftp.ca.debian.org/debian/
Suites: trixie
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://ftp.ca.debian.org/debian/
Suites: trixie-updates
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/
Suites: trixie-security
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: https://deb.debian.org/debian/
Suites: trixie
Components: main non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Not sure who's right there as some but not all use mirror sites ("ca" "vs "nl")


is package "intel-microcode" installed? if not, after correcting debian .sources. apt update && apt upgrade -y && apt install intel-microcode then reboot
Click to expand...
Intel-microcode is installed
 
You must log in or register to reply here.
Top Bottom