Proxmox mount issues with NAS

[darthtidus]

Hi everyone,

maybe somebody can help me.
I have proxmox version 8.1.4 and I would use my NAS-Share to store vm data.
So I add my NAS-Share in proxmox via CIFS.
After connect i become the mount error: device is busy.
In the terminal of proxmox vm, the mount exists already but in the web portal under syslog register I can see following messaging:

proxmox kernel CIFS: Attempting to mount //<Server>/<Share>

The problem is, that proxmox does not recognized the mount that is already exists and try to mount it infinity.

But I have no idea, how to solve this problem.

kinds regards,

darthtidus

 

[bbgeek17]

In the terminal of proxmox vm, the mount exists already

You need to provide actual command output to explain exactly what you mean by this.

I'd advise to reboot and provide the below outputs after reboot:
cat /etc/pve/storage.cfg
mount
pvesm status
df -h
dmesg|tail -10
journalctl -n 20

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[darthtidus]

Hi bbgeek17,

here the outputs:

• cat /etc/pve/storage.cfg:

dir: local
path /var/lib/vz
content vztmpl,iso,backup

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

cifs: Daten-NAS
path /mnt/pve/Daten-NAS
server <IP NAS>
share VMs
content images
preallocation full
prune-backups keep-all=1
subdir /proxmox/
username <NAS-USER>

• mount:

ysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=12224468k,nr_inodes=3056117,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2451628k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19295)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
//<IP NAS>/VMs/proxmox on /mnt/pve/Daten-NAS type cifs (rw,relatime,vers=3.1.1,cache=strict,username=<NAS-USER>,uid=0,noforceuid,gid=0,noforcegid,addr=<IP-NAS>file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=2451624k,nr_inodes=612906,mode=700,inode64)

• pvesm status:

mount error(16): Device or resource busy
mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Name Type Status Total Used Available %
Daten-NAS cifs inactive 0 0 0 0.00%
local dir active 69661936 19962992 46114536 28.66%
local-lvm lvmthin active 144035840 76194959 67840880 52.90%

• df -h:

Filesystem Size Used Avail Use% Mounted on
udev 12G 0 12G 0% /dev
tmpfs 2.4G 1.2M 2.4G 1% /run
/dev/mapper/pve-root 67G 20G 44G 31% /
tmpfs 12G 46M 12G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 128K 24K 100K 20% /sys/firmware/efi/efivars
/dev/sda2 1022M 344K 1022M 1% /boot/efi
/dev/fuse 128M 20K 128M 1% /etc/pve
//<IP NAS>/VMs/proxmox 496G 14G 482G 3% /mnt/pve/Daten-NAS
tmpfs 2.4G 0 2.4G 0% /run/user/0

• dmesg|tail -10:

[ 3017.862313] CIFS: Attempting to mount //<IP NAS>VMs/proxmox
[ 3027.335123] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3037.495095] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3047.792311] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3057.112163] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3067.589737] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3077.755108] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3087.270813] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3097.590332] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
[ 3107.797872] CIFS: Attempting to mount //<IP NAS>/VMs/proxmox

• journalctl -n 20:

Feb 07 19:27:58 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:27:58 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:28:08 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:28:08 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:28:18 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:28:18 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:28:28 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:28:28 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:28:38 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:28:38 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:28:48 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:28:48 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:28:58 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:28:58 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:29:09 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:29:09 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:29:18 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:29:18 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Feb 07 19:29:28 proxmox kernel: CIFS: Attempting to mount //<IP NAS>/VMs/proxmox
Feb 07 19:29:28 proxmox pvestatd[969]: mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)



I think, after the first successfully mount auf the NAS-Share, the service to detect this state does not recognized, that the mount is successful and so the deamon try to mount the share every 10 seconds.

But I don't know, why the mount is not recoginized by the deamon.

 

[jack74r]

hi

I have exactly same problem, i try many things but cant fix ..

Proxmox create folder (images, dump etc..) in the smb folder (Openmediavault) but volume in proxmox still inactive and try to mount every 10s ..

 

[tannertech]

Also having this issue. I can access and fully interact with the folder under /mnt/pve/volumename but proxmox can't. It creates the folders but I get all the same errors as OP and cannot create or view backups.

I think the issue is despite it successfully mounting the volume it doesn't think it has so tries again, when the second attempt fails it seems to just give up instead of using the already fully working R/W mount it created.

 

[wbravin]

Hello all

I have been struggling to add Jellyfin as an LXC for over 2 weeks. I'm not an IT savvy individual.

Last night I finally had all my truenas shares mounted /mnt/truenas/Movies. However during my first attempt i screwed up the command line and ended up with all the contents of my media in the same folder (movies, Music and shows.
so i vent into the the pve shell and proceeded to delete all the content of /mnt/truenas/Movies.
I created the proper dir in /mnt/truenas/ one for music one for movies and one for shows

So i amended the /etc/fstab mount command to reflect /mnt/truenas/Movies /mnt/truenas.Music and /mnt/truenas/Shows

however when i try to mount these directories with mount/mnt/tuernas/Movies
I get

root@pve:~# mount /mnt/truenas/Movies
mount: /etc/fstab: parse error at line 1 -- ignored
mount error(16): Device or resource busy
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

I would agree with @tannertech's assessment
I stopped all the vms and lxcs rebooted the server and tried again with same results.

 

[m1293b]

Hello all,

Has anyone solved this issue? I have just started to get this error message, and I couldn't figure out what the problem could be.

 

[m1293b]

Hello all,

Has anyone solved this issue? I have just started to get this error message, and I couldn't figure out what the problem could be.

I deleted all the storage points, and mounted the shares manually in /etc/fstab. In Proxmox I mapped the directory and I then had to delete the original disk from the VM's hardware section, and map the new directory as a "Hard disk". Since I didn't change the layout of the files, my VM was able to boot without an issue, and without the need of rebooting the host. I did systemctl daemon-reload as well at some point. I hope this helps someone save a couple of hours of forensic investigation.