media-automount-generator is not automounting drive

I made a fresh install of Bazzite and my freshly formatted drive appears to not auto mount. The drive has only one partition which is formatted as btrfs.
30 Replies
asen23
asen233d ago
this is interesting cases, the issue is at boot the generator only found the nvme drives as seen here
No description
asen23
asen233d ago
but if you trigger daemon-reload, the generator will find the other device that is initially not included
No description
asen23
asen233d ago
below the red line is when you trigger the daemon-reload
asen23
asen233d ago
the generated mount unit arent active so it still doesnt work
No description
asen23
asen233d ago
@Zeglius any idea what causes this? i think there is some race condition https://paste.centos.org/view/029e77cd the full logs
Zeglius
Zeglius3d ago
somewhat the storage devices arent detected the moment the generator runs
asen23
asen233d ago
The weird part is even nvme0 aren't even detected initially
Zeglius
Zeglius3d ago
I had someone with an nvme, and they got it detected By any chance is there any LVM/LUKS related with these partitions?
asen23
asen233d ago
@Neil
Neil
NeilOP3d ago
shouldn't be I only used the defaults for installing Bazzite only other OS on here is Windows 11
Zeglius
Zeglius3d ago
okay, turn off the pc, turn on again and run this in the terminal
systemd-analyze dot "*.device" local-fs.target | dot -Tpng > systemd.png; wl-copy < systemd.png
systemd-analyze dot "*.device" local-fs.target | dot -Tpng > systemd.png; wl-copy < systemd.png
This will put a graph image into your clipboard, paste it here
Zeglius
Zeglius3d ago
Something kinda like this
No description
Zeglius
Zeglius3d ago
After that run the sudo systemctl daemon-reload and run the command above again and paste here
Neil
NeilOP3d ago
bash: dot: command not found
Zeglius
Zeglius3d ago
oh god forgot, brew install graphviz and try again
Neil
NeilOP3d ago
Before reload
No description
Neil
NeilOP3d ago
After Reload
No description
Zeglius
Zeglius3d ago
mm okay no clue maybe lsblk for some reason is not detecting the devices. What we can do is try with the next release of the generator and see if works
cd $(mktemp -d) && \
curl -fsSLo - https://github.com/Zeglius/media-automount-generator/archive/refs/tags/v0.2.4.tar.gz | \
tar -xz --strip-components=1 && \
sudo DESTDIR=/usr/local ./install.sh
cd $(mktemp -d) && \
curl -fsSLo - https://github.com/Zeglius/media-automount-generator/archive/refs/tags/v0.2.4.tar.gz | \
tar -xz --strip-components=1 && \
sudo DESTDIR=/usr/local ./install.sh
try running that, and reboot
Neil
NeilOP3d ago
./install.sh: line 1: +#!/bin/bash: No such file or directory typo in the install script?
Zeglius
Zeglius3d ago
aaaa it seems yeah
Neil
NeilOP3d ago
edit it out are rerun?
Zeglius
Zeglius3d ago
ye well actually simply run sudo DESTDIR=/usr/local ./install.sh after editing it
Neil
NeilOP3d ago
ok done that didnt work
Zeglius
Zeglius3d ago
pfff no clue then, need to look into that. For now run this to uninstall and after do the manual steps in the docs
cd $(mktemp -d) && \
curl -fsSLo - https://github.com/Zeglius/media-automount-generator/archive/refs/tags/v0.2.5.tar.gz | \
tar -xz --strip-components=1 && \
sudo DESTDIR=/usr/local ./install.sh uninstall
cd $(mktemp -d) && \
curl -fsSLo - https://github.com/Zeglius/media-automount-generator/archive/refs/tags/v0.2.5.tar.gz | \
tar -xz --strip-components=1 && \
sudo DESTDIR=/usr/local ./install.sh uninstall
Neil
NeilOP3d ago
rm: cannot remove '/usr/local/lib/systemd/system-generators/media-automount-generator': Is a directory
Zeglius
Zeglius3d ago
what
Zeglius
Zeglius3d ago
No description
Neil
NeilOP3d ago
file /usr/local/lib/systemd/system-generators/media-automount-generator output: /usr/local/lib/systemd/system-generators/media-automount-generator: directory
Zeglius
Zeglius3d ago
okay so sudo rm -rf /usr/local/lib/systemd/system-generators/media-automount-generator /usr/local/lib/media-automount.d/ should do it
Neil
NeilOP3d ago
done

Did you find this page helpful?