Skip to main content Nightly Drop Of Mapped Network Drive : r/Proxmox

Nightly Drop Of Mapped Network Drive

Every morning when i log into my new proxmox server a mapped drive from proxmox to unraid for backups has a question mark on it and gives the following error

unable to activate storage 'backups' - directory '/mnt/pve/backups' does not exist or is unreachable (500)

findmnt shows

└─/mnt/pve/backups //10.0.3.20/backups

cifs rw,relatime,vers=3.1.1,cache=strict,username=csmashe,uid=0,noforceuid,gid=0,noforcegid,addr=10.0.3.20,file_mode

A reboot of the system fixes the issue but i can not find any other way to get it to recognize the drive anymore.

Unriad drives spin down but the backups share is set to cache yes and the cache drive never spins down so it is always available.

Any ideas please?

The feeling of not having enough time to finish all your tasks is real! Well, with monday.com’s work management platform, get more done in less time with automations, real-time communication, and notifications. Smash that done button! Try now.
Thumbnail image: The feeling of not having enough time to finish all your tasks is real! Well, with monday.com’s work management platform, get more done in less time with automations, real-time communication, and notifications. Smash that done button! Try now.
Sort by:
Best
Open comment sort options

If anyone else finds this because they are having the same issue it has been resolved.

The issue is when the mover moves the files from the cache drive in Unraid to the storage drive some information that linux uses is now stale and it breaks the share.

Fix is set your network share that you are using for proxmox to cache = no so you bypass the cache drive.

Oh my God, I think that was it. THANK YOU!

Where did you set that flag?

More replies
More replies

if i traverse to /mnt/pve/backups in the shell it works but if i ls i get

ls: cannot open directory '.': Stale file handle

I turned on NFS and redid the mount using that (was using SMB) and it is
now connected. I will see if it keeps the connection over night and
report back tomorrow if not.

Same issue is happening with NFS.

There is an error now in dmesg

[133319.065010] NFS: server 10.0.3.20 error: fileid changed fsid 0:159: expected fileid 0x3300000022801a, got 0x901000180000080

Any other ideas?

I have spun up a vm and connected to the mount point. I will see if its still connected tomorrow. Yes would mean its a proxmox issue, no would mean its an unraid issue.

Will add more info tomorrow

More replies
More replies

Next time it happens try “mount -a” and see if it comes back. If so then I’d just put it in Cron as an entry that starts every hour or so.

But you do have an underlying problem, machines don’t “just disconnect randomly”

TBH I think there’s a bunch of issues with the last couple of revisions of Proxmox with tons of problems, I just recently switched back to ESXI because of all of the problems I was having (literally killing my network problems)

the last couple of revisions of Proxmox with tons of problems, I just recently switched back to ESXI

mount -a did not bring it back.

I have not rebooted today so that i can run tests people send

More replies
More replies