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

last updated in Categories , , , , , ,

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:

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
# 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

Posted by: Vivek Gite

The author is the creator of nixCraft and a seasoned sysadmin, DevOps engineer, and a trainer for the Linux operating system/Unix shell scripting. Get the latest tutorials on SysAdmin, Linux/Unix and open source topics via RSS/XML feed or weekly email newsletter.

Notable Replies

  1. I have been fideling and fooling around with that for yet rather a lang time.

    A short and a long solution.

    This is the short one:

    • First see that your fstab file is okay, especially your swap partition.
    • Than run:
    sudo update-initramfs -u

    and your problems should be over.

    The long version written by someone else which I did not take note of. (Sorry people!)

    Use blkid to determine the UUID of your swap partition, and while at it, make sure all other partitions have correct UUID’s in /etc/fstab. Also can use lsblk -f to find the UUID’s.

    Put the correct UUID’s into /etc/fstab, especially swap, for this error.

    Put the correct UUID for swap into /etc/initramfs-tools/conf.d/resume.


    sudo update-initramfs -u

    Reboot. Fixed my triple boot of Stretch all with this error, as the swap file had changed. The problem was due to my swap being encrypted. So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device.

    To disable this (as resuming from swap is not possible with an encrypted swap, and I don’t use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume.

    In this file, a line with


    (instead of the UUID that was here) will disable waiting for a resume device.


    sudo update-initramfs -u

    to apply the changes.

    System now boots normally.


Continue the discussion www.nixcraft.com


Historical Comment Archive

18 comment

  1. 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… :)

  2. 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

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

  4. 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.

  5. These commands work in the terminal:

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

  6. 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

  7. 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

  8. 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?

  9. 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

    Still, have a question? Get help on our forum!