Arch Linux

turbochamp

Member

Registered: 2021-11-05

Posts: 23

Cloned NVMEs - lsblk showing prvs drive that's physically disconnected

Had Arch installed on NVME, bought a new bigger NVME and use rsync to clone to the new drive. Booted live usb and reinstalled bootloader.

All is well, and all my connected drives show up and work fine (7 drives) except one SSD is not being found and its completely unrelated. However, the previous NVME which is physically disconnected is showing up with `lsblk`, `fdisk -l` and gparted. I don't understand why. My suspicion is somehow the drive that's not found is being replaced by this previous NVME. No idea.

If this matters: previous system was an lvm, new one is ext4

This drive is not connected:
lsblk:

sdf                     8:80   0 931.5G  0 disk
├─sdf1                  8:81   0   500M  0 part
└─sdf2                  8:82   0   931G  0 part
  ├─volgroup0-lv_root 254:0    0   531G  0 lvm
  └─volgroup0-lv_home 254:1    0   400G  0 lvm

fdisk -l:

Disk /dev/sdf: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC  WDS100T2B0A
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: A4C8D45D-DBC8-B946-8036-A7FB89864C32

Device       Start        End    Sectors  Size Type
/dev/sdf1     2048    1026047    1024000  500M EFI System
/dev/sdf2  1026048 1953525134 1952499087  931G Linux LVM

Plus it still shows

/dev/mapper/volgroup0...

in fdisk-l, how can I also update this since it's not connected?

EDIT: I also removed previous drive entries in fstab and ran systemctl daemon-reload

Last edited by turbochamp (2023-07-09 01:45:54)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,237

Re: Cloned NVMEs - lsblk showing prvs drive that's physically disconnected

Drop lvm2 from your hooks and rebuild your initramfs: https://wiki.archlinux.org/title/Mkinit … generation

Last edited by V1del (2023-07-09 13:18:48)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,647

Re: Cloned NVMEs - lsblk showing prvs drive that's physically disconnected

If you just unplugged the drive, the device name (/dev/sdf) would still be around since the drive is still in use (by LVM mappings). Those don't vanish automatically, you're supposed to umount, cryptsetup close,  vgchange -a n, mdadm --stop, losetup -d etc., and also clean up any running processes that might be working with the drive, before unplugging (depends what's on the drive / what's using the drive). If it still reappears after a reboot, the drive should still be connected and maybe you confused what's where...