NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
volume expansion failed
1 Topic
Replaced failing disk in NV+ v2 - both volume expansion and volume scan fail
Hi folks, I'm getting some slightly peculiar behaviour from my NV+ v2, and would really appreciate some help in troubleshooting. A week or so ago, I started getting errors on disk 1 of my NAS, which was configured as follows: 1: 3Tb 2: 4Tb 3: 3Tb 4: 4Tb For reference, the original configuration when I first set up the NAS, was 2x3Tb. I bought a new 4Tb disk (same type as in bays 2 and 4), pulled out disk 1, and replaced it with the new 4Tb disk. The following is (unfortunately reverse time order) the current log info from the admin view, beginning from the second (and last) failed attempt to expand the volume: Mon Sep 14 15:11:51 EST 2015 Volume expansion failed Mon Sep 14 14:58:17 EST 2015 Incompleted file system expansion detected. Resuming... Mon Sep 14 14:57:04 EST 2015 Volume expansion failed Mon Sep 14 14:39:56 EST 2015 Newly added drive has more space to expand the volume, will start volume expansion. Mon Sep 14 14:39:35 EST 2015 RAID sync finished on volume C. Sat Sep 12 11:17:21 EST 2015 RAID sync started on volume C. Sat Sep 12 11:16:46 EST 2015 Data volume will be rebuilt with disk 1. Sat Sep 12 11:16:27 EST 2015 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1] Sat Sep 12 11:11:20 EST 2015 A disk was removed from the ReadyNAS. One or more RAID volumes are currently unprotected, and an additional disk failure or removal may result in data loss. Please add a replacement disk as soon as possible. As you can see, everything seemed fine until 14:57 on 14 September when the first attempt at volume expansion fails. And then a second time at 15:11 on 14 September. After that, it appeared to give up on the idea of volume expansion, so I tried a reboot (with a volume scan). Here's where it gets a bit more unsettling: volume scan also failed, quite quickly, when it attempted to run. On wading through the logs, I see the system killed fsck (or fsck killed itself) because it is out of memory. This seems a bizarre condition to encounter on startup... and yet, it now appears to do it every time. Although - for now - it is claiming to be redundant (albeit still the old size), there doesn't appear any reason why the expansion should have failed (I don't believe I'm at the 8TiB expansion limit yet - that should happen the next time I replace a 3Tb with a 4Tb, not this time)... and no way to clear its head so it can do something as straightforward as a volume scan. Is there a known bug in the system? Any idea what options I have? I'm not averse to doing things via SSH if there are further options to pursue there, but I want to be sure to do the right things.5.4KViews0likes31Comments