Hi. There is some progress after stopping services recommended by Ralphael:
02 26 23:44:18 23:50:40 372 0:06:12
02 27 02:20:54 02:21:12 8 0:00:08
02 27 03:15:15 03:15:33 8 0:00:08
02 27 03:40:00 04:17:10 2220 0:37:00
02 27 04:27:21 07:03:15 9344 2:35:44
02 27 07:13:26 07:15:16 100 0:01:40
02 27 07:27:30 07:27:49 9 0:00:09
02 27 07:51:13 07:51:31 18 0:00:18
02 27 08:01:42 08:02:24 42 0:00:42
02 27 08:12:35 08:13:33 58 0:00:58
02 27 08:34:56 08:35:14 18 0:00:18
02 27 08:45:25 09:17:09 1904 0:31:44
02 27 09:27:20 15:02:41 20121 5:35:21
02 27 15:27:12 16:01:10 2038 0:33:58
02 27 16:11:21 16:21:54 633 0:10:33
At 07:03:15 the drive woke up for “no reason”, but I think I found the problem in the daemon.log:
2016-02-27T07:03:15.608072+01:00 di=H10IhkTgem info dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67
2016-02-27T07:03:15.611328+01:00 di=H10IhkTgem info dhclient: DHCPACK from 192.168.1.1
2016-02-27T07:03:16.799404+01:00 di=H10IhkTgem info dhclient: bound to 192.168.1.130 – renewal in 14999 seconds.
For now I switched the Network Mode to Static (instead of DHCP), and I’ll see if there is any progress.
I also edited file: /etc/default/cron
and added the following line:
TZ=“America/Los_Angeles”
I’m not sure if it will work, but I wanted cron to do scheduled on 3:00 tasks at 18:00 my time (CET), It’s because I set on my smartphone automatic Camera folder sync, everyday at 18:00, so the drive has to wake up at that time anyway.
Does anybody know if cron does something really useful, or it could be safely disabled? I think it might also be the reason of some wake-ups.
The only thing I’m affraid of, are still those 7-8 seconds wake-ups… I’m worrying about the drive life
@tzalewski, check in your router configuration, if DHCP server (or something like this) hasn’t got too short Lease Time, however you might still need to apply some of solutions from this topic to prevent often wake-ups.