[SOLVED] New Proxmox - NFS Error 500

M

Mythology89

Member
Nov 20, 2021
8
0
6
36
I just installed Proxmox 7.1

I access the web, I add NFS storage, when I put the IP of the NAS (Synology) the shared folder appears.

Adding gives a 500 error.

All that appears on many websites is that this error is a permission error on the NAS. I have checked the Synology NAS several times and they are allowed (if not, the directory would not appear when I added it). In fact, it was working on this Proxmox with the same IP before formatting.

Any ideas?
 

Attachments

  • photo_2021-11-30_09-02-19.jpg
    photo_2021-11-30_09-02-19.jpg
    26.1 KB · Views: 115
  • photo_2021-11-30_08-52-42.jpg
    photo_2021-11-30_08-52-42.jpg
    15.8 KB · Views: 127
Moayad said:
Please provide us with the output of pveversion -v
Click to expand...
root@proxmox1:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.4.34-1-pve)
pve-manager: 7.1-4 (running version: 7.1-4/ca457116)
pve-kernel-5.13: 7.1-4
pve-kernel-helper: 7.1-4
pve-kernel-5.13.19-1-pve: 5.13.19-2
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.14-1
proxmox-backup-file-restore: 2.0.14-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.4-2
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-1
pve-qemu-kvm: 6.1.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-3
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
 
Moayad said:
Thank you for the output!

Could you please try to upgrade to the latest version [0] of Proxmox VE and try again (After a new pve-kernel install you should restart the PVE server)?

Bash: 
apt update && apt full-upgrade

[0] https://pve.proxmox.com/wiki/Downlo...Proxmox_Virtual_Environment_7.x_to_latest_7.1
Click to expand...
root@proxmox1:~# apt update && apt full-upgrade
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.es.debian.org/debian bullseye InRelease
Hit:3 http://ftp.es.debian.org/debian bullseye-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 212.224.123.70 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@proxmox1:~#

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.

root@proxmox1:~# cat /etc/apt/sources.list
deb http://ftp.es.debian.org/debian bullseye main contrib

deb http://ftp.es.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.

root@proxmox1:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.4.34-1-pve)
pve-manager: 7.1-4 (running version: 7.1-4/ca457116)
pve-kernel-5.13: 7.1-4
pve-kernel-helper: 7.1-4
pve-kernel-5.13.19-1-pve: 5.13.19-2
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.14-1
proxmox-backup-file-restore: 2.0.14-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.4-2
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-1
pve-qemu-kvm: 6.1.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-3
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
 
tom said:
Please fix your repo settings for getting updates.

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories
Click to expand...
I do not understand exactly why it would have to be repaired since it is a new installation from the last available ISO ... But I think it is already done, I have updated and upgraded

We continue with the same NFS problem

root @ proxmox1: ~ # pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.4.34-1-pve)
pve-manager: 7.1-7 (running version: 7.1-7 / df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1 + pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1 + pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0 ~ rc1 + 2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
 
If I use smb / cifs something similar happens ... I put the data, scan and find the shared folders but it does not mount the access.
 

Attachments

  • Captura1.JPG
    Captura1.JPG
    14.5 KB · Views: 45
I dont know if this is important:

root@proxmox1:~# modprobe nfs
modprobe: FATAL: Module nfs not found in directory /lib/modules/5.4.34-1-pve
 
[SOLVED]

Basically I have followed a lot of tuto and errors of other users ...

Summary (if I have not been wrong because I have tried many things)

I was missing "pve-kernel-5.4.34-1-pve". Add a line to source-list, update and install.
 
You must log in or register to reply here.
Top Bottom
Back