Error in time set, SPD8020, FW7.0 and 8.0

[wd9895]

Hi Julien, Hi fvdw

I just recognized that my SPD8020's (I have 2) have wrong timestamps.
I use fw7.0 and actually tried fw8.0, same error.

Manual timestamp: error message "could not update field Time and Date (1)"
NTP time set: not working automatically !
My NTP server 129.187.254.32

After setting once to manual and try, setting back to NTP it updates time and date correctly. After power down, error's back again.

Any idea or workaround ?

[fvdw]

mmm...I use 129.132.2.21 and 130.149.17.8 seems to work fine, also after boot

Where do you get this error ? I can not find in my log files

It could be caused if there is no connection to internet when the ntp daemon is started, I remember someone else mentioned this issue before.
But if I can not reproduce it its difficult to solve

[Jocko]

Hi fvdw & wd9895

:idea: fvdw, it's me who mentioned this issue ... (with a NWSP).

It is possible to reproduce it :
- Disconnect the network cable from NAS
- Restart the NAS
- Wait for the boot script runs completely to reconnect the network cable.

=> The NTP server did not update the system date even waiting a long time (one day!).

It should then change the NTP server settings so that the update is done.

[fvdw]

If it is because there is no internet connection (as in the simulation of Jocko without network cable) then I do not how to solve it. Must be a bug in ntp client.
The ntp client on the NAS is started after an IP address is obtained from the dhcp server. (normally a router) typically there should be an internet connection then.
Maybe I should consider to recompile the ntp client.
But as said on my spd's it is no issue, ntp is working directly after boot

[fvdw]

think I found what wd9895 is reffering to, the manual command to set time doesn't work anymore. You get the error message in the webinterface when you try to modify the time manually. The cause is the new version of busybox, in the fvdw7-0 upgrade we introduced a new version of busybox. Busybox is used to set the time. The new version contains a date command that needs a different format.
This is probably not the reason that the ntp server fails after boot on wd9895 system, I can not reproduce that error on my system ntp set time correct at boot

Anyhow to make the manual date setting working again the sym link "date" in the system directory /bin must be modified.
It must be linked to "busybox1" instead of "busybox".
If you are familiar with winscp its easy to do by right clicking on it and choose edit sym link from the menu

With putty you could use the following commands after accessing your nas via ssh

Code: Select all

unlink /bin/date
ln -s busybox1 /bin/date

[wd9895]

Dear both,

some explanations to my system:
The DSL modem, a Router and the NAS is on one power connection which I switch off in the night or when I'm not at home.
So it looks on power on, that the DHCP server in the router is faster that the synch of the (internet) DSL modem. The boot script fails, must fail.
I wonder why the NTP time resynch is only on the boot phase but this is the situation as it is.

Nevertheless the manual date/time set fails. I will try the workaround proposed by fvdw.

P.S. workaround works ! Thank you both.