NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Expanding NV+
Hi Folks,
I have a question related to progressive expansion of my NV+ as I can't seem to get it to expand to the full capacity and I suspect it is due to the sequence I have used to expand.
Originally it had 2 x 500GB drives.
I added a third disk of 2TB capacity which then pushed it up to 923GB capacity. It was then that I realised that it would limit the size of the third disk to the smallest of the two original disks so the 2TB was being wasted.
All good, bought two more 2TB drives, replaced the first and let it init etc, all worked fine and remained, as expected at 923GB capacity.
Replaced disk 2 and let it init etc at which point I rebooted to complete and expected to see 4TB capacity (3 disks of 2TB each). It remains however, at 923GB capacity!
Is this because the progressive disk additions have all been working from the original base of 500GB and the NV+ is not bright enough to realise it now has overall a much larger capacity?
Or is it that I am not bright enough and have missed something obvious?
My bold assumption is that I may be able to do a factory reset and let it trash what is there and start from scratch however, I am also fundamentally lazy and don't really want to set up all my shares etc again.
Any thoughts on what I have done wrong/right and a possible way ahead to get the full capacity?
Cheers,
Gary
I have a question related to progressive expansion of my NV+ as I can't seem to get it to expand to the full capacity and I suspect it is due to the sequence I have used to expand.
Originally it had 2 x 500GB drives.
I added a third disk of 2TB capacity which then pushed it up to 923GB capacity. It was then that I realised that it would limit the size of the third disk to the smallest of the two original disks so the 2TB was being wasted.
All good, bought two more 2TB drives, replaced the first and let it init etc, all worked fine and remained, as expected at 923GB capacity.
Replaced disk 2 and let it init etc at which point I rebooted to complete and expected to see 4TB capacity (3 disks of 2TB each). It remains however, at 923GB capacity!
Is this because the progressive disk additions have all been working from the original base of 500GB and the NV+ is not bright enough to realise it now has overall a much larger capacity?
Or is it that I am not bright enough and have missed something obvious?
My bold assumption is that I may be able to do a factory reset and let it trash what is there and start from scratch however, I am also fundamentally lazy and don't really want to set up all my shares etc again.
Any thoughts on what I have done wrong/right and a possible way ahead to get the full capacity?
Cheers,
Gary
21 Replies
- What brand and model 2TB disks?
If you download your logs (Status > Logs > Download all logs) and extract the zip contents what does your partition.log look like? - Will check that out tonight when I get home and drop a post with the details, Thanks.
- Disks are:
CH1 Samsung HD204UI (1862GB)
CH2 Western Digital WD20EARX-00PASB0 (1862GB)
CH3 Western Digital WD20EARX-00PASB0 (1862GB)
Partition Log:
Disk /dev/hde doesn't contain a valid partition table
Disk /dev/hdc: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdc1 2 4096001 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdc2 4096002 4608001 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdc3 4608002 3907008687 1951200343 5 Extended
/dev/hdc5 4608003 976736305 486064151+ 8e Linux LVM
/dev/hdc6 976736312 3906992303 1465127996 8e Linux LVM
Disk /dev/hde: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Disk /dev/hdg: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdg1 2 4096001 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdg2 4096002 4608001 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdg3 4608002 3907008687 1951200343 5 Extended
/dev/hdg5 4608003 976736305 486064151+ 8e Linux LVM
/dev/hdg6 976736312 3906992303 1465127996 8e Linux LVM
Cheers,
Gary - Your disks are not 4k sector partition aligned. Hence you may have poor write performance.
It's recommended to backup your data, ensure you are running RAIDiator 4.1.7 or later then do a factory default.
Have a look at Why you might want to factory reset a Sparc ReadyNAS - Thanks for that, just confirming the backup is good and will embark upon the reset. Currently running RAIDiator 4.1.8.
Cheers, - Factory reset this morning, still churning away when I departed for work however, the LCD screen was showing 3.6TB so we appear to have won. Thank you very much for your help.
- Glad to hear it.
Simply doing reboot or two may have lead to expansion, however with terrible (pretty much unusable) write performance that wouldn't have been worth it. - I seem to be having a similar problem with resizing. The unit is sending a not very helpful error message of "Disk capacity expansion error. resize2fs". My partion log contains:
Disk /dev/hde doesn't contain a valid partition table
Disk /dev/hdc: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdc1 2 4096001 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdc2 4096002 4608001 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdc3 4608002 3907008687 1951200343 5 Extended
/dev/hdc5 4608003 976736305 486064151+ 8e Linux LVM
/dev/hdc6 976736312 3906992303 1465127996 8e Linux LVM
Disk /dev/hde: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Disk /dev/hdg: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdg1 2 4096001 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdg2 4096002 4608001 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdg3 4608002 3907008687 1951200343 5 Extended
/dev/hdg5 4608003 976736305 486064151+ 8e Linux LVM
/dev/hdg6 976736312 3906992303 1465127996 8e Linux LVM
Disk /dev/hdi: 2000.3 GB, 2000388448256 bytes
255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/hdi1 2 4096001 2048000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/hdi2 4096002 4608001 256000 82 Linux swap / Solaris
Partition 2 does not end on cylinder boundary.
/dev/hdi3 4608002 3907008687 1951200343 5 Extended
/dev/hdi5 4608003 976736305 486064151+ 8e Linux LVM
/dev/hdi6 976736312 3906992303 1465127996 8e Linux LVM
I've upgraded from four 500MB drives to four WD2002FAEX-007BA0 (1862GB) drives under X-RAID and firmware 4.1.8. The existing volume is still redundant and accessable and other than the inability to expand to the full capacity of the new drives, everything is working OK. Back-up and factory reset? :( - You could try an on-line support ticket
- If this is an older NV+ that was shipped before RAIDiator 4.1.x came out, and was later upgraded to the newer version, but never was factory defaulted on 4.1.x, then your system may be still using 4k blocks rather than 16k blocks which are necessary for expansion beyond 2GB. Go into Frontview, then status and then Logs. In the upper right you should have a button labeled download all logs. Clicking on that will download a zipped file of all logs (not the alerts you see on screen). Open the zipped file and go down to the volume.log and scan down looking for block size. If it is 4096, then yes you will have to backup and do a factory default to get the expansion. If it is 16,384 it is something else. Backing up all the data and performing a factory default will still cure a lot of ills.
If you have removed the older drives one at a time and replaced them with the larger drive the old drives are no longer a viable array. Only the first drive is as it was when it was first removed and every drive after that was sychronized with at least one of the larger drives. They can however, have the partitions removed with Windows disk management and reformatted to serve as drives onto which you can copy your data for backup purposes.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
