Ive been thinking of making a post about this for a while and having issues with my new system has motivated me to revisit this and see what the solution may be or tweaking how 66-tools handles fstab mounting.

The problem I'm having with the system im trying to update, is with the boot sequence stopping at "fstab starts..."

However, looking at the log it seems the root volume /dev/sdawhatever is not getting mounted and there is no cleasr reason reading the logs as to why....


On the same topic, though it may be unrelated, when I try to mount binderfs on any system using 66 at boot by adding the following to /etc.fstab:

none /dev/binderfs binder nofail 0 0

it results in the boot sequence ending in:" fstab crashed"

This is when I'm trying to make running anbox,waydroid or similar faster, rather than having to mount after boot.

Any insight eric or anyone?
When you edit fstab before reboot try:
# mount -a
Mount all gives you any direct errors at attempting to mount everything on fstab. The fatal crashed message comes from 66, it doesn't give you specific output. Based on the errror output search for the reason it fails to mount. If mount all doesn't have output everything to be mounted was successful, use df to verify everything is mounted correctly.
Unfortunately mount -a doesnt give any output and running any command that requires a write to the system volume gives output of read-only fille system.

so I gotta manually remount the system in order to write anything or start root,boot-user, and user trees.
if on emergency tty12 on a read only file system

% sudo mount -o remount,rw /dev/sdxxx /

where sdxxx is your root partition

% sudo pacman -S arch-install-scripts

if you don't already have them

% genfstab -U /

compare the output to what you have on fstab or manually mount what you want to always mount on boot and then run genfstab
Yep, that "% sudo mount -o remount,rw /dev/sdxxx /" is the command I use to remount thru emergency tty12. I can get most services running after but it's not convenient.

% genfstab -U / output... is what I have already in my fstab...

It seems to me my system fails to start "mount rw" immediately after starting "mount fstab"...

So how could I get it to start "mount rw" before it tries to mount nfs?
Interesting update, It seems related to the kernel I boot. Linux-clear kernel doesnt seen to work past "mount-fstab...starts" but other kernels go past that.
So you mean the entire problem described above doesn't exist with other kernels only with clear, or is it more severe with clear?
Trying to mount "none /dev/binderfs binder nofail 0 0" thru fstab fails in all kernels,

but the other "fstab-mount... starts..." without mounting rw after seems to be kernel specific.
What's the contents of your grub.cfg? Do you mount your / ro or rw. It should be ro.
Does it not crash for you at boot sequence when you mount "none /dev/binderfs binder nofail 0 0" in your fstab?
5 days later
Thank you for helping fix the mount-rw issue, you were correct and all it needed was a change in my grub entry. However the other issure remains. It still crashes but not a huge deal.
4 days later
instead of passing through the fstab file, try to create a separate service which create the necessary mount point
for exemple create the file /etc/66/service/binderfs with the following
[main]
@ type = oneshot
@ description = "mount binderfs type"
@ version = 0.0.1
@ user = ( root )

[start]
@ execute = ( 
execl-toc -m /dev/binderfs -t binder -d binder
66-yeller -p  binderfs service successfully started
)
The exec-toc will check if the /dev/binderfs is a mountpoint, if not it will create the /dev/binderfs directory and mount it with the following mount command
# mount -t binder binder /dev/binderfs
Then enable it at your e.g. root tree and tell us what happens.

Powered by Obarun