Thanks for the reply.
pvscan of the borked internal drive yeilds this (note the distinct lack of a volume group!):
Code:
PV /dev/dm-6 lvm2 [59.20 GiB]
Total: 1 [59.20 GiB] / in use: 0 [0 ] / in no VG: 1 [59.20 GiB]
lvscan and vgscan both give "No Volume groups found". Can't run lvdisplay either, because I've got no vgname to put in. If I try 'ubuntu' (what it should be', it just says it can't find that group.
ON the other hand, pvscan of the working backup yeilds this:
Code:
PV /dev/dm-6 VG ubuntu lvm2 [59.20 GiB / 0 free]
Total: 1 [59.20 GiB] / in use: 1 [59.20 GiB] / in no VG: 0 [0 ]
lvscan gives:
Code:
ACTIVE '/dev/ubuntu/root' [55.28 GiB] inherit
ACTIVE '/dev/ubuntu/swap_1' [3.92 GiB] inherit
vgscan gives:
Code:
Found volume group "ubuntu" using metadata type lvm2
"lvdisplay /dev/ubuntu/root" gives
Code:
--- Logical volume ---
LV Name /dev/ubuntu/root
VG Name ubuntu
LV UUID vVIhVO-aUa8-XgSc-zd57-e0Bl-X9Sd-eqJoaQ
LV Write Access read/write
LV Status available
# open 0
LV Size 55.28 GiB
Current LE 14151
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:7
The backup boots if I put it in my laptop and start it up, and also mounts fine when plugged into my desktop, and is recognized in disk utility as an LVM device.
The borked internal drops to initramfs if I try to boot off it, and any attempt to mount it on the desktop system results in an 'Not a mountable file system' error.
Originally Posted by
steeldriver
I don`t know anything about disk encryption but it sounds like the LV (or parent VG) might not be activated
With the drive plugged into your desktop what are the actual outputs of
Code:
pvscan
vgscan
lvscan
Have you run lvdisplay on the LV
Code:
sudo lvdisplay /dev/vgname/lvname
Bookmarks