Requesting help on how to delete files and replace drives so that pool is no longer degraded

[wdockery]

Hello, I am a FreeNAS novice/intermediate user; I am using FreeNAS currently as a hobby while I learn, moving toward becoming a knowledgeable user, at which point I will start using it for mission-critical data. None of the involved data is mission-critical. I do not have a pool backup.

And I am dealing with my first degraded pool incident.

My hardware is listed in my signature. It's currently lousy (non-ECC RAM, etc), but I will improve it as funds allow.

I would like to know i) whether it would be helpful to delete the files with permanent errors (they are non-essential), ii) when during this troubleshooting episode I should replace the faulty drive, iii) whether my post content and formatting passes muster; and iv) anything else I should be thinking about.

I am trying to figure out the best sequence of events to get my pool into a non-degraded state.

I have a few new unopened drives ready to deploy as needed.

Thanks for guidance--

Code:

System Information
Hostname freenas.local Edit
Build FreeNAS-9.2.1.8-RELEASE-x64 (e625626)
Platform Intel(R) Celeron(R) CPU 1037U @ 1.80GHz
Memory 8068MB
System Time Thu Dec 14 07:22:30 CST 2017
Uptime 7:22AM up 16 days, 59 mins, 1 user
Load Average 0.20, 0.05, 0.02

Code:

[root@freenas] ~# zpool status -xv

  pool: volume1

 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: scrub repaired 16.3M in 323h51m with 125 errors on Wed Dec 13 10:43:57 2017

config:


	NAME											  STATE	 READ WRITE CKSUM

	volume1										   DEGRADED	 0	 0   250

	  raidz2-0										DEGRADED	 0	 0   500

		11251471821030809670						  UNAVAIL	  0	 0	 0  was /dev/gptid/79307d99-4e84-11e4-aaf8-b8975a5fd7e1

		gptid/79bde2c5-4e84-11e4-aaf8-b8975a5fd7e1	ONLINE	 250	 0	 0

		gptid/7a449a4b-4e84-11e4-aaf8-b8975a5fd7e1	ONLINE	   0	 0	 0

		replacing-3								   DEGRADED	 0	 0	 0

		  1995896866767123387						 UNAVAIL	  0	 0	 0  was /dev/gptid/7acdbff2-4e84-11e4-aaf8-b8975a5fd7e1

		  gptid/1140c6f2-d30f-11e7-a870-b8975a5fd7e1  ONLINE	   0	 0	 0

		  gptid/7a883fb6-d30f-11e7-a870-b8975a5fd7e1  ONLINE	   0	 0	 0


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


		/mnt/volume1/appleset/Retrospect/LaptopsToFreeNAS/1-LaptopsToFreeNAS/AA010299.rdb

		/mnt/volume1/appleset/Retrospect/LaptopsToFreeNAS/1-LaptopsToFreeNAS/AA010300.rdb

		/mnt/volume1/appleset/Retrospect/LaptopsToFreeNAS/1-LaptopsToFreeNAS/AA010301.rdb

		/mnt/volume1/appleset/Retrospect/LaptopsToFreeNAS/1-LaptopsToFreeNAS/AA010303.rdb

		/mnt/volume1/appleset/Retrospect/LaptopsToFreeNAS/1-LaptopsToFreeNAS/AA010306.rdb

[root@freenas] ~# 

 

[danb35]

whether it would be helpful to delete the files with permanent errors

Not really. I mean, yes, eventually you'd want to, but they aren't getting in the way of your pool rebuilding.

whether my post content and formatting passes muster

Mostly, though I think the indenting got broken on your zpool status output, which makes it a little hard to figure out what's going on there.

when during this troubleshooting episode I should replace the faulty drive

As soon as possible, really, especially if you have a spare SATA port you can connect the replacement to without removing the drive first. Right now it looks like you have one drive offline, one drive showing lots of errors, and a third drive in the process of being replaced.

 

[rs225]

Looks fatal to me, unless you get that drive that is unavail back online.

 

[Chris Moore]

I'm curious about how the pool got so far gone before corrective action was initiated?

Sent from my SAMSUNG-SGH-I537 using Tapatalk

 

[tvsjr]

It's not worth the time and effort to fix it... take a backup, destroy/rebuild the pool, recover the data.

I would be extremely concerned about hardware issues - like a flaky PSU (Rosewill sucks), bad SATA power splitters, etc. Drives might fail... but multiple drives going unavailable often points to a bigger hardware concern.

I share Chris' concerns as well... how did you get to this point? Was SMART checking enabled? Did you have the system properly configured to send you alert emails? It's highly doubtful 3 drives failed at once... so either something weird happened or the system has been degraded for a while.