Dependency failed for mnt-pve-storage.mount, can't find UUID (new to Linux, need some help)

jptruong

New Member
Mar 18, 2025
5
0
1
Hello,

Want to first apologize for any mis-used terminology, new with Proxmox. Well, Linux as a whole. Please bear with me.

So I picked up 3x Intel NUCs to create a Proxmox Cluster. Put things together, followed guides (written & YouTube) and got it to work, until I had to shut off the power for some electrical maintenance and now USB hard drive is not.. mounting(?).

I don't recall the exact steps of what I did, but will try to do so (as best as I can).

I have a USB hard drive
Plugged it in and it recognizes (ProxVE1 -> Disks -> /dev/sdb)
Created a directory (ProxVE1 -> Directory -> Create: Directory -> Disk: /dev/sdb -> FileSystem: xfs -> Name: myStorage)

chrome_vHJAh9bzTw.png

Forgot what else I did, maybe that's all.

Created a VM with TrueNas and was able to add "myStorage" using
Code:
qm set 101 -scsi1 /dev/disk/by-id/ata-ST8000NE0001-1WN112_ZA1299AM

EVERYTHING was working at this point. Created a Samba shared. Recognized it in Windows. It was working, I was feeling like a champion.... UNTIL I had to shut the breaker to the outlet that my beginner homelab was connected to.

I then tried to find the UUID of this external USB device.

Using blkid -sUUID, I don't see /dev/sdb or /dev/sdb1
Code:
root@ProxVE1:~# blkid -sUUID
/dev/mapper/pve-root: UUID="03322808-a201-4980-8feb-3e16c9c6f829"
/dev/nvme0n1p3: UUID="3Wzg0f-Pw5x-or1P-tuQu-tJcC-hKFk-R7ACV2"
/dev/nvme0n1p2: UUID="4F8E-3F39"
/dev/mapper/pve-swap: UUID="0e5a648f-8ec7-46df-8bd4-033aacc2cef0"
/dev/sda1: UUID="7530762269339758001"
/dev/zd0p3: UUID="14514589222447508440"
/dev/zd0p2: UUID="7662-E3CF"
/dev/zd16p2: UUID="787e8279-b186-4b21-b43e-e297c6585a3c"
/dev/zd16p3: UUID="V4asev-b6c0-A04v-3bHX-1UY4-neiI-blNQAe"

Using ls -l /dev/disk/by-uuid
Code:
root@ProxVE1:~# ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Mar 17 15:58 03322808-a201-4980-8feb-3e16c9c6f829 -> ../../dm-1
lrwxrwxrwx 1 root root 10 Mar 17 15:58 0e5a648f-8ec7-46df-8bd4-033aacc2cef0 -> ../../dm-0
lrwxrwxrwx 1 root root 11 Mar 17 15:58 14514589222447508440 -> ../../zd0p3
lrwxrwxrwx 1 root root 15 Mar 17 15:58 4F8E-3F39 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 10 Mar 17 15:58 7530762269339758001 -> ../../sda1
lrwxrwxrwx 1 root root 11 Mar 17 15:58 7662-E3CF -> ../../zd0p2
lrwxrwxrwx 1 root root 12 Mar 17 15:58 787e8279-b186-4b21-b43e-e297c6585a3c -> ../../zd16p2

Somewhere along the line, I used lshw and fdisk -l
I do see that the drive is there with fdisk -l but no UUID. I'm so confused.

checking systemctl status mnt-pve-myStorage.mount
Code:
root@ProxVE1:~# systemctl status mnt-pve-myStorage.mount
× mnt-pve-myStorage.mount - Mount storage 'myStorage' under /mnt/pve
     Loaded: loaded (/etc/systemd/system/mnt-pve-myStorage.mount; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2025-03-17 16:40:32 PDT; 10s ago
      Where: /mnt/pve/myStorage
       What: /dev/disk/by-uuid/6dca959d-a47a-445f-9c28-c8c48e40d8ee
        CPU: 1ms

Mar 17 16:40:32 ProxVE1 systemd[1]: Mounting mnt-pve-myStorage.mount - Mount storage 'myStorage' under /mnt/pve...
Mar 17 16:40:32 ProxVE1 mount[13026]: mount: /mnt/pve/myStorage: special device /dev/disk/by-uuid/6dca959d-a47a-445f-9c28-c8c48e40d8ee does not exist.
Mar 17 16:40:32 ProxVE1 mount[13026]:        dmesg(1) may have more information after failed mount system call.
Mar 17 16:40:32 ProxVE1 systemd[1]: mnt-pve-myStorage.mount: Mount process exited, code=exited, status=32/n/a
Mar 17 16:40:32 ProxVE1 systemd[1]: mnt-pve-myStorage.mount: Failed with result 'exit-code'.
Mar 17 16:40:32 ProxVE1 systemd[1]: Failed to mount mnt-pve-myStorage.mount - Mount storage 'myStorage' under /mnt/pve.

What happened to my /dev/disk/by-uuid/6dca959d-a47a-445f-9c28-c8c48e40d8ee ?! I don't know, please help! Thanks in advance!
 
What does just "blkid" show ?
PS: However an uuid of a device and a filesystem are not the same.
 
Last edited:
What does just "blkid" show ?
PS: However an uuid of a device and a filesystem are not the same.
Code:
root@ProxVE1:~# blkid
/dev/mapper/pve-root: UUID="03322808-a201-4980-8feb-3e16c9c6f829" BLOCK_SIZE="512" TYPE="xfs"
/dev/nvme0n1p3: UUID="3Wzg0f-Pw5x-or1P-tuQu-tJcC-hKFk-R7ACV2" TYPE="LVM2_member" PARTUUID="68c584cb-1b51-4475-9aee-4a3f39ca3ed0"
/dev/nvme0n1p2: UUID="4F8E-3F39" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="33874559-7cf2-47e9-88b2-9015f3c4fa4f"
/dev/mapper/pve-swap: UUID="0e5a648f-8ec7-46df-8bd4-033aacc2cef0" TYPE="swap"
/dev/sda1: LABEL="LocalZFS" UUID="7530762269339758001" UUID_SUB="9484680857488844998" BLOCK_SIZE="4096" TYPE="zfs_member" PARTLABEL="zfs-6da5cb8d9ed70c84" PARTUUID="7c2a5645-86e1-fa43-b233-df6cb1d09d29"
/dev/zd0p3: LABEL="boot-pool" UUID="14514589222447508440" UUID_SUB="7375156172452890898" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="ea884151-4201-4bfb-8002-ea0a911812fd"
/dev/zd0p2: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="7662-E3CF" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="cf1eadcf-e743-4497-8fb2-112ef2665d7b"
/dev/zd16p2: UUID="787e8279-b186-4b21-b43e-e297c6585a3c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1fe232a1-a97d-4cce-a012-c241774b070a"
/dev/zd16p3: UUID="V4asev-b6c0-A04v-3bHX-1UY4-neiI-blNQAe" TYPE="LVM2_member" PARTUUID="cdde67ce-b500-4ed2-ae6f-f93e99d2011f"
/dev/nvme0n1p1: PARTUUID="e183e3aa-183b-44b9-8119-377f5458ab06"
/dev/zd0p1: PARTUUID="def706f0-90f5-491d-ad95-d442300131c0"
/dev/zd16p1: PARTUUID="cedd75ae-80a2-4df3-bba7-63b1c4267def"
/dev/sda9: PARTUUID="f0e54ec8-72fc-e84e-a03a-021ea48b470a"

I think I need the UUID to properly mount the drive. I do believe I read that I should be editing /etc/fstab so it can mount after restarts.

chrome_sCuxkAaAKB.png
 
Still wondering what you made with like lvm on zfs pve inst ... but anyway ...
your usb disk isn't recognized anymore yet this time.
 
Still wondering what you made with like lvm on zfs pve inst ... but anyway ...
your usb disk isn't recognized anymore yet this time.
My apologies. I'm new to this and I'm not sure where I'm looking at/for the zfs pve inst, you're referring to. This is still a learning curve for me.

I noticed that other commands, show the existence of the USB disk, take for instance fdisk -l , does that help?
Code:
root@ProxVE1:~# fdisk -l /dev/sdb
Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: 2115
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 34D1BB5F-0816-480F-9CF3-EF2165DEA4C4

Device     Start         End     Sectors  Size Type
/dev/sdb1   2048 15628052479 15628050432  7.3T Linux filesystem

Also, thank you for your responses.

edit:
using LSHW -short
Code:
/0/100/14/1/4/0.0.0    /dev/sdb        disk           8001GB 2115
/0/100/14/1/4/0.0.0/1  /dev/sdb1       volume         7452GiB EFI partition
 
Last edited:
That's not healty to the kernel ... seeing sdb by fdisk but not with blkid.
What about a test mount like "xfs_info /dev/sdb1 ; mount /dev/sdb1 /net ; df" ?
 
That's not healty to the kernel ... seeing sdb by fdisk but not with blkid.
What about a test mount like "xfs_info /dev/sdb1 ; mount /dev/sdb1 /net ; df" ?
Code:
root@ProxVE1:~# xfs_info /dev/sdb1 ; mount /dev/sdb1 /net ; df
xfs_info: error - read only 0 of 4096 bytes
xfs_info: data size check failed
Metadata CRC error detected at 0x5a3b14b3c330, xfs_agf block 0x8/0x1000
xfs_info: cannot init perag data (74). Continuing anyway.
meta-data=/dev/sdb1              isize=512    agcount=8, agsize=268435455 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1    bigtime=1 inobtcount=1 nrext64=0
data     =                       bsize=4096   blocks=1953506385, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=521728, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
mount: /net: more filesystems detected on /dev/sdb1; use -t <type> or wipefs(8).
Filesystem                 1K-blocks    Used Available Use% Mounted on
udev                         7606672       0   7606672   0% /dev
tmpfs                        1528112    2920   1525192   1% /run
/dev/mapper/pve-root       100597760 9504516  91093244  10% /
tmpfs                        7640556   67488   7573068   1% /dev/shm
tmpfs                           5120       0      5120   0% /run/lock
efivarfs                         128      51        73  42% /sys/firmware/efi/efivars
/dev/nvme0n1p2               1046512   11944   1034568   2% /boot/efi
LocalZFS                   397758720     128 397758592   1% /LocalZFS
LocalZFS/subvol-102-disk-0   8388608 1378176   7010432  17% /LocalZFS/subvol-102-disk-0
/dev/fuse                     131072      28    131044   1% /etc/pve
tmpfs                        1528108       0   1528108   0% /run/user/0
 
That xfs is broken by any mixture of misused commands before.
Yikes... yea, I did try multiple commands I found online. Something may have made it worse.... /shrug

Going to try "TestDisk"(found this recommended on a few sites) and see if it can fix it but if not, I'll just have to wipe it and try again. If I can back up the information in the drive that'll be great. So fingers crossed..

I, unfortunately, do not have the drive backed up, no raid, nada... low budget homelab, oh wells. Thanks again for the help though!