> [root@alarm ~]# cat /etc/fstab > # Static information about the filesystems. > # See fstab(5) for details. > # <file system> <dir> <type> <options> <dump> <pass> > UUID=9514386f-6ba0-42b6-942a-939e87857591 / btrfs > rw,relatime,compress=lzo,discard=async,space_cache=v2,subvol=/System 0 0 > UUID=9514386f-6ba0-42b6-942a-939e87857591 /home btrfs > rw,relatime,compress=lzo,discard=async,space_cache=v2,subvol=/Home 0 0 > UUID=9514386f-6ba0-42b6-942a-939e87857591 /var/cache/pacman/pkg btrfs > rw,relatime,compress=lzo,discard=async,space_cache=v2,subvol=/Cache 0 0 > UUID=97BB-2AFA /boot vfat > rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro > 0 2 > UUID=4d995c91-fee4-4289-bade-85496d49e572 none swap defaults 0 0 > UUID=9514386f-6ba0-42b6-942a-939e87857591 /mnt btrfs > noauto,rw,relatime,compress=lzo,discard=async,space_cache=v2 0 0
I think there's a mistake with regards to <pass> / is already at pass 0 (correct) Everything else should be at pass 1 (or above). If you have multiple file system at pass 0, it's possible that when /boot (pass 2) wants to be mounted, it doesn't have a mountpoint, and it won't be mounted If you restart the computer, does /boot always get mounted as rw? What's your bootloader? (what device is this?) I saw that you're using alarm. ARM boot process can be complicated depending on what device you use. Are you using UEFI, depthcharge? Is this a raspberry pi or something? Did you make any changes in boot process / use custom kernel?
