Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[F1uX]

I've this same behaviour with my DNS-323. I've tried to disconnect the lan cable, and still the problem exists. Now that I've access via ssh to the internals, and the logs are written via syslogs on files, it's quite apparent there's some job scheduled to run every 90 minutes.
This is an example of last lines of my logs:

Oct 26 18:10:16 RAIDSTORAGE user.warn kernel:
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel: #              HD0 awake now !        #
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel:
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel: #              HD1 awake now !        #
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel:
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: *            HD0 stand by now!        *
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel:
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: *            HD1 stand by now!        *
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:20:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 32705 cmd /usr/sbin/offl_chk two &
Oct 26 18:30:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 450 cmd /usr/sbin/offl_chk two &
Oct 26 18:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 667 cmd /usr/sbin/offl_chk two &
Oct 26 18:50:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 884 cmd /usr/sbin/offl_chk two &
Oct 26 19:00:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1101 cmd /usr/sbin/offl_chk two &
Oct 26 19:10:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1318 cmd /usr/sbin/offl_chk two &
Oct 26 19:20:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1545 cmd /usr/sbin/offl_chk two &
Oct 26 19:30:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1769 cmd /usr/sbin/offl_chk two &
Oct 26 19:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1982 cmd /usr/sbin/offl_chk two &
Oct 26 19:50:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2200 cmd /usr/sbin/offl_chk two &
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel:
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel: #              HD0 awake now !        #
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel:
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel: #              HD1 awake now !        #
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel:
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: *            HD0 stand by now!        *
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel:
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: *            HD1 stand by now!        *
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 20:00:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2417 cmd /usr/sbin/offl_chk two &
Oct 26 20:10:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2634 cmd /usr/sbin/offl_chk two &
Oct 26 20:20:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2851 cmd /usr/sbin/offl_chk two &
Oct 26 20:30:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3068 cmd /usr/sbin/offl_chk two &
Oct 26 20:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3281 cmd /usr/sbin/offl_chk two &
Oct 26 20:50:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3498 cmd /usr/sbin/offl_chk two &
Oct 26 21:00:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3715 cmd /usr/sbin/offl_chk two &
Oct 26 21:10:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3932 cmd /usr/sbin/offl_chk two &
Oct 26 21:20:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4149 cmd /usr/sbin/offl_chk two &
Oct 26 21:30:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4372 cmd /usr/sbin/offl_chk two &
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel:
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel: #              HD0 awake now !        #
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel:
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel: #              HD1 awake now !        #
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel:
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: *            HD0 stand by now!        *
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel:
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: *            HD1 stand by now!        *
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4585 cmd /usr/sbin/offl_chk two &
Oct 26 21:50:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4802 cmd /usr/sbin/offl_chk two &
Oct 26 21:57:47 RAIDSTORAGE user.notice kernel: egiga0: link up<5>, full duplex<5>, speed 100 Mbps<5>
Oct 26 21:59:51 RAIDSTORAGE auth.info sshd[5011]: reverse mapping checking getaddrinfo for rfc-1918 [192.168.0.38] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 26 21:59:55 RAIDSTORAGE auth.info sshd[5011]: Accepted password for root from 192.168.0.38 port 54510 ssh2
Oct 26 22:00:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 5023 cmd /usr/sbin/offl_chk two &

The printer queue is free, no scheduled torrent downloads, all the servers (av, itunes, ftp) are down.
This is the crontab setting:
root@RAIDSTORAGE:~# crontab -l
32 2 * * * /usr/sbin/rtc -s
30 2 2 * * /usr/sbin/rtc -c
59 1 * * * /usr/sbin/daylight &
*/10 * * * * /usr/sbin/offl_chk two &

Any hints on how to find out the process which wakes up my hard drives?

One last thing I've observed, is that in case I remount the hd filesystem readonly the problem does not occur...

Thanks a lot,
               Fulvio

[fordem]

F1ux - since you appear to be running third party software on your DNS-323, perhaps the best place to seek help would be from someone familar with the third party software.

[Messe]

F1uX,

Thank you for very helpful investigation.  I'm in the completely same situation as yours.  I cleared all possibility which initiates HDD wake up and even tried both disconnecting LAN cable and factory reset.  But the problem is still there.  Whatever someone told you before, it's true that DNS-323 has unintentional wake up problem.  Perhaps D-Link have already noticed the issue.  They are ignoring the issue.  I'm waiting for 1.08 firmware release to confirm if it will be able to resolve this issue.

[kizer_rezik]

Mine used to turn on all the time and drove me bonkers. I reset all of my settings, installed 1.07, reset all my settings again and then configured my 323.

Actually I have two of them now and well they both sleep all day until I turn them on.

[Messe]

I have confirmed 1.08b can resolve this issue.  The reason of 1.07 unintentional wake up is still unknown.  I couldn't find any cron setting on Linux side by using funplug.  Even if D-Link is still silent for this issue, the fix is very welcome.  It's true that 1.08b is effective.  I expect release of the official 1.08 soon.  Actually I'm waiting for it from last summer  .  Anyway I don't find any problem with 1.08b so far.  So, I've decided to use it until the official 1.08 is released.