4
« on: September 23, 2018, 10:29:20 am »
Gemini Debian is not able to reliably poweroff. (I'll explain this more below.) It often crashes when trying to poweroff. When this happens, it often is not able to reboot. It just hangs in the splash screen and doesn't display "Linux".
Through various analyses, I have come to believe that the cause of the problem is that a reboot after a crash runs fsck and that often requires user input. AFAIK, Gemini has no equivalent of the grub and VT screens from Debian on amd64 that allow answering fsck queries or booting into a recovery mode.
In my case this is exacerbated by the fact that I have a 512GB SDXC card formatted as one large ext4 partition that I mount with an entry in /etc/fstab. I have discovered that this is likely the cause of the failure to reboot because when that happens, I reinstall Debian into the main flash device, reboot without the /etc/fstab entry, and manually run fsck on the SDXC card, discovering the errors.
This issue has required me to reinstall Debian from scratch 4 times now.
My two questions:
1. Is there an analog of grub booting to a recovery mode or booting with a VT so that I can answer fsck queries?
2. How can I reliably poweroff so this doesn't happen?
I mount the SDXC card as /fs. I have /home/qobi redirected to /fs/home/qobi. And when logged in as qobi, I run twm through .xsession instead of lxqt. I could try to reduce the likelihood of this occurring by eliminating the /etc/fstab entry but this would require me, every time I poweron, to login as gemini to lxqt, mount /fs, logout from gemini, and then login as qobi. And it would require me, every time I poweroff, to logout from qobi, login as gemini to lxqt, umount /fs, then try to poweroff, suspend, or hibernate. This would be tedious.
I poweroff, suspend, and hibernate by running the lxqt variants within my environment. Sometimes some of them work, sometimes not. Even when I use them from within lxqt logged in as gemini, sometimes they work, sometimes not.
It takes me 4 hours to reinstall and reconfigure Debian the way I like it from scratch. I am currently in an unbootable state so an answer to (1) above can help save me 4 hours.