NV+ v2 wrong capacity after expansion; 2TB instead of 3TB

If possible, please give a remote access for checking.

Hello Rabbie,

Sorry it is impossible to give a remote access, but you can get the logs. Please tell me what you need and where I can find it.

can you post "mdstat" and partitions log here?I am testing this issue in my lab.

couldn't replicate this issue,2*2TB+2*3TB created in JBOD mode without problem

Thank you for your test.

Here are my configuration and the logs:

Bay1: WD30EFRX (3TB)
Bay2: WD20EARS (2TB)
Bay3: WD20EARS (2TB)
Bay4: WD30EFRX (3TB)

I can't change the position of the HDDs in Bay 1 -3, because I don't have so much backup space at the moment ;)

"mdstat":

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md5 : active raid0 sdd3[0]
      1948794912 blocks super 1.2 16k chunks

md4 : active raid0 sdc3[0]
      1948794912 blocks super 1.2 16k chunks

md3 : active raid0 sdb3[0]
      1948794912 blocks super 1.2 16k chunks

md2 : active raid0 sda3[0]
      2925544832 blocks super 1.2 64k chunks

md1 : active raid1 sda2[0] sdd2[4] sdc2[2] sdb2[1]
      524276 blocks super 1.2 [4/4] [UUUU]

md0 : active raid1 sda1[0] sdd1[4] sdc1[2] sdb1[1]
      4193268 blocks super 1.2 [4/4] [UUUU]

unused devices: <none>

and here is the partions.log

***** Disk partition log from 2013/01/20 *****


***** Disk partition log for channel 1 [sda] *****

Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 66FC21AB-FB5C-4EF6-93F7-F033431A09F9
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 64-sector boundaries
Total free space is 4092 sectors (2.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              64         8388671   4.0 GiB     FD00  
   2         8388672         9437247   512.0 MiB   FD00  
   3         9437248      5860529072   2.7 TiB     FD00  
# partition table of /dev/sda
unit: sectors

/dev/sda1 : start=        1, size=4294967295, Id=ee
/dev/sda2 : start=        0, size=        0, Id= 0
/dev/sda3 : start=        0, size=        0, Id= 0
/dev/sda4 : start=        0, size=        0, Id= 0



***** Disk partition log for channel 2 [sdb] *****

Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): DD6C3DA2-A9DE-4D10-A897-68D01EEB8C6D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 64-sector boundaries
Total free space is 30 sectors (15.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              64         8388671   4.0 GiB     FD00  
   2         8388672         9437247   512.0 MiB   FD00  
   3         9437248      3907029134   1.8 TiB     FD00  
# partition table of /dev/sdb
unit: sectors

/dev/sdb1 : start=        1, size=3907029167, Id=ee
/dev/sdb2 : start=        0, size=        0, Id= 0
/dev/sdb3 : start=        0, size=        0, Id= 0
/dev/sdb4 : start=        0, size=        0, Id= 0



***** Disk partition log for channel 3 [sdc] *****

Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 5C6C8CBF-2185-4D84-9EDE-72E04C828870
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 64-sector boundaries
Total free space is 30 sectors (15.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              64         8388671   4.0 GiB     FD00  
   2         8388672         9437247   512.0 MiB   FD00  
   3         9437248      3907029134   1.8 TiB     FD00  
# partition table of /dev/sdc
unit: sectors

/dev/sdc1 : start=        1, size=3907029167, Id=ee
/dev/sdc2 : start=        0, size=        0, Id= 0
/dev/sdc3 : start=        0, size=        0, Id= 0
/dev/sdc4 : start=        0, size=        0, Id= 0

I tested this issue again and adjusted hard drives' order,still haven't found problem

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md5 : active raid0 sdd3[0]
2925546912 blocks super 1.2 16k chunks

md4 : active raid0 sdc3[0]
1948792832 blocks super 1.2 64k chunks

md3 : active raid0 sdb3[0]
1948792832 blocks super 1.2 64k chunks

md2 : active raid0 sda3[0]
2925544832 blocks super 1.2 64k chunks

md1 : active raid1 sdd2[3] sdc2[2] sdb2[1] sda2[0]
524276 blocks super 1.2 [4/4] [UUUU]

md0 : active raid1 sdd1[3] sdc1[2] sdb1[1] sda1[0]
4193268 blocks super 1.2 [4/4] [UUUU]

unused devices: <none>


So can you contact support center to take a look your device?

As the first, thank you for your help. I have now found the solution.

My problem is a bug in the firmware. These always uses the smallest HDD as an reference for the capacity when a new disk is added in JBOD mode. This is regardless of drive bay. After I had backed up the data of the two 2TB HDDs and these were removed. The 3TB HDD is correct formatted with 3TB.