Aquiring and exporting external disk software RAID and LVM
I had one of my computers die a short while ago. I wanted to get the data inside its disk into another computer.
Using the magical and rather cheap USB2SATA I was able to connect the disk, however, the disk was part of a software mirror (md device) and had LVM on it. Gets a little complicated? Not really:
(connect the device to the system)
Now we need to query which device it is:
dmesg
It is quite easy. In my case it was /dev/sdk (don’t ask). It shown something like this:
usb 1-6: new high speed USB device using address 2
Initializing USB Mass Storage driver…
scsi5 : SCSI emulation for USB Mass Storage devices
Vendor: WDC WD80 Model: WD-WMAM92757594 Rev: 1C05
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdk: 156250000 512-byte hdwr sectors (80000 MB)
sdk: assuming drive cache: write through
SCSI device sdk: 156250000 512-byte hdwr sectors (80000 MB)
sdk: assuming drive cache: write through
sdk: sdk1 sdk2 sdk3
Attached scsi disk sdk at scsi5, channel 0, id 0, lun 0
This is good. The original system was RH4, so the standard structure is /boot on the first partition, swap and then one large md device containing LVM (at least – my standard).
Lets list the partitions, just to be sure:
# fdisk -l /dev/sdk
Disk /dev/sdk: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytesDevice Boot Start End Blocks Id System
/dev/sdk1 * 1 13 104391 fd Linux raid autodetect
/dev/sdk2 14 144 1052257+ 82 Linux swap
/dev/sdk3 145 9726 76967415 fd Linux raid autodetect
Good. As expected. Let’s activate the md device:
# mdadm –assemble /dev/md2 /dev/sdk3
mdadm: /dev/md2 has been started with 1 drive (out of 2).
It’s going well. Now we have the md device active, and we can try to scan for LVM:
# pvscan
…PV /dev/md2 VG SVNVG lvm2 [73.38 GB / 55.53 GB free]
Activating the VG is a desired action. Notice the name – SVNVG (a note at the bottom):
# vgchange -a y /dev/SVNVG
3 logical volume(s) in volume group “SVNVG” now active
Now we can list the LVs and mount them on our desired location:
]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
LogVol00 SVNVG -wi-a- 2.94G
LogVol01 SVNVG -wi-a- 4.91G
VarVol SVNVG -wi-a- 10.00G
Mounting:
mount /dev/SVNVG/VarVol /mnt/
and it’s all ours.
To remove this connected the disk, we need to reverse the above process.
First, we will umount the volume:
umount /mnt
Now we need to disable the Volume Group:
# vgchange -a n /dev/SVNVG
0 logical volume(s) in volume group “SVNVG” now active
0 logical volumes active means we were able to disable the whole VG.
Disable the MD device:
# mdadm –manage -S /dev/md2
Now we can disconnect the physical disk (actually, the USB) and continue with out life.
A note: RedHat systems name their logical volumes using a default name VolGroup00. You cannot have two VGs with the same name! If you activate a VG which originated from RH system and used a default name, and your current system uses the same defaults, you need to connect the disk to an external system (non RH would do fine) and change the VG name using vgrename before you can proceed.
