| 1 |
Am Dienstag, den 13.06.2006, 13:36 +0200 schrieb |
| 2 |
ralf.prengel@×××××××.de: |
| 3 |
|
| 4 |
> |
| 5 |
> > -----Ursprüngliche Nachricht----- |
| 6 |
> > Von: Prengel, Ralf |
| 7 |
> > Gesendet: Dienstag, 13. Juni 2006 13:17 |
| 8 |
> > An: gentoo-user-de@l.g.o |
| 9 |
> > Betreff: Re: [gentoo-user-de] ext3 scheint hin zu sein |
| 10 |
> > |
| 11 |
> > Christian Diehl schrieb: |
| 12 |
> > > Meine Kristallkugel verrät mir, daß Du ein |
| 13 |
> > Linux-Software-Raid verwendest. |
| 14 |
> > > Was für ein Raid ist das? Ist das Raid intakt? Was sagt mdadm oder |
| 15 |
> > > 'cat |
| 16 |
> > |
| 17 |
> > Raid selber läuft. |
| 18 |
> > Es scheint nur das Filesystem darauf hin zu sein . |
| 19 |
> |
| 20 |
> linuxnfs:/tmp # e2fsck -b 8193 /dev/md1 |
| 21 |
> e2fsck 1.38 (30-Jun-2005) |
| 22 |
> e2fsck: Bad magic number in super-block while trying to open /dev/md1 |
| 23 |
> |
| 24 |
> The superblock could not be read or does not describe a correct ext2 |
| 25 |
> filesystem. If the device is valid and it really contains an ext2 |
| 26 |
> filesystem (and not swap or ufs or something else), then the superblock |
| 27 |
> is corrupt, and you might try running e2fsck with an alternate superblock: |
| 28 |
> e2fsck -b 8193 <device> |
| 29 |
|
| 30 |
Du scheinst ein 4k blocksize zu verwenden. |
| 31 |
> Block size: 4096 |
| 32 |
Versuch doch mal, ob Du einen anderen superblock bei 32768 findest. |
| 33 |
|
| 34 |
aus man fsck.ext3: |
| 35 |
-b superblock |
| 36 |
|
| 37 |
Instead of using the normal superblock, use an alternative |
| 38 |
superblock specified by superblock. This option is normally used |
| 39 |
when the primary superblock has been corrupted. The location of |
| 40 |
the backup superblock is dependent on the filesystem's |
| 41 |
blocksize. For filesystems with 1k blocksizes, a backup |
| 42 |
superblock can be found at block 8193; for filesystems with 2k |
| 43 |
blocksizes, at block 16384; and for 4k blocksizes, at block |
| 44 |
32768. |
| 45 |
Additional backup superblocks can be determined by using the |
| 46 |
mke2fs program using the -n option to print out where the |
| 47 |
superblocks were created. The -b option to mke2fs, which |
| 48 |
specifies blocksize of the filesystem must be specified in order |
| 49 |
for the superblock locations that are printed out to be |
| 50 |
accurate. |
| 51 |
If an alternative superblock is specified and the filesystem is |
| 52 |
not opened read-only, e2fsck will make sure that the primary |
| 53 |
superblock is updated appropriately upon completion of the |
| 54 |
filesystem check. |
| 55 |
|
| 56 |
|
| 57 |
Matthias |
Archives