Hi Luca >>Disk /dev/hdb - 3249 MB / 3098 MiB - CHS 6296 16 63 >> Partition Start End Size in sectors >>* Linux 0 1 1 202 15 63 204561 [/boot] >>D Linux 203 0 1 5645 15 63 5486544 [/] >>D Linux LVM 203 0 1 6295 15 63 6141744 >>D Linux 229 0 1 5560 15 63 5374656 >>D Linux 265 0 1 5596 15 63 5374656 >> > > try with each of the linux partitions found and see if you can mount it > and get your data back. If I look at the way Redhat created a similar on a working system, I get the following information for the lv's created: # lvscan ACTIVE '/dev/VolGroup02/LogVol00' [3.56 GB] inherit ACTIVE '/dev/VolGroup02/LogVol01' [320.00 MB] inherit Based on the above information, would you say that it is a reasonable to say that on the broken drive, the first lv was LogVol00, used for data and the second lv would have been LogVol01, used for swap. Could I, like you suggested create a logical volume for the total size and perhaps get my data back (since the swap is at the end of it all?) Is creating a logical volume with lvcreate also only adjusting the information about the lvm and not actually touching the data, which means I can safely experiment, trying to change the lv's until I find the correct size? (I hope my questions make sense) Regards Jannetta Random Thought: --------------- If you are smart enough to know that you're not smart enough to be an Engineer, then you're in Business. _______________________________________________ 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/
