Boot from SSD - Outdated description?

[drhm]

@adminX

@drhm

Because of the explicit hint to the Omnia 2019 and newer versions, I think, that this doc is up to date for my router.

It is as long as it is using MMC.

Not optimal, but I think, that I can live with that, because the eMMC is still there and if a rollback has installed the last snapshot from /dev/sda1 in the eMMC I should be able to reinstall it after that by hand again on /dev/sda1. Maybe with the help of the serial console.

@adminX

@drhm

And because of that and my minimal changes (I’ve only added a third boot prefix and have changed the boot order between scsi0 and mmc0) and the fact, that schnaps saves the new / directory mounted on the SSD, I think also, that the rollback modes should work with my changes.

Adding the third boot prefix (/@/boot/) is not necessary as there should be a symlink installed but this way is faster. /@/ would have worked too as the symlink in the subvolume-root should be there by default.

Interesting, but I’m pretty sure, that it didn’t work on my router. At first I tried it only with the change of the boot order and I then found out, that the boot script was not found.

@adminX

schnapps in the installed system works fine but there are a few bugs:
schnapps in the rescue system always uses /dev/mmcblk0p1 because this gets set before the rescue system checks if there is another partition set using root_uuid.
And there is absolutly no access to the SATA drive in the rescue system.

I think, that you can add another bug to your list, which is relevant, if you boot from a SSD. Look at this post.