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

I am a new Linux user and sysadmin. We have a CentOS 5.x/6.x server and Ubuntu/Debian Linux desktop running on Dell server hardware. I am getting the following error message in my /var/log/messages file (some time message is also display on the console). Durning Linux box startup and boot time I see many of the following messages on screen and it is driving me crazy:

ADVERTISEMENTS

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 on Linux based system?

A floppy disk is nothing but disk storage composed of a disk of thin and flexible magnetic storage medium. Floppy disks are read and written by a FDD (Floppy Disk Drive). This message appears when you do not have a floppy drive attached to the Linux server or VM or cloud 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
Sample outputs:

floppy                 95465  0

The error look as follows on screen:
Buffer I/O error on device fd0, logical block 0 end_request: I/O error, dev fd0, sector 0

Fixing Buffer I/O error on device fd0, logical block 0

Open file called /etc/modprobe.d/my-blacklist.conf:
# vi /etc/modprobe.d/my-blacklist.conf
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 the following line:
blacklist floppy
Save and close the file. Now reboot the Linux server:
# reboot
Once rebooted you can verify it:
# dmesg
# dmesg -T

Or use the grep command/cat command or tail command:
# grep 'I/O error' /var/log/messages
# tail -f /var/log/messages

How to fix “kernel: end_request: I/O error, dev fd0, sector 0” without rebooting the Linux box

Run the following modprobe command or rm command as root user:
# modprobe -r floopy
OR
# rmmod floopy

Disable Floppy Disk Drive in BIOS

If you do not use floppy drive, disable it in your BIOS too:

  1. When you boot the server or computer visit BIOS by pressing F2 or DEL as per version of BIOS
  2. Find BIOS section that list various peripherals or drives such as floppy, USB, hard disk
  3. Disable floppy (often called as Drive A in older systems)
  4. Save and exit from BIOS settings
🐧 Get the latest tutorials on SysAdmin, Linux/Unix, Open Source/DevOps topics:
CategoryList of Unix and Linux commands
File Managementcat
FirewallAlpine Awall CentOS 8 OpenSUSE RHEL 8 Ubuntu 16.04 Ubuntu 18.04 Ubuntu 20.04
Network Utilitiesdig host ip nmap
OpenVPNCentOS 7 CentOS 8 Debian 10 Debian 8/9 Ubuntu 18.04 Ubuntu 20.04
Package Managerapk apt
Processes Managementbg chroot cron disown fg jobs killall kill pidof pstree pwdx time
Searchinggrep whereis which
User Informationgroups id lastcomm last lid/libuser-lid logname members users whoami who w
WireGuard VPNAlpine CentOS 8 Debian 10 Firewall Ubuntu 20.04

ADVERTISEMENTS
17 comments… add one
  • SW Jan 19, 2008 @ 15:05

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

  • Vadim Feb 17, 2008 @ 19:00

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

  • Aaron Feb 18, 2008 @ 18:12

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

  • doez Mar 23, 2008 @ 0:19

    thank’s

  • treez Mar 28, 2009 @ 22:08

    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 Jun 7, 2009 @ 1:08

    thanks :)

  • anon Oct 30, 2009 @ 20:20

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

  • pABLO Mar 13, 2010 @ 20:57

    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 @ 13:30

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

  • Flip May 11, 2010 @ 20:17

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

  • ag Feb 9, 2011 @ 18:50

    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 Jul 11, 2011 @ 8:52

    These commands work in the terminal:

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

  • Asad Aug 21, 2012 @ 16:27

    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 Feb 12, 2013 @ 6:29

    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 Mar 13, 2013 @ 20:07

    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 Jul 12, 2015 @ 17:52

    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

  • LUBRY May 15, 2017 @ 2:36

    before do this, you must try disable floppy drive by bios setting.

Leave a Reply

Your email address will not be published.

Use HTML <pre>...</pre>, <code>...</code> and <kbd>...</kbd> for code samples.