6.4.0 Device is Disabled, Contents Emulated

[neebski]

I've read through several other topics as to why this might be happening. I can run smart tests on the drive so I know its still connected. It just passed a quick smart test and is currently running a long but I wanted to jump on here with the current smart data and see if anyone could tell me what I might be missing.

 

A little bit of background - I just yesterday had to run an xfs_repair -L on my cache disk since it wasn't mounting. It fixed the problem for about 24 hours. I again today had to run it and after I restarted the server this disk is disabled and emulated. PS is there an in depth guide to what all these values mean? If so it would really help my troubleshooting. 

 

1	Raw read error rate	      0x000f	113	100	006	Pre-fail	Always	Never	52351040
3	Spin up time	          0x0003	092	091	000	Pre-fail	Always	Never	0
4	Start stop count	      0x0032	098	098	020	Old age	Always	Never	2555
5	Reallocated sector count  0x0033	100	100	010	Pre-fail	Always	Never	0
7	Seek error rate	          0x000f	085	060	030	Pre-fail	Always	Never	14170308924
9	Power on hours	          0x0032	076	076	000	Old age	Always	Never	21026 (2y, 4m, 22d, 2h)
10	Spin retry count	      0x0013	100	100	097	Pre-fail	Always	Never	0
12	Power cycle count	      0x0032	100	100	020	Old age	Always	Never	276
183	Runtime bad block	      0x0032	100	100	000	Old age	Always	Never	0
184	End-to-end error      	  0x0032	100	100	099	Old age	Always	Never	0
187	Reported uncorrect	      0x0032	100	100	000	Old age	Always	Never	0
188	Command timeout           0x0032	100	087	000	Old age	Always	Never	28 28 32
189	High fly writes	          0x003a	097	097	000	Old age	Always	Never	3
190	Airflow temperature cel	  0x0022	071	051	045	Old age	Always	Never	29 (min/max 20/29)
191	G-sense error rate	      0x0032	100	100	000	Old age	Always	Never	0
192	Power-off retract count   0x0032	100	100	000	Old age	Always	Never	5
193	Load cycle count	      0x0032	042	042	000	Old age	Always	Never	116710
194	Temperature celsius	      0x0022	029	049	000	Old age	Always	Never	29 (0 17 0 0 0)
195	Hardware ECC recovered 	  0x001a	113	100	000	Old age	Always	Never	52351040
197	Current pending sector	  0x0012	100	100	000	Old age	Always	Never	0
198	Offline uncorrectable	  0x0010	100	100	000	Old age	Offline	Never	0
199	UDMA CRC error count	  0x003e	200	200	000	Old age	Always	Never	4
240	Head flying hours	      0x0000	100	253	000	Old age	Offline	Never	15740h+33m+42.387s
241	Total lbas written	      0x0000	100	253	000	Old age	Offline	Never	69635711756
242	Total lbas read	          0x0000	100	253	000	Old age	Offline	Never	743699718438

 

neberserv1-diagnostics-20180308-2025.zip

[trurl]

SMART for all disks looks OK. Nothing in the syslog since you rebooted. Either connection, cable, maybe controller. Check connections. You will have to rebuild the disk, either to another disk (saving the original just in case) or rebuild to the same disk.

 

unRAID disables a disk when a write to it fails. When the disk is disabled, unRAID will not use it. Instead, it emulates the disk from all the other disks using the parity calculation. The failed write, and any subsequent writes to the disk, are used to update parity. So the array has the valid data, but the disk data is now invalid and out-of-sync with parity, so it must be rebuilt from the parity calculation. Since you only have one parity, the array is unprotected until the disk is rebuilt.

 

A couple of links for you:

 

https://en.wikipedia.org/wiki/S.M.A.R.T.#Known_ATA_S.M.A.R.T._attributes

 

https://lime-technology.com/wiki/Troubleshooting#What_do_I_do_if_I_get_a_red_X_next_to_a_hard_disk.3F

[neebski]

Thanks @trurl I did as instructed and it worked great until this morning. I must have some sort of hardware issue with the cables or controller. Will have to troubleshoot further.