| 1 |
> -----Ursprüngliche Nachricht----- |
| 2 |
> Von: Ramin Torabi [mailto:ramin.t@×××.de] |
| 3 |
> Gesendet: Dienstag, 13. Juni 2006 14:20 |
| 4 |
> An: gentoo-user-de@l.g.o |
| 5 |
> Betreff: Re: AW: [gentoo-user-de] ext3 scheint hin zu sein |
| 6 |
> |
| 7 |
> ralf.prengel@×××××××.de wrote: |
| 8 |
> |
| 9 |
> > |
| 10 |
> >linuxnfs:/tmp # e2fsck -b 8193 /dev/md1 e2fsck 1.38 (30-Jun-2005) |
| 11 |
> >e2fsck: Bad magic number in super-block while trying to open /dev/md1 |
| 12 |
> > |
| 13 |
> >The superblock could not be read or does not describe a correct ext2 |
| 14 |
> >filesystem. If the device is valid and it really contains an ext2 |
| 15 |
> >filesystem (and not swap or ufs or something else), then the |
| 16 |
> superblock |
| 17 |
> >is corrupt, and you might try running e2fsck with an |
| 18 |
> alternate superblock: |
| 19 |
> > e2fsck -b 8193 <device> |
| 20 |
> > |
| 21 |
> > |
| 22 |
> > |
| 23 |
> Dann nimm doch mal einen anderen Superblock! |
| 24 |
> Wo die liegen bekommt man z.B. mit |
| 25 |
> mke2fs -n /dev/md1 |
| 26 |
> raus. |
| 27 |
> |
| 28 |
|
| 29 |
das habe ich jetzt auch gemacht aber |
| 30 |
linuxnfs:~ # fsck.ext2 -p -b 294912 /dev/md1 |
| 31 |
/dev/md1: Superblock has an invalid ext3 journal (inode 8). |
| 32 |
CLEARED. |
| 33 |
*** ext3 journal has been deleted - filesystem is now ext2 only *** |
| 34 |
|
| 35 |
/dev/md1: Superblock doesn't have has_journal flag, but has ext3 journal inode. |
| 36 |
CLEARED. |
| 37 |
/dev/md1: The filesystem size (according to the superblock) is 87915504 blocks |
| 38 |
The physical size of the device is 87915456 blocks |
| 39 |
Either the superblock or the partition table is likely to be corrupt! |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-user-de@g.o mailing list |
Archives