[SOLVED] Storage status unknown

[realamd]

I have 2 identical servers that I have install promox on. After fresh install of proxmox, I created the local storage on each server and then proceeded to join the hosts to a single cluster. However, I noticed that the volume group that I created on "maryland" shows the wrong label and has a grey question mark on it and when i hover over it, it says "status unknown". Attached a screenshot.

What seems to be the issue here?

 

[fiona]

Hi,
you need to add an entry to /etc/pve/storage.cfg for each distinct storage and limit availability to nodes. The configuration is shared across nodes, so you can't have a local version of it. You can use pvesm the web GUI Datacenter>Storage.

If I understand correctly, you'll need to create one storage with volume group mdstorage and restrict it to the node maryland and you'll need to restrict the vastorage to the node virginia

 

[realamd]

Hi Fabian,

What do I need to put in the /etc/pve/storage.cfg file?

I followed this tutorial to add the secondary disks to each host and after creating the cluster and joining maryland to virginia cluster, i noticed the issue.

How do I restrict each volume group (vastorage, mdstorage) to their respective nodes?

 

[realamd]

I solved my own questions.

For those who are looking at the same issue, here is what I did:

Datacenter > Storage > Add [LVM]

Type something for ID, select existing storage and pick the right volume group, select the apprpriate node to restrict it to click add.

Then click on the other (in my case vastorage) and click edit, restrict this to your node (in my case virginia) and click OK.

All good now

 

[Eria Rurunga]

any help, I have dell poweredge server, after the power outage and it looks like this, i cannot access encomputing

 

[fiona]

Hi,

any help, I have dell poweredge server, after the power outage and it looks like this, i cannot access encomputing

I'd start with checking the boot log about LVM-related errors. What is the output of the following

lvs
pvs
vgs

?

 

[roberto_fx]

We also have the same issue... the strange thing is that most hard drives come up except a couple of them..
It seems to happen every time we do a restart (not that it happens often)... and it takes about 5 mins per drive to re-enable.... i.e. downtime.
We're not in any HA nor even regular clustering scenario.
Interestingly also on a Dell poweredge (R550).

How do we make sure it doesn't happen in the future?

 

[fiona]

Hi,

We also have the same issue... the strange thing is that most hard drives come up except a couple of them..
It seems to happen every time we do a restart (not that it happens often)... and it takes about 5 mins per drive to re-enable.... i.e. downtime.

How do we make sure it doesn't happen in the future?

what kind of storage are these defined as in /etc/pve/storage.cfg? Can you see anything related in the system logs/journal, e.g. journalctl -b?

 

[roberto_fx]

Ok here are my reports, thanks for the followup!

Excerpt from storage.cfg...

lvmthin: hdd-1
thinpool hdd-1
vgname hdd-1
content rootdir,images
nodes neptune
lvmthin: hdd-2
thinpool hdd-2
vgname hdd-2
content rootdir,images
nodes neptune

Not sure what to look for in journalctl, but I believe these disks are sdc and sdc, so picking up some errors from there...

Feb 09 07:35:01 neptune smartd[1751]: Device: /dev/sdc [SAT], 56 Currently unreadable (pending) sectors
Feb 09 07:35:01 neptune smartd[1751]: Device: /dev/sdc [SAT], 56 Offline uncorrectable sectors
Feb 09 07:35:01 neptune smartd[1751]: Device: /dev/sdc [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 82 to 77
...
Feb 09 07:35:20 neptune pvestatd[2599]: activating LV 'hdd-1/hdd-1' failed: Activation of logical volume hdd-1/hdd-1 is prohibited while logical volume>
Feb 09 07:35:21 neptune pve-guests[2904]: activating LV 'hdd-2/hdd-2' failed: Activation of logical volume hdd-2/hdd-2 is prohibited while logical volu>
Feb 09 07:35:21 neptune pvesh[2674]: Starting VM 204 failed: activating LV 'hdd-2/hdd-2' failed: Activation of logical volume hdd-2/hdd-2 is prohibited>
Feb 09 07:35:21 neptune pvesh[2674]: Starting VM 407
Feb 09 07:35:21 neptune pve-guests[2677]: <root@pam> starting task UPID:neptune:00000BD5:000066DD:65C61C09:qmstart:407:root@pam:
Feb 09 07:35:21 neptune pve-guests[3029]: start VM 407: UPID:neptune:00000BD5:000066DD:65C61C09:qmstart:407:root@pam:
Feb 09 07:35:21 neptune pvestatd[2599]: activating LV 'hdd-2/hdd-2' failed: Activation of logical volume hdd-2/hdd-2 is prohibited while logical volume>
Feb 09 07:35:21 neptune pvestatd[2599]: status update time (11.545 seconds)
Feb 09 07:35:21 neptune systemd[1]: Started 407.scope.
...
Feb 09 07:35:22 neptune pvestatd[2599]: activating LV 'hdd-2/hdd-2' failed: Activation of logical volume hdd-2/hdd-2 is prohibited while logical volume>
Feb 09 07:35:23 neptune pvestatd[2599]: activating LV 'hdd-1/hdd-1' failed: Activation of logical volume hdd-1/hdd-1 is prohibited while logical volume>
...
Feb 09 07:35:35 neptune pvestatd[2599]: activating LV 'hdd-1/hdd-1' failed: Activation of logical volume hdd-1/hdd-1 is prohibited while logical volume>
Feb 09 07:35:35 neptune pvestatd[2599]: activating LV 'hdd-2/hdd-2' failed: Activation of logical volume hdd-2/hdd-2 is prohibited while logical volume>
Feb 09 07:35:35 neptune pve-guests[3755]: activating LV 'hdd-2/hdd-2' failed: Activation of logical volume hdd-2/hdd-2 is prohibited while logical volu>

And more of the same...

Others:
root@neptune:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
hdd-1 hdd-1 twi-aotz-- 3.61t 52.54 6.34
hdd-1_meta0 hdd-1 -wi------- 0.02t
hdd-2 hdd-2 twi-aotz-- 3.61t 25.37 1.93

 

[fiona]

Note that the log are cut off on the right side. But it might be the following: https://forum.proxmox.com/threads/l...rnel-update-on-pve-7.97406/page-2#post-430860