NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Web interface doesn't see second drive, Linux does
I just bought a Duo V2 with two WD Green 3TB. However, when I boot up, the web interface claims that there is only one disk, 2.7TB. I'm running RAIDiator 5.3.6. To investigate, I enabled ssh acce...
My disks were (past tense) also at 80 = 8 seconds before I set the value to 254.
And yeah, before learning about the WD Green's parking behavior, all sounded nice: low amps, low temp, etc.
The WD Red (http://www.wd.com/Red) were not available when I bought my disks a year ago, and the store where I just claimed warranty replacement didn't have them in their stock.
I was close to cut a deal with a colleague also buying 2 TB disks (but not WD) to swap one drive with each other (I get one of his non-WDs and he gets one of my WDs) to attempt to mitigate a "bad stock" problem. But I chose to not follow that through.
Its hard to tell at what LCC a disk will fail, but for sure - I'd prefer a low value before a high (if the effort does not hit some other MTBF factor negatively) and I can afford the extra milliamps spent by not parking heads (and inhibiting not used circuits) before spinning down one hour later.
I spent some days looking around for a good delay setting to use with the idletool, and since some people wrote (here and there) that disabling the timer (substitute value 0) may have resulted in bad behavior/problems I decided to go for 254 which I learnt from a few others. Since 254 corresponds to a period larger than one hour, my NAS's idle disk spindown timeout will occur first resulting in parking and winding down the disks instead of just parking the heads.
What the effects of totally disabling parking are hard to tell - some few more amp hours throughout the lifetime of the disks?
Some people gets annoyed of the clicking sound that you can hear when the heads are moved to the parking track, this sound will probably also be gone with disabling.
/f
And yeah, before learning about the WD Green's parking behavior, all sounded nice: low amps, low temp, etc.
The WD Red (http://www.wd.com/Red) were not available when I bought my disks a year ago, and the store where I just claimed warranty replacement didn't have them in their stock.
I was close to cut a deal with a colleague also buying 2 TB disks (but not WD) to swap one drive with each other (I get one of his non-WDs and he gets one of my WDs) to attempt to mitigate a "bad stock" problem. But I chose to not follow that through.
Its hard to tell at what LCC a disk will fail, but for sure - I'd prefer a low value before a high (if the effort does not hit some other MTBF factor negatively) and I can afford the extra milliamps spent by not parking heads (and inhibiting not used circuits) before spinning down one hour later.
I spent some days looking around for a good delay setting to use with the idletool, and since some people wrote (here and there) that disabling the timer (substitute value 0) may have resulted in bad behavior/problems I decided to go for 254 which I learnt from a few others. Since 254 corresponds to a period larger than one hour, my NAS's idle disk spindown timeout will occur first resulting in parking and winding down the disks instead of just parking the heads.
What the effects of totally disabling parking are hard to tell - some few more amp hours throughout the lifetime of the disks?
Some people gets annoyed of the clicking sound that you can hear when the heads are moved to the parking track, this sound will probably also be gone with disabling.
/f
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
