Re: UPDATE: MOD 2048-b/s media and 2.1.131ac10

Mark-Andre Hopf (hopf@informatik.uni-rostock.de)
Sun, 17 Jan 1999 15:11:58 +0100 (MET)

> When I partition the media (which I tried to avoid doing till now) with one
> primary partition, and THEN mke2fs -b 2048 -m0 -c /dev/sdb1 it, mke2fs tells
> me that
>
> Checking for bad blocks (read-only test): done
> Block 0 in primary superblock/group descriptor area bad.
> Blocks 0 through 2 must be good in order to build a filesystem.
> Aborting....
>
> OK, I fdisk the medium to use blocks 4..606 for partition 1. Perfect. No
> errors without -c. With -c, it complains about block 0 being bad. (How can I
> still use the medium?)

> I cannot trust my MOD media under these circumstances. Is there any way to
> resolve this and make them reliable?

Make sure your E2fsprogs are updated to version 1.12. I had the same
problem with my MO. The bug was that mke2fs calls badblocks when given
the `-c' option, badblocks reports the MO being okay but then the
communication between the two programs failed and mke2fs thinks the
medium is damaged.

Hope this helps,
Mark

+-----------------------------------------------------+----------------------+
| the wizard himself, Mark-André Hopf | Every sufficiently |
| hopf@informatik.uni-rostock.de | developed technology |
| Visit the TOAD GUI Toolkit Project Homepage at | is indistinguishable |
| http://toad.home.pages.de/ | from magic. (A.C.C.) |
+-----------------------------------------------------+----------------------+

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/