Ich habe mir inzwischen auch mal die /var/log/messages auf der DS angesehen. Es schaut so aus, als ob das Problem irgendwo zwischen dem letzten Eintrag in die messages beim Runterfahren, und vor dem ersten Eintrag beim Hochfahren auftritt.
Sprich:
Die Einträge beim (automatischen) Runterfahren schauen an Tagen mit Fehler genauso aus wie an Tagen ohne Fehler, z.B.:
Apr 3 01:05:01 DiskStation kernel: [64992.666968] init: crond main process (5186) killed by TERM signal
Apr 3 01:05:01 DiskStation kernel: [64992.677343] init: ftpd main process (11353) killed by TERM signal
Apr 3 01:05:01 DiskStation kernel: [64992.987289] init: sshd main process (5554) terminated with status 255
Apr 3 01:05:03 DiskStation kernel: [64993.621398] init: smbd main process (11664) killed by TERM signal
Apr 3 01:05:03 DiskStation kernel: [64994.173751]
Apr 3 01:05:03 DiskStation kernel: [64994.173757] Intel SMD Audio Driver: Deinitialize complete.
Apr 3 01:05:05 DiskStation syno_poweroff_task: System is going to poweroff.
Apr 3 01:05:35 DiskStation root: CS: [start.sh]: Cloud station stop...
Apr 3 01:05:35 DiskStation cloud-indexd: select(socket_fd): Interrupted system call (4)
Apr 3 01:05:39 DiskStation ipsec_setup: Stopping Openswan IPsec...
Apr 3 01:05:39 DiskStation ipsec_setup: stop ordered, but IPsec appears to be already stopped!
Apr 3 01:05:39 DiskStation ipsec_setup: doing cleanup anyway...
Apr 3 01:05:39 DiskStation ipsec_setup: ...Openswan IPsec stopped
Apr 3 01:05:44 DiskStation root: /usr/syno/etc/rc.d/S98findhostd.sh stop findhostd
Apr 3 01:05:44 DiskStation findhostd: findhostd.c:119(FHOSTDProcessNameGet) open [/proc/22792/cmdline] fail
2)[No such file or directory]
Apr 3 01:05:44 DiskStation findhostd: findhostd.c:69(FHOSTDExit) exit on signal[15]
killall: synolunbkp: no process killed
Apr 3 01:05:57 DiskStation synocheckshare: synocheckshare_vol_unmount.c:147 Unmount Share [INTERNAL] [/dev/mapper/vol1-origin] [/volume1]
Apr 3 01:05:59 DiskStation kernel: [65049.956936] md: md2: set sda5 to auto_remap [0]
Apr 3 01:05:59 DiskStation kernel: [65049.971783] md: md2: set sdb5 to auto_remap [0]
Apr 3 01:05:59 DiskStation kernel: [65050.089814] md: md3: set sdb6 to auto_remap [0]
Apr 3 01:05:59 DiskStation kernel: [65050.099973] md: md3: set sda6 to auto_remap [0]
Dann ist Stille im File, entweder bis zum funktionierenden Hochfahren, oder zu einem, das durch aus-/einstecken erzwungen wurde:
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: RSDP 0009fc00 00024 (v02 INTEL )
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: RSDT 00017fb0 00030 (v01 INTEL 00000000 00000000)
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: FACP 00013b10 000F4 (v03 INTEL 00000000 00000000)
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: DSDT 00013c10 010D7 (v01 Intel CE5300 00000001 INTL 20091112)
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: FACS 00017f70 00040
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: APIC 00011ae0 00078 (v01 INTEL 00000000 00000000)
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] ACPI: HPET 00011aa0 00038 (v01 INTEL 00000000 00000000)
Apr 3 09:09:24 DiskStation kernel: [ 0.000000] Zone PFN ranges:
...
Also liegt der Fehler anscheinend irgendwo dazwischen, relativ tief im System vermute ich. Arg :-(