Buster on buffalo NAS box: random reboots but cause unknown!

[jupet]

Hello!

I am running Buster on buffalo NAS box (LS220DE, specs https://buffalonas.miraheze.org/wiki/Linkstation_LS220D )
The project according to which I installed the system is here: https://github.com/1000001101000/Debian_on_Buffalo

The installation went fine and Samba and SSHFS work now fine after some configuration and I had some memory
management problems but they seem to be solved now. I have documented my personal experience on this here: https://github.com/1000001101000/Debian ... o/issues/4

But the system keep restarting seemingly randomly. As far as I can see, logs contain no explanation for reboots.

Not totally ruled out but didn't see this happen on Stretch. The current system is dist-upgraded from stretch installation.

syslog:

Code: Select all

...
Jan 28 08:49:37 LS220DEAA3 smartd[365]: Device: /dev/sda [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 69 to 71
Jan 28 08:49:37 LS220DEAA3 smartd[365]: Device: /dev/sda [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 69 to 71
Jan 28 08:49:38 LS220DEAA3 smartd[365]: Device: /dev/sdb [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 78 to 79
Jan 28 08:49:38 LS220DEAA3 smartd[365]: Device: /dev/sdb [SAT], SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 78 to 79
reboot happened here -- time inconsistent because system has no hw clock (running fake-hwclock) 
Jan 28 09:13:16 LS220DEAA3 systemd-modules-load[206]: Failed to find module '8192eu'
Jan 28 09:13:16 LS220DEAA3 systemd-modules-load[206]: Inserted module 'loop'
Jan 28 09:13:16 LS220DEAA3 fake-hwclock[198]: Current system time: 2019-01-28 07:12:50
Jan 28 09:13:16 LS220DEAA3 fake-hwclock[198]: fake-hwclock saved clock information is in the past: 2019-01-28 06:17:02
Jan 28 09:13:16 LS220DEAA3 fake-hwclock[198]: To set system time to this saved clock anyway, use "force"
Jan 28 09:13:16 LS220DEAA3 systemd[1]: Starting Flush Journal to Persistent Storage...
...

journalctl output:

Code: Select all

...
Jan 27 21:07:37 LS220DEAA3 systemd[774]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 27 21:07:37 LS220DEAA3 systemd[774]: Listening on D-Bus User Message Bus Socket.
Jan 27 21:07:37 LS220DEAA3 systemd[774]: Reached target Sockets.
Jan 27 21:07:37 LS220DEAA3 systemd[774]: Reached target Basic System.
Jan 27 21:07:37 LS220DEAA3 systemd[774]: Reached target Default.
Jan 27 21:07:37 LS220DEAA3 systemd[774]: Startup finished in 3.230s.
-- Reboot --
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Reached target Timers.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Reached target Paths.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Starting D-Bus User Message Bus Socket.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Listening on GnuPG network certificate management daemon.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Listening on D-Bus User Message Bus Socket.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Reached target Sockets.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Reached target Basic System.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Reached target Default.
Jan 28 07:20:51 LS220DEAA3 systemd[1703]: Startup finished in 824ms.
-- Reboot --
Jan 28 09:13:33 LS220DEAA3 systemd[775]: Reached target Paths.
Jan 28 09:13:33 LS220DEAA3 systemd[775]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 28 09:13:33 LS220DEAA3 systemd[775]: Starting D-Bus User Message Bus Socket.
Jan 28 09:13:33 LS220DEAA3 systemd[775]: Listening on GnuPG cryptographic agent and passphrase cache.
...

"last reboot" output:

Code: Select all

reboot   system boot  4.19.0-1-armmp   Mon Jan 28 09:12   still running
reboot   system boot  4.19.0-1-armmp   Mon Jan 28 06:48   still running
reboot   system boot  4.19.0-1-armmp   Sun Jan 27 21:06   still running
reboot   system boot  4.19.0-1-armmp   Sat Jan 26 03:15   still running
reboot   system boot  4.19.0-1-armmp   Fri Jan 25 14:53   still running
reboot   system boot  4.19.0-1-armmp   Thu Jan 24 13:38   still running
reboot   system boot  4.19.0-1-armmp   Thu Jan 24 11:46   still running
...

dmesg -w on ssh session had nothing interesting left on screen (though I cannot be sure if ssh session dies moments before reboot happens)

The system has no physical console/display etc.

What should I check and do next?

Now installing kdump-tools but unsure if I can figure those tools out.

[Head_on_a_Stick]

didn't see this happen on Stretch

I would go back to stretch and wait until the release (or the full freeze at least), it's called "testing" for a very good reason

Have you added any foreign sources?

[jupet]

didn't see this happen on Stretch

I would go back to stretch and wait until the release (or the full freeze at least), it's called "testing" for a very good reason

Have you added any foreign sources?

I would if I actually needed the box for some actual work etc, but this is a hobby and might reveal a bug that needs to be fixed!

Sources list is pure debian stuff. The "wildest" line is "deb http://deb.debian.org/debian buster-updates main contrib non-free" and as far as I know the only non-free thing installed is firmware for realtek wireless which is not plugged into the box and no module for that is loaded.