SlackwareThis Forum is for the discussion of Slackware 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.
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 458
Rep:
The "no" at the start of that list means that umount ignores the filesystem types that follow, i.e., unmounts everything else. This can be verified by rebooting or halting from tty, which should show that /boot/efi is unmounted at that point.
So far as I know, the message is harmless. A dirty bit just gets set for some reason.
The "no" at the start of that list means that umount ignores the filesystem types that follow, i.e., unmounts everything else. This can be verified by rebooting or halting from tty, which should show that /boot/efi is unmounted at that point.
So far as I know, the message is harmless. A dirty bit just gets set for some reason.
Well, I watched a reboot, and /boot/efi does get cleanly unmounted, so the fsck complaint was probably old.
In any case, fsck'ing the filesystem is easy enough to get rid of the complaint, and it's better to not ignore it.
There is no need to mount the EFI partition every time you reboot.
In fact, my thoughts are that you only need to mount it if you're upgrading the kernel. It probably shouldn't be auto-mounted by default.
Funny, /boot/efi is added to /etc/fstab by the installer, there's no harm in mounting it, and manually mounting it (to copy /boot/{vmlinuz,initrd.gz} to /boot/efi/EFI/Slackware for kernel upgrades sounds silly to me.
Seeing /boot/efi mounted on a system is a pretty good hint/reminder that a system is using EFI, so I like that it gets added to /etc/fstab by default.
Not so silly. In case it is mounted and your computer crashes the crappy FAT filesystem may get corrupted. Running fsck on it may or may not repair it. Why risk with all this trouble and keep it mounted unnecessarily?
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 458
Rep:
Quote:
Originally Posted by Emerson
Not so silly. In case it is mounted and your computer crashes the crappy FAT filesystem may get corrupted. Running fsck on it may or may not repair it. Why risk with all this trouble and keep it mounted unnecessarily?
That's a good point; maybe I've been too casual about this. Removed from fstab
I would agree with you if it used any other file system, (except possibly NTFS).
FAT is among the most flaky file systems around, and easily corruptible. Linux support for it (much like NTFS) has had to be reverse-engineered. FAT has a terrible track record when it comes to data loss, corruption and recoverability. If it were up to me, we wouldn't be using it anywhere... but here we are, so we have to make do with what we have.
If there is a sudden interruption in electricity supply and your computer crashes as a result of it, there is an increased possibility that your computer won't boot due to a corrupted EFI partition if this all happened while it was mounted.
Personally, I don't find it that difficult to type 'mount /boot/efi' whenever I want to access it.
Windows 10 doesn't mount the EFI partition by default. I can't help but wonder if even a small part of Microsoft's reasoning is that they know how flaky the file system is.
Quote:
Originally Posted by slvr32
I like that it gets added to /etc/fstab by default.
Yes, me too. But I think it should have the 'noauto' option included by default as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.