NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
System clock and spindown on NV+
Past February I enabled disk spindown on my NV+ (4.1.13, with 4 disks). This works nicely, but now I noticed that since then the system clock is very inaccurate. The system runs ntpdate every 4 hours,...
Amazingly, since yesterday I find entries about disk spinup/down in the daemon.log; none such appeared before. The only change I can recall is the installation of the ssh addon and a reboot.
Time error seems somewhat correlated with length of spindown:
Except the last one; but this is always like that when the reason for the spinup is me logging in with ssh.
I thought about installing the ntpd addon and letting ntp run freely (without syncing the clock), so I could monitor the offset from outside, but the file
NTP-Server_4.2.4pl7-readynas-0.9.0.bin that is mentionen in a couple of places is longer in the places where Google tells me it should be.
Does anyone have a copy for me?
Roman
Time error seems somewhat correlated with length of spindown:
Apr 19 11:11:04 rn601 noflushd[674]: Spinning down disks.
Apr 19 14:00:06 rn601 noflushd[674]: Disks spinning up after 169 minutes.
Apr 19 14:10:24 rn601 ntpdate[3890]: step time server 192.168.100.8 offset 22.299269 sec
Apr 19 14:20:55 rn601 noflushd[674]: Spinning down disks.
Apr 19 15:46:42 rn601 noflushd[674]: Disks spinning up after 85 minutes.
Apr 19 16:00:23 rn601 ntpdate[4306]: step time server 192.168.100.8 offset 22.271407 sec
Apr 19 16:07:06 rn601 noflushd[674]: Spinning down disks.
Apr 19 19:04:45 rn601 noflushd[674]: Disks spinning up after 177 minutes.
Apr 19 19:28:56 rn601 noflushd[674]: Spinning down disks.
Apr 20 00:00:41 rn601 noflushd[674]: Disks spinning up after 271 minutes.
Apr 20 00:10:47 rn601 ntpdate[6312]: step time server 192.168.100.8 offset 44.546045 sec
Apr 20 02:25:18 rn601 noflushd[674]: Spinning down disks.
Apr 20 02:25:29 rn601 noflushd[674]: Disks spinning up after 0 minutes.
Apr 20 02:45:30 rn601 noflushd[674]: Spinning down disks.
Apr 20 02:53:03 rn601 noflushd[674]: Disks spinning up after 7 minutes.
Apr 20 03:13:29 rn601 noflushd[674]: Spinning down disks.
Apr 20 04:00:12 rn601 noflushd[674]: Disks spinning up after 46 minutes.
Apr 20 04:10:16 rn601 ntpdate[6969]: step time server 192.168.100.8 offset 14.924754 sec
Apr 20 04:30:29 rn601 noflushd[674]: Spinning down disks.
Apr 20 06:25:10 rn601 noflushd[674]: Disks spinning up after 114 minutes.
Apr 20 06:34:51 rn601 ntpdate[7852]: step time server 192.168.100.8 offset 14.827573 sec
Apr 20 07:07:32 rn601 noflushd[674]: Spinning down disks.
Apr 20 10:20:17 rn601 noflushd[674]: Disks spinning up after 192 minutes.
Apr 20 10:30:02 rn601 ntpdate[8828]: step time server 192.168.100.8 offset 0.046450 sec
Except the last one; but this is always like that when the reason for the spinup is me logging in with ssh.
I thought about installing the ntpd addon and letting ntp run freely (without syncing the clock), so I could monitor the offset from outside, but the file
NTP-Server_4.2.4pl7-readynas-0.9.0.bin that is mentionen in a couple of places is longer in the places where Google tells me it should be.
Does anyone have a copy for me?
Roman
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
