This happened after a kernel update. Whenever I try to boot, my computer says "Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1) Welcome to emergency mode!..." followed by abunch of things I can do. It spits the same error out if I ctrl-d to boot into default mode, and the fstab file matches the drive UUIDs perfectly. But I think I found the culprit. When I run blkid, it takes a while, and then spits out "blk_update_request: I/O error, dev fd0, sector 0" followed by the drives' data. What is happening, why, and how do I fix it?

I tried the possible duplicate question, but it is a slightly different error and the solution doesn't work.

  • 1
    Possible duplicate of "Buffer I/O error on device fd0, logical block 0" error – Mark Kirby Jan 9 '16 at 14:38
  • I figured out that I can get it to work if I boot into recoovery mode and then tell it to fix broken packages. It doesn't seem to matter if this was sucessful or not. Then I can continue booting and it works. – Ben Jan 11 '16 at 12:20
  • Update: I discovered it doesn't NEED to be the fix broken packages option. It will in fact work with any option that remounts the file system in read-write mode. So I can only assume this problem originates from the file system not being mounted properly. – Ben Jan 12 '16 at 20:38
  • If you solved your problem yourself, please answer your own question and accept it. Don't put the answer in the comments! :-) – David Foerster Jan 13 '16 at 14:08
  • 1
    Bump. I feel no shame. – Ben Feb 7 '16 at 0:44


Your device doesn't have a floppy drive, but the floppy driver module is installed, so you have /dev/fd0, and many things will try to use it.

sudo rmmod floppy
echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf
sudo dpkg-reconfigure initramfs-tools
  • Thanks for that edit. That looks like exactly what was missing. – Auspex Jan 26 '18 at 10:26
  • 7
    For anyone coming here after searching for this error running Ubuntu in a VM under Microsoft Hyper-V, this is because by default, a floppy drive is added to the VM configuration, but not correctly activated. The answer above still solves it, but do check to see if you have a floppy device in the VM config first, and try removing that before applying this fix. I have 15 of the darn things, and so far 5 of them fixed by removing the rouge floppy from the Hyper-V machine config using Hyper-V manager. – shawty Mar 25 '18 at 15:27
  • @shawty Yes, I've seen that in VirtualBox, too. – Auspex Apr 6 '18 at 9:27

Just disable the floppy drive in the Bios system, same thing happend to me did that working fine now.


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 file.
  • Than run:

    sudo update-initramfs -u

    and your problems should be over.

The long version

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.

  • Run sudo update-initramfs -u

Reboot. Fixed my triple boot of Stretch all with this error, as the swap file had changed.

Explanation for the long version

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.

  • Run sudo update-initramfs -u to apply the changes.

  • System now boots normally.



I had a different situation. Installed ubuntu server lts 18.04 and mod floppy was active.

There was a fstab entry and activated kernel module floppy.

## check for mod floppy
lsmod | grep -i floppy

I did this:

  • comment fstab entry (or just delete it)
  • disable mod floppy - add to blacklist

Blacklist module

echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf

Without reboot:

sudo rmmod floppy
sudo dpkg-reconfigure initramfs-tools

Or with reboot


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.