On 4/22/26 8:13 PM, [email protected] wrote:
[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
There isn't any mistakes in my opinion as the btrfs doesn't need need fsck.
/boot is vfat so it fsck at boot time isn't meaningful.
It is marked to fsck on boot but this happens:
sudo fsck -f /dev/sdb1
fsck from util-linux 2.41.3
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]? 3
Dirty bit is set. Fs was not properly unmounted and some data may be
corrupt.
1) Remove dirty bit
2) No action
[12?q]? 1
** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave the
filesystem unmodified:
1) Write changes
2) Leave filesystem unchanged
[12?q]? 1
/dev/sdb1: 420 files, 15432/130811 clusters
If you restart the computer, does /boot always get mounted as rw?
Yes, all mounts are 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?
This is a raspberry pi 5
This is not archlinuxarm/alarm. The alarm is just the hostname for
this box and will be changed when I finish my project.
hostnamectl
Static hostname: alarm
Icon name: computer
Machine ID: 0e60745bb1214cd691de942658ab16c6
Boot ID: e6d9b6d1b47b4781acc0e98d9704cc66
Operating System: Arch Linux ARM
Kernel: Linux 6.18.20-1-rpi
Architecture: arm64
pacman -Qq|grep rpi
linux-rpi <-- This will chg to 16k kernel current build process
is for rpi 4
linux-rpi-headers
rpi4-eeprom
pacman -Qq|grep rasp
firmware-raspberrypi
raspberrypi-bootloader
raspberrypi-utils
Is what I use.
I also built all the packages from the archlinux x86_64 PKGBUILD's
All build except the following
argyllcms: BARFS
icmake: BARFS
fbida: BARFS
libtpms: BARFS
mupdf: BARFS
sequoia-sq: BARFS
python-dbus-deviation: BARFS
I am working to get those to build
It currently using lxqt desktop, all packages were built with
CFLAGS='-mcpu=cortex-a72 -O2 -pipe -ftree-vectorize -fomit-frame-pointer'
CXXFLAGS="-Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
-Wl,-z,pack-relative-relocs"
No LTO, that will be on the next build
I did use LTO when I was building using RPM
Currently my project is running on two desktops rpi 5 and a single rpi 4
which is running PiHole nginx unbound and gitweb
I also has a btrfs RAID 1 as network storage.
I don't do x86_64 any more.
--
Hindi madali ang maging ako
