I'm reluctant to eliminate the bad LV's because there's still a faint hope of recovering the failed disk. As for using --partial, the problem is that I don't know how to intervene in the current vgchange activation that's going on. If I could, I would just avoid activating the damaged VG at all. Ross
On Wed, May 15, 2013 at 11:07 PM, emmanuel segura <emi2f...@gmail.com>wrote: > Look this > http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/lost_PV_remove_from_VG.html > > > 2013/5/16 Ross Boylan <r...@biostat.ucsf.edu> > >> One of the disks that was in an LVM Volume Group died, as a result of >> which LVM reports an error when the system starts. I believe because of >> the errors from lvm the boot sequence stops. After several minutes it >> times out. At that point a shell prompt appears. The missing physical >> disk is no longer essential for the system to boot, and the damaged VG >> still has some good volumes in it, so I do >> vgchange -ay >> which reports errors but activates what it can >> and >> cryptsetup luksOpen /dev/myVG/myCryptRoot CryptRoot >> when I exit the shell the system boot continues successfully. I'm using >> grub2 on amd64 and a standard initramfs for wheezy. Note that myVG is not >> the damaged volume group. >> >> Is there some way I can achieve the same effect without manual >> intervention (except for the crypto pass-phrase) and without the wait for >> timeout? >> >> Ross Boylan >> >> >> -- >> To UNSUBSCRIBE, email to >> debian-user-REQUEST@lists.**debian.org<debian-user-requ...@lists.debian.org>with >> a subject of "unsubscribe". Trouble? Contact >> listmas...@lists.debian.org >> Archive: >> http://lists.debian.org/**519422cf.9010...@biostat.ucsf.**edu<http://lists.debian.org/519422cf.9010...@biostat.ucsf.edu> >> >> > > > -- > esta es mi vida e me la vivo hasta que dios quiera >
