Hey...
Having problems mounting a vfat/msdos floppy. Attached are the error
messages... the drive seeks, etc. It has worked in the past.
Kernel 2.3.99pre6-1
Epox MVP3C2 motherboard
3.5", 5.25" floppy drives
Error messages are as follows:
(basic errors)
mount: block device /dev/fd1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/fd1,
or too many mounted file systems
relevant entries /etc/fstab:
/dev/fd0 /mnt/floppy vfat noauto
0 0
/dev/fd1 /mnt/bigfloppy vfat noauto
0 0
more detailed errors:
klogd 1.3-3, log source = /proc/kmsg started.
Inspecting /boot/System.map
Loaded 11706 symbols from /boot/System.map.
Symbols match kernel version 2.3.99.
Loaded 337 symbols from 20 modules.
<7>VFS: Disk change detected on device fd(2,0)
<4>
<4>floppy driver state
<4>-------------------
<4>now=371361 last interrupt=371025 diff=336 last called
handler=c015eea8
<4>timeout_message=floppy start
<4>last output bytes:
<4> 0 90 371025
<4>13 90 371025
<4> 0 90 371025
<4>1a 90 371025
<4> 0 90 371025
<4> 3 90 371025
<4>c1 90 371025
<4>10 90 371025
<4> 7 80 371025
<4> 0 90 371025
<4> 8 81 371025
<4>e6 80 371063
<4> 0 90 371063
<4> 0 90 371063
<4> 0 90 371063
<4> 1 90 371063
<4> 2 90 371063
<4>12 90 371063
<4>1b 90 371063
<4>ff 90 371063
<4>last result at 371025
<4>last redo_fd_request at 371025
<4>20 0
<4>status=50
<4>fdc_busy=1
<4>DEVICE_INTR=c015df84
<4>fd_timer.function=c015def4
<4>cont=c0223a68
<4>CURRENT=c02a6d70
<4>command_status=-1
<4>
<4>floppy0: floppy timeout called<4>end_request: I/O error, dev 02:00
(floppy), sector 0
<7>VFS: Disk change detected on device fd(2,0)
<4>
<4>floppy driver state
<4>-------------------
<4>now=371661 last interrupt=371361 diff=300 last called
handler=c015eea8
<4>timeout_message=floppy start
<4>last output bytes:
<4> 0 90 371361
<4>13 90 371361
<4> 0 90 371361
<4>1a 90 371361
<4> 0 90 371361
<4> 3 90 371361
<4>c1 90 371361
<4>10 90 371361
<4> 7 80 371361
<4> 0 90 371361
<4> 8 81 371361
<4>e6 80 371361
<4> 0 90 371361
<4> 0 90 371361
<4> 0 90 371361
<4> 1 90 371361
<4> 2 90 371361
<4>12 90 371361
<4>1b 90 371361
<4>ff 90 371361
<4>last result at 371361
<4>last redo_fd_request at 371361
<4>20 0
<4>status=50
<4>fdc_busy=1
<4>DEVICE_INTR=c015df84
<4>fd_timer.function=c015def4
<4>cont=c0223a68
<4>CURRENT=c02a6d70
<4>command_status=-1
<4>
<4>floppy0: floppy timeout called
<4>end_request: I/O error, dev 02:00 (floppy), sector 0
<4>
<4>floppy driver state
<4>-------------------
<4>now=371961 last interrupt=371661 diff=300 last called
handler=c015eea8
<4>timeout_message=floppy start
<4>last output bytes:
<4> 0 90 371661
<4>13 90 371661
<4> 0 90 371661
<4>1a 90 371661
<4> 0 90 371661
<4> 3 90 371661
<4>c1 90 371661
<4>10 90 371661
<4> 7 80 371661
<4> 0 90 371661
<4> 8 81 371661
<4>e6 80 371661
<4> 0 90 371661
<4> 0 90 371661
<4> 0 90 371661
<4> 1 90 371661
<4> 2 90 371661
<4>12 90 371661
<4>1b 90 371661
<4>ff 90 371661
<4>last result at 371661
<4>last redo_fd_request at 371661
<4>20 0
<4>status=50
<4>fdc_busy=1
<4>DEVICE_INTR=c015df84
<4>fd_timer.function=c015def4
<4>cont=c0223a68
<4>CURRENT=c02a6d70
<4>command_status=-1
<4>
<4>floppy0: floppy timeout called
<4>end_request: I/O error, dev 02:00 (floppy), sector 0
<4>FAT bread failed
See what you can make of it... i think it's a kernel bug, possibly a
timing issue. If you think it's my hardware, feel free to explain how.
David Bronaugh
-
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/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:25 EST