My guess is that the partition table got sprayed with bad data on power down.

if one had a listing of partitions such as that provided by fdisk /dev/hda -l
you should be able to rebuild the partition table. 

Of course having a copy of the MBR would make life easier

dd if=/dev/hda of=backup-hda.mbr count=1 bs=512

Assuming one has neither, if one has notes from the partitioning, you could 
try them on a spare hard drive and see if they match the still working part 
on the machine with the bad table.

Of course, if the hard disk is bad, this is all pointless. The manufacturer 
usually provides a non-destructive test.

I have only had one or two cases like this come up and my memory is foggy.



On Wednesday 05 June 2002 06:44 am, you 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.

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to