Problem on a swap partition after resilvering

Status
Not open for further replies.

AxeL

Dabbler
Joined
Nov 1, 2014
Messages
11
Hi guys,
I recently replaced an HD in a RaidZ2 (6 identical drives) pool with another one identical drive.
The pool is encrypted with GELI, the resilvering process completes without error, data are OK.

The problem I am experiencing with relates to the swap partition: every time I unlock the volume I have an error in the console complaining it cannot access the partition 1 of the drive replaced

Code:
Dec 24 13:15:10 naos GEOM_ELI: Device ada5p1.eli created.
Dec 24 13:15:10 naos GEOM_ELI: Encryption: AES-XTS 256
Dec 24 13:15:10 naos GEOM_ELI:     Crypto: hardware
Dec 24 13:15:10 naos GEOM_ELI: Device ada1p1.eli created.
Dec 24 13:15:10 naos GEOM_ELI: Encryption: AES-XTS 256
Dec 24 13:15:10 naos GEOM_ELI:     Crypto: hardware
Dec 24 13:15:10 naos GEOM_ELI: Device ada2p1.eli created.
Dec 24 13:15:10 naos GEOM_ELI: Encryption: AES-XTS 256
Dec 24 13:15:10 naos GEOM_ELI:     Crypto: hardware
Dec 24 13:15:10 naos GEOM_ELI: Device ada3p1.eli created.
Dec 24 13:15:10 naos GEOM_ELI: Encryption: AES-XTS 256
Dec 24 13:15:10 naos GEOM_ELI:     Crypto: hardware
Dec 24 13:15:10 naos GEOM_ELI: Device ada4p1.eli created.
Dec 24 13:15:10 naos GEOM_ELI: Encryption: AES-XTS 256
Dec 24 13:15:10 naos GEOM_ELI:     Crypto: hardware
Dec 24 13:15:10 naos GEOM_ELI: Device ada0p1.eli created.
Dec 24 13:15:10 naos GEOM_ELI: Encryption: AES-XTS 256
Dec 24 13:15:10 naos GEOM_ELI:     Crypto: hardware
Dec 24 13:15:10 naos notifier: geli: Cannot access ada5p1 (error=1).


The output of `swapctl` shows all the 6 partitions are currently used

Code:
# swapctl -l
Device:       1024-blocks     Used:
/dev/ada5p1.eli   2097152         0
/dev/ada1p1.eli   2097152         0
/dev/ada2p1.eli   2097152         0
/dev/ada3p1.eli   2097152         0
/dev/ada4p1.eli   2097152         0
/dev/ada0p1.eli   2097152         0


Thanks for any suggestion on the matter.
AxeL
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Hardware, freenas version and you do/did everything through the GUI right?
 

AxeL

Dabbler
Joined
Nov 1, 2014
Messages
11
Hardware, freenas version and you do/did everything through the GUI right?

HW Configuration
- MB: SuperMicro A1SAi-2750F (8 core Intel Atom)
- RAM: 16GB
- 1xUSB 16GB as boot volume
- 6xWD RED 4TB configured as a single RaidZ2

FreeNAS version 9.3.1-201512121950.

Right, everything has been performed through the GUI.

Some output

Code:
# zpool status
  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h3m with 0 errors on Mon Dec 14 03:48:49 2015
config:

    NAME        STATE     READ WRITE CKSUM
    freenas-boot  ONLINE       0     0     0
      da0p2     ONLINE       0     0     0

errors: No known data errors

  pool: storage
state: ONLINE
  scan: scrub repaired 0 in 1h6m with 0 errors on Tue Dec 15 01:06:13 2015
config:

    NAME                                                STATE     READ WRITE CKSUM
    storage                                             ONLINE       0     0     0
      raidz2-0                                          ONLINE       0     0     0
        gptid/735b8267-aab6-11e4-bbaa-0cc47a317ec0.eli  ONLINE       0     0     0
        gptid/4cc2b5ab-d1e9-11e4-b6df-0cc47a317ec0.eli  ONLINE       0     0     0
        gptid/75284398-aab6-11e4-bbaa-0cc47a317ec0.eli  ONLINE       0     0     0
        gptid/7610e6a9-aab6-11e4-bbaa-0cc47a317ec0.eli  ONLINE       0     0     0
        gptid/76fa37db-aab6-11e4-bbaa-0cc47a317ec0.eli  ONLINE       0     0     0
        gptid/77e0562e-aab6-11e4-bbaa-0cc47a317ec0.eli  ONLINE       0     0     0

errors: No known data errors
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Did you follow the docs and rekey the new drive?
 

AxeL

Dabbler
Joined
Nov 1, 2014
Messages
11
Did you follow the docs and rekey the new drive?

Yes, everything worked as expected, the pool is fine.
The problem is with the swap partition on the drive I replaced.

BTW, do you know where the error come from? so I can narrow the source of the problem

Could it be related that somehow the swap still look for a "signature" of the previous drive?

Maybe I can swapoff/swapon the affected partition?
 
Last edited:
Status
Not open for further replies.
Top