unable to activate storage 'DIR01' - directory is expected to be a mount point but is not mounted: '/mnt/pve/DIR01' (500)

[adalimumab]

Hi everyone. Unfortunately by hard drives no longer appear to be recognized by proxmox. I am able to see them within TrueNas. I am having issues with DIR01 and DIR 02

the storage.cfg is following

root@pve0:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,backup,vztmpl

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

dir: DIR01
        path /mnt/pve/DIR01
        content snippets,iso,rootdir,images,backup,vztmpl
        is_mountpoint 1
        nodes pve0
        shared 0

dir: DIR02
        path /mnt/pve/DIR02
        content vztmpl,iso,snippets,rootdir,backup,images
        is_mountpoint 1
        nodes pve0
        shared 0

systemctl status mnt-pve-disc_images.mount is following

Unit mnt-pve-disc_images.mount could not be found.

lsblk is following

NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                            8:0    0   3.6T  0 disk
├─sda1                         8:1    0     2G  0 part
└─sda2                         8:2    0   3.6T  0 part
sdb                            8:16   0   3.6T  0 disk
├─sdb1                         8:17   0     2G  0 part
└─sdb2                         8:18   0   3.6T  0 part
nvme0n1                      259:0    0 931.5G  0 disk
├─nvme0n1p1                  259:1    0  1007K  0 part
├─nvme0n1p2                  259:2    0     1G  0 part
└─nvme0n1p3                  259:3    0 930.5G  0 part
  ├─pve-swap                 253:0    0     8G  0 lvm  [SWAP]
  ├─pve-root                 253:1    0    96G  0 lvm  /
  ├─pve-data_tmeta           253:2    0   8.1G  0 lvm 
  │ └─pve-data-tpool         253:4    0 794.3G  0 lvm 
  │   ├─pve-data             253:5    0 794.3G  1 lvm 
  │   ├─pve-vm--101--disk--0 253:6    0    32G  0 lvm 
  │   ├─pve-vm--100--disk--0 253:7    0   100G  0 lvm 
  │   ├─pve-vm--200--disk--0 253:8    0     4M  0 lvm 
  │   └─pve-vm--200--disk--1 253:9    0   100G  0 lvm 
  └─pve-data_tdata           253:3    0 794.3G  0 lvm 
    └─pve-data-tpool         253:4    0 794.3G  0 lvm 
      ├─pve-data             253:5    0 794.3G  1 lvm 
      ├─pve-vm--101--disk--0 253:6    0    32G  0 lvm 
      ├─pve-vm--100--disk--0 253:7    0   100G  0 lvm 
      ├─pve-vm--200--disk--0 253:8    0     4M  0 lvm 
      └─pve-vm--200--disk--1 253:9    0   100G  0 lvm

/etc/fstab is the following:

root@pve0:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
root@pve0:~#

 

[bbgeek17]

PVE is expecting these locations (/mnt/pve/DIR02 and /mnt/pve/DIR01) to be mounted. It is not responsible for mounting them, you are.
What makes you think that "mnt-pve-disc_images.mount" is something that should exist? Did you ever create that manually? If you did - what has changed recently?
What is the output of "ls -al /etc/fstab" ?
If you know which drives/partitions (sda,sdb,etc) should match the above mountpoins - add them to fstab.

Good luck

---

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

 

[Dunuin]

Unfortunately by hard drives no longer appear to be recognized by proxmox. I am able to see them within TrueNas.

I hope you don't mount them on the PVE host as well as passing them through into a VM using disk passthrough. This would sooner or later corrupt your data...

 

[adalimumab]

I hope you don't mount them on the PVE host as well as passing them through into a VM using disk passthrough. This would sooner or later corrupt your data...

Good to know. New to this my apologies. I presume if I dismount the HDDs from the PVE host, TrueNAS will not be able to access them?

 

[Dunuin]

I presume if I dismount the HDDs from the PVE host, TrueNAS will not be able to access them?

No, thats how its supposed to be done. You can either mount it within TrueNAS only or within PVE only. Not both at the same time. Block devices aren't made for this. Like you can't attach a physical Disk to two PCs at the same time.
If you want to access your data from multiple OSs you need to mount it to only one OS and then run a NFS/SMB server there, so other OSs can indirektly access them over the network using NFS/SMB shares.

And as mounting the disks filesystems is failing now, you probalby already damaged your data. I would restore the data from a backup you made before mounting the disk the first time or at least run a scrub or fsck to check your filesystems for data integrity.

 

[adalimumab]

No, thats how its supposed to be done. You can either mount it within TrueNAS only or within PVE only. Not both at the same time. Block devices aren't made for this. Like you can't attach a physical Disk to two PCs at the same time.
If you want to access your data from multiple OSs you need to mount it to only one OS and then run a NFS/SMB server there, so other OSs can indirektly access them over the network using NFS/SMB shares.

And as mounting the disks filesystems is failing now, you probalby already damaged your data. I would restore the data from a backup you made before mounting the disk the first time or at least run a scrub or fsck to check your filesystems for data integrity.

Thanks so much, Dunuin. From a conceptual standpoint, I plan to use TrueNAS as a NAS only. I will be managing VM's primarily from PVE. I presume it would be best practice to have my HDD's mounted to PVE and access the storage via NFS with TrueNAS?

 

[Dunuin]

Thanks so much, Dunuin. From a conceptual standpoint, I plan to use TrueNAS as a NAS only. I will be managing VM's primarily from PVE. I presume it would be best practice to have my HDD's mounted to PVE and access the storage via NFS with TrueNAS?

PVE doesn't offer any NAS functionalities. You can run a SMB/NFS server, but then you have to install and manage that using the CLI yourself, like you would do it with any normal headless Debian server.

Best would be to get a HBA card with some dedicated disks for that NAS only and then use PCI passthrough to passthrough the whole HBA card including all disks attached to it into the TrueNAS VM. If that is not an option, then at least dedicated disks for your TrueNAS with disk passthrough.

Other options could be:
- different partitions and then use disk passthorugh to passthough a partition instead of the whole disk (but not unproblematic...for example Win doesn't like that)
- put a virtual disk on that storage mounted on PVE and use that virtual disk with TrueNAS. But this will add overhead.

 

[adalimumab]

Thank you again. I opted to go the NFS share route on TrueNAS with disk passthrough. Your explanation really helped a lot with conceptualizing storage.