- Edited
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?
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?