NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Replacement fan ReadyNAS nv+ v2
I recently setup my ReadyNAS NV+ v2 from scratch with four 3 TB Hitachi DK7SAD300 drives, replacing the two 3 TB Western Digital WD30EFRX drives. This is now all working well, however recently the fan has been making a lot more noise than previously.
The larger number of drives installed (four vs two) plus the fact that the Hitachi ones spin at 7200 rpm (vs 5400 rpm) will no doubt drive a higher power consumption (and lead to higher temperatures).
Temperatures remain moderate in my view (40-45 degrees for the enclosure and individual drives), but I found that the fan varies between ~1350 en 3000+ rpm. The latter makes it very noisy, so for now I have relocated from the lounge to the electric cupboard in the hallway. This is a dry and clean space, however it's a little warmer than in the lounge (20-21 degrees).
I just wrote a small shell script to monitor some metrics from
/var/log/frontview/enclosure.log; here's what I see when it's making a lot of noise:
root@vanrun:/tmp# tail -f /tmp/log-rpm-fan.log
Sun May 17 09:55:52 CEST 2026 42.8 2792
Sun May 17 09:56:52 CEST 2026 42.8 3233
Sun May 17 09:57:52 CEST 2026 42.8 3150
Sun May 17 09:58:52 CEST 2026 41.8 3233
For a more permanent solution, I am considering replacing the stock fan
Protechnic MGT9212YB-O25 (39.6 dBA - 61.62 CFM - 0.41A - 4.92 W) with one of the following:
- Noctua NF-A9 PWM - 22.8 dB - 46.44 CFM - 0.1 A - 1.2 W
- Noctua NF-A9 FLX - 17.1 dB - 38.02 CFM - 0.07 A - 0.84 W
- Noctua NF-B9 redux-1600 PWM - 17.6 dB - 37.85 CFM - 0.08 A - 0.96 W
- Noctua NF-B9 redux-1600 - 17.6 dB(A) - 37.85 CFM - 0.11 A - 1.32 W
- ARCTIC P9 PWM
- ARCTIC P9 Silent
I noticed inA really silent fan! | NETGEAR Communities that there's been others opting for the Noctua NF-B9 in the ReadyNAS nv+. I could not find specs for the ARCTIC P9 though.
Any recommendations? The PWM models come with a 4 pin connector, but can achieve slightly higher CFM. Looks like the 4 pin connector could be connected to the 3 pin connector in my
ReadyNAS nv+ v2?
6 Replies
I could not find specs for the ARCTIC P9 though.
I am googling these specs
Arctic P9 Silent - 1900 RPM - 20.5 dB(A) - 23.96 CFM - 0.08 A - 0.96 W
Arctic P9 PWM - 200-3000 RPM - 20-49 dB(A) - 38.83 CFM - 0.12A - 1.44W
Some details here:
- https://www.enostech.com/arctic-p9-series-fans-a-comparative-analysis/
3-pin fans vary the speed by varying the input voltage. PWM fans vary it by sending a separate pulse that cycles the power on/off quickly. While most PWM fans' speeds can be varied by varying the input voltage like a 3-pin fan, they may have a higher stall speed using that method than a fan intended for 3-pin control. ReadyNAS typically do have the capability to adjust the minimum speed (via SSH) to prevent stalling, but I'm not sure how to implement it on an NV+ V2.
The NV+ V1 has a fan control "learning mode", where the V2 does not. Together with a fan capable of only half the CFM of the original, that could lead to some "searching" for the proper speed when the temperature changes. I don't recommend anything less than half the original's spec.
Unless somebody does have a recommendation of one they used in a V2, the only way to tell for sure is to try it. I suggest you run tests in both environments to insure it does the job in the warmer one and doesn't stall in the cooler one. Then, please report back here on your results.
Appreciate the feedback. I collected some data to show what I am seeing (and hearing), for some reason the temperature and RPM readings of the fan vary over time with a certain interval. What's confusing is that the RPM of the fan falls below the minimum specified of 1350 RPM. But also the fan speed does not seem to react in a timely manner to an increase in temperature.
I found the minimum specified RPM specified in /ramfs/enclosure.cfg:
root@vanrun:/# cat /ramfs/enclosure.cfg fan!!0!!desc=SYS,selfcontrolled=0,minrpm=1350,required=1,alternate=0,path=/proc/fan0_rpm,in_path=/proc/fan0_pwm fan!!1!!desc=,selfcontrolled=0,minrpm=0,required=0,alternate=1,path=,in_path= fan!!2!!desc=,selfcontrolled=0,minrpm=0,required=0,alternate=2,path=,in_path= fan!!3!!desc=,selfcontrolled=0,minrpm=0,required=0,alternate=3,path=,in_path= fan!!4!!desc=,selfcontrolled=0,minrpm=0,required=0,alternate=4,path=,in_path= temp!!0!!desc=,mintemp=0,maxtemp=80,divider=1000,path= temp!!1!!desc=,mintemp=0,maxtemp=65,divider=1000,path= temp!!2!!desc=,mintemp=0,maxtemp=0,divider=1000,path= vol!!0!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!1!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!2!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!3!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!4!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!5!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!6!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!7!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!8!!desc=,minvol=0,maxvol=0,divider=1000,path= vol!!9!!desc=,minvol=0,maxvol=0,divider=1000,path=Which gets loaded at boot I believe from the database /frontview/conf/enclosure.db:
root@vanrun:/# sqlite3 /frontview/conf/enclosure.db SQLite version 3.7.3 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .schema sensors CREATE TABLE sensors ( id integer primary key autoincrement, model text, pcbid integer, board_rev integer, system_rev integer, vpd_ver integer default 0, vpd text, paths text); sqlite> select * from sensors order by rowid desc LIMIT 1; 20|ReadyNAS NV+ v2|-1|-1|-1|1| minrpm: 1350 minpwm: 165 maxtemp0: 80 mintemp0: 0 maxtemp1: 65 mintemp1: 0 maxtemp2: 0 mintemp2: 0 cpu_target: 0 cpu_tolerance: 0 labelfan0: SYS reqfan0: 1 selffan0: 0 altfan0: 0 minfan0: 1350 typefan0: 1500 |faninput0: /proc/fan0_pwm fanpath0: /proc/fan0_rpm sqlite> select vpd from sensors where id=20; minrpm: 1350 minpwm: 165 maxtemp0: 80 mintemp0: 0 maxtemp1: 65 mintemp1: 0 maxtemp2: 0 mintemp2: 0 cpu_target: 0 cpu_tolerance: 0 labelfan0: SYS reqfan0: 1 selffan0: 0 altfan0: 0 minfan0: 1350 typefan0: 1500four 3 TB Hitachi DK7SAD300 drives
At idle these use about 6 watts each, so 24 watts total. The two WD30EFRX would use a total of 8 watts at idle. So the new setup will definitely require more cooling.
In addition to the fan replacement, you might consider enabling disk spindown.
Some more data from running overnight, temperature in the electric cupboard varied between 23.5 and 24.5 degrees so quite warm (not unusual for that place in the house).
I decided to set selfcontrolled to 1 in /ramfs/enclosure.cfg and set pwm to 200. Almost immediately, the fan speed stabilises around 2200 rpm. And the temperature remains around 40 degrees, I believe this is a much better setup than relying on the NAS to automatically regulate its temperature and fan speed!
root@vanrun:/tmp# cat /ramfs/enclosure.cfg fan!!0!!desc=SYS,selfcontrolled=1,minrpm=2000,required=1,alternate=0,path=/proc/fan0_rpm,in_path=/proc/fan0_pwm ... root@vanrun:/tmp# echo 200 > /proc/fan0_pwmFor those looking to collect similar data, here's the shell script I used. The date / time format allows for a smooth import as .csv into Excel or other tools.
root@vanrun:/tmp# cat log-rpm-fan-exp.sh log=/tmp/log-rpm-fan-exp.log while : do input=/var/log/frontview/enclosure.log rpm=`cat /proc/fan0_rpm` pwm=`cat /proc/fan0_pwm` temp=`sed -n 1p $input | cut -c 27-30 | sed '/[0-9]\./s/\./,/g'` disk1=`sed -n 5p $input | sed -r 's/([^0-9]*([0-9]*)){6}.*/\2/'` disk2=`sed -n 6p $input | sed -r 's/([^0-9]*([0-9]*)){6}.*/\2/'` disk3=`sed -n 7p $input | sed -r 's/([^0-9]*([0-9]*)){6}.*/\2/'` disk4=`sed -n 8p $input | sed -r 's/([^0-9]*([0-9]*)){6}.*/\2/'` date=`date +"%d/%m/%y %T"` echo $date\;$temp\;$rpm\;$pwm\;$disk1\;$disk2\;$disk3\;$disk4 >> $log sleep 5 done
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
