Unable to add disks to a pool. (GEOM_ELI: Encryption: AES-XTS 256)

[zicoz]

Hi, I'm trying to add some harddrives to my pool, I get a "volume succssfully added" message in the web-ui, but the pool doesn't grow and the drives aren't actually added to the pool.

In the console I get the following message for each drive:

Code:

GEOM_ELI: Device mfisyspd0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
         Crypto: hardware

The drives used to be in another pool earlier, but I've deleted all the partitions on the drives since then.

 

[cyberjock]

First, you are using the beta with encryption on if you are getting that message. You may be encountering a bug with the beta.

When you say "add some hard drives" explain further. If you read my guide adding harddrives to a zpool isn't really supported. If you are making a second vdev of drives, that's different and is supported. But ZFS doesn't let you do capacity expansion like many RAID5 and RAID6 controllers by adding a hard drive to expand the size without losing redundancy.

 

[zicoz]

Hi, thank you and sorry.

Yes, what I am doing is creating a 2nd RaidZ2 Vdev of 8 drives.

edit:

And yes I am using the beta, but I have not enabled ZFS encryption for the volume.

 

[digitizedsoul]

Hi, thank you and sorry.

Yes, what I am doing is creating a 2nd RaidZ2 Vdev of 8 drives.

edit:

And yes I am using the beta, but I have not enabled ZFS encryption for the volume.

I am having this same issue.

I have 18 drives.
I am adding them one by one to label them properly.
I create VDEV's of 3 drives each RAIDZ in the GUI.
I go to extend the volume by adding another 3 drives and selecting raidz, it sais it completed succesfully but the pool does not grow and a volume status reflects no added drives.
I also show lots of chatter about encryption for each volume in the log with some "cannot get gpt/id GUID VALUE" in there as well.
I do not have encryption enabled.

Running the latest beta.

 

[cyberjock]

I would go to IRC chat and see if the developers are there. Or open a ticket at support.freenas.org and provide step by step directions of what you are doing so they can reproduce the bug. Please include your hardware specs, version number, and any error messages with the ticket.

 

[Lars Jensen]

Using latest beta and got the same problem with:
Controller AOC-SAS2LP-H8IR Rev. 1.10
Backplane BPN-SAS2-216EB Rev. 1.02 + BPN-SAS2-216EL1 Rev. 1.02
and 24 Constellation.2 ST9500620SS 500GB disks

Any of you have some progress on the issue?

 

[andyclimb]

Ok so I have the same problem. Volume successfully added but it is not.

I have 6 hard drives. I created a mirrored volume using two drives, and then add a further two, and then the final two. previously this worked great. I have a volume with 3 vdevs, each contained a pair of mirrored drives. im just using this whole machine as a test bed.

Now i can add drives to a striped array no problem. but when I try to expand a mirrored pair, it does not work. However, the drives are thought to be used as i can't wipe them until i detach the volume. zpool status by command line gives the same as in freenas.... ie.. nothing has been added...

I have tried to use encryption, but it is NOT enabled for this! All drives can be made into mirrored pairs as a volume, just not extend one.

here is the log window
Feb 7 16:30:03 freenas INADYN[2779]: W:'RC_DYNDNS_RSP_NOTOK' (0x48) updating the IPs. (it 0)
Feb 7 16:30:03 freenas INADYN[2779]: E: The response of DYNDNS svr was an error! Aborting.
Feb 7 16:30:03 freenas INADYN[2779]: W:INADYN: Main: Error 'RC_DYNDNS_RSP_NOTOK' (0x48).
Feb 7 16:39:30 freenas notifier: Will not 'restart' inadyn because inadyn_enable is NO.
Feb 7 16:40:01 freenas kernel: GEOM_ELI: Detached ada2p1.eli on last close.
Feb 7 16:40:05 freenas kernel: GEOM_ELI: Detached ada1p1.eli on last close.
Feb 7 16:40:08 freenas kernel: GEOM_ELI: Detached ada5p1.eli on last close.
Feb 7 16:40:18 freenas kernel: GEOM_ELI: Detached ada4p1.eli on last close.
Feb 7 16:40:27 freenas kernel: GEOM_ELI: Detached ada3p1.eli on last close.
Feb 7 16:40:37 freenas kernel: GEOM_ELI: Detached ada6p1.eli on last close.
Feb 7 16:40:46 freenas notifier: swapoff: removing /dev/ada2p1.eli as swap device
Feb 7 16:40:46 freenas notifier: swapoff: removing /dev/ada1p1.eli as swap device
Feb 7 16:40:46 freenas notifier: swapoff: removing /dev/ada5p1.eli as swap device
Feb 7 16:40:46 freenas notifier: swapoff: removing /dev/ada4p1.eli as swap device
Feb 7 16:40:46 freenas notifier: swapoff: removing /dev/ada3p1.eli as swap device
Feb 7 16:40:46 freenas notifier: swapoff: removing /dev/ada6p1.eli as swap device
Feb 7 16:40:47 freenas notifier: 1+0 records in
Feb 7 16:40:47 freenas notifier: 1+0 records out
Feb 7 16:40:47 freenas notifier: 1048576 bytes transferred in 0.006586 secs (159216831 bytes/sec)
Feb 7 16:40:47 freenas notifier: dd: /dev/ada5: short write on character device
Feb 7 16:40:47 freenas notifier: dd: /dev/ada5: end of device
Feb 7 16:40:47 freenas notifier: 5+0 records in
Feb 7 16:40:47 freenas notifier: 4+1 records out
Feb 7 16:40:47 freenas notifier: 4939776 bytes transferred in 0.050543 secs (97733992 bytes/sec)
Feb 7 16:40:48 freenas notifier: 1+0 records in
Feb 7 16:40:48 freenas notifier: 1+0 records out
Feb 7 16:40:48 freenas notifier: 1048576 bytes transferred in 0.006705 secs (156386108 bytes/sec)
Feb 7 16:40:48 freenas notifier: dd: /dev/ada6: short write on character device
Feb 7 16:40:48 freenas notifier: dd: /dev/ada6: end of device
Feb 7 16:40:48 freenas notifier: 5+0 records in
Feb 7 16:40:48 freenas notifier: 4+1 records out
Feb 7 16:40:48 freenas notifier: 4939776 bytes transferred in 0.050457 secs (97900706 bytes/sec)
Feb 7 16:40:49 freenas notifier: cannot open 'mirror/dev/gptid/202c858d-7145-11e2-bc84-e839352caa53': no such GEOM provider
Feb 7 16:40:49 freenas notifier: must be a full path or shorthand device name
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Device ada2p1.eli created.
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Crypto: software
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Device ada1p1.eli created.
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Crypto: software
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Device ada5p1.eli created.
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Crypto: software
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Device ada4p1.eli created.
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Crypto: software
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Device ada3p1.eli created.
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Feb 7 16:41:08 freenas kernel: GEOM_ELI: Crypto: software
Feb 7 16:41:18 freenas kernel: GEOM_ELI: Device ada6p1.eli created.
Feb 7 16:41:18 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Feb 7 16:41:18 freenas kernel: GEOM_ELI: Crypto: software
Feb 7 16:41:18 freenas notifier: Stopping collectd.
Feb 7 16:41:27 freenas notifier: Waiting for PIDS: 2821.
Feb 7 16:41:27 freenas notifier: Starting collectd.
Feb 7 16:41:46 freenas notifier: geli: Cannot access ada2p1 (error=1).
Feb 7 16:41:46 freenas notifier: Stopping collectd.
Feb 7 16:41:47 freenas notifier: Waiting for PIDS: 4094.
Feb 7 16:41:47 freenas notifier: Starting collectd.
Feb 7 16:41:47 freenas notifier: Stopping cron.
Feb 7 16:41:47 freenas notifier: Starting cron.
Feb 7 16:45:04 freenas ntpd[2366]: kernel time sync status change 2001

 

[Lars Jensen]

Anyone tried to configure disks (extend pool) with FreeNAS-8.3.0-RELEASE-p1 and then switch to 8.3.1 beta 3, and have a working multi-raidz2 pool ?

 

[William Grzybowski]

I think you guys should learn to use the report bug system (support.freenas.org) instead of complaining in the forum, which the developers rarely take a look at.
Forum is for discussion, not reporting bugs to be fixed.

 

[Lars Jensen]

I think you guys should learn to use the report bug system (support.freenas.org) instead of complaining in the forum, which the developers rarely take a look at.
Forum is for discussion, not reporting bugs to be fixed.

It's a kind of magic, fixed in https://support.freenas.org/changeset/13286 by william

 

[Lars Jensen]

I've just tried the patch on https://support.freenas.org/changeset/13286 and restarted nginx. But pool still doesn't get extended. Is there something else which needs to be done?

 

[William Grzybowski]

Yes, restarting django.

 

[Lars Jensen]

Yes, restarting django.

Works, thanks :)