Hello...
I'll say as much as I can.
A couple of days ago I did a netinstall of suse 9.2 pro. I was looking around Yast cause I'm used to Debian/Slackware/Gentoo so I've never had it
Anyway... I was looking at how to add partitions with Yast -because I wanted to test whether or not I could give it away as a neat windows replacement.. Anyway It might have been late.. But I was in the LVM (guess it stands for Linux Volume Manager). However I could swear that I exited without saving the changes. I looked around the partitions and all was swell..
(The reason for the LVM part will become apparent later)
Ok fast forward. I bought a case for having a drive connected to my pc by USB. I put the drive I messed around with in and booted up.. Initially I could still browse the first partition on the disk which has my Debian system. The other partition (which holds *all* my personal data) was unbrowseable, couldn't mount it either..
So I messed around and say they were still LVM.. I thought I could change that by using fdisk to change the disk ID's to linux (83) and it seemed to work ok till after a reboot (still couldn't see the personal data partition)..
I backed up my partition table using sfdisk -d to a file and proceeded to wipe it with dd (using /dev/zero)
SO here I am.
This is the output when analyzing the disk with Test disk (which I'm told can reconstruct my partitiontable {hopefully also fixing it, fdisk said the partitions stretched beyond the capacity of the disk somehow})
-----------------
Disk /dev/sda - CHS 32253 64 32 - 32253 MB
Check the harddisk size: HD jumpers settings, BIOS detection, OS limitation...
The following partition can't be recovered. The harddisk seems too small!
Partition Start End Size in sectors
D Linux 19080 1 1 75350 20 32 115241600 [/data]
-----------------------------
What do I do from here ? I really would like to have that data if it is at all reconstructable..
This means alot to me and if I get saved from this I'll definatly have a redundant disk for backups or so heh...
-Jesper
