Print

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

[dblv]

I have two NAS units. One DNS-323 w/2 one TB drives and one DNS-325 with the same drives. They are WD Black Caviar 1TB drives. NOTE: They are NOT "green" drives. The 323 is configured as mirrored RAID configuration and works fine. The 325 is configured as Standard (each a separate volume). It had been previously configured as mirrored also. The problem in the 325 existed in either configuration.
 
PROBLEM - The 323 works fine. The drives in the 325, however, quickly spin down when not in use and take time to spin up when accessed. This is a problem in itself, whoever it is compounded by the fact that every time you do anything that looks out to local and network connected drives, whether or not you need it to, the action is delayed until these drives spin up. Drives me crazy. I find no way through the 325 interface to alter this in any way. Anyone got a solution other than s****ping the 325 and getting another 323 or different manufacturer's product?

[priitv8]

At least for the WDC drives there is a WDIDLE3 DOS-utility to change this parameter in drive-s firmware.

[dblv]

Thanks ... I'll check it out. Question is .. why does this only seem to be an issue in the 325?

[JavaLawyer]

Do you have hibernation enabled on your DNS-325?
Log into the web UI and navigate to Management > Power Management > Hard Drive Hibernation Settings

[dblv]

Negative ...  made sure it was off.

[dblv]

Appears that this recommended firmware change may not apply to the model drive I am using in the 325. Additionally, I did some looking at WD's site and found that this spin down "feature" is standard in all WD drives and cannot be turned off. The firmware change may allow altering the delay, but does not allow turning it off. Guess I'll just have to live with it for now. Very annoying though. Since both the 323 and the 325 are used for backup, I can't "disconnect" them. O well ... could be worse things happening.

[JavaLawyer]

Did you notice this behavior on multiple DNS-325 FW versions or is this something centric to the last release?

[dblv]

Honestly don't remember. Seems like it was years since I flashed it with 1.03, but it couldn't have been over a year since it was released a year ago. I'm going to try resetting the bios back to the original state and than bringing it back up slowly.

[dblv]

I backed the bios version to 1.02 and the issue seems to have gone away. I need to give it a little longer to be sure, but from what I just observed, it's gone. The drives have been idle for some time and I just performed an intentional seek to both drives and both were immediately responsive. May have been a fluke, but I don't think so. We'll give it a day or so and see what happens.

[dblv]

Backing the bios to 1.02 did the trick. Problem gone. Since none of the changes in 1.03 affect me, I'm leaving it where it is for now. Thanks the help ....

[JavaLawyer]

Glad I could help, although this still begs the question as to the root cause.