Preclear went fine, no SMART Errors, but 1 read error in Parity Rebuild and Parity Disk disabled. Fluke?

[RealActorRob]

It's a 4TB I've run other tests on and all turned out fine. I replaced my working 3TB Parity 2 drive for future upgrades. So, this drive got x'd during a rebuild of parity onto it.

 

Drive is in a disk tray on a server, so I doubt this is a 'cable' issue.

 

Preclear went normally.

 

Rebuild had 1 read errors but the SMART doesn't show ANY read errors or fails. 

 

 

running another preclear now and an extended test now. A short time ago, 800 hrs, this also passed an extended.

 

 

Diags attached. 

 

Thoughts?

 

To sum: other than the 1 read error on the parity rebuild, I don't see ANY indication of drive problems.

 

I'm sure this is an ex-data center drive, noting the power on hours vs. power cycle count.

 

blacktower-diagnostics-20211213-1224.zip

Edited December 13, 2021 by RealActorRob

[JorgeB]

Syslog is full of spam, and because of that the error from the rebuild is missing.

[trurl]

30 minutes ago, JorgeB said:

Syslog is full of spam

Why is this in your syslog several times per minute?

Dec 13 05:45:04 BlackTower vsftpd[24338]: connect from 192.168.1.105 (192.168.1.105)

 

[RealActorRob]

1 minute ago, trurl said:

Why is this in your syslog several times per minute?

Dec 13 05:45:04 BlackTower vsftpd[24338]: connect from 192.168.1.105 (192.168.1.105)

 

It's from Automounter, which helps keep SMB shares from dropping and/or it's a discovery of services from same. It's helped with my SMB issues doing backups on Mac OS X Mojave.

 

[RealActorRob]

Found this on the device page under SMART log: 

 

ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 54381 hours (2265 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 08 70 c9 a5 02 Error: IDNF Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 2f 00 01 10 00 00 00 00 3d+07:43:39.996 READ LOG EXT 60 20 08 e8 93 6d 40 00 3d+07:43:39.996 READ FPDMA QUEUED 60 00 00 e8 8f 6d 40 00 3d+07:43:39.996 READ FPDMA QUEUED 60 b0 00 38 8c 6d 40 00 3d+07:43:39.991 READ FPDMA QUEUED 60 00 00 38 88 6d 40 00 3d+07:43:39.986 READ FPDMA QUEUED

 

 

[trurl]

Diagnostics already contains SMART report for all attached disks.

 

6 minutes ago, RealActorRob said:

It's from Automounter, which helps keep SMB shares from dropping and/or it's a discovery of services from same. It's helped with my SMB issues doing backups on Mac OS X Mojave.

 

I think your workaround is more trouble than its worth.

[trurl]

Don't really see why it should be using FTP for that anyway. Also, its recommended that you disable builtin FTP on Unraid.

 

Maybe some other workaround that doesn't spam syslog?

 

 

[RealActorRob]

15 minutes ago, trurl said:

Don't really see why it should be using FTP for that anyway. Also, its recommended that you disable builtin FTP on Unraid.

 

Maybe some other workaround that doesn't spam syslog?

 

 

It wasn't, and I turned FTP off. It had no users enabled and firewall wasn't opened so it was pretty secure, but, one less thing. 

 

Thought I'd turned off FTP already...might have been doing something with it and forgot to re-disable.

 

I also turned off the mover log, since mover isn't having issues ATM to reduce log file size.

 

Edited December 13, 2021 by RealActorRob

[RealActorRob]

I'm doing a preclear at the same time as an extended test, which should hammer this drive pretty well.

[RealActorRob]

1 hour ago, JorgeB said:

Syslog is full of spam, and because of that the error from the rebuild is missing.

 

Will be doing another one if the drive passes another preclear or two and the extended SMART test passes. 

 

I have a WD Red CMR NAS on order to replace it.

 

Edit: Seagate Ironwolf NAS was a little cheaper and a little higher rated, review-wise.

 

 

Edited December 13, 2021 by RealActorRob