On Mon, Jan 26, 2004 at 02:05:10PM -0500, Eben King wrote:
> Hi. Whenever I read data from the floppy drive, I get messages like
> these:
>
> Jan 26 00:12:59 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 0
> Jan 26 00:13:12 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 0
> Jan 26 00:13:24 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 1
> Jan 26 00:13:36 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 2
> Jan 26 00:13:48 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 3
> Jan 26 00:14:00 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 4
> Jan 26 00:14:12 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 5
> Jan 26 00:14:24 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 6
> Jan 26 00:14:36 pc kernel: end_request: I/O error, dev 02:00 (floppy),
> sector 7
>
> and the reading process dies with "standard input: file: read failed
> (Input/output error)". How can I debug this?
>
If this happens on _every_ _formatted_ floppy you put in, then yeah,
maybe it's a hardware problem. But I've had this on individual floppies.
And in fact, I've found that sometimes the floppy drivers in kernels are
pretty dodgy. I've actually had to reboot Linux machines at times to get
them to properly read floppies. Somehow their internal tables must get
messed up at times. I don't know if that's the case with the 2.4.22
kernel, but as a last resort before replacing the drive, I'd reboot and
try to mount/read a _known_ _good_ floppy, DOS or ext2.
Paul
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:31:06 EDT