[SOLVED] pool UNAVAIL

[M0nte0]

new Freenas user here..
I hope to get some advice to this problem i'm having with the zfs pool.

One of the disks failed and the pool was degraded.
I think i had problems with sata cables because sometimes different disks would show as degraded.
So i replaced all sata cables for disks.
I did:
made faulty disk offline trough GUI and power off server,
then replacing faulty disk with new one,
and powering on the server
I would be getting errors when trying "replace" on the new drive, also from GUI.

Is there a way to add the missing disks into the pool and make it work again.
I've been reading forums but, could not find similar situation as mine.
Kinda stuck now.

Thanks for help

setup is:
freenas111-U1 running on a Intel MB DH61BE with 4Gb RAM
5 SATA disks
one of which is freenas-boot (250 Gb) , dmesg see it as ada0
four 1TB WD black, dmesg see them as ada1, ada2, ada3, ada4
this is the current pool status

Code:

zpool status
---------------------------
  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:25 with 0 errors on Tue May 29 03:45:25 2018
config:

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

errors: No known data errors
-----------------------------

zpool import
----------------------------------------
   pool: diska4
	 id: 5567117220389899294
  state: UNAVAIL
 status: One or more devices are missing from the system.
 action: The pool cannot be imported. Attach the missing
		devices and try again.
   see: http://illumos.org/msg/ZFS-8000-6X
 config:

		diska4										  UNAVAIL  missing device
		  mirror-0									  ONLINE
			gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26  ONLINE
			gptid/8dfde512-0b4c-11e8-963b-e06995f44d26  ONLINE

		Additional devices are known to be part of this pool, though their
		exact configuration cannot be determined.
----------------------------------------

Code:

glabel status
									  Name  Status  Components  Serial
gptid/70cc7a48-0b45-11e8-b272-e06995f44d26	 N/A  ada0p1	   K94PT972D6JV
gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26	 N/A  ada1p2	   WD-WCC6Y6XTFC9C
gptid/8dfde512-0b4c-11e8-963b-e06995f44d26	 N/A  ada2p2	   WD-WCC0S0521816
gptid/367c78be-68cd-11e8-98a3-e06995f44d26	 N/A  ada3p2	   WD-WCC6Y3HSFCN0
gptid/49f4da5f-68cd-11e8-98a3-e06995f44d26	 N/A  ada4p2	   WD-WCC6Y4AFJHUY

Code:

gpart show
=>	   40  488397088  ada0  GPT  (233G)
		 40	   1024	 1  bios-boot  (512K)
	   1064  488396056	 2  freebsd-zfs  (233G)
  488397120		  8		- free -  (4.0K)

=>		40  1953525088  ada1  GPT  (932G)
		  40		  88		- free -  (44K)
		 128	 4194304	 1  freebsd-swap  (2.0G)
	 4194432  1949330688	 2  freebsd-zfs  (930G)
  1953525120		   8		- free -  (4.0K)

=>		40  1953525088  ada2  GPT  (932G)
		  40		  88		- free -  (44K)
		 128	 4194304	 1  freebsd-swap  (2.0G)
	 4194432  1949330688	 2  freebsd-zfs  (930G)
  1953525120		   8		- free -  (4.0K)

=>		40  1953525088  ada3  GPT  (932G)
		  40		  88		- free -  (44K)
		 128	 4194304	 1  freebsd-swap  (2.0G)
	 4194432  1949330688	 2  freebsd-zfs  (930G)
  1953525120		   8		- free -  (4.0K)

=>		40  1953525088  ada4  GPT  (932G)
		  40		  88		- free -  (44K)
		 128	 4194304	 1  freebsd-swap  (2.0G)
	 4194432  1949330688	 2  freebsd-zfs  (930G)
  1953525120		   8		- free -  (4.0K)

zpool history for boot disk

Code:

History for 'freenas-boot':
2018-02-06.14:55:51 zpool create -f -o cachefile=/tmp/zpool.cache -o version=28 -O mountpoint=none -O atime=off -O canmount=off freenas-boot ada2p2
2018-02-06.14:55:52 zpool set feature@async_destroy=enabled freenas-boot
2018-02-06.14:55:52 zpool set feature@empty_bpobj=enabled freenas-boot
2018-02-06.14:55:52 zpool set feature@lz4_compress=enabled freenas-boot
2018-02-06.14:55:52 zfs set compress=lz4 freenas-boot
2018-02-06.14:55:52 zfs create -o canmount=off freenas-boot/ROOT
2018-02-06.14:55:53 zfs create -o mountpoint=legacy freenas-boot/ROOT/default
2018-02-06.14:55:58 zfs create -o mountpoint=legacy freenas-boot/grub
2018-02-06.14:58:53 zpool set bootfs=freenas-boot/ROOT/default freenas-boot
2018-02-06.14:58:53 zpool set cachefile=/boot/zfs/rpool.cache freenas-boot
2018-02-06.14:59:04 zfs set beadm:nickname=default freenas-boot/ROOT/default
2018-02-06.15:08:43 zfs snapshot -r freenas-boot/ROOT/default@2018-02-06-14:08:43
2018-02-06.15:08:44 zfs clone -o canmount=off -o mountpoint=legacy freenas-boot/ROOT/default@2018-02-06-14:08:43 freenas-boot/ROOT/Initial-Install
2018-02-06.15:08:49 zfs set beadm:nickname=Initial-Install freenas-boot/ROOT/Initial-Install
2018-02-06.15:47:13 zfs snapshot -r freenas-boot/ROOT/default@2018-02-06-15:47:13
2018-02-06.15:47:15 zfs clone -o canmount=off -o mountpoint=legacy freenas-boot/ROOT/default@2018-02-06-15:47:13 freenas-boot/ROOT/Wizard-2018-02-06_06:47:13
2018-02-06.15:47:20 zfs set beadm:nickname=Wizard-2018-02-06_06:47:13 freenas-boot/ROOT/Wizard-2018-02-06_06:47:13
2018-02-14.03:45:07 zpool scrub freenas-boot
2018-02-22.03:45:07 zpool scrub freenas-boot
2018-03-02.03:45:07 zpool scrub freenas-boot
2018-03-10.03:45:06 zpool scrub freenas-boot
2018-03-18.03:45:06 zpool scrub freenas-boot
2018-03-26.03:45:06 zpool scrub freenas-boot
2018-04-03.03:45:07 zpool scrub freenas-boot
2018-04-11.03:45:06 zpool scrub freenas-boot
2018-04-19.03:45:07 zpool scrub freenas-boot
2018-04-27.03:45:06 zpool scrub freenas-boot
2018-05-05.03:45:06 zpool scrub freenas-boot
2018-05-13.03:45:05 zpool scrub freenas-boot
2018-05-21.03:45:07 zpool scrub freenas-boot
2018-05-29.03:45:10 zpool scrub freenas-boot

 

[kdragon75]

You have two disks that are not showing up in your pool.

Code:

gptid/367c78be-68cd-11e8-98a3-e06995f44d26	 N/A  ada3p2	   WD-WCC6Y3HSFCN0
gptid/49f4da5f-68cd-11e8-98a3-e06995f44d26	 N/A  ada4p2	   WD-WCC6Y4AFJHUY

Seem to be the ones. Start with reseating cables and related connectors, then add 4GB of RAM as you are well below the absolute minimum for FreeNAS.
Once you have reseated the drives run camcontrol devlist to make sure the drives are actually detected then we can look at zpool status -v.

 

[M0nte0]

NEW drive that has replaced the bad one is on ada3

These are the outputs for both commands

Code:

camcontrol devlist
<FUJITSU MJA2250BH G2 8919>		at scbus0 target 0 lun 0 (ada0,pass0)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus2 target 0 lun 0 (ada1,pass1)
<WDC WD10EARX-00N0YB0 51.0AB51>	at scbus3 target 0 lun 0 (ada2,pass2)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus4 target 0 lun 0 (ada3,pass3)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus5 target 0 lun 0 (ada4,pass4)

Code:

zpool status -v
  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:25 with 0 errors on Tue May 29 03:45:25 2018
config:

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

errors: No known data errors

Thank You for helping out

 

[Chris Moore]

NEW drive that has replaced the bad one is on ada3

These are the outputs for both commands

Code:

camcontrol devlist
<FUJITSU MJA2250BH G2 8919>		at scbus0 target 0 lun 0 (ada0,pass0)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus2 target 0 lun 0 (ada1,pass1)
<WDC WD10EARX-00N0YB0 51.0AB51>	at scbus3 target 0 lun 0 (ada2,pass2)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus4 target 0 lun 0 (ada3,pass3)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus5 target 0 lun 0 (ada4,pass4)

Code:

zpool status -v
  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:25 with 0 errors on Tue May 29 03:45:25 2018
config:

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

errors: No known data errors

Thank You for helping out

I think you may have offlined the correct drive but physically replaced the wrong drive. That would explain why you have two drives missing. I suggest that you put all the original drives back into the system and don't reference drives in FreeNAS by the ada# because that can change from boot to boot. The number you should look at to identify a drive is the serial number of the drive which is shown in the GUI.

 

[Chris Moore]

freenas111-U1 running on a Intel MB DH61BE with 4Gb RAM

That is a desktop board, not a server board. In addition to installing the at least the minimum required memory, you really need to get on server grade hardware if your data is the least bit important to you.
Please review the following resources.

Hardware Requirements
http://www.freenas.org/hardware-requirements/

FreeNAS® Quick Hardware Guide
https://forums.freenas.org/index.php?resources/freenas®-quick-hardware-guide.7/

Hardware Recommendations Guide Rev 1e) 2017-05-06
https://forums.freenas.org/index.php?resources/hardware-recommendations-guide.12/

Updated Forum Rules 4/11/17
https://forums.freenas.org/index.php?threads/updated-forum-rules-4-11-17.45124/

Slideshow explaining VDev, zpool, ZIL and L2ARC
https://forums.freenas.org/index.ph...ning-vdev-zpool-zil-and-l2arc-for-noobs.7775/

Terminology and Abbreviations Primer
https://forums.freenas.org/index.php?threads/terminology-and-abbreviations-primer.28174/

 

[kdragon75]

I think you may have offlined the correct drive but physically replaced the wrong drive. That would explain why you have two drives missing.

That would certainly make sense.

<WDC WD10EARX-00N0YB0 51.0AB51> at scbus3 target 0 lun 0 (ada2,pass2)

This is not a good drive for a NAS. It will try to spin down and park the heads way to often. With intermittent use this can be almost a constant cycle causing premature failure. Also, there slow. Stick with recommended hardware, especially if you care about your data. Keep in mind when adding a brand new drive, you should perform a burn-in with badblocks as the least. New drives have higher failure rates than drives with thousands of hours on them.

 

[M0nte0]

I could not agree more with all what you all wrote.
The financial situation in our small company gave me what i've got.
Once better days come we will upgrade to a real server hardware.
In the meantime I'll definitely put 8GB of RAM to give more room for OS.

I started from beginning and installed bad drive again, exactly as it was before replacement.
I can see the pool now is state=DEGRADED
much better than before...

These are some of the outputs for troubleshooting.
Fujitsu disk is freenas OS
Seagate is the one i tried replacing

Thank You all for helping out

Code:

zpool status -v
  pool: diska4
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
		corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
		entire pool from backup.
   see: http://illumos.org/msg/ZFS-8000-8A
  scan: resilvered 0 in 0 days 00:00:01 with 31 errors on Tue Jun  5 23:17:24 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		diska4										  DEGRADED	31	 0	 0
		  mirror-0									  ONLINE	   0	 0	 0
			gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26  ONLINE	   0	 0	 0
			gptid/8dfde512-0b4c-11e8-963b-e06995f44d26  ONLINE	   0	 0	 0
		  mirror-1									  DEGRADED	62	 0	 4
			ada3p2									  ONLINE	   0	 0	66
			5972466314894734148						 UNAVAIL	  0	 0	 0  was /dev/gptid/90328d78-0b4c-11e8-963b-e06995f44d26

errors: Permanent errors have been detected in the following files:

		<metadata>:<0x0>
		<metadata>:<0x119>
		<metadata>:<0x69>
		<metadata>:<0x8a>
		<metadata>:<0x98>
		<metadata>:<0xbf>
		<metadata>:<0xc0>
		<metadata>:<0xd6>
		<metadata>:<0xff>
		diska4/users:<0x0>
		diska4/.system/cores:<0x0>
		/var/db/system/cores/syslog-ng.core

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:25 with 0 errors on Tue May 29 03:45:25 2018
config:

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

errors: No known data errors

Code:

camcontrol devlist
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus0 target 0 lun 0 (ada0,pass0)
<WDC WD10EARX-00N0YB0 51.0AB51>	at scbus1 target 0 lun 0 (ada1,pass1)
<FUJITSU MJA2250BH G2 8919>		at scbus2 target 0 lun 0 (ada2,pass2)
<ST1000DM010-2EP102 CC43>		  at scbus3 target 0 lun 0 (ada3,pass3)
<WDC WD1003FZEX-00K3CA0 01.01A01>  at scbus4 target 0 lun 0 (ada4,pass4)

Code:

glabel status
									  Name  Status  Components
gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26	 N/A  ada0p2
gptid/8dfde512-0b4c-11e8-963b-e06995f44d26	 N/A  ada1p2
gptid/70cc7a48-0b45-11e8-b272-e06995f44d26	 N/A  ada2p1
gptid/49f4da5f-68cd-11e8-98a3-e06995f44d26	 N/A  ada4p2

Code:

camcontrol identify /dev/ada0 | grep ^serial		 WD-WCC6Y6XTFC9C
camcontrol identify /dev/ada1 | grep ^serial		 WD-WCC0S0521816
camcontrol identify /dev/ada2 | grep ^serial		 K94PT972D6JV
camcontrol identify /dev/ada3 | grep ^serial		 Z9AAQFDK
camcontrol identify /dev/ada4 | grep ^serial		 WD-WCC6Y4AFJHUY

 

[M0nte0]

i hope i still have a chance to get this up and running ,or am i SOL ?

 

[kdragon75]

The financial situation in our small company gave me what i've got.

If the financial stability depends on the data being available, they will find the funds to do this the right way. Feel free to quote me. I have turned jobs down due to unrealistic budgets.

Ok, that looks better. I don't suppose you noted the serial numbers of the disks while they were out? no you just need to replace the seagate and use zpool replace <pool> <failed> <gptid/new-drive-id> as noted by @Chris Moore, you should avoid using adaX naming and stick with the gptid numbers. I also noticed that part of mirror-1 was added as ada3p2. Once you get teh replacement drive working and resilvered, you may consider removing ada3p2 and adding it back via gptid. Check your backups first.

 

[kdragon75]

i hope i still have a chance to get this up and running ,or am i SOL ?

Once its up, take a snapshot and then test everything out.

This is showing some metadata errors and depending on whats affected, you may be able to pul things back from a snapshot as needed. Otherwise its time to hit the backups. They paid for backups right?

Code:

	   <metadata>:<0x0>
	   <metadata>:<0x119>
	   <metadata>:<0x69>
	   <metadata>:<0x8a>
	   <metadata>:<0x98>
	   <metadata>:<0xbf>
	   <metadata>:<0xc0>
	   <metadata>:<0xd6>
	   <metadata>:<0xff>
	   diska4/users:<0x0>
	   diska4/.system/cores:<0x0>
	   /var/db/system/cores/syslog-ng.core

 

[Chris Moore]

Why are you doing this at the command line instead of the GUI?

Sent from my SAMSUNG-SGH-I537 using Tapatalk

 

[Chris Moore]

What I see doesn't indicate that the Seagate drive is at fault.

Sent from my SAMSUNG-SGH-I537 using Tapatalk

 

[M0nte0]

Seagate is not showing in
glabel status
I don't see ada3
Could that be the sign this drive is bad

Earlier in a day (before replacing it) i could hear weird / grinding sounds from inside Seagate disk.
Other disks were not making such sounds.
( hold tip of a scredriver on the disk casing, and the screwdriver handle inside ear )
not the other way around ;)

If i could cross-reference the number in bold 5972466... to some seral # would that give me
which disk to replace ?

mirror-1 DEGRADED 62 0 4
ada3p2 ONLINE 0 0 66
5972466314894734148 UNAVAIL 0 0 0 was /dev/gptid/90328d78-0b4c-11e8-963b-e06995f44d26

i have one more free SATA port in which i'll connect new drive, and then try the "replace" procedure.

Which process is easier for beginner to do replace, i preffer CLI, but i read other people like GUI to manage replacement. I don't know.

I'm on UTC +2, so i'll read up on it tommorow and based on your suggestions do the best thing.

Thank You all for providing such great help.

 

[kdragon75]

hold tip of a scredriver on the disk casing, and the screwdriver handle inside ear

Old mechanics trick!

 

[Chris Moore]

5972466314894734148 UNAVAIL 0 0 0 was /dev/gptid/90328d78-0b4c-11e8-963b-e06995f44d26

What happened to that disk? It isn't in the system now.
You must rebuild this missing drive before you worry about anything else.

 

[M0nte0]

i upgraded the RAM to min. requirements of 8GB
after couple of reboots pool is in degrated status,
and was usable enough to get all data backed up.

Still don't know what to do with UNAVAIL disk.
also ada3p2 is not showing it's gptid

Any help or advice greatly appreciated.
Thank You

camcontrol devlist
<WDC WD1003FZEX-00K3CA0 01.01A01> at scbus0 target 0 lun 0 (ada0,pass0)
<WDC WD10EARX-00N0YB0 51.0AB51> at scbus1 target 0 lun 0 (ada1,pass1)
<FUJITSU MJA2250BH G2 8919> at scbus2 target 0 lun 0 (ada2,pass2)
<ST1000DM010-2EP102 CC43> at scbus3 target 0 lun 0 (ada3,pass3)
<WDC WD1003FZEX-00K3CA0 01.01A01> at scbus4 target 0 lun 0 (ada4,pass4)

Code:

zpool status -v
  pool: diska4
 state: DEGRADED
status: One or more devices could not be opened.  Sufficient replicas exist for
		the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://illumos.org/msg/ZFS-8000-2Q
  scan: resilvered 0 in 0 days 00:00:01 with 0 errors on Wed Jun  6 16:17:33 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		diska4										  DEGRADED	 0	 0	 0
		  mirror-0									  ONLINE	   0	 0	 0
			gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26  ONLINE	   0	 0	 0
			gptid/8dfde512-0b4c-11e8-963b-e06995f44d26  ONLINE	   0	 0	 0
		  mirror-1									  DEGRADED	 0	 0	 0
			ada3p2									  ONLINE	   0	 0	 0
			5972466314894734148						 UNAVAIL	  0	 0	 0  was /dev/gptid/90328d78-0b4c-11e8-963b-e06995f44d26

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:20 with 0 errors on Wed Jun  6 03:45:21 2018
config:

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

errors: No known data errors

these the serials for disks and their gptid's ( K94PT972D6JV is the freenas-boot)

Code:

+========+============================================+=================+
| Device |				   GPTID					|	  Serial	 |
+========+============================================+=================+
| ada0   | gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26 | WD-WCC6Y6XTFC9C |
+--------+--------------------------------------------+-----------------+
| ada1   | gptid/8dfde512-0b4c-11e8-963b-e06995f44d26 | WD-WCC0S0521816 |
+--------+--------------------------------------------+-----------------+
glabel: No such geom: ada2p2.
| ada2   |											| K94PT972D6JV	|
+--------+--------------------------------------------+-----------------+
glabel: No such geom: ada3p2.
| ada3   |											| Z9AAQFDK		|
+--------+--------------------------------------------+-----------------+
| ada4   | gptid/49f4da5f-68cd-11e8-98a3-e06995f44d26 | WD-WCC6Y4AFJHUY |
+--------+--------------------------------------------+-----------------+

 

[Chris Moore]

Please look in the GUI and follow this resource:

Replacing a failed/failing disk
https://forums.freenas.org/index.php?resources/replacing-a-failed-failing-disk.75/

The disk to replace first is the one that is completely offline. You can see the serial numbers of the online disks in the GUI. Use a process of elimination and remove the disk (by serial number) that is not being used after the replace is complete.
Then you will move on and replace the disk that is making noise following similar steps.
After the NAS is healthy, you can do testing on the removed drives to ensure their condition, but I think that a healthy disk may have been removed when a different disk was causing the problem.
Mirrors are very unreliable as you can only survive a single disk fault. I prefer RAIDz2, even in this case, you would have had a similar amount of available storage, but any two disks could have failed without destroying any data.

 

[M0nte0]

Wow, Mr. Moore You Rock
Looks like Seagate drive was not at fault
When problem started, I offlined correct faulty drive, but physically disconnected wrong one.

What i did to fix problem for someone else if needed.
So first i printed the labels with serial numbers and labeled all the disks
Then poweroff and i removed the one i should have removed 2 days ago,
and replaced it with new one. Power On the box.
Then from GUI went to
Storage > diska4 pool (top one) > volume status button on the bottom,
highlighted the UNAVAIL disk and Replace button also on the bottom of page
and selected ada4 ( new disk ) on the member window prompt.
Resilvering was done in 5 min. And all looks ok now.

Except there's no glabel showing for two disks.
And in the zpool status instead of gptid there's only ada3p2 under mirror-1
I'll read somewhere on the forums how to change that.

I'm marking the topic SOLVED

Thank You for advice, suggestions , and the solution.
Like it says in the Slideshow explaining VDev, zpool, ZIL and L2ARC
https://forums.freenas.org/index.ph...ning-vdev-zpool-zil-and-l2arc-for-noobs.7775/

it is a steep learning curve, but worth it when disks are online.

Best Regards

These are disks with serial
+========+============================================+=================+
| Device | GPTID | Serial |
+========+============================================+=================+
| ada0 | gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26 | WD-WCC6Y6XTFC9C |
+--------+--------------------------------------------+-----------------+
| ada1 | gptid/8dfde512-0b4c-11e8-963b-e06995f44d26 | WD-WCC0S0521816 |
+--------+--------------------------------------------+-----------------+
glabel: No such geom: ada2p2.
| ada2 | | K94PT972D6JV |
+--------+--------------------------------------------+-----------------+
glabel: No such geom: ada3p2.
| ada3 | | Z9AAQFDK |
+--------+--------------------------------------------+-----------------+
| ada4 | gptid/b56d4079-69b4-11e8-948c-e06995f44d26 | WD-WCC6Y3HSFCN0 |
+--------+--------------------------------------------+-----------------+

And this is the pool status

Code:

zpool status
  pool: diska4
 state: ONLINE
  scan: resilvered 39.7G in 0 days 00:05:16 with 0 errors on Wed Jun  6 20:14:52 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		diska4										  ONLINE	   0	 0	 0
		  mirror-0									  ONLINE	   0	 0	 0
			gptid/8cb80fb9-0b4c-11e8-963b-e06995f44d26  ONLINE	   0	 0	 0
			gptid/8dfde512-0b4c-11e8-963b-e06995f44d26  ONLINE	   0	 0	 0
		  mirror-1									  ONLINE	   0	 0	 0
			ada3p2									  ONLINE	   0	 0	 0
			gptid/b56d4079-69b4-11e8-948c-e06995f44d26  ONLINE	   0	 0	 0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0 days 00:00:20 with 0 errors on Wed Jun  6 03:45:21 2018
config:

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

errors: No known data errors

 

[Chris Moore]

Except there's no glabel showing for two disks.
And in the zpool status instead of gptid there's only ada3p2 under mirror-1
I'll read somewhere on the forums how to change that.

The simple way to get the gptid is to do a replace of the drive. If you do the replace through the GUI, it should partition the drive and create the glabel as part of the process of putting a replacement in the pool.