encrypted volume not visible

Status
Not open for further replies.

maniek

Cadet
Joined
Apr 27, 2015
Messages
5
Version: FreeNAS-9.3-STABLE-201605170422

I have a 4-disk encrypted volume. I have problems accessing it after a power outage. The volume is not visible in the GUI.

I tried importing it via GUI (using either geli.key or geli_recovery.key), it was not visible in the third step (the volumes list was empty).

One of the disks has 2 uncorrectable sectors, otherwise disks are fine.

I tried "zpool import main". It made "main" show up in "zpool status -x". The current state is:

Code:

zpool status -v
  pool: freenas-boot
 state: ONLINE
status: One or more devices are configured to use a non-native block size.
	Expect reduced performance.
action: Replace affected devices with devices that support the
	configured block size, or migrate data to a properly configured
	pool.
  scan: scrub repaired 0 in 0h3m with 0 errors on Fri May 25 03:48:12 2018
config:

	NAME										  STATE	 READ WRITE CKSUM
	freenas-boot								  ONLINE	   0	 0	 0
	  gptid/0d9d29ee-540b-11e5-aa70-bc5ff49cb5ee  ONLINE	   0	 0	 0  block size: 8192B configured, 8388608B native

errors: No known data errors

  pool: main
 state: UNAVAIL
status: One or more devices could not be opened.  There are insufficient
	replicas for the pool to continue functioning.
action: Attach the missing device and online it using 'zpool online'.
   see: http://illumos.org/msg/ZFS-8000-3C
  scan: none requested
config:

	NAME					  STATE	 READ WRITE CKSUM
	main					  UNAVAIL	  0	 0	 0
	  raidz1-0				UNAVAIL	  0	 0	 0
		14991703810025712573  UNAVAIL	  0	 0	 0  was /dev/gptid/40c5aef0-0023-11e3-9c57-bc5ff49cb5ee.eli
		13137064666743026926  UNAVAIL	  0	 0	 0  was /dev/gptid/1c39a80b-ecf4-11e4-aa01-bc5ff49cb5ee.eli
		13243174571038450295  UNAVAIL	  0	 0	 0  was /dev/gptid/45ff5a6c-540f-11e5-91d4-bc5ff49cb5ee.eli
		3139402185917883452   UNAVAIL	  0	 0	 0  was /dev/gptid/bf26f725-6759-11e5-93ab-bc5ff49cb5ee.eli



Code:

geom disk list
Geom name: ada0
Providers:
1. Name: ada0
   Mediasize: 3000592982016 (2.7T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   descr: WDC WD30EZRX-00AZ6B0
   lunid: 50014ee20841f28b
   ident: WD-WCC070365513
   fwsectors: 63
   fwheads: 16

Geom name: ada1
Providers:
1. Name: ada1
   Mediasize: 3000592982016 (2.7T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   descr: WDC WD30EFRX-68EUZN0
   lunid: 50014ee261258ea3
   ident: WD-WCC4N1NA92RE
   fwsectors: 63
   fwheads: 16

Geom name: ada2
Providers:
1. Name: ada2
   Mediasize: 3000592982016 (2.7T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   descr: WDC WD30EFRX-68EUZN0
   lunid: 50014ee2b68fc4f1
   ident: WD-WCC4N4TZUA2C
   fwsectors: 63
   fwheads: 16

Geom name: ada3
Providers:
1. Name: ada3
   Mediasize: 3000592982016 (2.7T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w0e0
   descr: WDC WD30EFRX-68EUZN0
   lunid: 50014ee2b72c6a30
   ident: WD-WCC4N0EP7UNY
   fwsectors: 63
   fwheads: 16

Geom name: da0
Providers:
1. Name: da0
   Mediasize: 15854469120 (14G)
   Sectorsize: 512
   Stripesize: 8388608
   Stripeoffset: 4177920
   Mode: r1w1e3
   descr: SanDisk Sandisk Ultra
   lunname: PHISON  USB3
   lunid: 2000acde48234567
   ident: A2005626505E8F99
   fwsectors: 63
   fwheads: 255


please advise.
 
D

dlavigne

Guest
status: One or more devices could not be opened. There are insufficient
replicas for the pool to continue functioning.

That is never a good error :-( Do you have backups that you can restore from?

If you do end up recreating the pool and restoring from backup, that would also be a good time to install a later version of FreeNAS. Your current version is over 2 years old.
 

maniek

Cadet
Joined
Apr 27, 2015
Messages
5
Good news: I managed to get it to work. It was just that on newest Chrome, some javascript errors were preventing the volumes from showing in the GUI. Using Firefox the volumes showed in the gui, and could be mounted.

Also, I managed to mount the volume manually, like so:

Code:
geli attach -k geli.key '/dev/gptid/<PARTITION GUID HERE>' (repeated for every partition).
zpool import <NAME OF THE POOL>


Whew, that was scary...
 
Status
Not open for further replies.
Top