Storage is not connected- status Unknown.

slv

New Member
Jun 3, 2022
2
0
1
Good afternoon!
After pve3 is normaly shutdown, vmx storage is not connected- status Unknown. HA status pve 3 - wait_for_agent_lock.
Pve1, pve2, is ok!

please help me solve the problem.

1654239525316.png
1654239448862.png


systemctl status mnt.service
Loaded: loaded (/etc/systemd/system/mnt.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-06-02 16:49:19 +04; 17h ago
Process: 18959 ExecStart=/sbin/cryptsetup open /dev/pve/ls_vz vz --key-file /dev/disk/by-uuid/2018-11-14-16-35-14-0
Main PID: 18959 (code=exited, status=1/FAILURE)

pve3 systemd[1]: Starting mnt.service...
pve3 cryptsetup[18959]: the key file could not be opened.
pve3 systemd[1]: mnt.service: Main process exited, code=exited, status=1/FAILURE
pve3 systemd[1]: mnt.service: Failed with result 'exit-code'.
pve3 systemd[1]: Failed to start mnt.service.
 

Attachments

  • 1654239147934.png
    1654239147934.png
    78 KB · Views: 29
  • 1654239836117.png
    1654239836117.png
    17.9 KB · Views: 30
  • pvereport.txt
    pvereport.txt
    81.7 KB · Views: 5
Last edited:
Hi,

thx for the report. Makes it much quicker to check stuff :). According to it, you don't have a volume group named "vmx" only pve exist as a volume group. On which disk(s) do you set up that volume group?

Code:
# vgs
  /dev/sdb: open failed: No medium found
  VG  #PV #LV #SN Attr   VSize VFree  
  pve   1   4   0 wz--n- 1.09t <16.00g
 
vmx- cluster's storage, iSCSI from HP MSA2050.
why vmx is not mounted?
how to reconnect vmx?

pve3:/# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1,1T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 256M 0 part /boot/efi
└─sda3 8:3 0 1,1T 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 10G 0 lvm
│ └─pve-data-tpool 253:4 0 977,6G 0 lvm
│ ├─pve-data 253:5 0 977,6G 0 lvm
│ └─pve-ls_vz 253:6 0 600G 0 lvm
└─pve-data_tdata 253:3 0 977,6G 0 lvm
└─pve-data-tpool 253:4 0 977,6G 0 lvm
├─pve-data 253:5 0 977,6G 0 lvm
└─pve-ls_vz 253:6 0 600G 0 lvm
sdc 8:32 0 1,5T 0 disk
└─3600c0ff0003cbd82320bfc5b01000000 253:7 0 1,5T 0 mpath
sdd 8:48 0 1,5T 0 disk
└─3600c0ff0003cbd82320bfc5b01000000 253:7 0 1,5T 0 mpath
sde 8:64 0 1,5T 0 disk
└─3600c0ff0003cbd82320bfc5b01000000 253:7 0 1,5T 0 mpath
sdf 8:80 0 1,5T 0 disk
└─3600c0ff0003cbd82320bfc5b01000000 253:7 0 1,5T 0 mpath
sdg 8:96 0 6,5T 1 disk
sdh 8:112 0 6,5T 1 disk
sdi 8:128 0 6,5T 1 disk



PVE2 - ok.

@pve2:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 256M 0 part
└─sda3 8:3 0 931,2G 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 104M 0 lvm
│ └─pve-data-tpool 253:4 0 811,2G 0 lvm
│ ├─pve-data 253:5 0 811,2G 0 lvm
│ ├─pve-vm--140--disk--1 253:6 0 71G 0 lvm
│ └─pve-ls_vz 253:7 0 500G 0 lvm
│ └─vz 253:10 0 500G 0 crypt /var/lib/vz
└─pve-data_tdata 253:3 0 811,2G 0 lvm
└─pve-data-tpool 253:4 0 811,2G 0 lvm
├─pve-data 253:5 0 811,2G 0 lvm
├─pve-vm--140--disk--1 253:6 0 71G 0 lvm
└─pve-ls_vz 253:7 0 500G 0 lvm
└─vz 253:10 0 500G 0 crypt /var/lib/vz
sdb 8:16 1 7,3G 0 disk
└─sdb1 8:17 1 7,3G 0 part
sdd 8:48 0 1,5T 0 disk
└─3600c0ff0003cbd82320bfc5b01000000 253:9 0 1,5T 0 mpath
└─vmx 253:11 0 1,5T 0 crypt
├─vmx-vm--143--disk--0 253:12 0 8G 0 lvm
├─vmx-vm--104--disk--0 253:13 0 10G 0 lvm
├─vmx-vm--144--disk--0 253:14 0 110G 0 lvm
├─vmx-vm--142--disk--0 253:15 0 64G 0 lvm
├─vmx-vm--130--disk--0 253:16 0 16G 0 lvm
├─vmx-vm--126--disk--0 253:17 0 16G 0 lvm
├─vmx-vm--123--disk--0 253:18 0 10G 0 lvm
├─vmx-vm--102--disk--0 253:19 0 24G 0 lvm
├─vmx-vm--106--disk--0 253:20 0 16G 0 lvm
├─vmx-vm--139--disk--0 253:21 0 32G 0 lvm
├─vmx-vm--145--disk--0 253:23 0 90G 0 lvm
├─vmx-vm--103--disk--0 253:24 0 80G 0 lvm
├─vmx-vm--105--disk--0 253:25 0 64G 0 lvm
├─vmx-vm--146--disk--0 253:26 0 90G 0 lvm
├─vmx-vm--147--disk--0 253:27 0 40G 0 lvm
├─vmx-vm--148--disk--0 253:28 0 16G 0 lvm
├─vmx-vm--150--disk--0 253:29 0 164G 0 lvm
├─vmx-vm--135--disk--0 253:30 0 15G 0 lvm
├─vmx-vm--151--disk--0 253:31 0 32G 0 lvm
├─vmx-vm--152--disk--0 253:32 0 24G 0 lvm
├─vmx-vm--153--disk--0 253:33 0 8G 0 lvm
├─vmx-vm--154--disk--0 253:34 0 64G 0 lvm
├─vmx-vm--156--disk--0 253:35 0 16G 0 lvm
├─vmx-vm--157--disk--0 253:36 0 16G 0 lvm
├─vmx-vm--141--disk--2 253:38 0 32G 0 lvm
├─vmx-vm--141--disk--3 253:39 0 32G 0 lvm
├─vmx-vm--141--disk--0 253:40 0 16G 0 lvm
├─vmx-vm--141--disk--1 253:41 0 64G 0 lvm
└─vmx-vm--149--disk--0 253:42 0 64G 0 lvm
sde 8:64 0 1,5T 0 disk
└─3600c0ff0003cbd82320bfc5b01000000 253:9 0 1,5T 0 mpath
└─vmx 253:11 0 1,5T 0 crypt
├─vmx-vm--143--disk--0 253:12 0 8G 0 lvm
├─vmx-vm--104--disk--0 253:13 0 10G 0 lvm
├─vmx-vm--144--disk--0 253:14 0 110G 0 lvm
├─vmx-vm--142--disk--0 253:15 0 64G 0 lvm
├─vmx-vm--130--disk--0 253:16 0 16G 0 lvm
├─vmx-vm--126--disk--0 253:17 0 16G 0 lvm
├─vmx-vm--123--disk--0 253:18 0 10G 0 lvm
├─vmx-vm--102--disk--0 253:19 0 24G 0 lvm
├─vmx-vm--106--disk--0 253:20 0 16G 0 lvm
├─vmx-vm--139--disk--0 253:21 0 32G 0 lvm
├─vmx-vm--145--disk--0 253:23 0 90G 0 lvm
├─vmx-vm--103--disk--0 253:24 0 80G 0 lvm
├─vmx-vm--105--disk--0 253:25 0 64G 0 lvm
├─vmx-vm--146--disk--0 253:26 0 90G 0 lvm
├─vmx-vm--147--disk--0 253:27 0 40G 0 lvm
├─vmx-vm--148--disk--0 253:........
 
The Proxmox storage.cfg expects to find a a volume group named vmx. But as you can see it is not visible on that one server. What I see is that you have some crypt volume on the other servers. They might be encrypted volumes. Check your
Code:
/etc/fstab[/icode] there to hopefully see how it is mounted.