| 1 |
On Wednesday 23 August 2006 21:53, Ronald Vazquez wrote: |
| 2 |
> Checking root filesystem ...fsck.ext3: Invalid argument while trying |
| 3 |
> to open /dev/md0 |
| 4 |
> /dev/md0: |
| 5 |
> The superblock could not be read or does not describe a correct ext2 |
| 6 |
> filesystem. If the device is valid and it really contains an ext2 |
| 7 |
> filesystem (and not swap or ufs or something else), then the superblock |
| 8 |
> is corrupt, and you might try running e2fsck with an alternate superblock: |
| 9 |
> e2fsck -b 8193 <device> |
| 10 |
> |
| 11 |
> |
| 12 |
> * Filesystem couldn't be fixed :( |
| 13 |
|
| 14 |
apologies for multiple posting, I didn't actually address your primary |
| 15 |
concern, just skipped over it and went to what caused the problem. ext3 is an |
| 16 |
addition to ext2. ext3 is backwards compatible with ext2, you can overlook |
| 17 |
what fsck says, don't take it literally, it is just saying it can't find an |
| 18 |
ext* filesystem at all regardless of which version of ext* it tries. |
| 19 |
|
| 20 |
Hamish |
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-sparc@g.o mailing list |
Archives