I have been running along fine for the last while. I did have some issues after installing a WD 6TB Red drive as parity as I started getting 128 errors on each parity check, but after booting into Xen mode and having a clean parity check and then booting back into standard mode everything seemed fine.

 

I saw someone else on v5.0 post an issue with WD 6TB drives so thought I would check mine since it had been a while (and I hadn't checked since the 1st of the month when the parity check should kick off).

 

When I first looked at the screen it showed 128 write errors again, which was odd. After refreshing the screen (it had been idle but open the last couple of days), I see that the parity disk is red-balled and offline, and the syslog is full of read/write errors.

 

Can someone please review the attached syslog and provided a recommended path. I don't know if I should just stop the array, and re-add the parity drive, or if the drive is bad, and I should replace it.

 

Under UnMENU the drive does not show up in SMART history. If I look in the folder on the USB drive the data for that disk is dated Oct 7th, but is error free:

 

2014-10-06	querytime	1412641039
2014-10-06	health	PASSED
2014-10-06	ATA_Error_Count	
2014-10-06	Raw_Read_Error_Rate	0 
2014-10-06	Spin_Up_Time	8716
2014-10-06	Start_Stop_Count	13
2014-10-06	Spin_Retry_Count	0 
2014-10-06	Calibration_Retry_Count	0 
2014-10-06	Power_Cycle_Count	3
2014-10-06	Reallocated_Sector_Ct	0 
2014-10-06	Seek_Error_Rate 	0 
2014-10-06	Temperature_Celsius	22
2014-10-06	Reallocated_Event_Count	0 
2014-10-06	Current_Pending_Sector	0 
2014-10-06	Power_On_Hours	244
2014-10-06	Offline_Uncorrectable	0 
2014-10-06	UDMA_CRC_Error_Count	0 
2014-10-06	Multi_Zone_Error_Rate	0 
2014-10-07	querytime	1412691731
2014-10-07	health	PASSED
2014-10-07	ATA_Error_Count	
2014-10-07	Raw_Read_Error_Rate	0 
2014-10-07	Spin_Up_Time	8733
2014-10-07	Start_Stop_Count	14
2014-10-07	Spin_Retry_Count	0 
2014-10-07	Calibration_Retry_Count	0 
2014-10-07	Power_Cycle_Count	3
2014-10-07	Reallocated_Sector_Ct	0 
2014-10-07	Seek_Error_Rate 	0 
2014-10-07	Temperature_Celsius	23
2014-10-07	Reallocated_Event_Count	0 
2014-10-07	Current_Pending_Sector	0 
2014-10-07	Power_On_Hours	258
2014-10-07	Offline_Uncorrectable	0 
2014-10-07	UDMA_CRC_Error_Count	0 
2014-10-07	Multi_Zone_Error_Rate	0 

 

Any suggestions would be appreciated.

syslog.zip

I've tried rebooting the server, and it sees the parity drive as a new drive. I have it building parity and so far (10%) it seems to be going okay, but I would appreciate it if someone could review my syslog and provide some thoughts on whether I should be replacing the drive, or if there is anything else that should be done to diagnose the issue.

 

I figured once parity is built I could run some SMART tests to see if anything is reported. However, after rebooting I checked smartstatus and it still shows no errors on the disk, so I am hoping the disk is physically okay.

I saw a post recently that there was some issue with the 6TB disks and spin down.  I think they disabled spin down on the 6tb drives, and the problem seemed to go away. 

Yes, I was reading that as well. It was actually that users issues with the 6TB Red that prompted me to double-check mine since I had had issues previously. I can try something similar, but want to make sure there is no other issues present. My syslog shows a TON of read/write errors after starting the server up on Oct 31st, but it had been fine for a month or more before that, even with the server being rebooted several times. It's just strange that on this boot things went to crap and it got to a point that UnRAID saw the drive as invalid and red-balled it, however on reboot life is back to normal (or so it appears so far).

Are you running under Xen or non-Xen?

Non-Xen. I originally had an issue where the 6TB disk would report errors and every parity check would do the same (http://lime-technology.com/forum/index.php?topic=35689.0), and when booting into Xen mode these issues went away. I rebooted back into non-Xen mode and everything was fine again, so I've left it that way.

 

I had thought about going back into Xen mode to test, but will see the results of the current parity build first. As Jonp noted at the time there is no good reason why Xen mode should make a difference, but I know others had reported a better experience under that config.

I would think there would be no difference, but under non-Xen, I can't make it through 1 day without an issue, Xen mode has been rock solid. 

 

Might be temporal logic, but if it works, it works..

 

There is probably nothing LT is doing differently, but I am guessing there is something in the Xen kernel that is handling some issue differently.

 

 

I suppose that's possible, but strange non-the-less as you wouldn't expect adding Xen modules would impact disk interactions.

 

Hopefully LT can figure this out as it's annoying.

I was just looking at adding a few of the 6TB drives, guess I will hold off for now and see what happens...

I am definitely rethinking 6TB at this point. I bought the one to be forward thinking as a parity drive with the expectation that I would be buying only 6TB drives moving forward for data, but I think I will stick with 4TB Reds for a bit until there is higher confidence with the 6TB disks.

I use 2 6's and both are fine. Both went through 60 hours of preclear. It is the unraid mode that seems to make a difference for a lot of people. Boot into xen mode till fixed and see if parity errors go away.

Unfortunately the LT team can't seem to replicate the issue, so it makes it challenging to resolve the issue. I did preclear fine on the 6TB drive too (2 full passes), and other than the hiccups in early Oct it's been running fine until this last weekend. I agree that if the worst case scenario is to run in Xen mode then it's not horrible, but I'd be happier if a resolution could be found.

 

I am 78.4% through a parity build without a single disk error. I will try a parity check in the AM once the build is complete.

 

These random issues are frustrating - however it could always be worse... I could be living life like JustinChase.

 

Sorry Justin...

For what it's worth to those paying attention.... I completed the parity build with 1 error showing on the parity disk. I started a parity check and within 5 minutes showed an additional 128 errors on the parity disk (similar to my issue in early Oct). I've now rebooted into Xen mode and am doing a parity check and everything appears clean.

 

I still don't understand why, but the WD 6TB Red drives behave much better under the Xen config than non-Xen.

 

I guess I am booting into Xen mode for the foreseeable future.