[SOLVED] pvesm shows nfs share inactive after it rebooted. How to re Activate or Re add a Storage volume?

[SoMoney]

I have an NFS Appliance called 'BIGNAS' that rebooted and came back up.

Proxmox however doesn't appear to assume nfs volumes ever come back and has it listed "inactive"

root@pve:~# pvesm status
unable to activate storage 'BIGNAS' - directory '/mnt/pve/BIGNAS' does not exist or is unreachable
Name Type Status Total Used Available %
BIGNAS nfs inactive 0 0 0 0.00%
NVME-STORE zfspool active 1885339477 62541565 1822797911 3.32%
local dir active 432959232 17643520 415315712 4.08%
local-zfs zfspool active 453672344 38356548 415315796 8.45%
root@pve:~

I Removed the storage volume, REBOOTED PROXMOX, and now when I try and add it back I'm greeted with the following error.




create storage failed: error with cfs lock 'file-storage_cfg': mkdir /mnt/pve/BIGNAS/template: Read-only file system at /usr/share/perl5/PVE/Storage/Plugin.pm line 1030. (500)



[SOLVED] DISCOVERY::
"/mnt/pve/********' does not exist" : Can also indicate the NFS mount does not have WRITE permission to create the 'images','templates', etc directories needed BEFORE the /mnt/pve/***** mount on proxmox is allowed....

 

[wolfgang]

Hi,
did you change something on the NAS like an update of the Software?
What PVE version do you use?

 

[SoMoney]

No Adds, what happened to start this was my NAS had the wrong saved subnet mask and became unresponsive after a reboot. I since corrected the subnetting issue and can ping and telnet to the SMB port on the nas, but ProxMox can't seam to make changes to its r/o filesystem configs.. I'm Running 6.1-3

I can see it and confirmed basic NFS connectivity is there:::
root@pve:~# telnet BIGNAS 111
Trying 192.168.1.11...
Connected to BIGNAS.
Escape character is '^]'.


Connection closed by foreign host.
root@pve:~#



I think I'll need to add the volume back Manually from the command line somehow mounting the volume r/w and getting the needed config change and /mnt/pve/BIGNAS directory in that way... Dunno though...

 

[oguz]

hi,

PVE is trying to create the directory structure while creating the storage

maybe you just need to check the file permissions on the NFS and make sure you have write access

 

[SoMoney]

Hey, there you go!

I had R/O permissions for my BIGNAS:/ISO volume and that worked originally.

I Set BIGNAS:/ISO to read/write and that seems to have woken it up!

Dont know why my QNAP decided to enforce all of a sudden... Maybe some weird bug with my QNAP but Im working again...

Thanks!

 

[oguz]

great, you can mark the thread as [SOLVED] so others with the same problem know what to expect!

 

[SoMoney]

Will do, FYI the error message for the user should indicate the "Write to NFS was unsuccessful". This would have focused my attention on the NFS read/write access, not only " '/mnt/pve/BIGNAS' does not exist " and saved me/us some time...