doglott ext2

Marton Fabo morton at eik.bme.hu
2001. Május. 25., P, 19:16:42 CEST


Hali!

Bocs, hogy itt kerdezek ilyesmit, de nem vagyok linuxos listan, es 
titeket segitokeszebb tarsasagnak ismerlek, mint az inkabb erintetteket 
(nem flame-elni akarok).

Szoval egy debian linuxos gepben valahogy (???) megdoglott egy ext2 
particio, es nem tudom, mit lehetne vele csinalni, hogy az adatok ne 
vesszenek el. Ime amit az fsck mond:

>spawn:~# fsck /dev/hda1
>Parallelizing fsck version 1.18 (11-Nov-1999)
>e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
>fsck.ext2: Filesystem revision too high while trying to open /dev/hda1
>The filesystem revision is apparently too high for this version of 
e2fsck.
>(Or the filesystem superblock is corrupt)
>
>
>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>
>
>spawn:~# fsck -b 8193 /dev/hda1
>Parallelizing fsck version 1.18 (11-Nov-1999)
>e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
>fsck.ext2: Bad magic number in super-block while trying to open /dev/
hda1
>
>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>
>
>spawn:~# fsck -b 16385 /dev/hda1
>Parallelizing fsck version 1.18 (11-Nov-1999)
>e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
>fsck.ext2: Bad magic number in super-block while trying to open /dev/
hda1
>
>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>
>
>spawn:~#     

Az fsck.ext2 man-jabol:

>OPTIONS
>[...]
>       -b superblock
>              Instead  of  using  the  normal  superblock, use an
>              alternative  superblock  specified  by  superblock.
>              This  option  is  normally  used  when  the primary
>              superblock has  been  corrupted;  most  filesystems
>              have  primary  superblocks  located at blocks 8193,
>              16385, etc.  If an alternative superblock is speci-
>              fied  and  the  filesystem is not opened read-only,
>              e2fsck will make sure that the  primary  superblock
>              is  updated  appropriately  upon  completion of the
>              filesystem check.  

Ha valakinek van valami otlete, irja mar meg...

koszi

											mortee



További információk a(z) BSD levelezőlistáról