NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
4.2.20 : Volume expansion will not work beyond 16 TB...
Can someone explain to me what that means or give us more details ...
I encountered this issue as well with my Ultra6. I opened a case but managed to resolve the issue as it was taking too much time for me. Please note that the backup and factory reset is the best solution, but for me the offline expansion through ssh login worked. Please realize that this may not work for you, this procedure is at your own risk!.
I did the expansion under 4.2.19 and now have 13,7 TB with a single redundant array (6*3TB Hitachi drives). Starting point was a hot added HDD which successfully was checked and striped. After this the volume was expanded upto 8TB beyond the original size after which a "Volume Expansion Failed" error appeared. I was asked by Netgear support to remove the last added HDD and power down the ReadyNAS after which the HDD should be reinserted and booted. This did not work for me as the "Volume Expansion Failed" error reappeared.
1. First log into the ReadyNAS. For this the ssh addon has to be installed. Use a Linux machine with standard SSH or Putty or similar from a windows machine on the same LAN.
2. Optional:
a. As the filesystem expansion and check commands can be lengthy make sure that your terminal remains connected during the operations. If you want to play it safe use the Linux "screen" command which still may have to be installed:
b. Run screen so your session will remain to run even after the ssh session is disconnected:
c. You can detach the session by pressing "CTRL-A" and then "D" and reconnect by typing:
2. In order to do an offline expansion no services should be using the volume /c. As I only used SMB and NFS the following commands were sufficient:
3. After this I could unmount volume /dev/c/c/ with the following command. If the command fails something is still using the /c volume. You could check what that is with the lsof command. You may have to disable addons or other services such as AFP, FTP, etc.
4. The e2fsck and resize2fs commands use a lot of memory and fail if memory runs out. I increased available memory (my ReadyNAS has only 1GB ram) by making a temporary 1GB swap file. With the "df" command you can check if there is enough room in /root. This was the case for me. If you don't have enough room look for an alternative location. Even an external USB HDD can be used for the swap file.
5. First check filesystem consistency, I had errors after adding the 5th and 6th drive.
6. Now expand the volume with the following command:
7. And run another file system check:
8. Mount the volume again:
Now I had the full volume size as could be expected. I hope this information is useful.
9. Before I forget it, the swap file should be deleted again :D:
I did the expansion under 4.2.19 and now have 13,7 TB with a single redundant array (6*3TB Hitachi drives). Starting point was a hot added HDD which successfully was checked and striped. After this the volume was expanded upto 8TB beyond the original size after which a "Volume Expansion Failed" error appeared. I was asked by Netgear support to remove the last added HDD and power down the ReadyNAS after which the HDD should be reinserted and booted. This did not work for me as the "Volume Expansion Failed" error reappeared.
1. First log into the ReadyNAS. For this the ssh addon has to be installed. Use a Linux machine with standard SSH or Putty or similar from a windows machine on the same LAN.
2. Optional:
a. As the filesystem expansion and check commands can be lengthy make sure that your terminal remains connected during the operations. If you want to play it safe use the Linux "screen" command which still may have to be installed:
apt-get install screen
b. Run screen so your session will remain to run even after the ssh session is disconnected:
screen
c. You can detach the session by pressing "CTRL-A" and then "D" and reconnect by typing:
screen -R
2. In order to do an offline expansion no services should be using the volume /c. As I only used SMB and NFS the following commands were sufficient:
/etc/init.d/nfs-kernel-server stop
/etc/init.d/samba stop
3. After this I could unmount volume /dev/c/c/ with the following command. If the command fails something is still using the /c volume. You could check what that is with the lsof command. You may have to disable addons or other services such as AFP, FTP, etc.
umount /c
4. The e2fsck and resize2fs commands use a lot of memory and fail if memory runs out. I increased available memory (my ReadyNAS has only 1GB ram) by making a temporary 1GB swap file. With the "df" command you can check if there is enough room in /root. This was the case for me. If you don't have enough room look for an alternative location. Even an external USB HDD can be used for the swap file.
dd if=/dev/zero of=swap bs=1M count=1000
mkswap swap
swapon swap
5. First check filesystem consistency, I had errors after adding the 5th and 6th drive.
e2fsck -f /dev/c/c
6. Now expand the volume with the following command:
resize2fs -pf /dev/c/c
7. And run another file system check:
e2fsck -f /dev/c/c
8. Mount the volume again:
mount /c
Now I had the full volume size as could be expected. I hope this information is useful.
9. Before I forget it, the swap file should be deleted again :D:
swappoff swap
rm swap
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
