Pity
Which ‘its’ method do you mean,
- a specific Raspbian method
- regular Debian method
- the Yunohost migration
Getting back to your initial questions, numbered for easy reference:
- you proved not to work in your case.
- may offer another way than 3) by changing something on the system to make it compatible with RPi5. Maybe another reader will chime in; otherwise you could try asking over at the Raspbian forum (Yunohost is ‘plain Debian’, so if they can help you make a change that boots Debian/Raspbian off RPI5, it will be valid for Yunohost)
- sounds more desperate than it is, as long as your backup device is large enough of course. In my experience the backup on one device / restore on another works flawless. You’d restore your backup instead of running
post-install
on the new installation
To migrate from RPi3b to RPi5 using a backup:
- backup the whole system+apps; pay attention that some apps (such as Nextcloud) by default don’t include data in the backup (it would unnecessarily get too large in the regular case of upgrades) → set
BACKUP_CORE_ONLY=0
(‘readme’) - move the backup to secondary storage, so you have it somewhere safe
- install Yunohost 12 on your RPi5, either by
- installing Debian/Raspbian Bookworm +
curl https://install.yunohost.org | bash
, or - using a RPi-specific Yunohost image
- installing Debian/Raspbian Bookworm +
- move your backup + the json-file to
/home/yunohost.backup/archives/
(after creating the directory if necessary) - instead of running
yunohost postinstall
, runyunohost backup restore name_of_backup
Here is a post with an earlier write-up for a somewhat similar situation: Server upgrade of the newe server - #8 by wbk (though that thread has some off-topic problems)
For context, about how much data is involved? Will you re-use the same SSD, or do you intend to replace that as well?