Mounting SSD to external hardware

[mrowcp]

Hello guys,
I recently removed one of the SSDs from an HP proliant dl380 with proxmox 7.3-4 with the idea of putting it on another machine without Proxmox installed, just Debian.
So I removed the disk from the HP server, put it in a USB box and connected it to one of the Fujitsu ports. The problem is that it recognizes itself as "lvm" and cannot mount it.

If it matters, the box is this WAVLINK WL ST239 2.5 USB 3.0 and under Windows recognizes it as a scsi controller

Here is what I have tested so far:

/usr/sbin/vgscan
  Found volume group "subspace6" using metadata type lvm2

/usr/sbin/lvmdiskscan
/dev/nvme0n1p1 [     512.00 MiB]
/dev/sda1      [      <1.82 TiB]
/dev/nvme0n1p2 [      23.28 GiB]
/dev/sda2      [      <1.82 TiB]
/dev/nvme0n1p3 [       9.31 GiB]
/dev/nvme0n1p4 [     977.00 MiB]
/dev/nvme0n1p5 [       1.86 GiB]
/dev/nvme0n1p6 [    <441.03 GiB]
/dev/sdb       [      <3.64 TiB]
/dev/sdc1      [      <1.75 TiB]
/dev/sdd1      [       3.49 TiB]
/dev/sde1      [      <3.64 TiB]
/dev/sdf       [      <3.64 TiB] LVM physical volume
1 disk
11 partitions
1 LVM physical volume whole disk
0 LVM physical volumes


/usr/sbin/vgchange -a subspace6
  Invalid argument for --activate: subspace6
  Error during parsing of command line.

# /usr/sbin/vgchange -ay subspace6
  0 logical volume(s) in volume group "subspace6" now active

And then /usr/sbin/lvs and /usr/sbin/lvdisplay returns no result.
If I try to create it again:

/usr/sbin/vgcreate "subspace6" /dev/sdf
  Physical volume '/dev/sdf' is already in volume group 'subspace6'
  Unable to add physical volume '/dev/sdf' to volume group 'subspace6'
  /dev/sdf: physical volume not initialized.

journalctl log

May 08 16:05:38 subspace kernel: usb 1-6: new high-speed USB device number 6 using xhci_hcd
May 08 16:05:38 subspace kernel: usb 1-6: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00
May 08 16:05:38 subspace kernel: usb 1-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
May 08 16:05:38 subspace kernel: usb 1-6: Product: ASMT105x
May 08 16:05:38 subspace kernel: usb 1-6: Manufacturer: ASMT
May 08 16:05:38 subspace kernel: usb 1-6: SerialNumber: 23456789017B
May 08 16:05:38 subspace kernel: scsi host5: uas
May 08 16:05:38 subspace mtp-probe[2089539]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
May 08 16:05:38 subspace kernel: scsi 5:0:0:0: Direct-Access     SPCC Sol id State Disk    0    PQ: 0 ANSI: 6
May 08 16:05:38 subspace mtp-probe[2089539]: bus: 1, device: 6 was not an MTP device
May 08 16:05:38 subspace mtp-probe[2089541]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] Write Protect is off
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] Mode Sense: 43 00 00 00
May 08 16:05:38 subspace kernel: sd 5:0:0:0: Attached scsi generic sg5 type 0
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] Preferred minimum I/O size 512 bytes
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] Optimal transfer size 33553920 bytes
May 08 16:05:38 subspace mtp-probe[2089541]: bus: 1, device: 6 was not an MTP device
May 08 16:05:38 subspace kernel: sd 5:0:0:0: [sdf] Attached SCSI disk
May 08 16:05:38 subspace lvm[2089550]: PV /dev/sdf online, VG subspace6 is complete.
May 08 16:05:38 subspace lvm[2089550]: VG subspace6 finished

 

[Kingneutron]

You'll need to unmount any active filesystems using that disk, issue ' vgchange -a n ' and run ' wipefs -a ' on the disk to clean it, if you want to reuse/repurpose it. Note this will wipe out any partition tables and filesystems, so anything you want to salvage should already be backed up. I take NO RESPONSIBILITY for data loss.

Penultimate Last resort, you can run fdisk or gdisk and put a whole new partition table on it.

Last resort, dd zeros to the entire drive - or since it's an SSD you could do a factory reset on it.

https://wiki.archlinux.org/title/Solid_state_drive/Memory_cell_clearing

 

[mrowcp]

My idea was to keep the information on it. Where did I actually go wrong in setting it up in Proxmox so I can't use it in another Linux distribution now?

 

[Kingneutron]

Ah, I misunderstood. Did you do a ' vgchange -a y ' and see if the LVM sorts itself out?

https://access.redhat.com/documenta...-to-another-system-managing-lvm-volume-groups

> If I try to create it again:

FYI, do NOT try to re-create something that you are trying to mount and re-use. You're lucky it didn't work - if it had you would have screwed up your whole plan and would likely be facing data loss. What you tried there is the rough equivalent of FORMAT C:

 

[mrowcp]

Yes I tried...

/usr/sbin/vgchange -a y
  0 logical volume(s) in volume group "subspace6" now active

about the recreation... ah... thx. Good to know

So if I now return the disc to the VM and follow these steps

https://access.redhat.com/documenta...-to-another-system-managing-lvm-volume-groups

I will "fix" the issue?

 

[Kingneutron]

All you can do is read the docs and try it, pls report back if it did/not work

 

[mrowcp]

All you can do is read the docs and try it, pls report back if it did/not work

it's not working... doesn't work... When the disk is connected back to the server, proxmox recognizes a new LV, but can't do anything with it.

I have a second disc still attached to proxmox. Is possible to "destroy" LV before moving it to the new server and use it as "standard" disk without loosing the information of course

 

[Kingneutron]

You may need expert help at this point. If you can afford it, I would recommend purchasing a subscription + support contract with Proxmox and file a ticket with them.

If not possible, then you are free to ask around more; I'm more of a ZFS guru ;-)