[SOLVED] /dev/data/pve volume shows up as inactive

[anshulrao]

Hello, a year ago when I was setting up my server, I had initially set it up with proxmox and couldn't get it to work successfully and instead flashed and booted Ubuntu Jammy 22.04. However, as I was looking through my disks/volumes, I am only able to use 100gb of my 2tb SSD and unable ot use the remaining storage because it is listed as inactive and believe that the initial proxmox setup is the reason. I'm not sure how to activate and access that remaining storage of the SSD and have no idea what the next steps could be. Would anyone be able to direct me to a solution?

Here are the commands I ran through the terminal:
```
homelab@homelab-server:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 10.1M 1 loop /snap/canonical-livepatch/278
loop2 7:2 0 10.1M 1 loop /snap/canonical-livepatch/282
loop3 7:3 0 104M 1 loop /snap/core/16928
loop4 7:4 0 104.2M 1 loop /snap/core/17200
loop5 7:5 0 63.9M 1 loop /snap/core20/2264
loop6 7:6 0 63.9M 1 loop /snap/core20/2318
loop7 7:7 0 74.2M 1 loop /snap/core22/1122
loop8 7:8 0 74.2M 1 loop /snap/core22/1380
loop9 7:9 0 268.4M 1 loop /snap/firefox/4650
loop11 7:11 0 349.7M 1 loop /snap/gnome-3-38-2004/143
loop12 7:12 0 504.2M 1 loop /snap/gnome-42-2204/172
loop13 7:13 0 505.1M 1 loop /snap/gnome-42-2204/176
loop14 7:14 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop15 7:15 0 12.9M 1 loop /snap/snap-store/1113
loop16 7:16 0 12.3M 1 loop /snap/snap-store/959
loop17 7:17 0 38.7M 1 loop /snap/snapd/21465
loop18 7:18 0 38.8M 1 loop /snap/snapd/21759
loop19 7:19 0 476K 1 loop /snap/snapd-desktop-integration/157
loop20 7:20 0 452K 1 loop /snap/snapd-desktop-integration/83
loop21 7:21 0 268.9M 1 loop /snap/firefox/4630
sda 8:0 0 12.7T 0 disk
└─sda1 8:1 0 12.7T 0 part /mnt/disk1
sdb 8:16 0 12.7T 0 disk
└─sdb1 8:17 0 12.7T 0 part /mnt/parity1
nvme0n1 259:0 0 1.8T 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 1G 0 part /boot/efi
└─nvme0n1p3 259:3 0 1.8T 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
└─pve-root 252:1 0 96G 0 lvm /var/snap/firefox/common/host-hunspell
/
homelab@homelab-server:~$ sudo lvdisplay
WARNING: Unrecognised flag CROP_METADATA in segment type thin-pool+CROP_METADATA.
WARNING: Unrecognised segment type thin-pool+CROP_METADATA
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID 3sf7YL-luCv-AcNi-KR3m-ws3m-ZCyI-Xp4Z8l
LV Write Access read/write
LV Creation host, time proxmox, 2023-11-25 13:39:38 -0600
LV Status available
# open 2
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0

--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID TKudBx-KedF-B6vf-819Z-Ppr7-SMQ7-qW0Rd3
LV Write Access read/write
LV Creation host, time proxmox, 2023-11-25 13:39:38 -0600
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:1

--- Logical volume ---
LV Path /dev/pve/data
LV Name data
VG Name pve
LV UUID OHbrfR-Nfol-j1Rv-bmXH-RCWe-qUdj-4fiFeJ
LV Write Access read/write
LV Creation host, time proxmox, 2023-11-25 13:39:43 -0600
LV Status NOT available
LV Size <1.67 TiB
Current LE 437763
Segments 1
Allocation inherit
Read ahead sectors auto

homelab@homelab-server:~$ sudo pvdisplay
WARNING: Unrecognised flag CROP_METADATA in segment type thin-pool+CROP_METADATA.
WARNING: Unrecognised segment type thin-pool+CROP_METADATA
--- Physical volume ---
PV Name /dev/nvme0n1p3
VG Name pve
PV Size <1.82 TiB / not usable <4.07 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 476675
Free PE 4158
Allocated PE 472517
PV UUID 8TuBfu-9p7y-517t-GXpO-zeNy-xuTl-rGIkFr

homelab@homelab-server:~$ sudo vgdisplay
WARNING: Unrecognised flag CROP_METADATA in segment type thin-pool+CROP_METADATA.
WARNING: Unrecognised segment type thin-pool+CROP_METADATA
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 7
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size <1.82 TiB
PE Size 4.00 MiB
Total PE 476675
Alloc PE / Size 472517 / 1.80 TiB
Free PE / Size 4158 / 16.24 GiB
VG UUID DrTuzn-3Ve6-5Igy-N2BK-vzRg-xJ4y-KBsh2z

homelab@homelab-server:~$ sudo lvscan
WARNING: Unrecognised flag CROP_METADATA in segment type thin-pool+CROP_METADATA.
WARNING: Unrecognised segment type thin-pool+CROP_METADATA
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [96.00 GiB] inherit
inactive '/dev/pve/data' [<1.67 TiB] inherit
homelab@homelab-server:~$ sudo lvck /dev/pve/data
sudo: lvck: command not found
homelab@homelab-server:~$ ls /dev/pve/
root swap
homelab@homelab-server:~$ sudo lvdisplay /dev/pve/data
WARNING: Unrecognised flag CROP_METADATA in segment type thin-pool+CROP_METADATA.
WARNING: Unrecognised segment type thin-pool+CROP_METADATA
--- Logical volume ---
LV Path /dev/pve/data
LV Name data
VG Name pve
LV UUID OHbrfR-Nfol-j1Rv-bmXH-RCWe-qUdj-4fiFeJ
LV Write Access read/write
LV Creation host, time proxmox, 2023-11-25 13:39:43 -0600
LV Status NOT available
LV Size <1.67 TiB
Current LE 437763
Segments 1
Allocation inherit
Read ahead sectors auto
```

 

[gfngfn256]

That 1.8T NVMe looks well & truly messed up. As I understand from your post you are no longer running Proxmox on this drive at all. If so, really your post belongs on a Ubuntu site.

But I'm going to tell you what I would do in your situation; Backup your critical data & WIPE THAT NVMe COMPLETLY CLEAN (removing all partitions & data) & then reinstall your OS, & restore your data.

 

[anshulrao]

How do I go about backing everything up? /home is easy to back up but I mean system files and other configurations. Can I back up the whole OS or what? I'll also post it on the ubuntu forums since this isn't a proxmox issue then.

 

[gfngfn256]

Can I back up the whole OS or what?

You can probably use something like timeshift. I don't really use Ubuntu, so maybe first give it a test-run: Make a timeshift of your complete Ubuntu OS to an external flash/usb/drive, & then on a different drive (spare one laying around?) install a fresh Ubuntu Jammy, & then attempt to restore that timeshift.

As I said this is a Ubuntu Jammy centric question, so look elsewhere. Good luck.

 

[anshulrao]

Thanks, this solved my problem. Appreciate it a bunch.