Well idk what the hell happened, but from the timing of the logs, it sounds like you started the migration, then it failed, then you somehow thought “well it failed but whatever, let’s launch a system upgrade anyway”
Anyway … let’s first get rid of some boring warnings with :
rm /etc/apt/sources.list.d/sury.list
Then : it looks like the actual upgrade issue is related to
The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information.
[...]
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi'
Does “appstream” means anything to you ? It sounds like it’s related to desktop environment stuff, which honestly is just boring, it’s not related to Yunohost and i’m starting to get tired of fixing stuff that are unrelated to yunohost itself…
I have no idea what appstream is and I’m not concerned with it either.
When I originally attempted the migration it failed telling me that I needed to complete existing system upgrades first, or at least that’s what I thought:(
To give you some background, I was nervous to do these upgrades and break the whole system so I decided to use Clonezilla and simply clone the entire drive to a second identical drive in case something terrible went wrong.
Is there a better way of getting to Yunohost 4x? Possibly by doing a clean install on the new drive and restoring a backup from my original install?
Or you can just try to run the one command I provided about grub-pc (btw this particular issue ain’t really about yunohost itself, it’s just the grub people who somehow broke the upgrade of the grub-pc package … maybe it’s not even related to moving from stretch to buster)
and possibly relaunch the migration after this …
Don’t underestimate the cost of reinstalling everything from scratch (or from a backup) compared to taking “only” a couple hours to iterate with us on the support …
There are already a bunch of archives named nextcloud-pre-upgrade2 and same for other apps … the may be remains from failed upgrade attempts earlier, maybe you can delete those
I thought that might be the issue. I had a similar error with my initial Mastodon failed upgrade, I removed the existing file and tried again. Please compare the 2 Mastodon logs:
I think this may be an issue with the backup utility. I’ve been having issues for months where the Web Admin doesn’t load the backup tool, it simply times out. The only way I’ve been able to do backup is with the command line.
I will try Nextcloud to see if I remove the duplicate, the issue persists. Thanks!
Sounds like the issue is that yunohost got killed while trying to perform the backup … that’s usually indicative of an overloaded machine, lack of RAM, etc…
Do you have a lot of stuff running on your server ? Anything in particular in the diagnosis section “System resources” ?