/etc/fstab issue

Hi Gang,
I just did a second update (alll my boxes are Manjaro…hence) and I could nog log in, it did not find my /home
Upon inspection, I found errors in my originat FSTAB:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=########                            /boot/efi      vfat    umask=0077 0 2
UUID=########-2bf2-4ced-aada-1da3969df356 /              ext4    defaults,noatime 0 1
UUID=########-1130-4a5f-8328-7f5a9c465d84 /home          ext4    nosuid, nodev, noatime 0 2
UUID=########-10b4-4ff7-98f4-046caf40f2d1 swap           swap    defaults,noatime 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

(hashes for privacy), notice the spaces in the line for the /home partition, they need to be removed.
Then update.
thanks to @anon33601770 for this insight :wink:
:rose: Melissa :rose:
(and always have a backup first)

EDIT : after a mod correcterd me: this seems to be my FSTAB, sorry for the mis info…

An update does not touch the content of your /etc/fstab, your /home mount point is user-created, and in that sense you are solely responsible for the content.

Following Stable Update 2026-02-23, default DE and home directory changed?

Check the file (example)

 $ stat /etc/fstab
  File: /etc/fstab
  Size: 676             Blocks: 8          IO Block: 4096   regular file
Device: 259,2   Inode: 9700186     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2026-03-01 06:41:00.719680705 +0100
Modify: 2025-12-19 15:36:01.433225439 +0100
Change: 2025-12-19 15:36:01.433225439 +0100
 Birth: 2024-08-07 10:05:48.210566035 +0200
1 Like

As @linux-aarhus said, this seems to be user error.

I don’t like wiping out solutions so I’ll keep the thread hidden for now. We may decide to delete it later.

They’re version 4 UUIDs which means they’re just random numbers. There’s no need to censor them.

1 Like

I think the thread will be made visible again once you’ve changed the somewhat unfortunately chosen title.
:footprints:

3 Likes

I have edited the thread title, moved the thread to Support and relisted the thread.

3 Likes

I did consider that, but they already have a solved thread on the issue and I didn’t think merging would be helpful.

Forgot to check the category.

Likely, one I need to apologize for…I learned a lot in this one post…thanks for editing the title…it was misleading…

3 Likes

On the same issue? :thinking: Then I may have missed something. Would you be so kind as to provide me with a link?

It’s in @linux-aarhus’s post, but I’ll post it here for convenience.

That said, this thread may relate to a different computer, but I’m not sure it counts as a separate issue.

Ah yes, it does indeed appear to pertain to the same problem, and thus, the same solution. I’ll therefore unlist the thread again, and I’ll move the other one to Support, since it was not the result of an update. :wink:

3 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.