On Wed, 05 Jun 2002 12:44:43 +0200 Laurent BOULEAU <[EMAIL PROTECTED]> wrote:
> Hi > > On a mandrake 8.1 with a 40 Go DD, and with this partitions : > hda1 : /boot > hda5 : swap > hda6 : / ext3 > hda7 : /usr ext3 > hda8 : /var ext3 > hda9 : /home ext3 > hda10 : /web ext3 > hda11 : /mysql ext3 > > After a freeze and a hard reboot, I lost hda8, 9 10 and 11 partitions. > Suite � un plantage, j'ai perdu les partitions hda8, 9, 10 et 11 > > /Procs/partitions end with hda8, no 9, 10, 11 at all : the description > of the 8th is : > > major minor #blocks name rio rmerge rsect > ruse wio wmerge wsect wuse running use aveq > 3 8 5004247 ide/host0/bus0/target0/lun0/part8 1 0 2 > 20 0 0 0 0 0 20 20 > > > Same things with /dev/hda*. I have /dev/hda1, /dev/hda2, /dev/hda5, > /dev/hda6, /dev/hda7, /dev/hda8 as link to respectives > /dev/ide/host0/bus0/target0/lun0/disc/partx, and a /dev/hda11, but no > hda9, 10 and 11 > > I try an fsck of /dev/hda8 and I have : > couldn't find ext2 superblock, trying backup blocks... > fsck.ext3 : Bad magic number in super-block while trying to open > /dev/hda8 > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the > superblock is corrupt, and you might try running e2fsck with an > alternate superblock : > e2fsck -b 8193 <device> > > I try this command but it return same things. > > > Someone could help ? > > Thanks > Excuse my bad english. Laurent, I had something simular happen recently, and for me there was a way out. 1. First run fdisk /dev/hda then at the new prompt enter p This will give you what it currently thinks the partition table is. Write it down and keep it so if it doesn't work you can at least return to this point. 2. Get tomsrtbt or another recovery disk (disk 1 of your Mandrake install for example) boot from it and run gpart /dev/hda Gpart will attempt to "discover" the partition table of the disk. I've had really good luck with it finding the lost partitions. 3. Run fdisk again on /dev/hda and modify your current partition table to match the "missing" partions that gpart found. Most likely partition 8 has "grown" to include 9 10 and 11 and will have to be shrunk. 4. To test, try and mount 9 10 and 11 and you should see your data returned to a usable state. (minor tweaking may be needed but so far for me if gpart said the partition was 1004mb it was exactly that.) 5. fsck those partions. 6. Reboot and enjoy. Like I said I've had to use this 3 or 4 times and so far I've had 100% recovery when all I did was lose partition data. James > > -- > Laurent BOULEAU > Universit� de Reims > Centre de Ressources Informatiques > mailto:[EMAIL PROTECTED] > Tel : 0326913127 > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
