Proxmox local “dir” storage mount disappeared

[hisokami98]

Hi all,
I’m stuck and need help recovering a local disk storage that held all my VM disks (~32TB).

Environment​

• PVE 8.4 cluster (4 node cluster)
• Each node has local storage only (not shared)
• The affected Local storage data-one contains ~32TB of VM disks (very important)

Problem​

The local "directory" storage data-one is no longer accessible/mounted

• Proxmox won’t start VMs that use data-one
• UI / CLI error: TASK ERROR: unable to activate storage 'data-one' - directory is expected to be a mount point but is not mounted: '/mnt/pve/data-one'

/etc/pve/storage.cfg :

dir: data-one
path /mnt/pve/data-one
content snippets,rootdir,iso,vztmpl,images,backup
is_mountpoint 1
nodes sni-one

when booting up :

Found 0 @8159
_common_interrupt: 124:55 No irq handler for vector
3 logical volume(s) in volume group "pve" now active
/dev/mapper/pve-root: clean, 89737/6291456 files, 9346723/25165824 blocks
/dev/mapper/pve-data: clean, 82/7864320 files, 48064/31457280 blocks
[DEPEND] Dependency failed for mnt-pve-data.mount
[DEPEND] Dependency failed for /mnt/pve-data
/dev/disk/by-uuid/8a7cdde7-487c-4a65-80a5-c632cddf6ab1
Timed out waiting for device /dev/disk/by-uuid/8a7cdde7-487c-4a65-80a5-c632cddf6ab1.

It tries to mount an ext4 filesystem by UUID, but:

• That UUID is no longer visible
• blkid and /dev/disk/by-uuid do not show it
• The disk itself (/dev/sda, ~32TB) is present, but no filesystem is detected

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 32.7T 0 disk
nvme0n1 259:0 0 1.7T 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 512M 0 part /boot/efi
└─nvme0n1p3 259:3 0 1.7T 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 96G 0 lvm /
├─pve-data_tmeta 252:2 0 15.8G 0 lvm
│ └─pve-data-tpool 252:4 0 1.6T 0 lvm
│ └─pve-data 252:5 0 1.6T 1 lvm
└─pve-data_tdata 252:3 0 1.6T 0 lvm
└─pve-data-tpool 252:4 0 1.6T 0 lvm
└─pve-data 252:5 0 1.6T 1 lvm


sda1 should be there as the mountpoint but its missing . please help me fix this , these are critical VMs. Are they gone ? what's the problem and how can i recover that?

​

 

[cheiss]

What kind of disk is /dev/sda? Is it a hardware RAID?

Can you provide the output of lsblk --ascii -M -o +HOTPLUG,ROTA,PHY-SEC,FSTYPE,MODEL,TRAN,WWN /dev/sda and file -s /dev/sda? (You may need to install the file package for the latter first)

Also, do you (hopefully!) have any backups?

 

[hisokami98]

What kind of disk is /dev/sda? Is it a hardware RAID?

Can you provide the output of lsblk --ascii -M -o +HOTPLUG,ROTA,PHY-SEC,FSTYPE,MODEL,TRAN,WWN /dev/sda and file -s /dev/sda? (You may need to install the file package for the latter first)

Also, do you (hopefully!) have any backups?

The problem is fixed . The problem was that the partition table was missing, so Linux could see the disk but didn’t know where the filesystem started.
TestDisk recreated the partition table pointing to the existing ext4 filesystem, which made /dev/sda1 visible again and allowed Proxmox to mount /mnt/pve/data-one without touching the data. thank you.