NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NV+v2 repalcing a 2TB JBOD drive with 4TB builds 2TB volume
I have previously replaced 2TB JBOD drives with 3TB and 4TB in the NV+v2 without issue. Replacing a drive recently (remove /c 2TB, replace with 4TB) the new drive volume is only 2TB. It is the same type and vintage WD Red as before, and I have tried several drives without success. Is there an SSH method to see what is preventing the full 4TB volume and correct it? Dashboard seems useless in this case other than seeing the wrong volume size.
Other ideas? Any help is appreciated!
My method of replacement is as follows:
Unit on, remove 2TB drive, reboot.
Unit on, Install new 4TB drive (previously formatted GPT, unallocated).
Allow volume creation, only 2TB every time even after successive reboots.
All unit drives are full of media and there are 8 JBOD USB drives attached and mapped, so a factory reset is undesirable.
FW 5.3.13
Current HDD configuration, JBOD/FlexRAID 0:
/c - 4TB (replaced a 2TB, volume created is 2TB instead of 4TB)
/d - 2TB JBOD
/e - 3TB JBOD (successfully replaced a 2TB)
/f - 4TB JBOD (successfully replaced a 2TB)
22 Replies
Since each drive is a separate JBOD volume, the 8TB volume expansion limit shouldn't be coming into play, but I wonder if it is somehow. I've not done any multi-volume experiments on a V2 unit, and only have a DuoV2 on which to do so.
Via SSH, looking at the output of cat /proc/mdstat may be helpful. There may also be info in the downloaded logs .zip, which one of the Netgear Mods may help you decipher.
Since you have previously used drives >2TB, that shows you do have a real V2, so the 2TB drive size limit of the V1 is not in play.
If you do end up doing a factory reset to gain use of all drives, that should not affect the content of your USB drives.
When your message first appeared, it was locked against replies (at least from us mortals). Now that it's unlocked, maybe you'll get more.
Note to Netgear mods: The KB artical pointed to above lists hard limits for the 300, 500, and 700 series ReadyNAS that are clearly based on 4TB drives are way out of date.
The Partition log follows. Should I reformat EXT3 to get rid of the GPT error?
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdi'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sdj'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000Device Boot Start End Blocks Id System
/dev/sda1 1 4294967295 2147483647+ ee GPTDisk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000Device Boot Start End Blocks Id System
/dev/sdb1 1 3907029167 1953514583+ ee GPTDisk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf74775ddDevice Boot Start End Blocks Id System
/dev/sde1 2048 3907026943 1953512448 7 HPFS/NTFSDisk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa58ea3d9Device Boot Start End Blocks Id System
/dev/sdf1 1985 3907022847 1953510431+ f W95 Ext'd (LBA)
/dev/sdf5 2048 3907022847 1953510400 7 HPFS/NTFSDisk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000Device Boot Start End Blocks Id System
/dev/sdc1 1 4294967295 2147483647+ ee GPTDisk /dev/sdd: 4000.8 GB, 4000787030016 bytes
255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000Device Boot Start End Blocks Id System
/dev/sdd1 1 4294967295 2147483647+ ee GPTDisk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9df3f892Device Boot Start End Blocks Id System
/dev/sdg1 2048 3907026943 1953512448 7 HPFS/NTFSDisk /dev/sdh: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd12243a0Device Boot Start End Blocks Id System
/dev/sdh1 1985 3907026943 1953512479+ f W95 Ext'd (LBA)
/dev/sdh5 2048 3907026943 1953512448 7 HPFS/NTFSDisk /dev/sdi: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x2d39e5a8Device Boot Start End Blocks Id System
/dev/sdi1 1 4294967295 2147483647+ ee GPTDisk /dev/sdj: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes /
WARNING: GPT (GUID Partition Table) detected on '/dev/sdk'! The util fdisk doesn't support GPT. Use GNU Parted.Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md7 doesn't contain a valid partition table
Disk /dev/md6 doesn't contain a valid partition table
Disk /dev/md4 doesn't contain a valid partition table
Disk /dev/md5 doesn't contain a valid partition table
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3 doesn't contain a valid partition table
512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69e34743Device Boot Start End Blocks Id System
/dev/sdj1 1 4294967295 2147483647+ ee GPTDisk /dev/sdl: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3534be60Device Boot Start End Blocks Id System
/dev/sdl1 1985 3907022847 1953510431+ f W95 Ext'd (LBA)
/dev/sdl5 2048 3907022847 1953510400 7 HPFS/NTFSDisk /dev/sdk: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000Device Boot Start End Blocks Id System
/dev/sdk1 1 4294967295 2147483647+ ee GPTDisk /dev/md0: 4293 MB, 4293906432 bytes
2 heads, 4 sectors/track, 1048317 cylinders, total 8386536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders, total 1048552 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md7: 1995.6 GB, 1995563909120 bytes
2 heads, 4 sectors/track, 487198220 cylinders, total 3897585760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/md6: 1995.6 GB, 1995563909120 bytes
2 heads, 4 sectors/track, 487198220 cylinders, total 3897585760 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/md4: 2995.8 GB, 2995760037888 bytes
2 heads, 4 sectors/track, 731386728 cylinders, total 5851093824 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/md5: 3996.0 GB, 3995954085888 bytes
2 heads, 4 sectors/track, 975574728 cylinders, total 7804597824 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0: 1984.8 GB, 1984811761664 bytes
255 heads, 63 sectors/track, 241306 cylinders, total 3876585472 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1: 1984.8 GB, 1984811761664 bytes
255 heads, 63 sectors/track, 241306 cylinders, total 3876585472 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2: 3985.2 GB, 3985192779776 bytes
255 heads, 63 sectors/track, 484505 cylinders, total 7783579648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Disk /dev/dm-3: 2985.0 GB, 2985002270720 bytes
255 heads, 63 sectors/track, 362905 cylinders, total 5830082560 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disk identifier: 0x00000000
Sandshark, thanks for the pointers...here is the mdstat data. Oddly, md0 and md1 show "active raid1", whereas the box is set to RAID0. I'm not sure how to read this, so input welocme here...
root@ReadyNAS2:/# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md5 : active raid0 sdd3[0]
3902298912 blocks super 1.2 16k chunksmd4 : active raid0 sdc3[0]
2925546912 blocks super 1.2 16k chunksmd6 : active raid0 sdb3[0]
1948792880 blocks super 1.2 16k chunksmd7 : active raid0 sda3[0]
1948792880 blocks super 1.2 16k chunksmd1 : active raid1 sda2[5] sdd2[3] sdc2[2] sdb2[4]
524276 blocks super 1.2 [4/4] [UUUU]md0 : active raid1 sdc1[2] sda1[5] sdb1[4] sdd1[3]
4193268 blocks super 1.2 [4/4] [UUUU]Sandshark, thanks for the feedback...please see status below:
root@ReadyNAS2:/# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md5 : active raid0 sdd3[0]
3902298912 blocks super 1.2 16k chunksmd4 : active raid0 sdc3[0]
2925546912 blocks super 1.2 16k chunksmd6 : active raid0 sdb3[0]
1948792880 blocks super 1.2 16k chunksmd7 : active raid0 sda3[0]
1948792880 blocks super 1.2 16k chunksmd1 : active raid1 sda2[5] sdd2[3] sdc2[2] sdb2[4]
524276 blocks super 1.2 [4/4] [UUUU]md0 : active raid1 sdc1[2] sda1[5] sdb1[4] sdd1[3]
4193268 blocks super 1.2 [4/4] [UUUU]
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
