[SOLVED] Unraid Storage Mount Questions

[jShomp]

The other day I added an Unraid CIFS share to Storage which I use for backups, and everything was working perfect fine. After rebooting Prox today I started some backups, the first one went through fine, but then the others I tried said it couldn't find the mount, and when I clicked on the storage link under the pve node it showed the same error. I'm guessing it has something to do with Unraid also being a VM in Proxmox(it was up and running before I started the backups). Other than adding it through the GUI is there anything else I need to do avoid such issues with Storage mounts, especially with Unraid being a VM? I haven't added it to fstab because frankly I'm not sure what needs to go in there, or if it even should be added. I'm not a Linux expert and still green when it comes to Prox.

 

[Dunuin]

You should exclude your Unraid VM from the backup job so the SMB share won't get interupted when doing backups to it. Same for network related VMs like a virtualized OPNsense/pfsense in case routing is needed to access the SMB share.

 

[jShomp]

You should exclude your Unraid VM from the backup job so the SMB share won't get interupted when doing backups to it. Same for network related VMs like a virtualized OPNsense/pfsense in case routing is needed to access the SMB share.

Thank you, and let me clarify, I'm not trying to back up Unraid, only my other Linux/Windows OS VMs to the Unraid share. Also I'm not doing by job yet, I've just been kicking off manual backups.

After recreating the storage again everything is working fine, but just trying to avoid having to do that every time I reboot Proxmox, especially if I start adding more shares.

Here's an example of what I'm doing with it, just a basic backup.

 

[jShomp]

I rebooted and it happened again though I was able to manually backup one VM to Unraid which completed successfully, and immediately after it's unreachable. I can still access the Unraid share from my PC without any issue. No network related VMs are currently installed, and all my VMs were shutdown except for Unraid.

 

[jShomp]

I woke up this morning and the mount seemingly fixed itself, I queued 2 backups and the first was successful, then the 2nd one failed to start because the mount is unreachable again. So it seems unrelated to reboots, something is happening after a backup completes. Any ideas?

 

[jShomp]

In case anyone is interested, this appears to be an Unraid issue and there are 3 potential workarounds, none desirable and all can be done from the Unraid GUI:

Enable SMB1(enabling NetBios for SMB effectively does this)
Disable the cache drive on the share(the workaround I'm using and it did "fix" the issue)
Disable hardlinks(under Global Share Settings)

 

[Neobin]

In case anyone is interested, this appears to be an Unraid issue and there are 3 potential workarounds, none desirable and all can be done from the Unraid GUI:

Enable SMB1(enabling NetBios for SMB effectively does this)
Disable the cache drive on the share(the workaround I'm using and it did "fix" the issue)
Disable hardlinks(under Global Share Settings)

This problem seems to be around for a while:

• https://forum.proxmox.com/threads/unable-to-activate-storage-cifs-mount-dies-randomly.58922
• https://forum.proxmox.com/threads/vm-internal-disk-ata-errors-nfs-share-disconnecting.116119
• https://forums.unraid.net/topic/86707-cifs-smb-stale-file-handle

Only for reference...