DSM-G600, DNS-3xx and NSA-220 Hack Forum

Have you done a restart or eventually a shutdown with power switch ?

Fair questions.  I've done shutdowns via the WWW interface, holding the button down for a few seconds and also the back switch.  My drives are identical Western Digital drives.

Thanks for brainstorming this with me, guys.

Last edited by sp000n (2009-01-06 06:03:28)

I'm really stumped on this.  My drives continue to run.  Moreover, the cooling fan doesn't seem to be coming on to save the day.  Is it possible to revert to an older Firmware version?

There goes the Seagate theory.  I have one Seagate 500 Gb and one Western Digital 500 Gb drive set up as Raid 1.  I have also turned off lldp, ddns, timeserver, itunes, upnp, but I have ftp on.  Nothing is in my bittorrent folders right now, but the client is installed.  HDD timeout 5 minutes.

Where can I get 1.05 from?  The file doesn't come up when I try to download from dlink's website : http://www.dlink.com/products/support.asp?pid=509

I haven't changed the configuration since 1.05 and I didn't have the disks starting then spinning down issue back then.

for alb:

try this link instead: http://support.dlink.com/products/view. … d=DNS-323#

Biscotte: As far as I have understood from previous discussions and posts, the FW for DNS-323 is not country specific. It would be a surprise to me that GB releases a different 1.06 FW.

I'm living in Norway and has since FW 1.05 used the USA releases. Officially the scandinavian support pages only show 1.04 as the latest with 1.05 on their FTP site. I guess that's just poorly updated web pages - nothing else. I would believe the case to be similar with GB support pages, if you have not been told otherwise.

deurges

I noticed when doing some syslogging that the drives are put to sleep but there is two cronjobs waking up the disks.

*/10 * * * * /usr/sbin/offl_chk two &
*/60 * * * * /usr/sbin/getdhcp&

In earlier releases getdhcp was running much more frequently. However they seem to have changed that.
Anyway as I upgraded from 1.03 I have never seen offl_chk before. Is this new for 1.06 or was it there in 1.05 as well?

Both of these entries will wake up the drives.

fordem wrote:

deurges wrote:

for alb:

try this link instead: http://support.dlink.com/products/view. … d=DNS-323#

Biscotte: As far as I have understood from previous discussions and posts, the FW for DNS-323 is not country specific. It would be a surprise to me that GB releases a different 1.06 FW.

I'm living in Norway and has since FW 1.05 used the USA releases. Officially the scandinavian support pages only show 1.04 as the latest with 1.05 on their FTP site. I guess that's just poorly updated web pages - nothing else. I would believe the case to be similar with GB support pages, if you have not been told otherwise.

deurges

That's not entirely correct - I believe if you check you'll find there's a different version of the firmware available for China - with a Chinese language interface - and if I'm not mistaken, USA & Australia have different versions of the 1.06 firmware available on their support sites.

Ok Fordem, I'm really not certain. I understand that the chinese version is different due to language and Astralia setteled with an older beta of the 1.06 FW. USA ended up on beta 65 and Australia on beta 62. (?)

Anyways.. we'll see what GB does..

deurges

Dont think it is:

/mnt/debian/ffp/var/log # offl_chk
Usage : two : check 2 bays NAS
        four : check 4 bays NAS

It touches the disks. If you do strings on it you will find patterns like this:

/mnt/debian/ffp/var/log # strings /usr/sbin/offl_chk | grep HD
mount /dev/%s /mnt/HD_%c2
touch /mnt/HD_a4/awake_call /mnt/HD_b4/awake_call
rm /mnt/HD_a4/awake_call /mnt/HD_b4/awake_call
touch /mnt/HD_a4/awake_call /mnt/HD_b4/awake_call /mnt/HD_c4/awake_call /mnt/HD_d4/awake_call
rm /mnt/HD_a4/awake_call /mnt/HD_b4/awake_call /mnt/HD_c4/awake_call /mnt/HD_d4/awake_call

Which seems to obviosly wake up the drives... Something todo with trying to detect broken drives?

More strings here:

mdadm /dev/md0 -a /dev/sdb2&
/tmp/wait_sync
rm /tmp/wait_sync
device a off line
echo 0 > /tmp/wait_sync
mdadm /dev/md0 -a /dev/sda2&
System formatting , needn't to check
Check Raid1 !
device %s off line

Makes you wonder...

Is this a hijacking?  I have no idea what you guys are talking about and can't seem to relate it to disks that won't stop running.

Any other thoughts out there on the original issue?

Read a lot but my first time posting. Feels good to be able to contribute.

I had this same issue. It has something to do with the RAID1. I had 1.05 and no issues with spinning down. Then in 1.06 it would go down for 2 mins every 10 then spin back up. I disconnected the ethernet cable and it still did it so that told me it was something in the box not the router causing it to sping back up. Then I changed to 2 standard disks and got rid of RAID1 and it stays in power save mode now till I use it again.

I'm also using RAID1 and 1.06 with no spindown issues - that go down for 2 mins every 10 mins and then spin back up is reminescent of the old "uncleared print job in the spool file issue" where the unit would try to spool up every 10 minutes until you cleared the spool file, so reformatting the drives, which would have deleted anything in the \.lpd folder, would have exactly the same effect.

Maybe this is stupid, but how do you guys determine that the HDDs wake-up?