Comment 6 for bug 1898934

Attaching some extra info as I got access to the affected system.

Two quick observations (both included in the attached document):
- fsck.vfat is not on PATH (apparently it's an old core18 image that didn't manage to refresh to have a fix for this), it's only present on the core image.
- snapd service is running (but no current symlink is present as noted earlier).
- boot parition is not mounted because it was manually unmounted in one of the previous debugging sessions.