Trying again: moving from armhf to arm64. Backups restore not working

Support
1

Note this is a repeat of an old thread that closed. I still need help and stopped getting reponses…I REALLY need to get this migration done.

My YunoHost server

Hardware: Raspberry Pi 4
YunoHost version: 11.2.9.1
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes, some custom config

Description of my issue

I’ve built up significant “config crust” over the years so I want t migrate to a new instance. I backed everything up, made note of all my custom config things lie fstab and my swap settings and started copying everything over. The first issue I’ve run into is trying to restore the *arr apps, and Nextcloud:

2024-02-09 17:13:55,902: WARNING - setfacl: /home/yunohost.multimedia/<every single user>/Share/Torrents: No such file or directory

I suppose I could just manually make the folders but then I wouldn’t know what to do for permissions etc. Is making the folders not part of the restore script? It must have been part of the install script, no?

Next is a similar issue with Transmission:

2024-02-09 17:23:41,011: WARNING - chown: cannot access '/home/yunohost.app/transmission/progress': No such file or directory

EDIT:

I’m seeing a common theme here. Synapse is doing the same:

2024-02-09 18:48:22,774: WARNING - ../settings/scripts/_common.sh: /opt/yunohost/matrix-synapse/bin/pip3: /opt/yunohost/matrix-synapse/bin/python3: bad interpreter: No such file or directory
2

Hmpf yeah that’s related to some multimedia / transmission fuckups … It would help debugging if you can share the ~50ish log lines before/after those very lines

3

Here’s the yunopaste from the old thread a few months ago:

https://paste.yunohost.org/raw/tumowehuko

Thank you so much for the prompt reply!

4

Eeeeh okay but that’s a backup create and not a backup restore ?

5

Ah, my bad. I’ll have to wait until I get home to pull the logs, sorry. I’ll try again in a few and give you fresh logs.

6

https://paste.yunohost.org/raw/wagovatohe

Brand new.

7

Sooo hm what if you run for example ls -l /home/yunohost.multimedia/admin/Share/Torrents

could it be that the file exists but is a broken symlink ?

8 
lrwxrwxrwx 1 root root 41 Oct  4  2023 /home/yunohost.multimedia/admin/Share/Torrents -> /home/yunohost.app/transmission/completed

the latter directory doesn’t seem to exist on the original server…shouldn’t the backup flag those?

/home/yunohost.app/transmission/ only has progress and watched as subdirectories

9

The issue was patched 7 month ago in 11.2.10 in multimedia: fix again edgecase where setfacl crashes because of broke… · YunoHost/yunohost@1ce606d · GitHub … though the backup restore will use the backup of the original system the backup was created on … Isn’t there any way to upgrade your system before creating the backup and restoring it on the new machine ?

10

Ok, upgraded to 11.2.27. checked upgrades again, nothing available.

Did a fresh backup/restore and it’s the same thing:
https://paste.yunohost.org/raw/dinegitabe

11

Ah well my bad, I guess it’s in fact because the new setup is using an old version … : yunohost_version: 11.2.8.2 … so upgrading the new setup before restoring should fix the issue ?

12

Ha! I actually did upgrade both but then I re-flashed the OS on the new one and forgot to again lol.

That seems to have done it, everything recovered successfully except:

  • Transmission (not the biggest deal, there’s not much config to do if I have to start form scratch)
  • Synapse (I would rather not lose our chat history)

Some recovered services are having issues:

  • *arr are giving me radarr.service: Failed to execute /var/www/radarr/Radarr: No such file or directory
  • same as above for vaultwarden
  • Syncthing isn’t telling me anything useful
  • My Trilium backup is ancient. Can I extract the db file from the archive and use that on a new install of the app?

EDIT:

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.