gpart recovery arg0 'ada1': Invalid argument

[wombat-fertilizer]

Long time, first time...

<TLDR>: (resolved?) I had an unavailable disk after upgrading and then reverting an HBA ada1 aka gptid/2725ca3e-3817-11e7-8768-00400510e336. I "replaced" it via the GUI, traceback occurred, but drive rejoined the vdev raidz2-1 without being resilvered.

It feels like I didn't recover this correctly. Another reboot doesn't show any problems at all...

1. So am I ok here? What should I test, if anything, to be sure?
2. Is there anything I should have done differently?
3. Why is the drive listed as ada1p2 instead of its gptid? Can and/or should I fix it?

</TLDR>

I have been having ada1: corrupt or invalid GPT detected. for a while now. I tried recover on multiple occasions without success. Skipping ahead, I tried upgrading a HighPoint RocketRaid 1640 (PCI) with a HighPoint RocketRaid 2220 (PCI-X in a PCI-X slot). FreeNAS generated all kinds of errors and timeouts accessing any drive connected to it. I did some research, but not a bunch. I tried the card in an Ubuntu box with similar results. Maybe it's the card....

Anyway, ada1 just so happened to one of the drives attached to the new card. I have reverted to the previous working hardware config (nothing else changed), but now ada1 is barely recognized by the system:

Code:

grep ada1 /var/log/messages
Mar 15 14:13:10 cobalt ada1 at ata3 bus 0 scbus1 target 0 lun 0
Mar 15 14:13:10 cobalt ada1: Serial Number xxxxxxxx
Mar 15 14:13:10 cobalt ada1: 100.000MB/s transfers
Mar 15 14:13:10 cobalt ada1: 1430799MB (2930277168 512 byte sectors)
Mar 15 14:13:10 cobalt GEOM: ada1: corrupt or invalid GPT detected.
Mar 15 14:13:10 cobalt GEOM: ada1: GPT rejected -- may not be recoverable.

<This is where I replaced the disk in the gui with the existing disk>
Mar 15 14:33:11 cobalt GEOM: ada1: corrupt or invalid GPT detected.
Mar 15 14:33:11 cobalt GEOM: ada1: GPT rejected -- may not be recoverable.
Mar 15 14:33:11 cobalt notifier: dd: /dev/ada1: short write on character device
Mar 15 14:33:11 cobalt notifier: dd: /dev/ada1: end of device

Code:

  pool: vol250x8
 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 Thu Mar 15 14:12:51 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		vol250x8										DEGRADED	 0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/e91da02e-8f3e-11e7-acc3-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/8ac0a1cb-8f3e-11e7-acc3-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/4eb11777-94f6-11e7-97f0-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/bbbb5823-8f9a-11e7-b9cd-0024817b9c4a  ONLINE	   0	 0	 0
		  raidz2-1									  DEGRADED	 0	 0	 0
			13858242310574651614						UNAVAIL	  0	 0	 0  <cont.>
   was /dev/gptid/2725ca3e-3817-11e7-8768-00400510e336
			gptid/38fca8e5-3845-11e7-aaa2-00400510e336  ONLINE	   0	 0	 0
			gptid/9cf019e0-3826-11e7-b8d8-00400510e336  ONLINE	   0	 0	 0
			gptid/429b5349-3839-11e7-b829-00400510e336  ONLINE	   0	 0	 0

I attempted to replace it via the gui, which i really didn't think would work:

Code:

Exception Type: MiddlewareError at /storage/zpool-vol250x8/disk/replace/13858242310574651614/
Exception Value: [MiddlewareError: Disk replacement failed:   <cont.>
"cannot open 'gptid/14a830fb-2890-11e8-b895-0024817b9c4a':   <cont.>
no such GEOM provider, must be a full path or shorthand device name, "]

But now it shows that its ok?

Code:

  pool: vol250x8
 state: ONLINE
  scan: resilvered 4K in 0 days 00:00:01 with 0 errors on Thu Mar 15 14:33:25 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		vol250x8										ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/e91da02e-8f3e-11e7-acc3-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/8ac0a1cb-8f3e-11e7-acc3-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/4eb11777-94f6-11e7-97f0-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/bbbb5823-8f9a-11e7-b9cd-0024817b9c4a  ONLINE	   0	 0	 0
		  raidz2-1									  ONLINE	   0	 0	 0
			ada1p2									  ONLINE	   0	 0	 0
			gptid/38fca8e5-3845-11e7-aaa2-00400510e336  ONLINE	   0	 0	 0
			gptid/9cf019e0-3826-11e7-b8d8-00400510e336  ONLINE	   0	 0	 0
			gptid/429b5349-3839-11e7-b829-00400510e336  ONLINE	   0	 0	 0

errors: No known data errors

 

[dlavigne]

Were you able to figure this out?

 

[wombat-fertilizer]

Were you able to figure this out?

no. it seems to be ok but zpool status is the same:

Code:

  pool: vol250x8
 state: ONLINE
  scan: scrub repaired 0 in 0 days 15:46:54 with 0 errors on Sun Apr 15 16:46:58 2018
config:

		NAME											STATE	 READ WRITE CKSUM
		vol250x8										ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/e91da02e-8f3e-11e7-acc3-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/8ac0a1cb-8f3e-11e7-acc3-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/4eb11777-94f6-11e7-97f0-0024817b9c4a  ONLINE	   0	 0	 0
			gptid/bbbb5823-8f9a-11e7-b9cd-0024817b9c4a  ONLINE	   0	 0	 0
		  raidz2-1									  ONLINE	   0	 0	 0
			ada1p2									  ONLINE	   0	 0	 0
			gptid/38fca8e5-3845-11e7-aaa2-00400510e336  ONLINE	   0	 0	 0
			gptid/9cf019e0-3826-11e7-b8d8-00400510e336  ONLINE	   0	 0	 0
			gptid/429b5349-3839-11e7-b829-00400510e336  ONLINE	   0	 0	 0

 

[Rob Townley]

Are your scrubs catching anything?