Dietpi don't start after last upgrade

Troubleshooting
1

Creating a bug report/issue

Required Information

HP MiniPC

  • DietPi version | DietpiOS 8.15
  • Distro version | Debian 11
  • Kernel version | Linux DietPi 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64
  • Power supply used | 65W
  • SD card used | none

Steps to reproduce

  1. sudo dietpi-update

Expected behaviour

  • it should work

Actual behaviour

I’m stuck with that after dietpi-upgrade for few minutes. Server cannot start, non service don’t work:

 ssh dietpi@192.168.0.19
Linux DietPi 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

When I reboot nothing works. Looks like there’s no network. There’s some DNS problems. I go to dietpi-config and change do cloudflare DNS. Test show me online. After reboot its again offline.

2

Can you ping anything on the internet like Google or Cloudflare IP 1.1.1.1 ?

3

Hi, Yes I can ping but some services are down.

sudo dietpi-services status

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: status 

[  OK  ] DietPi-Services | avahi-daemon		 active (running) since Tue 2023-03-21 20:06:29 CET; 24min ago
[  OK  ] DietPi-Services | proftpd		 active (running) since Tue 2023-03-21 20:06:56 CET; 24min ago
[FAILED] DietPi-Services | ● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-03-21 20:11:36 CET; 19min ago
    Process: 904 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
    Process: 1628 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
    Process: 1630 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
        CPU: 3ms

Mar 21 20:06:57 DietPi systemd[1]: Starting NFS server and services...
Mar 21 20:10:05 DietPi exportfs[904]: exportfs: Failed to stat /mnt/skyhawk/dietpi_userdata: No such device
Mar 21 20:11:35 DietPi exportfs[904]: exportfs: /mnt/Toshiba does not support NFS export
Mar 21 20:11:36 DietPi systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE
Mar 21 20:11:36 DietPi systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Mar 21 20:11:36 DietPi systemd[1]: Stopped NFS server and services.
[  OK  ] DietPi-Services | redis-server		 active (running) since Tue 2023-03-21 20:11:36 CET; 19min ago
[FAILED] DietPi-Services | ● mariadb.service - MariaDB 10.5.18 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-03-21 20:17:37 CET; 13min ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 1639 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 1640 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 1642 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 1692 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 1692 (code=exited, status=1/FAILURE)
     Status: "MariaDB server is down"
        CPU: 69ms

Mar 21 20:11:36 DietPi systemd[1]: Starting MariaDB 10.5.18 database server...
Mar 21 20:13:06 DietPi mariadbd[1692]: 2023-03-21 20:13:06 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.18-MariaDB-0+deb11u1) starting as process 1692 ...
Mar 21 20:16:06 DietPi mariadbd[1692]: 2023-03-21 20:16:06 0 [Warning] Can't create test file /var/lib/mysql/DietPi.lower-test
Mar 21 20:17:37 DietPi mariadbd[1692]: [89B blob data]
Mar 21 20:17:37 DietPi mariadbd[1692]: 2023-03-21 20:17:37 0 [ERROR] Aborting
Mar 21 20:17:37 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Mar 21 20:17:37 DietPi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Mar 21 20:17:37 DietPi systemd[1]: Failed to start MariaDB 10.5.18 database server.
[  OK  ] DietPi-Services | php7.4-fpm		 active (running) since Tue 2023-03-21 20:17:37 CET; 13min ago
[  OK  ] DietPi-Services | lighttpd		 active (running) since Tue 2023-03-21 20:17:37 CET; 13min ago
[  OK  ] DietPi-Services | emby-server		 active (running) since Tue 2023-03-21 20:17:37 CET; 13min ago
[FAILED] DietPi-Services | ● bazarr.service - Bazarr (DietPi)
     Loaded: loaded (/etc/systemd/system/bazarr.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-03-21 20:20:37 CET; 10min ago
    Process: 1780 ExecStart=/usr/bin/python3 /opt/bazarr/bazarr.py -c /mnt/dietpi_userdata/bazarr (code=exited, status=1/FAILURE)
   Main PID: 1780 (code=exited, status=1/FAILURE)
        CPU: 208ms

Mar 21 20:17:37 DietPi systemd[1]: Started Bazarr (DietPi).
Mar 21 20:20:37 DietPi Bazarr[1780]: Python 3.9.x is unsupported. Current version is 3.9.2. Keep in mind that even if it works, you're on your own.
Mar 21 20:20:37 DietPi Bazarr[1780]: Traceback (most recent call last):
Mar 21 20:20:37 DietPi Bazarr[1780]:   File "/opt/bazarr/bazarr.py", line 84, in <module>
Mar 21 20:20:37 DietPi Bazarr[1780]:     os.remove(restartfile)
Mar 21 20:20:37 DietPi Bazarr[1780]: OSError: [Errno 19] No such device: '/mnt/dietpi_userdata/bazarr/bazarr.restart'
Mar 21 20:20:37 DietPi systemd[1]: bazarr.service: Main process exited, code=exited, status=1/FAILURE
Mar 21 20:20:37 DietPi systemd[1]: bazarr.service: Failed with result 'exit-code'.
[  OK  ] DietPi-Services | noip2		 active (running) since Tue 2023-03-21 20:17:37 CET; 13min ago
[  OK  ] DietPi-Services | docker		 active (running) since Tue 2023-03-21 20:29:47 CET; 1min 37s ago
[  OK  ] DietPi-Services | cron			 active (running) since Tue 2023-03-21 20:17:37 CET; 13min ago
[  OK  ] DietPi-Services | ssh			 active (running) since Tue 2023-03-21 20:06:29 CET; 24min ago
[  OK  ] DietPi-Services | tailscaled		 active (running) since Tue 2023-03-21 20:06:29 CET; 24min ago
[ INFO ] DietPi-Services | dietpi-vpn		 inactive (dead)
[  OK  ] DietPi-Services | fail2ban		 active (running) since Tue 2023-03-21 20:06:29 CET; 24min ago
[ INFO ] DietPi-Services | dietpi-cloudshell	 inactive (dead)
[  OK  ] DietPi-Services | dietpi-dashboard	 active (running) since Tue 2023-03-21 20:06:29 CET; 24min ago
[  OK  ] DietPi-Services | dietpi-ramlog	 active (exited) since Tue 2023-03-21 20:06:28 CET; 24min ago
[  OK  ] DietPi-Services | dietpi-preboot	 active (exited) since Tue 2023-03-21 20:06:28 CET; 24min ago
[  OK  ] DietPi-Services | dietpi-postboot	 active (exited) since Tue 2023-03-21 20:06:29 CET; 24min ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor	 inactive (dead)
4

Do you have an external disk that might be not available? /mnt/Toshiba for example? Or /mnt/skyhawk/ ?

2 Likes
5

Yes, everything now works. I think my HDD Bay don’t wake after reboot.
Thanks for fast help :slight_smile: