External HDD missing after reboot. vm-115-disk-0.raw' does not exist

[Kavil194]

Hello Everyone.
I have 1 SATA 2 TB HDD connected to Proxmox host using USB 3.0 with external power supply.
It is added to system and Frigate LXC container is only user of it for NVR storage. It was working non stop for 6 days without a problem and i had to shutdown and reboot PVE today for physical maintenance. After rebooting i receve the following error of the Frigate LXC when it starts to boot up.

()
TASK ERROR: volume 'NVR2TB:115/vm-115-disk-0.raw' does not exist

I have checked my Datacenter and disks, partitions. It everything seems okay there.



However when i go inside the mounted volume it is around 100 gb (it should be 1.75 Tb) I am able to access and touch txt files without problem so disk is alive and responding.



I could format it and start over from my backup config for Frigate etc but before doing it i would like to learn the cause of this problem and remedy it so that it does not happen in the future. I have tried to shutdown everything and start HDD first then proxmox host later but it still does not solve the issue, only accessible partition is around 100 GB on the external HDD even though it shows single partition with 1.8 TB size.

Thank you for an kind of help.

 

[Onslow]

Hi,
what exactly does "when i go inside the mounted volume" mean?

I'm asking about factual commands you issued and where you issued them

Edit: please post the output of df -hT

 

[Kavil194]

Hi,
what exactly does "when i go inside the mounted volume" mean?

I'm asking about factual commands you issued and where you issued them

Edit: please post the output of df -hT

Thank you for the speedy reply.

I mean when i go on the host machine using Shell cd /mnt/NVR2TB and using FileBrowser quantum Addon and using WEB Gui and creating reading removing files on the mounted volume. http://10.0.0.20:8080/files/mnt/NVR2TB

our put of the requested command.

Filesystem            Type      Size  Used Avail Use% Mounted on
udev                  devtmpfs  7.7G     0  7.7G   0% /dev
tmpfs                 tmpfs     1.6G  3.2M  1.6G   1% /run
/dev/mapper/pve-root  ext4       94G  5.5G   84G   7% /
tmpfs                 tmpfs     7.7G   34M  7.7G   1% /dev/shm
efivarfs              efivarfs  246K  180K   62K  75% /sys/firmware/efi/efivars
tmpfs                 tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs                 tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs                 tmpfs     7.7G     0  7.7G   0% /tmp
/dev/nvme0n1p2        vfat     1022M  8.8M 1014M   1% /boot/efi
/dev/fuse             fuse      128M   32K  128M   1% /etc/pve
tmpfs                 tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
//10.0.0.5/FrigateNVR cifs      5.0T  617M  5.0T   1% /mnt/pve/FrigateNVR
//10.0.0.5/Video      cifs      2.5T  264G  2.3T  11% /mnt/pve/Video
//10.0.0.5/PVE-Backup cifs      3.0T  753G  2.3T  25% /mnt/pve/PVE
//10.0.0.5/Audio      cifs      2.5T  264G  2.3T  11% /mnt/pve/Audio
tmpfs                 tmpfs     1.6G  8.0K  1.6G   1% /run/user/0

Strangely i do not see 2TB drive here. this might be the problem even though i can access the volume under mounted folder structure.

 

[Kavil194]

Ok for any rookies like i am the problem is apparently my mounted HDD was not persistent and only available on the current session. Which after reboot automaticly dismounted itself. After running this command on the Proxmox shell i am able to get the container raw file and able so start it.
mount /dev/sda1 /mnt/NVR2TB

I have avoided adding it to fstab because last time i have done it and had to remove external HDD, entire proxmox host became unresponsive. Maybe i have done something not correctly last time and would open to suggestions how to do it properly so that it does not prevents proxmox from booting incase of HDD removal and/or failure.

 

[Impact]

Use the nofail option

UUID=UUID_FROM_BLKID_HERE /mnt/NVR2TB ext4 defaults,nofail 0 2

Make sure the /mnt/NVR2TB path (when unmounted) is immutable. See here for more information.

 

[Onslow]

Ok for any rookies like i am the problem is apparently my mounted HDD was not persistent and only available on the current session. Which after reboot automaticly dismounted itself.

This was one of my suspicions and that's why I asked for df -hT

I have avoided adding it to fstab because last time i have done it and had to remove external HDD, entire proxmox host became unresponsive.

Yeah, one of Systemd "innovations" in the way devices are tried to be mounted during start of a machine...