Copying Data for SSD

Just mount both and you can copy and paste files as you expect. Is this just the casual data or are you wanting to clone the drive?

I have replaced my old mother board Gigabyte H81M -S2H V1
With new one Gigabyte H510-S2H V2 It has a M.2 SSD of 500GB
(KINGSTON SNV2S500G (SBI02102) S/No:50026B7282DB457E

The Problem is that I can’t see the OLD SSD
(KINGSTON SHSS37A480G (SAFM00.Y) S/No:50026B726801870E
+ Other Locations Only the NEW SSD is visible or can it be seen

So can’t copy or move anything.

I can see the new & old SSD with the Disk management utility for GNOME with is were I got the above information.

I did not wish to clone the new SSD as I have done a clean install and only wish copy by backups data to the new SSD.

Rich.B

What is the output of:

sudo parted -l

Thanks

Model: ATA WDC WD20PURX-64P (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
 1 1016kB 944GB 944GB extended lba
 5 1049kB 524GB 524GB logical ntfs
 6 524GB 944GB 419GB logical ext4
 2 944GB 2000GB 1057GB primary ext4

Model: ATA ST2000DM008-2UB1 (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
 1 1049kB 500GB 500GB primary ext4
 2 500GB 1000GB 500GB primary ext4
 3 1000GB 1500GB 500GB primary ext4
 4 1500GB 2000GB 500GB primary ext4

Model: ATA KINGSTON SHSS37A (scsi)
Disk /dev/sdc: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
 1 1049kB 538MB 537MB fat32 EFI System Partition boot, esp
 2 538MB 480GB 480GB lvm

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vgubuntu-swap_1: 2051MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
 1 0.00B 2051MB 2051MB linux-swap(v1)

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/vgubuntu-root: 498GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
 1 0.00B 498GB 498GB ext4

Model: KINGSTON SNV2S500G (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
 1 1049kB 538MB 537MB fat32 boot, esp
 2 538MB 500GB 500GB lvm

If you have named the volume group with the new disk the same as it was in the past with the old disk, then you may have a name conflict.

Try lvm commands like pvscan, lvscan, vgscan, vgdisplay, etc. to identify what the system now thinks about your disks and logical volumes.

 Thanks Manfred, I thought that could be the cause why I could not see the old SSD.
I have notice after grub, that there is a message that includes "ERROR" but its to fast before it has got off.

WARNING: VG name vgubuntu is used by VGs XmQjS5-Upqe-FUHX-N25P-aHYK-dBt9-ZsVzHc and T2Kl9H-2Iny-7qEg-oeEA-03x0-cUDR-fHHm9m.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  PV /dev/sdc2 VG vgubuntu lvm2 [<446.63 GiB / 0 free]
  PV /dev/nvme0n1p2 VG vgubuntu lvm2 [<465.26 GiB / 0 free]
  Total: 2 [<911.89 GiB] / in use: 2 [<911.89 GiB] / in no VG: 0 [0 ]
geek@hal-h510m-s2h-v2:~$ sudo lvscan
  WARNING: VG name vgubuntu is used by VGs XmQjS5-Upqe-FUHX-N25P-aHYK-dBt9-ZsVzHc and T2Kl9H-2Iny-7qEg-oeEA-03x0-cUDR-fHHm9m.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  inactive '/dev/vgubuntu/root' [445.67 GiB] inherit
  inactive '/dev/vgubuntu/swap_1' [980.00 MiB] inherit
  ACTIVE '/dev/vgubuntu/root' [<463.35 GiB] inherit
  ACTIVE '/dev/vgubuntu/swap_1' [1.91 GiB] inherit
geek@hal-h510m-s2h-v2:~$ sudo vgscan
  WARNING: VG name vgubuntu is used by VGs XmQjS5-Upqe-FUHX-N25P-aHYK-dBt9-ZsVzHc and T2Kl9H-2Iny-7qEg-oeEA-03x0-cUDR-fHHm9m.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  Found volume group "vgubuntu" using metadata type lvm2
  Found volume group "vgubuntu" using metadata type lvm2
geek@hal-h510m-s2h-v2:~$ sudo vgdisplay
  WARNING: VG name vgubuntu is used by VGs XmQjS5-Upqe-FUHX-N25P-aHYK-dBt9-ZsVzHc and T2Kl9H-2Iny-7qEg-oeEA-03x0-cUDR-fHHm9m.
  Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
  --- Volume group ---
  VG Name vgubuntu
  System ID
  Format lvm2
  Metadata Areas 1
  Metadata Sequence No 3
  VG Access read/write
  VG Status resizable
  MAX LV 0
  Cur LV 2
  Open LV 0
  Max PV 0
  Cur PV 1
  Act PV 1
  VG Size <446.63 GiB
  PE Size 4.00 MiB
  Total PE 114337
  Alloc PE / Size 114337 / <446.63 GiB
  Free PE / Size 0 / 0
  VG UUID XmQjS5-Upqe-FUHX-N25P-aHYK-dBt9-ZsVzHc

  --- Volume group ---
  VG Name vgubuntu
  System ID
  Format lvm2
  Metadata Areas 1
  Metadata Sequence No 3
  VG Access read/write
  VG Status resizable
  MAX LV 0
  Cur LV 2
  Open LV 2
  Max PV 0
  Cur PV 1
  Act PV 1
  VG Size <465.26 GiB
  PE Size 4.00 MiB
  Total PE 119106
  Alloc PE / Size 119106 / <465.26 GiB
  Free PE / Size 0 / 0
  VG UUID T2Kl9H-2Iny-7qEg-oeEA-03x0-cUDR-fHHm9m

Just see your output and follow the instructions contained:

WARNING: VG name vgubuntu is used by VGs XmQjS5-Upqe-FUHX-N25P-aHYK-dBt9-ZsVzHc and T2Kl9H-2Iny-7qEg-oeEA-03x0-cUDR-fHHm9m.
Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.

(I cannot help more, because I do not have any experience with repairing a LVM system that is misconfigured like yours.)

Thank you Manfred so far for your information.

0.126953] x86/cpu: SGX disabled by BIOS.
0.210937] ACPI BIOS Error (bug): Failure creating named object [\ADBG), AE_ ALREADY_EXISTS (20210730/dswload2-326)

[ 0.210944] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (202107 30/psobject-220)

/dev/mapper/vgubuntu-root: clean, 227540/30367744.files, 5860486/121463808 blocks [ 5.706726] mtd device must be supplied (device name is empty)

This is what have videoed shortly after Grub, not sure if this will help you.
Let me know.
Thanks

Rich.b

I do not think that these messages have something to do with your LVM misconfiguration problem.

You have to use vgrename to rename one of the two identically-named volume groups.