≡ Menu

Buffer I/O error on device fd0, logical block 0 error and simply soultion

Q. I’ve CentOS 5 server running on Dell hardware. I’m getting following error message in my /var/log/message file (some time message is also shown on console):

Jul 05 12:04:05 dell01 kernel: end_request: I/O error, dev fd0, sector 0
Jul 05 12:04:05 dell01 kernel: Buffer I/O error on device fd0, logical block 0
Jul 05 12:04:18 dell01 kernel: end_request: I/O error, dev fd0, sector 0
Jul 05 12:04:18 dell01 kernel: Buffer I/O error on device fd0, logical block 0
Jul 05 12:04:30 dell01 kernel: end_request: I/O error, dev fd0, sector 0
Jul 05 12:04:42 dell01 kernel: end_request: I/O error, dev fd0, sector 0

What do they mean? How do I fix this problem?

A. This message appears when you don’t have a floppy drive attached to Linux server. Solution is quite simple just disable driver for floppy and reboot the system. You can verify this with the following command (this solution works with RHEL, CentOS, Redhat, Ubuntu/Debian and other Linux distros) :
# lsmod | grep -i floppy
Output:

floppy                 95465  0

Open file called /etc/modprobe.d/blacklist:
# vi /etc/modprobe.d/blacklist
Listing a module (driver name) in this file prevents the hotplug scripts from loading it. Usually that'd be so that some other driver will bind it instead,
no matter which driver happens to get probed first. Sometimes user mode tools can also control driver binding. Append following line:
blacklist floppy
Save and close the file. Now reboot the Linux server:
# reboot

Tweet itFacebook itGoogle+ itPDF itFound an error/typo on this page?

{ 16 comments… add one }

  • SW January 19, 2008, 3:05 pm

    Thanks for the helpful info! I ran into this issue and your solution does seem to fix it!

  • Vadim February 17, 2008, 7:00 pm

    thanks for info. it is also possible to do:
    sudo modprobe -r floppy
    so there will be no need to reboot

  • Aaron February 18, 2008, 6:12 pm

    where do u do the lsmod | grep -i floppy thing?

  • doez March 23, 2008, 12:19 am

    thank’s

  • treez March 28, 2009, 10:08 pm

    Aaron, you have to put this into your terminal or console, e.g. by going with Ctrl-Alt-F1 into the first TTY (TTY1). Enter user and password and su to root. There you go. Now you are ready to insert these commands and everything works as expected… :)

  • asd June 7, 2009, 1:08 am

    thanks :)

  • anon October 30, 2009, 8:20 pm

    you may also comment out the line (fd0) in /boot/grub/device.map file.

  • pABLO March 13, 2010, 8:57 pm

    Hi, can somebody tell me step by step what should I do? Im not so into computer system. I already disable floppy, Im not getting the same error anymore, but it doesnt go anywhre. It send me to a busybox 3.1 screen, but I dont know what am I supposed to write iin order to make it finish the intallation. Thanks in advance. I have windows vista and Im trying to intall UBUNTU

  • Steff May 7, 2010, 1:30 pm

    Type it in Terminal? When I paste ”blacklist floppy” it says ”cklist floppy”. Could you please be more specific?

  • Flip May 11, 2010, 8:17 pm

    Thanks, this fix also worked on a Thinkpad T42 running Xubuntu 10.04

  • ag February 9, 2011, 6:50 pm

    Thanks for the tip. I was having these messages for a long time and with a quick look have found the solution in your web.

  • NoahY July 11, 2011, 8:52 am

    These commands work in the terminal:

    sudo su
    echo -e ‘\nblacklist floppy’ >> /etc/modprobe.d/blacklist.conf
    exit

  • Asad August 21, 2012, 4:27 pm

    Wow, i spent 2 days working on it. i was getting i.o error on ubuntu live usbs and also in boot-repar application so i disabled my floppy and i also diasbled by dvd(may not be required). and it worked. THANK YOU

  • chad February 12, 2013, 6:29 am

    disable the floppy device in BIOS

    make sure that the floppy drive is getting power
    make sure that the floppy drive cable is attached at both ends
    make sure that the floppy drive light is not on ALL THE TIME (if it is, flip it around you put it on backwards)
    replace the floppy drive with a known working unit

  • Carl March 13, 2013, 8:07 pm

    My BIOS has no options pertaining to floppies. The floppy driver is not being used. What gives? Does anyone have another explanation for these errors?

  • Xosupher Anderson July 12, 2015, 5:52 pm

    This method works however the correct path of the modprobe file is /etc/modprobe.d/blacklist.conf
    sudo su
    nano /etc/modprobe.d/blacklist.conf
    blacklist floppy
    reboot

Leave a Comment