Unable to login via the display manager and when I go to a TTY I get the above error.
My home partition is on a separate partition
When I go to /home in tty the directory is empty. Could it be an fstab issue or something else.
Any suggestions??
If you have a Live Workstation USB Installer you can boot that and use Gnome Disks to view the partitions on the system storage device and compare with the contents of fstab.
This issue commonly occurs when the home partition uses a device name in fstab that can change with hardware or software upgrades. Using a UUID in fstab avoids the problem.
How to get same info from terminal?? lsblk - f?? Is that the right command?
Will lhave a look later, only thing as far as I know is I comment out my external hdd in fstab. Don’t recall doing anything else
UUID=aeb982de-cb3d-49bb-90d9-71620172191c / btrfs subvol=root,compress=zstd:1 0 0
UUID=d1205351-97c4-409d-9274-f6a26cdd5e75 /home ext4 defaults 1 2
UUID=61469ef5-023a-42d0-a451-3e0bf5ae4a54 none swap defaults 0 0
All uuids are correct in fstab. Any other suggestions?
Did you run ‘systemctl daemon-reload’ to update systemd units generated from your fstab?
Yes I did that.
Looks like we are post simple errors and omissions, so time to look for details.
Posting the output (as pre-formatted text) from running inxi -Fzxx in a terminal can help others with similar hardware and issues (and perhaps solutions) discover this topic. You will need to install inxi in the Live environment.
I would start by mounting your root and home in a Live USB environment using Gnome Disks. Make sure the directories mount and check the S.M.A.R.T “health” of the drives. Then use journalctl --no-hostname --directory=<path_to_root>/var/log/journal/<machine_id> -b (<machine_id>is a long hex string – usually there is just one candidate) and look for relevant errors.
Mount - a mounts the UUID correctly and all the directories and files are shown in the TTY.
I assume you are able to login as root in the TTY. Look at ls -ldZ /home.
If I do mount-a I’m able to login to budgie via gdm but not kde. Kde I can login to by running dbus-run-session start plasma-wayland.
Obviously neither of these solutions are particularly great.
So /home is mounted and the permissions for /home look normal. Try ls -ldZ /home/spaceboy.
journalctl may have error messages related to /home. If you can arrange to post them as (pre-formatted) text, others with similar issue may find this topic with a web search.
Yes mounted but not automatically at boot, had to manually mount from a tty
I assumed that from your previous posts. journalctl may provide some insights into the faiiure to mount /home at startup. I notice that the 5th field (dump frequency) is 1. Are you really using dump?