ReadyOS 6 Issue with Large Volumes (missing space)

[powellandy1]

Hi

This is a follow on from - https://community.netgear.com/t5/Using-your-ReadyNAS/Adding-a-4th-10TB-drive-to-a-XRAID-array-on-Pro...

I've placed the 4x10TB and 2x6TB drives in the 516 and factory reset.

It is only showing a 27TB volume.

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
md127 : active raid5 sda3[0] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
      29278364160 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
      [>....................]  resync =  1.5% (92339416/5855672832) finish=482.5min speed=199047K/sec
      
md1 : active raid6 sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1] sda2[0]
      2094848 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]
      
md0 : active raid1 sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
      4190208 blocks super 1.2 [6/6] [UUUUUU]
      
unused devices: <none>
/dev/md/0:
        Version : 1.2
  Creation Time : Sat Aug 18 20:44:59 2018
     Raid Level : raid1
     Array Size : 4190208 (4.00 GiB 4.29 GB)
  Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
   Raid Devices : 6
  Total Devices : 6
    Persistence : Superblock is persistent

    Update Time : Sat Aug 18 20:52:20 2018
          State : clean 
 Active Devices : 6
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 0

           Name : 0ed5d010:0  (local to host 0ed5d010)
           UUID : 6f9e2c56:3498cd6e:706c27f3:97c019e0
         Events : 19

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       2       8       33        2      active sync   /dev/sdc1
       3       8       49        3      active sync   /dev/sdd1
       4       8       65        4      active sync   /dev/sde1
       5       8       81        5      active sync   /dev/sdf1
/dev/md/1:
        Version : 1.2
  Creation Time : Sat Aug 18 20:44:59 2018
     Raid Level : raid6
     Array Size : 2094848 (2045.75 MiB 2145.12 MB)
  Used Dev Size : 523712 (511.44 MiB 536.28 MB)
   Raid Devices : 6
  Total Devices : 6
    Persistence : Superblock is persistent

    Update Time : Sat Aug 18 20:45:18 2018
          State : active 
 Active Devices : 6
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : 0ed5d010:1  (local to host 0ed5d010)
           UUID : 5a9e34db:a32bc6cd:f723f220:62cfff8d
         Events : 18

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2
       2       8       34        2      active sync   /dev/sdc2
       3       8       50        3      active sync   /dev/sdd2
       4       8       66        4      active sync   /dev/sde2
       5       8       82        5      active sync   /dev/sdf2
/dev/md/data-0:
        Version : 1.2
  Creation Time : Sat Aug 18 20:45:16 2018
     Raid Level : raid5
     Array Size : 29278364160 (27922.02 GiB 29981.04 GB)
  Used Dev Size : 5855672832 (5584.40 GiB 5996.21 GB)
   Raid Devices : 6
  Total Devices : 6
    Persistence : Superblock is persistent

    Update Time : Sat Aug 18 20:50:21 2018
          State : active, resyncing 
 Active Devices : 6
Working Devices : 6
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

  Resync Status : 1% complete

           Name : 0ed5d010:data-0  (local to host 0ed5d010)
           UUID : 86bd18e6:9f28a484:85e22e96:9b3d249e
         Events : 6

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
       2       8       35        2      active sync   /dev/sdc3
       3       8       51        3      active sync   /dev/sdd3
       4       8       67        4      active sync   /dev/sde3
       5       8       83        5      active sync   /dev/sdf3

It doesn't seem to have created the second array across the 4 10TB drives.

I thought the whole point of XRAID was it was supposed to pick this up automatically.

Will it find it on a reboot?? should I factory reset again?? do it manually??

Thanks

Andy

[StephenB · Accepted solution]

---

@powellandy1 wrote:

Correct. I've only just reset.

I've rebooted it it and nothing changed (although I accept it might not as it's in the middle of a rebuild).

---

Just leave it until the resync completes.  It won't start on the second RAID group until it's done with the first one.

[StephenB]

It looks to me like the resync isn't finished - is that correct?

[powellandy1]

Correct. I've only just reset.

I've rebooted it it and nothing changed (although I accept it might not as it's in the middle of a rebuild).

I checked with the XRAID calculator and it should be 38TB.

I'm just mindful of the issue I had with the Pro6 when the 4th drive didn't expand properly and mdgm kindly did it manually but it lost XRAID and therefore the ability to seamlessly expand in the future... I was hoping a factory reset would have found all 38TB initially.

I've used mdadm -G before to expand a volume but in this case there isn't a md126 to expand.... and I would have thought there should be...

Thanks

Andy

[StephenB · Accepted solution]

---

@powellandy1 wrote:

Correct. I've only just reset.

I've rebooted it it and nothing changed (although I accept it might not as it's in the middle of a rebuild).

---

Just leave it until the resync completes.  It won't start on the second RAID group until it's done with the first one.

[powellandy1]

My bad... I was expecting it to allocate both at once. Thank you.

Kind regards,

Andy

[powellandy1]

All sorted. 38TB as expected.

Thanks

Andy