How to restore proxmox storage (no backups)

S

sibainu

New Member
Mar 30, 2024
7
0
1
I was working on mounting HDDs in proxmox and noticed that one LVMthin storage was lost.

Being a novice, I had not made any backups.

I would appreciate if you could tell me the procedure to recover it.
 
Can you give a rough layout of your disks as they should be and which one is missing?

I assumed you tried a reboot, which should autoscan and mount most things if they were setup correctly.
 
The current storage layout is shown in the image.
There used to be a storage called "unipro" here, but it has disappeared.
Screenshot from 2024-03-30 13-33-16.png
 
jlauro said:
Can you give a rough layout of your disks as they should be and which one is missing?

I assumed you tried a reboot, which should autoscan and mount most things if they were setup correctly.
Click to expand...
I have not rebooted.

The attached image is a log of the loss of unipro storage that prevented it from starting.
1711773786059.png
 
What is your boot disk? Normally it's sda, but that log shows it was initialized?

What is the output of pvdisplay ?
 
The bood disk uses an M.2 SSD.
The sda is the HDD you wanted to mount. (I had trouble creating the partitions and deleted them several times.)

pvdisplay results.
--- 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 uDFNHC-SswR-YJAD-TuCR-GDQW-9Hex-bQWOPg
 
Does /dev/sda show with
fdisk -l

Does it show with
pvscan

Looks like it was wiped at 11:33-11:50... and you noticed problem at 12:17? You did mention HDDs (as in plural). Was that a different disk that was wiped and you only need to remount it, or are you wanting to recover the data from the reinitialized drive?
 
fdisk -l　 is the result of executing
Code: 
Disk /dev/sda: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: TOSHIBA MN08ADA8
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: 6BEECFDA-0E5F-4CB2-A96B-47DEC06CED8D

Device          Start        End    Sectors Size Type
/dev/sda1        2048 4294969343 4294967296   2T Linux filesystem
/dev/sda2  4294969344 6442452991 2147483648   1T Linux filesystem


Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: KIOXIA-EXCERIA G2 SSD                   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4A67C741-6BE1-4DB9-A94C-C62A3FF800EC

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1      34       2047       2014 1007K BIOS boot
/dev/nvme0n1p2    2048    2099199    2097152    1G EFI System
/dev/nvme0n1p3 2099200 3907029134 3904929935  1.8T Linux LVM


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-vm--200--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 591BBD5C-B603-472C-B433-5D84391240C2

Device                                   Start      End  Sectors Size Type
/dev/mapper/pve-vm--200--disk--0-part1    2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--200--disk--0-part2    4096  4198399  4194304   2G Linux filesystem
/dev/mapper/pve-vm--200--disk--0-part3 4198400 67106815 62908416  30G Linux filesystem


Disk /dev/mapper/pve-vm--102--state--First: 20.02 GiB, 21495808000 bytes, 41984000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--103--disk--0: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 8D757117-E5F5-11EE-B73D-BC2411030A15

Device                                 Start       End   Sectors  Size Type
/dev/mapper/pve-vm--103--disk--0-part1    40      1063      1024  512K FreeBSD boot
/dev/mapper/pve-vm--103--disk--0-part2  1064 209683495 209682432  100G FreeBSD ZFS

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/pve-vm--102--disk--0: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: C9AC0A99-0935-4C35-8294-6311203D2984

Device                                   Start       End   Sectors Size Type
/dev/mapper/pve-vm--102--disk--0-part1    2048      4095      2048   1M BIOS boot
/dev/mapper/pve-vm--102--disk--0-part2    4096   4198399   4194304   2G Linux filesyst
/dev/mapper/pve-vm--102--disk--0-part3 4198400 104855551 100657152  48G Linux filesyst


Disk /dev/mapper/pve-vm--102--state--install2: 20.02 GiB, 21495808000 bytes, 41984000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--200--state--md: 8.49 GiB, 9114222592 bytes, 17801216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--101--state--installlater: 10.25 GiB, 11010048000 bytes, 21504000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--101--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 6C77A737-AF73-4B7B-A679-A2EFECBE58C6

Device                                   Start      End  Sectors Size Type
/dev/mapper/pve-vm--101--disk--0-part1    2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--101--disk--0-part2    4096  4198399  4194304   2G Linux filesystem
/dev/mapper/pve-vm--101--disk--0-part3 4198400 67106815 62908416  30G Linux filesystem


Disk /dev/mapper/pve-vm--101--state--install--later: 10.25 GiB, 11010048000 bytes, 21504000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--101--state--resolv--edit: 10.25 GiB, 11010048000 bytes, 21504000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--108--disk--0: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 7367EDEE-11C3-4BDB-BB8D-A4B2838F26DA

Device                                   Start       End   Sectors Size Type
/dev/mapper/pve-vm--108--disk--0-part1    2048      4095      2048   1M BIOS boot
/dev/mapper/pve-vm--108--disk--0-part2    4096   4198399   4194304   2G Linux filesyst
/dev/mapper/pve-vm--108--disk--0-part3 4198400 209713151 205514752  98G Linux filesyst


Disk /dev/mapper/pve-vm--108--state--create: 64.49 GiB, 69243764736 bytes, 135241728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--106--disk--0: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: DEBEC841-FB8E-4B80-8E47-3AAC44F2FA1B

Device                                   Start       End   Sectors Size Type
/dev/mapper/pve-vm--106--disk--0-part1    2048      4095      2048   1M BIOS boot
/dev/mapper/pve-vm--106--disk--0-part2    4096   4198399   4194304   2G Linux filesyst
/dev/mapper/pve-vm--106--disk--0-part3 4198400 104855551 100657152  48G Linux filesyst


Disk /dev/mapper/pve-vm--106--state--created: 8.49 GiB, 9114222592 bytes, 17801216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--100--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--100--disk--1: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 12FDBFCB-AD6A-491B-A7BA-BDBD8FED17E5

Device                                   Start      End  Sectors  Size Type
/dev/mapper/pve-vm--100--disk--1-part1    2048  2203647  2201600    1G EFI System
/dev/mapper/pve-vm--100--disk--1-part2 2203648  6397951  4194304    2G Linux filesyste
/dev/mapper/pve-vm--100--disk--1-part3 6397952 67106815 60708864 28.9G Linux filesyste


Disk /dev/mapper/pve-vm--100--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--109--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 8C5A0CA0-3C2E-40C9-A5FB-CF3C8DF340BE

Device                                   Start      End  Sectors Size Type
/dev/mapper/pve-vm--109--disk--0-part1    2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--109--disk--0-part2    4096  4198399  4194304   2G Linux filesystem
/dev/mapper/pve-vm--109--disk--0-part3 4198400 67106815 62908416  30G Linux filesystem


Disk /dev/mapper/pve-vm--107--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--107--disk--1: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: B74833B0-5A29-4C2E-98BB-7880E0976327

Device                                   Start      End  Sectors  Size Type
/dev/mapper/pve-vm--107--disk--1-part1    2048  2203647  2201600    1G EFI System
/dev/mapper/pve-vm--107--disk--1-part2 2203648  6397951  4194304    2G Linux filesyste
/dev/mapper/pve-vm--107--disk--1-part3 6397952 67106815 60708864 28.9G Linux filesyste


Disk /dev/mapper/pve-vm--107--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--104--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--104--disk--1: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 7440566B-3009-4475-B801-E9B4C02E876E

Device                                   Start      End  Sectors  Size Type
/dev/mapper/pve-vm--104--disk--1-part1    2048  2203647  2201600    1G EFI System
/dev/mapper/pve-vm--104--disk--1-part2 2203648  6397951  4194304    2G Linux filesyste
/dev/mapper/pve-vm--104--disk--1-part3 6397952 67106815 60708864 28.9G Linux filesyste


Disk /dev/mapper/pve-vm--104--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

pvscan
is the result of executing
PV /dev/nvme0n1p3 VG pve lvm2 [<1.82 TiB / 16.24 GiB free]
Total: 1 [<1.82 TiB] / in use: 1 [<1.82 TiB] / in no VG: 0 [0 ]

The storage I want to recover is called unipro and I created the storage with LVM-Thin type.
The options when I created it were,
Volume Group was set to pve.
 
New information.

The following error occurred on the proxmox startup screen.

/dev/mapper/pue-root: clean, 55512/6291456 files, 4955657/25165824 blocks 6.847356] ccp 0000:03:00.2: SEU: failed to INIT error 0x8004, rc -5

If anyone knows the cause of this error and how to resolve it, please let me know.
 
I gave up and recreated the storage and the data was restored.
Thank you for your response.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back