DietPi shutdown after some time in an x86_64 fresh install. Topic is solved

[esturniolo]

Hi guys!
I installed debian 10 in an old netbook and then ran the script to turn it into a DietPi system. That's was a piece of cake.

The problem is now that I can't realize why the system shutdowns after 3 or 4 hours. I changed the log system to try to understand why, but there's a lot of "DietPi-Preboot" and "DietPi-Boot" when the system shutdown. Yesterday the last line in the log was on 21:17:13

This is a VERY little fragment of the syslog where you can see some DietPi-PreBoot and DietPi-Boot:

Code: Select all

Jan 27 21:17:05 example systemd[1]: Started DietPi-PreBoot.
Jan 27 21:17:05 example systemd[1]: Reached target Network (Pre).
Jan 27 21:17:05 example systemd[1]: Starting Raise network interfaces...
Jan 27 21:17:05 example systemd[1]: Started ifup for wlan0.
Jan 27 21:17:05 example systemd[1]: Started ifup for eth0.
Jan 27 21:17:06 example systemd[1]: Started Raise network interfaces.
Jan 27 21:17:06 example systemd[1]: Reached target Network.
Jan 27 21:17:06 example systemd[1]: Starting Permit User Sessions...
Jan 27 21:17:06 example systemd[1]: Starting containerd container runtime...
Jan 27 21:17:06 example systemd[1]: Starting DietPi-Boot...
Jan 27 21:17:06 example systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
Jan 27 21:17:06 example systemd[1]: Starting /etc/rc.local Compatibility...

It's seems like the system is "starting" again...


The last lines in the log before completely shutdown are these ones:

Code: Select all

Jan 27 21:17:13 example DietPi-Boot[450]: [ INFO ] DietPi-Boot | Waiting for valid network connection before continuing boot | Mode=1
Jan 27 21:17:13 example DietPi-Boot[450]: [  OK  ] DietPi-Boot | Valid network connection found
Jan 27 21:17:13 example DietPi-Boot[450]: [ .... ] DietPi-Run_NTPD | systemctl restart systemd-timesyncd
Jan 27 21:17:13 example systemd[1]: Starting Network Time Synchronization...
Jan 27 21:17:13 example systemd[1]: Started Network Time Synchronization.
Jan 27 21:17:13 example DietPi-Boot[450]: [  OK  ] DietPi-Run_NTPD | systemctl restart systemd-timesyncd
Jan 27 21:17:13 example systemd[1]: Reached target System Time Synchronized.
Jan 27 21:17:13 example DietPi-Boot[450]: [ INFO ] DietPi-Run_NTPD | Waiting for completion of systemd-timesyncd (1/60)

After that, the next line is for today, when I power on the system manually.

Any ideas?

Thanks!!!

[Joulinar]

Hi,

the time stamp is a little bit misleading. The initial time you see Jan 27 21:17 is a save time stamp that is used by the system to get an initial time before time sync is done. Usually you should see a time jump after systemd-timesyncd succeed.

Code: Select all

Jan 27 21:17:13 example DietPi-Boot[450]: [ INFO ] DietPi-Run_NTPD | Waiting for completion of systemd-timesyncd (1/60)

This Initial time stamp Jan 27 21:17 is saved every hour at the 17th minute or on a clean shutdown/reboot. That's as well the reason it looks like system was restarted as this time. But it's not the true, it's just the saved time that was restored from disk

The time stamp Jan 27 21:17 is indicating your system crashing after Jan 27 21:17 and before the next run at 22:17.

Did you switched log mode to FULL already?

[esturniolo]

Thanks for your fast reply.
Yes, the log is in FULL mode.

About the famous 17th minute, that's interesting. Is good to know it.

So, any clue about the shutdown itself?
There is someway to view/edit the ACPI settings?


EDIT: I see that the system shutdown when is in idle mode. Because during the day I'm working on it without any problems...
I added a rc.local file to turnoff the screen on lid close.

Code: Select all

#!/bin/bash
setterm --blank 1
exit 0

And uncomment

Code: Select all

/etc/systemd/login.conf

in the

Code: Select all

/etc/systemd/logind.conf

file.

But I think that this settings doesn't affect the shutdown problem.

[Joulinar]

you would need to have a look to /var/log and check the log files why system is crashing. Could be power or hardware. Quite a lot of possibilities and not all of them will be documented.

[esturniolo]

I found some ACPI error con kern.log at 21:17.

Code: Select all

Jan 27 21:17:05 minimocker kernel: [   14.064161] ACPI: Video Device [PEGP] (multi-head: yes  rom: no  post: no)
Jan 27 21:17:05 minimocker kernel: [   14.064175] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GFX0.DD02._BCL], AE_NOT_FOUND (20180810/psargs-330)
Jan 27 21:17:05 minimocker kernel: [   14.064194] ACPI Error: Method parse/execution failed \_SB.PCI0.RP01.PEGP.DD02._BCL, AE_NOT_FOUND (20180810/psparse-516)
Jan 27 21:17:05 minimocker kernel: [   14.064517] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1b/LNXVIDEO:00/input/input16
Jan 27 21:17:05 minimocker kernel: [   14.084072] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)

There is a way to modify the ACPI settings?

[Joulinar]

looks like messages from boot process. I guess this is happen at the 14th second after reboot [ 14.064161]

[esturniolo]

I wanna cry.

[esturniolo]

I discovered that if I don't close the lid, the system doesn't shutdown... So the problem is the lid or ACPI settings... 12 hours without shutdown.