Description of problem: This used to be limited to during kernel install, but with current development kernels the boot process is slowed by about 4 minutes while it tries to access the floppy drive. This is unacceptable. Messages are: Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 Loading iSCSI transport class v2.0-724. end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 This did not happen with F7 kernels. Instead I simply got: Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 Hardware is a Dell Inspiron 4150 with the removable floppy device out of the machine. Version-Release number of selected component (if applicable): 2.6.23-0.115.rc3.git1.fc8
If it helps, last message printed without "quiet" in the command line is: Mounting root filesystem Boots don't seem to hanging quite so long with 2.6.23-0.174.rc6.fc8, don't get as many messages: Loading iSCSI transport class v2.0-724. end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0 Buffer I/O error on device fd0, logical block 0 but each "end_request" takes about 30 seconds I think and it is still a pain.
Is there some other device in the bay where the floppy normally goes or is it completely empty?
Currently the CD-RW drive is in the slot.
(In reply to comment #3) > Currently the CD-RW drive is in the slot. Try it with the bay completely empty.
With the bay completely empty I get no noticeable boot delays and only a singe: end_request: I/O error, dev fd0, sector 0 line.
(In reply to comment #5) > With the bay completely empty I get no noticeable boot delays and only a singe: > > end_request: I/O error, dev fd0, sector 0 > > line. > Okay, what happens if you disable the "bay" driver and boot with the CD drive present? (Edit /etc/modprobe.d/blacklist to disable the driver.)
This is really driving me crazy and has gotten worse again. After some exploring I think this my have to do with populating /dev/disk/by-label to that mount can fine the root partition (LABEL=/1 in this case). I've been running across a lot of code in various places that insists on probing the floppy device for labels, often before searching hard disks (because /sys/block/fd0 comes before /sys/block/sda). I imagine that is this case populating /dev/disk/by-label may require probing all devices, but perhaps we could "background" probing /dev/fd0. Is any one going to rely on disklabels on floppies?
Culprit is mkinitrd's nash and block device scanning searching for labels. This really needs to get tweaked so that we probe hard drives first, or maybe completely exclude floppies from the by label/uuid search.
Based on the date this bug was created, it appears to have been reported during the development of Fedora 8. In order to refocus our efforts as a project we are changing the version of this bug to '8'. If this bug still exists in rawhide, please change the version back to rawhide. (If you're unable to change the bug's version, add a comment to the bug and someone will change it for you.) Thanks for your help and we apologize for the interruption. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.