NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNas 2120 : Disk not expanding after replacement
Hello there,
ReadyNAS 2120 v2
Running firmware 6.2.4
Using X-RAID (Raid5)
Had 4x4To disks, replaced 1 of them with a 8To in order to expand volume.
Formatted and waited for sync to finish.
Rebooted.
Storage did not expand automatically :(
I tried doing what worked in this post but didn't work for me : https://community.netgear.com/t5/Using-your-ReadyNAS/ReadyNAS-OS-6-not-expanding-storage/m-p/1207849#M123035
Tried doing balace, but that didn't work either.
Here are the logs :
[17/01/17 12:27:02 CET] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST4000VN000-1H4168 Serial:Z303XPTT has been removed from Channel '4' of the head unit.
[17/01/17 12:27:09 CET] warning:volume:LOGMSG_HEALTH_VOLUME Volume 'data' health changed from 'Redundant' to 'Degraded'.
[17/01/17 12:31:54 CET] notice:disk:LOGMSG_ADD_DISK Disk Model:ST8000VN0022-2EL112 Serial:ZA14VBZ3 has been added to Channel '4' of the head unit.
[17/01/17 12:35:31 CET] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Rebuilding started for Volume 'data'.
[17/01/18 00:17:08 CET] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume 'data' has been rebuilt.
[17/01/18 00:18:08 CET] notice:volume:LOGMSG_HEALTH_VOLUME Volume 'data' health changed from 'Degraded' to 'Redundant'.
[17/01/18 08:42:16 CET] notice:volume:LOGMSG_BALANCE_STARTED_VOLUME Balance started for Volume 'data'.
[17/01/18 09:16:47 CET] notice:volume:LOGMSG_BALANCE_COMPLETED_VOLUME Balance completed for Volume 'data'.
[17/01/18 09:21:19 CET] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting.
[17/01/18 09:27:25 CET] warning:volume:LOGMSG_VOLUME_USAGE_WARN Volume 'data' usage exceeds 80 % of size (10.9 TB).
[17/01/18 09:27:25 CET] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
Any ideas ?
Thanks !
You need to replace another disk with an 8TB one before redundant space can be added.
Also you are running very old firmware.
3 Replies
Replies have been turned off for this discussion
You need to replace another disk with an 8TB one before redundant space can be added.
Also you are running very old firmware.
Thanks for the quick answer. I'm just wondering why do I need to change a minimum of 2 disks for redudancy ?
I thought that the first 2 disks are for redudancy, and the rest of the disks are for more space. I installed the new disk at the end...
Concerning old firmware, I'll dig into that asap (seems that I need to go 6.5.2 first, then latest).
sinfo wrote:
I thought that the first 2 disks are for redudancy, and the rest of the disks are for more space. I installed the new disk at the end...
No, it doesn't work that way. The RAID parity blocks that achieve redundancy are spread across all the drives. The capacity rule for single redundancy is "sum the disks and subtract the largest).
Even if the first two disks were allocated for redundancy, you'd still end up with a 12 TB volume size (4+8). It's simpler not to use the extra space on the first installed larger disk, and there is no space gain possible if you do use it. No matter how you organize the parity blocks, the space devoted to them has to match the largest installed disk (otherwise you can't recover from a failure of that disk).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
