I was using DietPi normally on my RPi 4 with a LCD display and then I ran “reboot” and now it’s stuck on the startup part, all the services are running fine but I can’t enter the TTY.
It’s on a screen with “[ OK ]” and it keeps getting stuck on the “Reached target … Basic System” message. The last thing I ran before rebooting was dietpi-cloudshell. It’s a new clean installation with just pihole, unbound, and pivpn on it. I can access it with SSH perfectly but I want to use my LCD display.
Can you log in via SSH and deactivate the autostart option DietPi-CloudShell. Does the system reboot normally afterwards?
I’ve set the autostart in dietpi-config to “Manual login” and it still does not start up completely after a reboot.
can you login via SSH and export the whole system log using journalctl. The log will be long one, copy it to a text file and attach it to your post. As an alternative, you can use https://pastebin.com/
Aug 02 06:25:58 DietPi systemd[1]: Startup finished in 1.295s (kernel) + 55.642s (userspace) = 56.937s.
Your system takes quite a long time to start up. 1 minute is a really long time. Does the boot process continue after a while?
Aug 02 06:24:55 DietPi systemd[1]: Reached target network-pre.target - Preparation for Network. Aug 02 06:24:55 DietPi systemd[1]: Starting ifup@eth0.service - ifup for eth0... Aug 02 06:24:55 DietPi systemd[1]: Starting ifup@wlan0.service - ifup for wlan0... Aug 02 06:24:55 DietPi systemd[1]: Starting networking.service - Raise network interfaces...
It looks like you have both Ethernet and WiFi connected.
Aug 02 06:40:20 DietPi dhclient[502]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 Aug 02 06:40:23 DietPi dhclient[502]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Aug 02 06:40:30 DietPi dhclient[502]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 Aug 02 06:40:42 DietPi dhclient[502]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 Aug 02 06:41:01 DietPi dhclient[502]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Aug 02 06:41:14 DietPi dhclient[502]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Aug 02 06:41:21 DietPi dhclient[502]: No DHCPOFFERS received. Aug 02 06:41:21 DietPi dhclient[502]: No working leases in persistent database - sleeping.
If you are not using Ethernet, you should disable the interface as your system will try to get an IP address on eth0.
Aug 02 06:48:48 DietPi dropbear[2247]: [2247] Aug 02 06:48:47 Child connection from 218.92.0.34:57540 Aug 02 06:48:48 DietPi dropbear[2247]: [2247] Aug 02 06:48:48 Failed loading /etc/dropbear/dropbear_dss_host_key Aug 02 06:48:49 DietPi dropbear[2247]: [2247] Aug 02 06:48:49 Exit before auth from <218.92.0.34:57540>: Disconnect received Aug 02 06:48:59 DietPi dropbear[2253]: [2253] Aug 02 06:48:59 Child connection from 185.224.128.142:51898 Aug 02 06:48:59 DietPi dropbear[2253]: [2253] Aug 02 06:48:59 Failed loading /etc/dropbear/dropbear_dss_host_key Aug 02 06:49:07 DietPi dropbear[2253]: [2253] Aug 02 06:49:07 Exit before auth from <185.224.128.142:51898>: Exited normally Aug 02 06:49:07 DietPi dropbear[2263]: [2263] Aug 02 06:49:07 Child connection from 185.224.128.142:51934 Aug 02 06:49:07 DietPi dropbear[2263]: [2263] Aug 02 06:49:07 Failed loading /etc/dropbear/dropbear_dss_host_key Aug 02 06:49:37 DietPi dropbear[2263]: [2263] Aug 02 06:49:37 Bad password attempt for 'root' from 185.224.128.142:51934 Aug 02 06:49:47 DietPi dropbear[2284]: [2284] Aug 02 06:49:47 Child connection from 185.224.128.142:46388 Aug 02 06:49:47 DietPi dropbear[2284]: [2284] Aug 02 06:49:47 Failed loading /etc/dropbear/dropbear_dss_host_key Aug 02 06:49:52 DietPi dropbear[2263]: [2263] Aug 02 06:49:52 Exit before auth from <185.224.128.142:51934>: (user 'root', 1 fails): Exited normally Aug 02 06:49:55 DietPi dropbear[2284]: [2284] Aug 02 06:49:55 Exit before auth from <185.224.128.142:46388>: Exited normally Aug 02 06:49:55 DietPi dropbear[2290]: [2290] Aug 02 06:49:55 Child connection from 185.224.128.142:36506 Aug 02 06:49:55 DietPi dropbear[2290]: [2290] Aug 02 06:49:55 Failed loading /etc/dropbear/dropbear_dss_host_key Aug 02 06:50:03 DietPi dropbear[2290]: [2290] Aug 02 06:50:03 Exit before auth from <185.224.128.142:36506>: Exited normally
Furthermore it seems your system is directly connected to the internet. It see quite some login attempts
I’ve disabled Ethernet, and made Wireguard’s port the only open port instead. The system does not continue to start up after a while, i’ve left it over night and it’s still on the same screen and message. I’m not sure why it would take the system a long time to start up, I have minimal packages installed.
can you reboot, wait 5 minutes and share the journalctl again
I ended up just reinstalling DietPi and now it’s working. Thanks for your help.
