NV+v2 Expansion failed going from 3x3Tb to 4x3Tb

[FrankAu]

Hmmm ... I have just suffered the "Expansion Failure" on introducing the 4th 3TB disk to my RND4000 ReadyNAS NV+ v2.

The history is ... initial boot was with 2 x 3TB Seagate Barracuda ... all good until space got low ... so I introduced a 3rd 3TB Barracuda ... which was AOK delivering about 5.4TB out of the possible 9 'ish.

Then I introduced 4th 3TB Barracuda at which point it ground on for a day before it choked!!!

The firmware is RAIDiator 5.3.10-T3 (to address TimeMachine + Mavericks) and the question is how do I find out if its a faulty disk ... or the 8TB limit ... or ????.

Curiously if its the latter how come it can cope with 3x3TB drives but not 4? I have dumped the log files but haven't found any useful info yet.

[FrankAu]

Interesting bits from expand_md.log ... it seems like it was happy to set sail past 8TB (to vg_total = 13.39T) ... but resize2fs was not up to it.

[2014/02/11 06:38:31 11091] Facts:vg_total=133920,vg_alloc=89120,vg_free=44800,lv_new=44640,lv_total=%
[2014/02/11 06:38:31 11091] LINE 4694: exec command: lvextend /dev/c/c -l +44640
Extending logical volume c to 8.16 TiB
Logical volume c successfully resized
[2014/02/11 06:38:31 11091] LINE 4892: exec command: /frontview/bin/volumescan &

[2014/02/11 06:38:31 11091] LINE 540: exec command: echo "DOING_F_RESIZE" > /.os_V_E_continue
[2014/02/11 06:38:32 11091] LINE 4569: exec command: resize2fs -pf /dev/c/c
resize2fs 1.41.14 (22-Dec-2010)
resize2fs: Memory allocation failed while trying to resize /dev/c/c
Please run 'e2fsck -fy /dev/c/c' to fix the filesystem
after the aborted resize operation.
Filesystem at /dev/c/c is mounted on /c; on-line resizing required
old desc_blocks = 349, new_desc_blocks = 523
[2014/02/11 06:45:39 11091] Expand second phase error 10: resize2fs, err=0x100
[2014/02/11 06:45:41 11091] Volume expand failed, no drive added
[2014/02/11 06:45:41 11091] Failed to expand LVM
[2014/02/11 06:45:41 11091] STAGE_WIPE: Clean my_pid 11091

[FrankAu]

Next question is ... should I take any immediate action to settle things down pending a solution?

Is it feasible to drop the 4th disk out of the md array until perhaps new firmware?

[Raaahbin]

Did you ever get an answer or find a solution to this? I'm having a similar issue, which I'm pretty certain is not because of any 8TiB limit... but I am getting that "memory allocation failed" message every time it tries to do the resize. About all I've been able to come up with is going to buy a big USB drive, backing the whole thing up, and doing a factory reset. But if there's a better solution, I'd love to hear it!