[SOLVED] 'Dependency failed for local filesystems' hanging up boot
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
'Dependency failed for local filesystems' hanging up boot
I'm having an issue booting, that I've not had before. The boot hangs on fsck checking some large storage drives I have, as well as my Windows partition (I dual-boot), and then drops me into the emergency mode. Fortunately, if I remove those drives from my fstab (using the live installer on a USB stick), the system will boot normally. I'm able to manually mount all 3 normally as well, and I've checked my two ext4 drives (the internal and external) for errors, and can find nothing wrong with them. For that matter, I find it rather hard to believe all 3 are bad. So why is giving me trouble?
The only thing I can think is maybe my fstab file is configured wrong?
This is it:
Code:
#/etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p3 during installation
UUID=c2b1b8a2-b4cc-4995-9510-c688683a1be4 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme1n1p1 during installation
UUID=9605-F2A3 /boot/efi vfat umask=0077 0 1
# swap was on /dev/nvme0n1p2 during installation
UUID=10073f9a-0a59-4de9-86f1-e32fdeea2bc4 none swap sw 0 0
# /home/sda1 - internal storage
UUID=33DC0CBC-7E5B-49BD-A06F-27DD1F36E4D5 /home/sda1 ext4 defaults 0 1
# /home/external - external storage
UUID=5990C1C8-E82D-C149-A23F-7B87D3C3073D /home/external ext4 defaults 0 1
# /home/windows - Windows NTFS partition
UUID=5C3E8B9F-B74B-4964-9DA7-73CDE123CA5E /home/windows ntfs-3g defaults 0 0
Any ideas? I've seen similar threads here, but no solution that seems to help for me, so far.
The uuids appear to be wrong in the fstab:
fstab:# /home/external - external storage
UUID=5990C1C8-E82D-C149-A23F-7B87D3C3073D
lsblk:
external d579bf5d-b06a-4b8c-8cff-00440b00a74d
It appears that no UUIDs match other then the system filesystems. If you have reformatted any of those filesystems the UUID will change. You need to change your /etc/fstab to match.
It appears that no UUIDs match other then the system filesystems. If you have reformatted any of those filesystems the UUID will change. You need to change your /etc/fstab to match.
Yeah that was the problem. I simply put the wrong UUIDs in. I was copying them over from KDE's Partition Manager, and was using the partition UUIDs instead. I just changed them to the proper UUID and my system booted normally. Problem solved.
Thanks, and also thanks to colorpurple21859 for pointing out that simple mistake. I shoulda known... *groans*
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.