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 a bunch 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.
5 Answers
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
Just disable the floppy drive in the Bios system, same thing happend to me did that working fine now.
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
reboot
I have been fiddling and fooling around with that for yet rather a long 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 -uand your problems should be over.