Drives no longer automount when configured in fstab

Ask Fedora
,
1

After upgrading to Fedora 41, my drive configured in /etc/fstab no longer mounts when plugged in. Before upgrading, this was the case. I am NOT talking about drives being mounted when they are not configured in /etc/fstab. My fstab entry is as follows:

UUID=e878b990-ee59-49a0-a2a7-e0fd064be5b5 /drv/external2 ext4 users,nosuid,nodev,nofail,x-gvfs-show 0 0

2

If the drive is already connected when you boot or reboot does it mount?

A drive that is connected after the system is booted is managed by udev whether entered in fstab or not.

1 Like
3

Hi Jeff,

The drive does indeed mount on boot if it is connected. I don’t remember configuring anything with udev to make it mount on plugin before. Maybe some default changed? Could you point me to a place to look for some sort of configuration?

Thanks in advance

4

Added f41, udev-rules

5

In the past I have not needed to do anything with udev for connecting drives after boot (similar to what you report). It is possible something has changed.

A search online for ‘udev rules’ will provide a lot of links.
This is one that seems to provide guidance on how to structure the rules.
https://wiki.debian.org/udev

You will, of course, need to tailor the rule to match your hardware.

6

Do you have a similar setup in the moment? If so, does it work for you?
Thanks for the wiki link, I will check it out

7

Have not for quite some time.

9

Hello Vladislav,

Thanks for the tip but that did not seem to work.

10

I think I found the issue: Fedora 41 includes the /usr/lib/udev/rules.d/64-ext4.rules file. This rule forbids ext4 automounting and was not present in Fedora 40. Overwriting it with an empty file /etc/udev/rules.d/64-ext4.rules fixed the issue. Can anyone confirm the properness/safety of this fix?

4 Likes
11
1 Like
12

Yep, so seems to me that it’s preventing a quite marginal attack vector and so would be safe to disable

3 Likes