NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Krado
Apr 28, 2018Tutor
ReadyNAS Pro Business Edition with Intel Xeon X3230 CPU
Hi All,
I've been following some of the CPU upgrade articles on this forum and pulled the trigger on upgrading my Pro BE to Intel Xeon x3230. Also upgraded OS4 to OS6.9.3 - Thanks to all of the talented people in this community I was able to follow some of the instructions and tips to successfully upgraded my CPU. However I have the following questions....
1. In OS 6.9.3, It seems like it only detected 2 cores instead of the quad cores. I have attached a picture. The log did not show any errors. Can someone confirm this is what I supposed to see on a quadcore?
2. I like to upgrade the system and cpu fans to keep things a bit cooler. Any recommandations?
OK, that's a configuration file issue, then. Your screen dumps didn't show up when I first replied, and I didn't realize you were using the core temperatures to determine you only have two. Check dmesg.log and see if you see a line continaing x86: Booted up 1 node, 4 CPUs. If so, it's seeing a 4-core CPU. The command lscpu can show you even more.
The configuration you need to modify is /etc/sensors.d/system.conf, which by default on a Pro6 should be a pointer to /etc/frontview/sensors/NV6.conf. Restoring the link or just copying the NV6.conf to /etc/sensors.d/system.conf should fix the voltage issues, but I don't know about the CPU core issues since I don't have a Pro6 with a quad-core CPU. The configuration for my 4-core Xeon based 4200s actually ignore all core temperatures and set the CPU temperature in the lower section of the file to "temp2".
7 Replies
Replies have been turned off for this discussion
- SandsharkSensei - Experienced User
That likely means you missed the first step, which is assuring your BIOS is the latest. Only the latest BIOS supports quad cores. Check bios_ver.log in the downloaded log zip and see if you have version 07/26/2010 FLAME6-MB V2.0.
It;'s a lot easier to update the BIOS form OS4.2.x. You may want to put in just a scratch drive, downgrade the OS, update the BIOS, and then re-upgrade the OS before returning the original drive set. The BIOS update add-on for OS4.2.x is here: http://www.readynas.com/download/addons/x86/4.2/BIOS_Update_Package_0.5-x86.bin.
- KradoTutor
Actually, that was one of my first steps. It was from one of your posts i picked up bios update. I also just double checked and made sure that it is the latest bios 07/26/2010 FLAME6-MBV2.0
However, one thing i didn't fix when I upgraded my CPU whilie in OS 4.2.31 althought, the system seems to be running fine, I get this string of errors, exactly the same as this post from Denis1, I couldn't find the solution to this, so I upgraded to OS6 then the error below disappeared. If the indication means I have to fix the error below prior to updating OS 6, then any suggestions would be much appreciative.
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].
Fan 1 has failed (SYS -1 rpm).- SandsharkSensei - Experienced User
OK, that's a configuration file issue, then. Your screen dumps didn't show up when I first replied, and I didn't realize you were using the core temperatures to determine you only have two. Check dmesg.log and see if you see a line continaing x86: Booted up 1 node, 4 CPUs. If so, it's seeing a 4-core CPU. The command lscpu can show you even more.
The configuration you need to modify is /etc/sensors.d/system.conf, which by default on a Pro6 should be a pointer to /etc/frontview/sensors/NV6.conf. Restoring the link or just copying the NV6.conf to /etc/sensors.d/system.conf should fix the voltage issues, but I don't know about the CPU core issues since I don't have a Pro6 with a quad-core CPU. The configuration for my 4-core Xeon based 4200s actually ignore all core temperatures and set the CPU temperature in the lower section of the file to "temp2".
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!