NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chsu83
Mar 29, 2017Luminary
ReadyNAS Volume not expanding - with encryption
 Don't not the exact Pro 6 Model..     I've got a Pro6 with  2x 2TB and 2x 3TB     All worked fine except the XRAID2 isn't working.. at least not how expected.  I've installed ReadyNAS OS6 with factor...
- Mar 29, 2017md1 is the swap volume, so no need to touch that. If the volume is encrypted, X-RAID won't be able to create sub RAID arrays on unused disk capacity in case of mixed capacity HDDs. It's just not compatible. This is why the logs say " Skipping X-RAID auto-expansion on encrypted pool data Your solutions: use disks of the same capacity, or create separate encrypted volumes, or don't use volume encryption. 
chsu83
Mar 29, 2017Luminary
puh.. it seems like theres something over from the raid6 test :S
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
md127 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
      5845994496 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
      [>....................]  resync =  0.5% (10276820/1948664832) finish=291.4min speed=110830K/sec
      
md1 : active raid6 sda2[0] sdc2[3] sdd2[2] sdb2[1]
      1046528 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4] [UUUU]
      
md0 : active raid1 sda1[0] sdc1[2] sdd1[3] sdb1[1]
      4190208 blocks super 1.2 [4/4] [UUUU]
      
unused devices: <none>
/dev/md/0:
        Version : 1.2
  Creation Time : Tue Mar 28 23:30:15 2017
     Raid Level : raid1
     Array Size : 4190208 (4.00 GiB 4.29 GB)
  Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent
    Update Time : Wed Mar 29 21:33:52 2017
          State : clean 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
           Name : 33eb049b:0  (local to host 33eb049b)
           UUID : 73f582d4:eb212081:661a269e:0369cfed
         Events : 238
    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       3       8       49        2      active sync   /dev/sdd1
       2       8       33        3      active sync   /dev/sdc1
/dev/md/1:
        Version : 1.2
  Creation Time : Wed Mar 29 00:07:57 2017
     Raid Level : raid6
     Array Size : 1046528 (1022.00 MiB 1071.64 MB)
  Used Dev Size : 523264 (511.00 MiB 535.82 MB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent
    Update Time : Wed Mar 29 00:29:12 2017
          State : clean 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
         Layout : left-symmetric
     Chunk Size : 512K
           Name : 33eb049b:1  (local to host 33eb049b)
           UUID : 8af43a31:0aabdd5a:7cbd7294:fc716ca5
         Events : 20
    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2
       2       8       50        2      active sync   /dev/sdd2
       3       8       34        3      active sync   /dev/sdc2
/dev/md/data-0:
        Version : 1.2
  Creation Time : Wed Mar 29 07:48:01 2017
     Raid Level : raid5
     Array Size : 5845994496 (5575.17 GiB 5986.30 GB)
  Used Dev Size : 1948664832 (1858.39 GiB 1995.43 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent
    Update Time : Wed Mar 29 21:32:46 2017
          State : clean, resyncing 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
         Layout : left-symmetric
     Chunk Size : 64K
  Resync Status : 0% complete
           Name : 33eb049b:data-0  (local to host 33eb049b)
           UUID : b8e3be8c:5c3f556b:90d6189c:4a27892f
         Events : 134
    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
- chsu83Mar 29, 2017LuminaryHave done: mdadm --grow /dev/md/1 --level=raid5 mdadm --grow /dev/md/1 --raid-devices=4 rebooted but have Skipping X-RAID auto-expansion on encrypted pool data in LOG - chsu83Mar 29, 2017Luminaryseems perhaps expanding doesn't work.. at least for uneven devices. But this seems like it should work: https://community.netgear.com/t5/Using-your-ReadyNAS/Setting-up-encryption/td-p/841686 ok that seems a statement: https://community.netgear.com/t5/Using-your-ReadyNAS/X-RAID-expansion-on-Pro4-with-OS6/td-p/904490 are there any newer knowings? 
- jak0lantashMar 29, 2017Mentormd1 is the swap volume, so no need to touch that. If the volume is encrypted, X-RAID won't be able to create sub RAID arrays on unused disk capacity in case of mixed capacity HDDs. It's just not compatible. This is why the logs say " Skipping X-RAID auto-expansion on encrypted pool data Your solutions: use disks of the same capacity, or create separate encrypted volumes, or don't use volume encryption. - chsu83Mar 29, 2017Luminarythank you for that.. good to know. yep.. the swap I only touched because I thougt if something is checking raid level of different raids.. and only if all ar good and in same way configured then the expansion starts.. thats why I tried to make them similiar. The statement, I've seen later :) Skipping X-RAID auto-expansion on encrypted pool data 
 
 
Related Content
NETGEAR Academy
 
 Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 
Join Us!
