System clock and spindown on NV+

Thanks for all the helpful suggestions and questions. Here's some more info about this case, which narrows down the problem.

1. I use my own ntp server which is very accurate and closely monitored. No chance that it could be the cause. After the corrections the clock is indeed correct.

2. After I wrote my last post I left myself accidentally logged into the unit, and when I returned about 4 hours later I found the disks idle. An "ntpdate -q" showed to my surprise that the clock was still accurate! I then did something which caused the disks to spin up (which introduces a delay of about 10s), and after they were running, the clock was suddenly 14 s late. Within 10 minutes the delayed cron job adjusted it as usual.

So it looks like the clock loses between 14 and 22 s during the actual spin up, but runs normally otherwise.
And if there are several spindown/up cycles before the next ntpdate, it loses several times that amount; this is also visible from the log file I posted. Could the timing system in the kernel be hanging during the spinup?

3. As for the h/w version, the back label doesn't have any "V" in it. The unit is from 2006, except for the power supply, which went up in smoke in 2009 (and took the UPS with it..).

EDIT:
I analyzed another spindown while logged in. Immediately after spin up the clock was still ok, but then within a few minutes it suddenly jumps those 14 seconds. The syslog has an entry:

Apr 20 15:13:54 rn601 kernel: :40000002|1

which seems correlated with the spinup events. What does this mean?

Roman