NextcloudPi - Backup restore or Buster, I can't have both

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1

Hi,

I am currently running NextcloudPi with berryboot on a Raspberry Pi 3B+. My installation broke in an automatic update and now I want to restore it and update to buster (to run it on a Pi 4B). And I have different problems that won’t let me update to Buster. Sorry for throwing so much into one post, feel free to pick what seems like the easiest to solve.

Problem 1:
My installation was down one day (after 2019-07-12), and displays
[4.162815] bcm2835_vchiq 3f00b840.mailbox: Missing firmware node
before berryboot’s selection menu comes up.
Neither keyboard+mouse nor ssh works.

This installation is based originally on NextCloudPi_RPi_Berryboot_01-13-19 (2019-01-13).

Problem 2:
I installed the latest berryboot release (2019-06-12) and latest NCP release (2019-07-20) on a different sd card and wanted to restore a backup, but it fails:

Running nc-restore
check free space...
extracting backup file /media/NCPI_BU/ncp-backups/nextcloud-bkp_20190805_1565024662.tar...
restore files...
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
Cleanup...
systemctl status redis-server.service 

pi@nextcloudpi:~ $ systemctl status redis-server.service
â—Ź redis-server.service - Advanced key-value store
  Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
  Active: failed (Result: exit-code) since Sun 2019-08-04 21:11:09 CEST; 2min 15s ago
    Docs: http://redis.io/documentation,
          man:redis-server(1)
 Process: 14619 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=203/EXEC)

Aug 04 21:11:09 nextcloudpi systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart.
Aug 04 21:11:09 nextcloudpi systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
Aug 04 21:11:09 nextcloudpi systemd[1]: Stopped Advanced key-value store.
Aug 04 21:11:09 nextcloudpi systemd[1]: redis-server.service: Start request repeated too quickly.
Aug 04 21:11:09 nextcloudpi systemd[1]: redis-server.service: Failed with result 'exit-code'.
Aug 04 21:11:09 nextcloudpi systemd[1]: Failed to start Advanced key-value store.
journalctl -xe 

pi@nextcloudpi:~ $ journalctl -xe
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit redis-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 04 21:11:09 nextcloudpi systemd[1]: Stopped Advanced key-value store.
-- Subject: A stop job for unit redis-server.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit redis-server.service has finished.
--
-- The job identifier is 1942 and the job result is done.
Aug 04 21:11:09 nextcloudpi systemd[1]: redis-server.service: Start request repeated too quickly.
Aug 04 21:11:09 nextcloudpi systemd[1]: redis-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit redis-server.service has entered the 'failed' state with result 'exit-code'.
Aug 04 21:11:09 nextcloudpi systemd[1]: Failed to start Advanced key-value store.
-- Subject: A start job for unit redis-server.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit redis-server.service has finished with a failure.
--
-- The job identifier is 1942 and the job result is failed.
Aug 04 21:11:46 nextcloudpi sudo[14432]: pam_unix(sudo:session): session closed for user root
Aug 04 21:12:59 nextcloudpi sshd[14638]: Connection from 192.168.178.41 port 64504 on 192.168.178.49 port 22
Aug 04 21:13:08 nextcloudpi sshd[14638]: Accepted password for pi from 192.168.178.41 port 64504 ssh2
Aug 04 21:13:08 nextcloudpi sshd[14638]: pam_unix(sshd:session): session opened for user pi by (uid=0)
Aug 04 21:13:08 nextcloudpi systemd-logind[388]: New session c2 of user pi.
-- Subject: A new session c2 has been created for user pi
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c2 has been created for the user pi.
--
-- The leading process of the session is 14638.
Aug 04 21:13:08 nextcloudpi systemd[1]: Started Session c2 of user pi.
-- Subject: A start job for unit session-c2.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-c2.scope has finished successfully.
--
-- The job identifier is 1999.
Aug 04 21:13:08 nextcloudpi sshd[14638]: User child is on pid 14674
Aug 04 21:13:08 nextcloudpi sshd[14674]: Starting session: shell on pts/0 for pi from 192.168.178.41 port 64504 id 0

Problem 3:
I installed the old release NCP release from 2019-01-13 on the sd card from Problem 2 and managed to restore my backup, update NextcloudPi, Nextcloud, apps and packets and made a new backup, even from berryboot this time.
Running was: ncp v1.15.3, nc v16.0.3, Rasbian 9.9

Then I tried ncp-dist-upgrade but it failed:

Setting up mount (2.33.1-0.1) ...
Setting up systemd (241-5+rpi1) ...
Installing new version of config file /etc/systemd/journald.conf ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/resolved.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Installing new version of config file /etc/systemd/timesyncd.conf ...
Job for systemd-timesyncd.service failed because the control process exited with error code.
See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for details.
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Something went wrong. Fix it and try again

At this point all php-packets etc are already uninstalled, meaning nextcloud can’t work.

systemctl status systemd-timesyncd.service 

pi@nextcloudpi:~ $ systemctl status systemd-timesyncd.service
â—Ź systemd-timesyncd.service - Network Time Synchronization
  Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
 Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
          └─disable-with-time-daemon.conf
  Active: failed (Result: exit-code) since Mon 2019-08-05 21:18:13 CEST; 2min 53s ago
    Docs: man:systemd-timesyncd.service(8)
 Process: 22821 ExecStart=/lib/systemd/systemd-timesyncd (code=exited, status=203/EXEC)
Main PID: 22821 (code=exited, status=203/EXEC)

Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), schedu
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: Stopped Network Time Synchronization.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: Failed to start Network Time Synchronization.
journalctl -xe 

pi@nextcloudpi:~ $ journalctl -xe
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit systemd-timesyncd.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: Stopped Network Time Synchronization.
-- Subject: A stop job for unit systemd-timesyncd.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit systemd-timesyncd.service has finished.
--
-- The job identifier is 1142 and the job result is done.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit systemd-timesyncd.service has entered the 'failed' state with result 'exit-code'.
Aug 05 21:18:13 rw-ncpBUv5 systemd[1]: Failed to start Network Time Synchronization.
-- Subject: A start job for unit systemd-timesyncd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-timesyncd.service has finished with a failure.
--
-- The job identifier is 1142 and the job result is failed.
Aug 05 21:18:18 rw-ncpBUv5 sudo[2333]: pam_unix(sudo:session): session closed for user root
lines 1760-1789/1789 (END)

Current situation:
Restored the backup mentioned in Problem 3, and it is running.

Question:

  • Is there a way for me to get to Raspbian Buster from here? All above mentioned installs still exist on sd cards and can be experimented with.

Side question:

  • I didn’t try apt-get dist-upgrade, as I figured the added fluff of ncp-dist-upgrade is necessary. Should I try it anyways?

Unrelated questions:

  • Can backups also be restored to a different type of install, for example in docker? (My guess is yes, but I want to make sure)
  • Something really minor, that I noticed: ncp-config displays “press any key to continue” but only reacts to pressing “enter”.

Thanks in advance for your time and help, R.