Tried to update doesnt boot aynmore

[nephros]

@HeinrichJolla

The filesystem check I had made output:
…
root: ***** FILE SYSTEM WAS MODIFIED ****** .

after it the Shell option is showing:

> /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
> 2 logical volume(s) in volume group “sailfish” now active
*> *
> WARNING: Locking directory /run/cryptsetup is missing!

so the correct command would be the one you suggested

mount -vv -t ext4 -o ro /dev/mapper/sailfish-home /myhome

However, whats next? saving the data and than factory reset? Or maybe I dont need to make any factory reset ?

Btw. why cant I find a command to make a backup from the command line ?

Well I can’t really tell you what to do no next as I’m not quite sure what’s broken precisely.

You are now in a position to, for example:

• backup/save whatever data you have on your /home to the SD card (if inserted and mounted). This will have to be done manually using tar and friends, there is no ready-made script to do it.
• change your /etc/systemd/journald.conf file from volatile to persistent storage. This can be used to see what is actually failing when the device tries to boot. see also here
• using chroot, enter the SailfishOS filesytem proper and e.g. remove RPMs that are known to cause prolbems. like here. There’s a couple of possible candidates from OpenRepos that can cause boot to fail or apparently to fail.
• using chroot, manually install or reinstall RPMs you know have failed to install correctly.
• any amount of other tricks to fix broken things.

Note these are just examples.

I would try the systemd thing first, edit the file to persistent, create the log file location, and reboot the device again. After it failed, go into recovery mode again, and inspect the log files created at the log file location. Maybe even copy it to SD card for easier viewing/pastebin etc.