Re: 2048 bytes/sector MOD + 2.2.1ac6

Alan Cox (alan@lxorguk.ukuu.org.uk)
Mon, 1 Mar 1999 00:36:04 +0000 (GMT)

> (albeit slow). But as soon as I do a 'mke2fs -c -m0 -b 2048' on my MOD
> medium, and start a 'copy -av ~ /mod', after a couple minutes, the kernel
> spits out things like this
>
> Feb 28 19:36:28 debian kernel: scsi0: MEDIUM ERROR on channel 0, id 2, lun
> 0, CDB: Write (6) 00 00 00 04 00

Medium error; Thats "disk sucks"

> Feb 28 19:36:28 debian kernel: Additional sense indicates Write error - auto
> reallocation failed

"Couldnt figure where to put the block to work around the crud disk"

> Feb 28 19:37:03 debian kernel: scsi : aborting command due to timeout : pid

Its dead Jim ?

> Feb 28 19:37:04 debian kernel: SCSI bus is being reset for host 0 channel 0.
> Feb 28 19:37:04 debian kernel: ncr53c8xx_reset: pid=146877 reset_flags=2
> serial_number=146886 serial_number_at_timeout=146886

Kick the device

> Why does the write reallocation fail? why are there medium errors on the
> drive, when neither badblocks (mke2fs -c) nor SCSI BIOS low level format

Write reallocation is up to the drive . Do you have write reallocation turned
off in the mode pages ?

Alan

-
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/