> Before doing any more damage, > make at least one disk image of what you have. > If a disk image is a file of a larger drive, > you can use loopback to examine it. > If you want to make changes, don't use your only copy. > > -- > Mike hennebry@xxxxxxxxxxxxxxxxxxxxx > "Horse guts never lie." -- Cherek Bear-Shoulders I'm not sure how to do that when I can't even mount the disk. Any suggestions on what to do next? I've noticed that lvm archives a volume group configuration when a change is made to it (under /etc/lvm/archive.. In plain text too!) By looking at these I can tell exactly what commands I ran in order to muck things up... Fri Sep 21 17:56:48 2007: 'vgextend VolGroup00 /dev/sdb2' Fri Sep 21 18:25:40 2007: 'vgreduce VolGroup00 /dev/sdb2' Fri Sep 21 18:25:45 2007: 'vgcreate VolGroup01 /dev/sdb2' Mon Sep 24 18:37:52 2007: 'vgremove VolGroup01' Tue Sep 25 13:51:10 2007: 'vgcreate VolGroup01 /dev/sdb2' I can also tell what pv's and lv's belonged to the corresponding VolGroup in each archive. (btw, I've seen archived threads from what looks to be an old linux-lvm specific mailing list. Anyone know if this still exists? I can't find it anywhere) -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
