cant mount home on boot
Im giving a go fedora silverblue on a new laptop but Im unable to boot (and since im a linux noob the first thing i tried was installing it fresh again but that didnt resolve it).
its a single drive partitioned to ext4 and encrypted with luks (its basically the default config from the fedora installation)
any ideas for things to try?
This entry was edited (6 months ago)
Max-P
in reply to evasync • • •The error says
/home
is a symlink, what if youls -l /home
?Since this is an atomic distro,
/home
might be a symlink to/var/home
.evasync
in reply to Max-P • • •mvirts
in reply to evasync • • •a2part2
in reply to mvirts • • •evasync
in reply to Max-P • • •Possibly linux
in reply to evasync • • •lurch (he/him)
in reply to evasync • • •Nanook
in reply to evasync • — (Shoreline, WA, USA) •mkdir /home
make /var/home a symlink to it.
Alternative, edit your /etc/fstab to mount on /var/home.
Linux reshared this.
evasync
in reply to Nanook • • •data1701d (He/Him)
in reply to evasync • • •evasync
in reply to data1701d (He/Him) • • •do still need to update it regardless the reboot?
data1701d (He/Him)
in reply to evasync • • •Edit: Probably try @nanook@friendica.eskimo.com's solution of
systemctl daemon-reload
first.Yes. When booting, your system has an initial image that it boots off of before mounting file systems. You have to make sure the image reflects the updated fstab.
Nanook
in reply to data1701d (He/Him) • •Linux reshared this.
data1701d (He/Him)
in reply to Nanook • • •You might be right. I was thinking of it in terms of a traditional distro, as I use vanilla Debian where my advice would apply and yours probably wouldn't.
From what I do know, though, I guess /etc would be part of the writable roots overlaid onto the immutable image, so it would make sense if the immutable image was sort of the initramfs and was read when root was mounted or something. Your command is probably the correct one for immutable systems.
Nanook
in reply to data1701d (He/Him) • •Linux reshared this.
data1701d (He/Him)
in reply to evasync • • •sudo dracut -f
.DNOS
in reply to evasync • • •Telorand
in reply to Nanook • • •mkdir /var/home
then symlink/home
from that, no? Otherwise, you'll wind up with a home directory that is immutable.Nanook
in reply to Telorand • •Linux reshared this.
ravhall
in reply to evasync • • •Possibly linux
in reply to evasync • • •Nanook
in reply to Possibly linux • •Linux reshared this.
psmgx
in reply to Nanook • • •secret300
in reply to Nanook • • •Possibly linux
in reply to Nanook • • •Nanook
in reply to Possibly linux • •Linux reshared this.
Nanook
in reply to evasync • •Linux reshared this.
dustyData
in reply to evasync • • •Nanook
in reply to dustyData • — (Shoreline, WA, USA) •Linux reshared this.
evasync
in reply to dustyData • • •dustyData
in reply to evasync • • •Nanook
in reply to dustyData • •Linux reshared this.
dustyData
in reply to Nanook • • •Universal Blue - Powered by the future, delivered today
universal-blue.orgUrist
Unknown parent • • •like this
dhhyfddehhfyy4673 likes this.
dhhyfddehhfyy4673
Unknown parent • • •Linux reshared this.
mvirts
Unknown parent • • •20 or 30 generations 😹
I have space for 1 ðŸ˜
Edit: you've got me worried now, is the behavior you're referring to normal running out of inodes behavior or some sort of bug? Is this specific to ext4 or does it also affect btrfs nix stores?
I've run across the information that ext4 can be created with extra inodes but cannot add inodes to an existing filesystem.
mvirts
Unknown parent • • •