GoFlex Home boot time problems [SOLVED]

[VicTic]

I think I solved this. See my notes at the end of this post

I've already asked this in Marvel Kirkwood forum, without much luck: viewtopic.php?f=53&t=6469

I'm running Arch on Goflex Home 3TB.

When I reboot my system, the transmission service is running but not accessible via web UI. When I investigated the problem, I also noticed timestamp during boot is wrong.

$this->bbcode_second_pass_code('', '[root@alarm ~]# uname -a
Linux alarm 3.1.10-28-ARCH #1 PREEMPT Thu Oct 17 22:11:45 CDT 2013 armv5tel GNU/Linux
[root@alarm ~]# systemctl status transmission
transmission.service - Transmission BitTorrent Daemon
Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
Active: active (running) since Fri 2015-02-20 22:23:02 EST
Main PID: 233 (transmission-da)
Status: "Idle."
CGroup: /system.slice/transmission.service
└─233 /usr/bin/transmission-daemon -f --log-error

Feb 20 22:23:02 alarm systemd[1]: Started Transmission BitTorrent Daemon.
Feb 20 22:23:02 alarm transmission-daemon[233]: sendto: Network is unreachable')

Please note the timestamp and "running since".

Restarting service corrects the problem:
$this->bbcode_second_pass_code('', '[root@alarm ~]# systemctl restart transmission
[root@alarm ~]# systemctl status transmission
transmission.service - Transmission BitTorrent Daemon
Loaded: loaded (/usr/lib/systemd/system/transmission.service; enabled)
Active: active (running) since Sun 2013-11-17 13:19:40 EST; 2s ago
Main PID: 395 (transmission-da)
Status: "Idle."
CGroup: /system.slice/transmission.service
└─395 /usr/bin/transmission-daemon -f --log-error

Nov 17 13:19:40 alarm systemd[1]: Starting Transmission BitTorrent Daemon...
Nov 17 13:19:40 alarm systemd[1]: Started Transmission BitTorrent Daemon.')

The service file:

$this->bbcode_second_pass_code('', '[root@alarm ~]# cat /usr/lib/systemd/system/transmission.service
[Unit]
Description=Transmission BitTorrent Daemon
After=network.target

[Service]
User=transmission
Type=notify
ExecStart=/usr/bin/transmission-daemon -f --log-error

[Install]
WantedBy=multi-user.target')

So, two questions:

* What's with the wrong time during boot? If I do "systemctl status ..." for any service, it shows that the service is running since Feb 20 2015, 22:23, no matter when was the last reboot. The hardware clock was synchronized (hwclock --systohc) and "hwclock -r" shows correct time.

* How do I get rid of "sendto: Network is unreachable" in transmission service on boot?

Thank you!

EDIT:
I kind of solved this. Instead of enabling transmission service, I'm now starting it from netctl by editing ExecUpPost in /etc/netctl/eth0 file

before:$this->bbcode_second_pass_code('', 'ExecUpPost='/usr/bin/ntpd -gq || true'')

after:$this->bbcode_second_pass_code('', 'ExecUpPost='/usr/bin/ntpd -gq || true; /usr/bin/systemctl start transmission || true'')

I also found out that if you have two "ExecUpPost=..." in interface file, only the last one gets executed.

Also, I think I know now why the system time is screwed up - in journal it's wrong up until the point when "ntpd -gq" is executed. So, my guess now is that GoFlex Home is not capable of storing hardware clock value during reboot.

[moonman]

Try running transmission-daemon in foreground and look for any errors that may appear.

[VicTic]

$this->bbcode_second_pass_quote('', 'T')ry running transmission-daemon in foreground and look for any errors that may appear.

[moonman]

Did you try following this? https://wiki.archlinux.org/index.php/Time The whole thing, especially Time Standard and timezone

[VicTic]

Yes, I did everything described there.

I think I know why the time is like this - this is part of journalctl output:
$this->bbcode_second_pass_code('', '1...
160:Feb 20 22:37:33 alarm systemd[1]: PID file /run/httpd/httpd.pid not readable (yet?) after start.
161:Feb 20 22:37:35 alarm systemd[1]: Started Apache Web Server.
162:Feb 20 22:37:35 alarm systemd[1]: Starting Multi-User System.
163:Feb 20 22:37:35 alarm systemd[1]: Reached target Multi-User System.
164:Feb 20 22:37:35 alarm systemd[1]: Starting Graphical Interface.
165:Feb 20 22:37:35 alarm systemd[1]: Reached target Graphical Interface.
166:Feb 20 22:37:35 alarm systemd[1]: Startup finished in 8.337s (kernel) + 19.218s (userspace) = 27.556s.
167:Nov 24 10:44:55 alarm ntpd[372]: ntpd: time set -39181960.013757 s
168:Nov 24 10:44:55 alarm systemd[1]: Time has been changed
169:Nov 24 10:44:55 alarm ifplugd[227]: client: ntpd: time set -39181960.013757s
170:Nov 24 10:44:55 alarm ifplugd[227]: client: Started network profile 'eth0'
171:Nov 24 10:44:55 alarm ifplugd[227]: Program executed successfully.
...')

The time becomes correct when ntpd is run. It's run once during boot, from network interface profile: "ExecUpPost='/usr/bin/ntpd -gq || true'"

I thought that "hwclock --systohw" should set correct value to hardware clock. Yet is's lost at reboot. So, I'm guessing that maybe the Goflex Home does NOT have a battery to keep the correct time?