If it's just the MBR that got wiped, you may be able to just reinstall
grub/lilo and be good to go, but you may also need to use some sort of
partition guesser to see all of your filesystems again.
The group I work in automatically collects our MBR's via our usual,
automated system-statistics collection, the relevant portion of which
looks like:
dd if=/dev/$disk bs=512 count=1 2> /dev/null | \
openssl base64 -e | \
sed "s#^#mbr-$disk #"
HTH.
On Mon, 2005-03-14 at 09:52 +0200, go0ogl3 wrote:
> Hello!
>
> I'm new at lvm but maybe Windows just overwrited the first 512 bytes
> of that disk. Try dd_rescue or search the list arhive you'll find some
> similar situation (oliver with a hex editor).
>
> I hope you'll make it!
>
> On Sun, 13 Mar 2005 19:48:47 -0500, Andrew <andy_b@softhome.net> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > My problem is that I accidentally left my LVM disks in my system when I
> > installed windows XP On a seperate drive. I did not install windows to
> > either of the LVM's so that should not be an issue.
> >
> > However when I replaced my linux drive, and booted into linux, I got the
> > following error when my system tried to start up LVM
> > (for vgchange -ay)
> > mog root # vgchange -ay
> > 2 logical volume(s) in volume group "vg0" now active
> > Logical volume (lv0) contains an incomplete mapping table
> > Unable to find volume group "vg_samsung"
> >
> > vg0 is my other lvm which thankfully is still there.
> >
> > now, whenever I do any of the 'scan' tools (vgscan, pvscan, lvscan) I get the
> > following errors:
> > vgscan:
> > ...
> > Logical volume (lv0) contains an incomplete mapping table
> > Unable to find volume group "vg_samsung"
> >
> > pvscan:
> > Logical volume (lv0) contains an incomplete mapping table
> > ...
> >
> > lvscan:
> > ...
> > Logical volume (lv0) contains an incomplete mapping table
> > Unable to find volume group "vg_samsung"
> >
> > however, if I do pvdisplay on my 2 drives I get some info
> > mog root # pvdisplay /dev/hde <--my 160gig drive, I think the second drive
> > in the LVM
> >
> > - --- NEW Physical volume ---
> > PV Name /dev/hde
> > VG Name /vg_samsung
> > PV Size 19.84 MB
> > Allocatable NO
> > PE Size (K..) 0
> > Total PE 0
> > Free PE 0
> > Allocated PE 0
> > PV UUID fXhdbW-S1KK-lSNs-kGSQ-dsb6-9Kkn-Q7xeTk
> >
> > That looks bad to me, but the first drive in the volume looks ok:
> >
> > mog root # pvdisplay /dev/hdg <--my 80gig drive
> > - --- Physical volume ---
> > PV Name /dev/hdg
> > VG Name /vg_samsung
> > PV Size 74.56 GB / not usable 31.57 MB
> > Allocatable yes (but full)
> > PE Size (K..) 16384
> > Total PE 4770
> > Free PE 0
> > Allocated PE 4770
> > PV UUID aE0Tfs-UX8r-oTma-Eo35-mxSg-ZT5w-ZHPPTW
> >
> > so it looks like windows only blasted the second of the two drives (which
> > came first in the bios) (or the
> > first one it found?)
> >
> > I am desperate to get this data back (and unfortunately my /etc/lvm/backup or
> > archive are empty :(
> >
> > Thankyou very much in advance!
> > - --
> >
> > - --Andrew Bovill
> > PGP fingerprint: A00A 1E75 3AB0 610E 2300 6855 1890 C61E E590 F777
> > Link to PGP key: http://linuxboy.dyndns.org/~andy/public_key.gpg
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.1 (GNU/Linux)
> >
> > iD8DBQFCNN9xGJDGHuWQ93cRAtPnAJ9FbTYTo4qQHq4KAtCgchboewhtRQCfce/l
> > Bk3ODWAXSpgnJz0i55RJK/Y=
> > =bymV
> > -----END PGP SIGNATURE-----
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
