Upgrading the Readynas Pro 4 (RNDP4000/4220) with 4 x 8TB disks

I can give you a partial answer.

• I have a ReadyNAS 4 Ultra (RNDU4000) running OS6.6.1
• 4 x 6TB WD60EFRX
• On the "Cool" setting, the fan runs about 1830 rpm in a 68 degree room.  Drive temps range from 91 to 96 degrees.
• Running X-RAID (RAID 5) gives me a total capacity of 16.36TB.

Here's Netgear's RAID size estimate calculator.  It only offers 6TB drives, but you might be able to estimate for 8TB drives:  http://rdconfigurator.netgear.com/raid/index.html

Not sure if that data is of any use to you, but figured I'd offer it up as you try to find a solution.

You should be able to use the full capacity of 4x8TB drives (after redandancy and overhead) with OS4.2.x, but you really should at least try OS 6.6.x since you are going to have to factory reset, anyway.  You can go back to 4.2.x if you don't like it (with another factory reset), but I think most who have made the switch have grown to like 6.6.x over 4.2.x.  There are still a few things 4.2.x had that 6.6.x doesn't, or at least are very different, but there is a lot more that 6.6.x has that 4.2.x lacks.

With a room temperature of around 72F and 4 2TB Seagate Enterprise drives (NS suffix -- these guys produce a lot of heat), my RNDU4000 fan is running at 1771RPM, whihc should be similar to an RNDP4000.  But it's not very noisy.  If yours makes a lot of noise at that RPM, you may have a failing fan.

Let me start by saying thank you Bob, Sandshark and ReadyAS for chiming in. It's always difficult thinking about moving on to something new especially as 4.2 has been rock solid for us over the years. Neither of us realised it was possible to revert back to 4.2 after OS6 so thank you for that information and you're right, what have we got to lose!?

The fan info you provided is also very helpful as we at least now have some idea of what to expect under the new platform. It could also be as Sandshark suggested that we have a faulty fan but that will require a little more investigation.

We're not quite ready to make the transition to the bigger drives but as soon as we do I'll report back and let you know how we got on.

Again thank you all for your help with this and I hope you've each had a nice weekend.

So after an initial successful upgrade from OS 4 to 6.1 and 4 x 8TB drives we've begun to experience some access issues with our Readynas (RN). The error is repeatable as per the steps outlined below (although we're not exactly sure which steps/combination of steps restores access) and the only workaround that will alleviate our issue is to login to FRONTVIEW, select the SHARES panel, EXPLORE a few of the shares and then click on REFRESH. This has the effect of 'unblocking' whatever is causing the RN to lock up but it then functions normally thereafter.

Error steps

1.    Boot the RN
2.    Access the RN via file synchronising program (Goodsync)
3.    Files begin copying (70/80 MB/s) for 5 seconds before slowing down to a halt.
4.    RN led activity light is still showing activity but eventually (after 10/20 seconds) the unit freezes and becomes unresponsive (LED won't light up either) and only holding down the power button to force a shutdown enables us to reboot the RN.

We still have to use the 'workaround' before doing any kind of accessing of data on the RN otherwise if we were to initiate Goodsync first (like we did successfully without any issues in OS 4) it will cause the unit to lock up. Then we're back at step 4.

Current Frontview Settings:

5.    Model: Readynas Pro 4
6.    Properties > No Quota Size has been set
7.    Network Access > Only SMB access has been activated
8.    Snapshots > are turned OFF
9.    File Access > Share access has been restricted to admin and one other user and both these users are checked for R/W access under all relevant share listings (i.e. the default EVERYONE and USERS remain unchecked).
10.    Grant Rename and Delete Privileges > Checked
11.    No spin down settings have been activated
12.    Firmware: 6.6.1
13.    Antivirus: Disabled
14.    Available free space: 11.73 TB

Any ideas what could be causing our issue please?