lvm - problem replacing failed disk
Quoted 11 lines · Steven Mosimann
Quoted 6 lines
(1) Replaced the failed disk with one of the same size
(2) Used pvcreate to make the same physical volumes on the new disk that were present on the failed disk. Example of the actual command I used was:
pvcreate --uuid xxxxx/dev/sdb1
where xxxxx was the pv uuid from pvdisplayMissing the --restorefile arg there (for safety - if it was originally created by lvm2 with default options it'll make no difference).
Quoted 8 lines
Missing a 'vgcfgrestore' step.
Quoted 1 line
(3) Used vgchange -a y -P to activate the volume group
No need for -P here. That's what you use if you *don't* do steps 1 and 2 etc.
Alasdair
I checked the commands I issued. I got the pvcreate correct and the vgcfgrestore is present (though it was out of order with vgchange). Here is what I have done in detail:
fdisk /dev/sdb
(created three partitions of type LVM that are identical to those on the failed disk)
mkfs.ext3 /dev/sdb1
mkfs.ext3 /dev/sdb2
mkfs.ext3 /dev/sdb3
(formatted as ext3)
pvcreate --uuid xxxxx --restorefile /etc/lvm/archive/xxxx.ar /dev/sdb1 pvcreate --uuid xxxxx --restorefile /etc/lvm/archive/xxxx.ar /dev/sdb2 pvcreate --uuid xxxxx --restorefile /etc/lvm/archive/xxxx.ar /dev/sdb3
(chose archive file with all PV, LV and VG's from the functioning LVM setup)
vgcfgrestore -f /etc/lvm/backup/VG_data VG_data
(the VG_data matches the functioning LVM setup from above)
vgchange -ay
mount -t ext3 /dev/VG_data/LV_data /data
gives
"error: wrong fs type, bad option, bad superblock on /dev/VG_data/LV_data, or too many mounted filesystems"
mount /dev/VG_data/LV_data /data
gives
"mount: you must specify filesystem type"
Any suggestions regarding how to proceed.
Steve
(PS. our lab was out of town for a week so I'm only back at it now).
Signature · 1 line
Steven Mosimann, PhD