Well you did set the title to
Having problems with Gnome Disks no longer auto mounting after updating?
And your topic states
Both places state that Gnome Disk is to blame.
I am merely pointing out that Gnome Disk is not auto mounting anything and the point of failure must lie somewhere else.
I see a that all the extra devices has the nofail option.
Therefore the device will not be mounted if it is not present when fstab is parsed by systemd.
I suggest you re-evaluate how you mount devices and make sure they are accessible when accessed.
using mount units
The following guides was migrated from the previous forum in August 2020, but they are equally valid today.
[root tip] [How To] Use systemd to mount ANY device
[root tip] [How To] systemd mount unit samples
Sampling the required units for your last addition
Example of mount unit if devices is NOT removable
File /etc/systemd/system/Heavy2.mount
[Unit]
Description=Mount Heavy2
[Mount]
What=/dev/disk/by-partlabel/Heavy2
Where=/mnt/Heavy2
Type=auto
# the following lines should be omitted when using automount unit
# omitting them will prevent direct activation by `systemctl enable` command
[Install]
WantedBy=multi-user.target
Example of automount unit if device is removable - can be omitted if it permanently attached to your system.
File `/etc/systemd/system/Heavy2.automount
[Unit]
Description=Automount Heavy2
ConditionPathExists=/mnt/Heavy2
[Automount]
Where=/mnt/Heavy2
TimeoutIdleSec=3600 # if idle for more than an hour unmount it
[Install]
WantedBy=multi-user.target
Depending on whether the device is removable or not you will start and enable ONLY one of the units. NEVER enable both - only one or the other.
If removable - enable ONLY the automount unit - which will then trigger the mount unit when you access the mountpoint - e.g. using your file manager.
systemctl enable --now Heavy2.automount
Otherwise you can enable and start the mount unit
systemctl enable --now Heavy2.mount