On booting I noticed some services failing, though systems boots normally without any problem , only swap partition is not mounted as its service depends on
mount-allhere are boot logs
Thu Jun 23 16:28:03 2022: [ OK ] binfmt
Thu Jun 23 16:28:03 2022: [ OK ] cgroups
Thu Jun 23 16:28:03 2022: [ OK ] kmod-static-nodes
Thu Jun 23 16:28:03 2022: [ OK ] net-lo
Thu Jun 23 16:28:03 2022: [ OK ] tmpfiles-dev
Thu Jun 23 16:28:03 2022: [ OK ] udevd
Thu Jun 23 16:28:03 2022: [ OK ] udev-trigger
Thu Jun 23 16:28:03 2022: [ OK ] hwclock
Thu Jun 23 16:28:03 2022: [ OK ] udev-settle
Thu Jun 23 16:28:03 2022: %Gfsck from util-linux 2.38
Thu Jun 23 16:28:03 2022: fsck.fat 4.2 (2021-01-31)
Thu Jun 23 16:28:03 2022: /dev/sda1: 370 files, 28648/261627 clusters
Thu Jun 23 16:28:03 2022: [ OK ] vconsole
Thu Jun 23 16:28:03 2022: [ OK ] tmpfiles-setup
Thu Jun 23 16:28:03 2022: [ OK ] fsck
Thu Jun 23 16:28:03 2022: [ OK ] cleanup
Thu Jun 23 16:28:03 2022: [ OK ] modules
Thu Jun 23 16:28:03 2022: [ OK ] misc
Thu Jun 23 16:28:03 2022: dinit: Service mount-all command failed with exit code 64
Thu Jun 23 16:28:03 2022: [FAILED] mount-all
Thu Jun 23 16:28:03 2022: [FAILED] swap
Thu Jun 23 16:28:03 2022: [FAILED] root-rw
Thu Jun 23 16:28:03 2022: [FAILED] locale
Thu Jun 23 16:28:03 2022: [ OK ] mount
Thu Jun 23 16:28:03 2022: [ OK ] random-seed
Thu Jun 23 16:28:03 2022: [ OK ] sysusers
Thu Jun 23 16:28:03 2022: ModemManager[676]: <info> ModemManager (version 1.18.8-1) starting in system bus...
Thu Jun 23 16:28:03 2022:
Thu Jun 23 16:28:03 2022: ModemManager[676]: [qrtr] socket lookup from 1:0
Thu Jun 23 16:28:03 2022: ModemManager[676]: [qrtr] initial lookup finished
Thu Jun 23 16:28:03 2022: ModemManager[676]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10': not supported by any plugin
Thu Jun 23 16:28:03 2022:
Thu Jun 23 16:28:03 2022: ModemManager[676]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin
Thu Jun 23 16:28:03 2022:
Have you been able to mount swap with swap on?
Have you rebooted again to see if the error persists?
Have you booted from usb live artix and run file checks on your system?
swap can be mounted with swapon command.
I have not run file check . I have doubt that will it delete any data on Drives?
I recently switched to used lts kernel , it does not compiled with binder, so i had used anbox on system , I enabled binder mount in fstab.
which causing errors. Disable from fstab it fixed error
most of that i do not understand. i have no idea what binder or anbox are. Glad you got it worked out though!