Please help re-adding a usb drive after a fresh installation.

Steveuk

New Member
Apr 20, 2023
7
0
1
HI all,
just to point out first i'm not great with Proxmox or Linux but trying to get through with great guides etc.
I had Proxmox running for about 8 months no issue and i think it was THIS guide i followed to add a USB hard drive to backup 2 VM's i had and that was working fine up until my proxmox instance crashed.
Anyway i ended up formatting and reinstalling V8.1.3 and now i am trying to re add this USB drive back onto the new proxmox but all the guides/youtube videos i'm finding aren't working,
Right at the beginning of this new install when i tried to mount it i got a error
Code:
Unknown filesystem type 'LVM2_member'
So now i know its because it's a LVM partition.
I found THIS guide which i tried to follow with the end step resulting in this error

Code:
/mnt/backups: wrong fs type, bad option, bad superblock on /dev/mapper/pve-data, missing codepage or helper program, or other error.

I've attached a screenshot of my disks in proxmox my USB is /dev/sdb i was guessing /dev/sdb3 was where my backups might be ?
And the code at the bottom is what i was getting when following the guide linked above.
Thanks for any help as you can see i'm useless :D

Code:
root@pve:~# fdisk -l /dev/sdb
Disk /dev/sdb: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Portable       
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: A86ED1E4-6DE7-4E25-A6F0-A4D0C8DC833E

Device       Start       End   Sectors   Size Type
/dev/sdb1       34      2047      2014  1007K BIOS boot
/dev/sdb2     2048   2099199   2097152     1G EFI System
/dev/sdb3  2099200 488397134 486297935 231.9G Linux LVM
root@pve:~# lvmdiskscan
  WARNING: VG name pve is used by VGs 3qtDED-WkaU-lH4W-udBR-EKxG-sDQk-zU9fJ2 and Ao1ejO-Hvu1-XdZV-SQbT-3XzS-inOa-vnStzi.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  /dev/sda2 [       1.00 GiB]
  /dev/sda3 [    <222.57 GiB] LVM physical volume
  /dev/sdb2 [       1.00 GiB]
  /dev/sdb3 [     231.88 GiB] LVM physical volume
  0 disks
  2 partitions
  0 LVM physical volume whole disks
  2 LVM physical volumes
root@pve:~# vgchange -ay
  WARNING: VG name pve is used by VGs 3qtDED-WkaU-lH4W-udBR-EKxG-sDQk-zU9fJ2 and Ao1ejO-Hvu1-XdZV-SQbT-3XzS-inOa-vnStzi.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  WARNING: activating multiple VGs with the same name is dangerous and may fail.
  Consider pruning pve VG archive with more then 181 MiB in 54624 files (check archiving is needed in lvm.conf).
  Consider pruning pve VG archive with more then 181 MiB in 54625 files (check archiving is needed in lvm.conf).
  device-mapper: create ioctl on pve-swap LVM-3qtDEDWkaUlH4WudBREKxGsDQkzU9fJ290yBPoWTqF3wufiaa4USKBhwpG2eaXDZ failed: Device or resource busy
  device-mapper: create ioctl on pve-root LVM-3qtDEDWkaUlH4WudBREKxGsDQkzU9fJ2Mqa2MA9y1nUm78jRGldKdPpjqv9y8nAK failed: Device or resource busy
  device-mapper: create ioctl on pve-data_tmeta LVM-3qtDEDWkaUlH4WudBREKxGsDQkzU9fJ2LfuizZzpcYdoLcpuTy3fMPsN7ltNsIYL-tmeta failed: Device or resource busy
  0 logical volume(s) in volume group "pve" now active
  WARNING: activating multiple VGs with the same name is dangerous and may fail.
  Consider pruning pve VG archive with more then 181 MiB in 54626 files (check archiving is needed in lvm.conf).
  Consider pruning pve VG archive with more then 181 MiB in 54627 files (check archiving is needed in lvm.conf).
  3 logical volume(s) in volume group "pve" now active
root@pve:~# lvscan
  WARNING: VG name pve is used by VGs 3qtDED-WkaU-lH4W-udBR-EKxG-sDQk-zU9fJ2 and Ao1ejO-Hvu1-XdZV-SQbT-3XzS-inOa-vnStzi.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  inactive          '/dev/pve/data' [137.36 GiB] inherit
  inactive          '/dev/pve/swap' [<7.67 GiB] inherit
  inactive          '/dev/pve/root' [68.05 GiB] inherit
  ACTIVE            '/dev/pve/data' [<130.52 GiB] inherit
  ACTIVE            '/dev/pve/swap' [7.66 GiB] inherit
  ACTIVE            '/dev/pve/root' [<65.73 GiB] inherit
root@pve:~# mount /dev/pve/data /mnt/backups
mount: /mnt/backups: wrong fs type, bad option, bad superblock on /dev/mapper/pve-data, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
 

Attachments

  • proxmox.png
    proxmox.png
    32.7 KB · Views: 3
It appears no one responds to these requests. It doesn't seem like members are very active on this forum. No one has helped me with my issue either. --Tim
 
> Fix duplicate VG names with vgrename uuid

You have a duplicate volume group and need to import the LVM with a different name, or try it on another computer and copy the files off there.

Just a reminder, this is *community support* - apart from actual Proxmox employees, we're all on here trying to provide help on our own time, FOR FREE. If that's not sufficient for you, consider buying a Proxmox subscription + support contract, and file a ticket with them.
 
  • Like
Reactions: leesteken

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!

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!