IDE problems ? or just a dead disk ?

hi guys,
Since its relativley quiet at the moment, please excuse me for
asking for some advice about the following problem.

for a while now ive had a disk that causes errors to occur during reads, however, ive finally got round to doing a

# badblocks -c 32 -o mybadblocks  -w -v -s /dev/hdc

so after one part of the test its found 2048 bad blocks, and dumped alot of error messages, which look like this:

kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604, sector=2116604
kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604, sector=2116604
kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604, sector=2116604
kernel: ide1: reset: success
kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
kernel: hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=2116604, sector=2116604
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 }, LBAsect=2116607, sector=2116607
kernel: end_request: I/O error, dev 16:00 (hdc), sector 2116607
kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
kernel: hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=2116608, sector=2116608
kernel: end_request: I/O error, dev 16:00 (hdc), sector 2116608
kernel: hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
kernel: hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=2116610, sector=2116610

i have tried the disk in 2 systems, one Socket7 pentium and a PII /w a BX chipset ... the only thing i can think this is is either a geometry problem ?? or a hard disk failiure ...

anyone got any ideas ?

Thanks.

Dave

i dont usually like following up my own sensless ramblings, but here is an interesting twist (probabally caused by my ill understanding of the issues involved)

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

root:/root# cat /proc/ide/hdc/geometry
physical     2100/16/63
logical      525/64/63

is there a geometry problem ? whats causing bad blocks to give apparently excessivly large bad blocks ...?

any ideas ?

Thanks,

Dave

of

LBAsect=2116607,

LBAsect=2116608,

LBAsect=2116610,

problem

Your disk has 2116800 sectors of size 512, that is, 1083801600 bytes (slightly over 1 GB).

Nothing wrong here.

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.

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

"David Flynn" <[email protected]> writes:

[...]

That is probably because badblocks was working with badblocks of a smaller size than that of the filesystem (i.e. probably 1024 bytes instead of 4096 bytes, solution in this case is to divide all bad block numbers by 4).

Well that's what happened to me today (worryingly on my newish IBM DTLA hd).

	http://ape.n3.net