> ive done the badblock test, and compiled a list of 2302 bad blocks on this
> disk ... however, when running mke2fs -l badblocfile /dev/hdc1
>
> i got this interesting errormessage for every one of the bad blocks :
>
> Bad block 1006290 out of range; ignored.
>
> mke2fs said my disk was my disk would be 132480 inodes, 264592 blocks in
> size ...
>
> some bits in proc (well this capacity one i dont know what it measures)
>
> root:/root# cat /proc/ide/hdc/capacity
> 2116800
Your disk has 2116800 sectors of size 512, that is, 1083801600 bytes
(slightly over 1 GB).
> root:/root# cat /proc/ide/hdc/geometry
> physical 2100/16/63
> logical 525/64/63
>
> is there a geometry problem ?
Nothing wrong here.
> whats causing bad blocks to give apparently
> excessivly large bad blocks ...?
2116800 sectors of size 512 is the same as 1058400 blocks of size 1024.
Nothing is wrong with block 1006290 being mentioned.
Note that hdc1 is a partition on hdc, not all of hdc.
> > kernel: end_request: I/O error, dev 16:00 (hdc), sector 2116604
> > kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest
> > Error }
> > kernel: hdc: read_intr: error=0x40 { UncorrectableError },
At first sight this is just a rotten disk.
But since this is very close to the end of the disk, you might
investigate some details. (Some ZIP disks can be used as big floppy
and as removable disk, that is, without or with partition table,
and differ a little in size depending on what you do.
Don't know whether something similar could apply in your case.)
Of interest:
(i) the output of dmesg | grep hdc
(ii) the first sector that fails (is it this 2116604?)
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/