I inserted an sdcard. Formatted it with F2FS. Added it to /etc/fstab and rebooted.
Now I the boot process hangs at: fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress.
BTW the message isn’t fit on the screen and hence can’t be fully read.
@Dlonk was in that situation for a different reason he described here:
He was able to
Unfortunately I have problems with my wireless keyboards with USB-Dongles typing CTRL+ALT+F2. Not sure if I actually typed that correctly because of the fn-key overloaded binding of
How do I get SSH access at this stage? The usual way ssh pruism@librem5 does not work.
Proabaly sshd has not been started, so no ssh access.
I can think of two ways to go:
use a different (not wireless) keyboard and try CTRL+ALT+F2 with that. If you can get your hands on a USB-C-to-A adapter and attach a regular USB keyboard that way
or
use jumpdive to access the disk from another computer, then edit /etc/fstab back to how it was before. (Or add some kernel commandline option to ignore filesystem checks or something like that)
Or at least, edit /etc/fstab so that you specify the nofail option for the µSD card mounting. That way you should be able to shut down and remove the card if something has gone pear-shaped, and the phone will then boot without complaining about problems with the card - assuming of course that you didn’t move anything critical to the µSD card.
It is CRITICAL that you add the nofail option to any microSD card-related entries in /etc/fstab, that way if you boot without the microSD card it will fail to mount but still continue the boot process. Without the nofail option, the boot will stall and you will have to modify the file system from a remote computer to remove the mount point from /etc/fstab
Note that using Jumpdrive and fixing fstab from the host computer is one option - and probably the easiest in this case - but another option is using Jumpdrive and telnetting in to the phone and fixing fstab on the phone itself.
The nofail option makes absolute sense there. Unfortunately it is not documented everywhere. I plan to document what how I got F2FS running for the community and me.
man mount
under FILESYSTEM-INDEPENDENT MOUNT OPTIONS
Maybe you mean that Purism doesn’t officially document that nofail is generally recommended. There are presumably two reasons for that.
Nothing about this consideration is specific to Purism platforms or to PureOS. It is a consideration that comes up with any Linux usage where a device is mounted via /etc/fstab.
There is no formal way for anyone besides the owner/operator of the device to know whether nofail is appropriate i.e. whether the device being mounted plays a critical role in correct booting of the system or it’s non-critical so if the device can’t be mounted then log it, move on with the boot, and don’t worry about it.
No I meant this: I had a couple of pages opened which document F2FS, fstab, mount, mkfs.f2fs. Some from Debian’s Wiki. Others where man pages and I think Kernel docs. And Some details where written here others there. So I had to collect the pieces together and nofail was one of them.
It is worth noting that there are the filesystem-independent mount options - that in principle apply regardless of the specific file system type - and there are the filesystem-dependent mount options - where you may have to scrabble around to find documentation.
For example, if you want to know about filesystem-dependent mount options for Samba, you need man mount.cifs or likewise for NTFS, you need man mount.ntfs but not all supported file system types apparently have a man page (or a mount helper program).