I couldn't resist and went and bought the Q6700 for my readynas Pro Pioneer. However, installing it wasn't as straightforward as I thought. Once installed, the system started sending out scary alarms like:
DDB18 power is out of normal range [expected: 1.80 current: -0.00]. AVCC power is out of normal range [expected: 3.30 current: -0.00]. VCC3 power is out of normal range [expected: 3.30 current: -0.00]. VCC1_25 power is out of normal range [expected: 1.25 current: -0.00]. VCC1_5 power is out of normal range [expected: 1.50 current: -0.00]. VCC1_05 power is out of normal range [expected: 1.04 current: -0.00]. 3VDUAL power is out of normal range [expected: 3.30 current: -0.00]. VBAT power is out of normal range [expected: 3.30 current: -0.00].
However, the CPU seemed to be running fine. After some research I traced the cause to the /frontview/conf/enclosure.db file. Fortunately this file is a sqlite DB, which I could modify. To make a long story short, you have to change the paths where the system looks for voltage and temp data from /sys/class/hwmon/hwmon2 (which assumes a dual core CPU) to /sys/class/hwmon/hwmon4 (which assumes a quad core CPU).
I wonder if the people that tried quad core CPUs before ran into this too? Maybe this format was introduced recently? I'm running Radiator 4.2.21
I know it's too much to ask but maybe netgear can make this conf more CPU independent in later releases?
can we make the short story a bit longer? 😄 Does that mean replace all instances of hwmon2 with hwmon4 - or only specific instances?
I just put in my quad and am getting those errors... also getting a fan failure error
Hmm, ok well i answered my own question by checking the paths of ever hwmon2 and finding out they are file not found. Whereas all of the hwmon4 paths existed. So the answer is, swap out all hwmon2 for hwmon4. However, you can't just nano or vi the enclosure.db file. Doing so is what caused my odd fan 1 has failed message. I used an sqlite editor, scp'd the enclosure.db file down local, upon viewing the data, I found that its structure had a main list containing all the readynas models. I clicked my readynas model, edited the column "paths", replaced all hwmon2 with hwmon4, saved, and uploaded back to my nas, overwriting the old file (i of course made a backup first).
Once done, the readynas seems to be fully and properly functional now. No more errors and the "health" view properly displays everything.
If anyone gets stuck on this part, let me know, I'll up screenshots and more details.
my idle temp is 3C° more, about 56C° which is fine for me (Room temperature is 28C°, no air-con in the office 😞 ) I have 4GB (4-5-5-18 DDR2) Memory, maybe I will upgrade this at well to 8GB 🙂
Has anyone tried using this BIOS Update method on a Pro running OS6 v6.0.8. If so did you have any success? EDIT/P.S.: I just tried this on an Ultra 4 running OS6 v6.0.8. I got an error that said "Error: Only Debian package is allowed". So I'm guessing that this will not work on the Pro either. . . If not, is there an alternative method for performing the BIOS update without having to go back to Frontview v4.2.23? Additionally, is this the latest and greatest BIOS revision that we currently know of?
You have to install dmidecode and flashrom via apt-get. Then download the add-on onto the NAS and extract the contents of the add-on .bin manually, look at the contents of install.sh and run flashrom manually. Do make sure to check the current bios version and make sure to attempt to flash the correct BIOS.
I haven't tried this recently but it did work for me some months ago so I presume it would still work.
Looking at upgrading my ultra 2 and getting a pro 6 from the bay to upgrade, is there a certain model, I know pro 6 but of the pro 6 models is there better ones to try to go after (or avoid). Is there a way to tell with the pictures if a version is a newer vs older version like the location of the display etc....
The ReadyNAS Pro 6 is the RNDP6000-200. It has "ReadyNAS" written at the bottom right on the front of the unit.
Thanks for the usual quick reply, just reading through the threads it appears there are dofferent versions and I wasn't sure if the later ones were better then the older ones, so I thought I would ask. For example I see some with an LCD and some without, does it matter when wanting one to upgrade the CPU etc.
If you want to upgrade the CPU in a system running 4.2.x the best unit to get is a Pro 6. But you replace the CPU at your own risk.
I am looking at pro 6, I understand the risks also, I have been upgrading hacking stuff for many moons. From the pictures when they are off it was hard to tell that the top piece was part of the display, I see that now.
I just enjoy doing stuff like that, I have the ultra 2 and thought it would be nice to have more bays and came across the CPU upgrade, I am wanting to run plex in the future and that would be a good fit if I can find one at the right price, I don't need many of the bells and whistles just something that is reliable running NFS to serve up my data. I may end up just staying with my ultra 2 and spooling up a vm to run plex on, I have a 16 core box that I fold on that I could fire up a VM but thought that this might be something fun to play with. 🙂
Hmm, ok well i answered my own question by checking the paths of ever hwmon2 and finding out they are file not found. Whereas all of the hwmon4 paths existed. So the answer is, swap out all hwmon2 for hwmon4. However, you can't just nano or vi the enclosure.db file. Doing so is what caused my odd fan 1 has failed message. I used an sqlite editor, scp'd the enclosure.db file down local, upon viewing the data, I found that its structure had a main list containing all the readynas models. I clicked my readynas model, edited the column "paths", replaced all hwmon2 with hwmon4, saved, and uploaded back to my nas, overwriting the old file (i of course made a backup first).
Once done, the readynas seems to be fully and properly functional now. No more errors and the "health" view properly displays everything.
If anyone gets stuck on this part, let me know, I'll up screenshots and more details.
I've changed all hwmon2 to hwmon4 in the enclosure.db. The Fan fail message doesn't come back anymore but still does not display RPM's, although the status is green/OK Sadly the voltage messages still occurs 😞
Just wanted to let you know that I was able to upgrade my Pro Business from the slow E2160 to a much faster E7600 (30EUR on ebay) as well. Especially VirtualBox running Zarafa runs much smoother after enabling all VT-x features but also SqueezeCenter is now so much more responsive. I can only recommend this incredible upgrade. Temperature is a little higher when having high load (59/48 vs. 58/38) but lower when idling (56/24 vs. 58/25). My UPS also expects a longer remaining runtime (93 min vs. 88 min) when idling.
ok, so I also upgraded a pro to an Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz with a small stop at an E6400, both work, ok but now the system health screen reports this
Device Description Status Disk 1 Seagate ST31000528AS 931 GB , 36 C / 96 F , Write-cache ON OK Disk 2 SAMSUNG HD103UJ 931 GB , 33 C / 91 F , Write-cache ON OK Fan SYS 953 RPM OK Fan CPU 2083 RPM OK Temp SYS 54 C / 129 F [Normal 0-65 C / 32-149 F] OK Temp CPU 16.5 C / 61 F [Normal 0-60 C / 32-140 F] OK UPS 1 Not present
is a CPU temp of 17 correct?, the E2160 that was in there ran at 50-55 C
Seems to be quite low. My E7600 shows around 20.5C but that one runs at 3GHz. Are you sure you really had 50C for the E2160 cpu? Mine had an idle average of 25C.
I'm pretty sure......although I am getting old now
this is my Ultra 6 + which is in the same room, this is a stock unit, running an E5300,................and I have just looked at that, because that was running at 52-57 and now is running at 30-31!
ok, I think I need more coffee.......and maybe an increase in the old medication!
Device Description Status Disk 1 Seagate ST2000DM001-9YN164 1863 GB , 40 C / 104 F , Write-cache ON OK Disk 2 Seagate ST2000DM001-9YN164 1863 GB , 41 C / 105 F , Write-cache ON OK Disk 3 Seagate ST2000DM001-1CH164 1863 GB , 37 C / 98 F , Write-cache ON OK Disk 4 Seagate ST2000DM001-1CH164 1863 GB , 34 C / 93 F , Write-cache ON OK Fan SYS 937 RPM OK Fan CPU 2057 RPM OK Temp SYS 58 C / 136 F [Normal 0-65 C / 32-149 F] OK Temp CPU 31 C / 87 F [Normal 0-85 C / 32-185 F] OK UPS 1 Not present NA
The Ultra 4 + is running about normal though
Device Description Status Disk 1 WDC WD20EARS-00MVWB0 1863 GB , 34 C / 93 F , Write-cache ON OK Disk 2 WDC WD20EARS-00MVWB0 1863 GB , 35 C / 95 F , Write-cache ON OK Disk 3 WDC WD20EARX-00PASB0 1863 GB , 33 C / 91 F , Write-cache ON OK Fan SYS 1800 RPM OK Temp CPU 52 C / 125 F [Normal 0-80 C / 32-176 F] OK Temp SYS 37 C / 98 F [Normal 0-65 C / 32-149 F] OK UPS 1 Not present NA
I test my system by compiling my large code base which stress tests the system for about 30 minutes. In addition I downloaded the stress command line utility from https://github.com/cooljeanius/stress-1.0.4 which can also put some load on your cpu.
