NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Readynas NV+ V2 Upgrade from 3 X 4TB to 4 X 4TB drives not working
I have been running 3 4TB drives in my NAS for around 3 years. I added a fourth 4TB drive yesterday and after syncing for about 21 hours I have gained no expansion. With the 3 drive configuration I h...
Hello Dooger,
Your NAS is running on a EXT4 file system, the only to fix this would be to seek assistance from the engineers and/or higher tier who can remote in to the NAS and fix this from the backend.
Unfortunately, It shows on your records that the support warranty of your product is already expired. You may try contacting support center and avail a support contract. That should allow you to extend the support for your product so they can escalate your issue to L3 or patiently wait for anyone in the community who has the knowledge in the SSH commands and fixing some issues from the backend. Another option is if you have a back up of the data save on the NAS you may factory default the NAS and reconfigure it from scratch then transfer back the data.
Regards,
Marty_M
NETGEAR Community Team
Do you recall what disk configuration you used when you first set up the NAS?
There is an 8 TiB growth limit to the volume - so if you started with a single disk of 3 TB or smaller you might be hitting that limit. A single disk of 4 TB wouldn't reach that limit.
Yes, my first configuration was 3 X 3TB standard desktop drives. These original drives were having to resync every so often do to errors so I upgraded to the 3 X 4TB NAS drives. I removed all the drives and started fresh with the new drives.
Dooger wrote:
I removed all the drives and started fresh with the new drives.
Ok. Then you aren't running into the volume expansion limits.
I am a bit puzzled because the resync message is for disk 3, and says nothing about disk 4.
Did you see any log entries about disk 4 being inserted? Also, download the log zip file. There should be a file in there for expansion (not sure of the name for OS 5 though, since I don't own that particular NAS model).
By the way thanks a lot for your help.
Disk 3 was the empty drive bay so that was where the new disk was added. I have downloaded the Log file and went through it looking for maybe something obvious that I might make sense of. I will add the log file from the time the expansion started.
The only thing I found was this:
[2017/09/19 12:39:24 4545] LINE 540: exec command: echo "DOING_F_RESIZE" > /.os_V_E_continue
[2017/09/19 12:39:24 4545] LINE 4569: exec command: resize2fs -pf /dev/c/c
resize2fs 1.41.14 (22-Dec-2010)
File descriptor 3 (/etc/resolv.conf (deleted)) leaked on vgscan invocation. Parent PID 4717: sh
File descriptor 3 (/etc/resolv.conf (deleted)) leaked on lvdisplay invocation. Parent PID 4677: sh
File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvdisplay invocation. Parent PID 4677: sh
File descriptor 3 (/etc/resolv.conf (deleted)) leaked on pvdisplay invocation. Parent PID 4677: sh
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 = 465, new_desc_blocks = 698
[2017/09/19 12:47:26 4545] Expand second phase error 10: resize2fs, err=0x100
[2017/09/19 12:47:26 4545] LINE 5210: exec command: /usr/sbin/expand_md -a super >> /var/log/frontview/expand_md.log 2>&1 &
[2017/09/19 12:47:26 4545] LINE 5213: exec command: /frontview/bin/volumescan &Anyone have any idea what this might mean?
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
