questions on ReadyNAS 3200 -> 4200 move and 16 TB limitation

emonkia wrote:
In the current 4.2.17 firmware, is it still true that the only way to get 16TB+ compatibility is to factory default with 16TB+ disk space installed? I know a factory default will be required either way.

Yes. To get a volume with greater than 16TB of space you need to do a factory reset with the disks in place.

emonkia wrote:
Is the 16TB raw disk space available (disk manufacturer size), usable space (GPT available size), or volume size (XRAID6 available size)?

I believe it's the volume size.

emonkia wrote:
factory defaulted with something like v4.2.5-9 or so firmware

You can download the logs (Status > Logs > Download all logs), extract the zip contents and look in initrd.log. The oldest RAIDiator version mentioned there will be the one you factory defaulted on.

emonkia wrote:
Will the fact that it has already been factory defaulted work for auto-expansion when we pass the 16TB size?

Have a read of http://www.readynas.com/forum/viewtopic.php?p=288457#p288457
Once the 16TB limitation has been addressed eventually I think yoh-dah would probably make a post about it.

emonkia wrote:
To say this with no confusion, is it possible to: factory default system with 12 TB raw disk space in the future add more than 4 TB more disk space have auto-expansion automatically work without need to factory default again -----

I believe the limit is on volume capacity not raw disk space. When the limitation is eventually overcome, I'd expect yoh-dah would explain what is necessary for the fix to work.

emonkia wrote:

Also, we need to know if the following is still relevant: ReadyNAS 3200 and 4200 are limited to 2TB on channels 5-12. Channels 1-4 supports 3TB+ drives with RAIDiator 4.2.16+. Does the fact that the firmware v4.2.18 notes web page not mentioning the above line mean that this version of firmware fixes the firmware in the LSI controller, or does the 2TB limit for disks 5-12 still exist even with firmware v4.2.18?

A firmware update is not going to overcome a hardware issue.

emonkia wrote:
If the problem is the LSI controller, can we just replace the LSI controller with the model used in the new version of the RN4200?

That is a good question. Hopefully a Jedi notices this thread and can answer that.