Bug report - [MAJOR] [Installer] [Architect] (UNBOOTABLE) Manjaro Architect generates an invalid fstab

When installing via Architect, it generates an invalid /etc/fstab (for me) with an invalid option, causing the FS to become mounted read-only and failing to boot.

To reproduce:

  • install architect
  • try to boot

To fix:

  • boot to GRUB by spamming esc on boot
  • press e
  • scroll down to the line that says linux ...
  • change ro (read-only) to rw (read-write) to force a proper mount (temporary solution as fsck runs improperly here)
  • press ctrl+x
  • continue to boot
  • log in as your user
  • open terminal
  • attempt to run mount -o remount /
  • check dmesg --human
  • see invalid option error
  • nano /etc/fstab, change the / mount options from rw,[...others] ([...others] is a set of other options) to rw,defaults
  • press ctrl+x then y+enter
  • reboot, it works!

Not sure if this is a VM problem or a bug.

Check your grub configuration in
/etc/default/grub
The last line
GRUB_ROO_FS_RO=true … or false

what is that error?

Configuring mount options in /etc/fstab was part of the installation procedure.
You probably just missed a step or made a mistake.
There are many of them and one can get a bit lost …

I just did an install of XFCE using Architekt in a VM and it boots and works flawlessly.

nano /etc/fstab, change the / mount options from rw,[...others] ([...others] is a set of other options)

to rw,defaults

change from rw to rw? - so your change essentially did nothing and isn’t/wasn’t the cause
However, the here glanced over other options may have been …

I chose rw,noatime in the VM
On my real system I have rw,relatime
In /etc/default/grub the “read only” option is set in both.

Hmm… It happened once (even after reinstalls), then I replicated it exactly, and it’s not happening!