Hi all,

 

I'm experiencing quite a bit of frustration with one of my drives in my array. Every 24-48 hours or so, when i go to my main dashboard, one of my drives shows a * for temperature and its data is inaccessible. When I boot the array into maintenance mode, I can do a filesystem check and repair, which results in a mountable drive with my data still present. After running the extended SMART test, everything came back as good and all of my pre-fail and old age indicators are clean. Not sure if its UnRaid or one of my docker applications causing this issue, but it's definitely worrying.

 

Thanks in advance

 

 

 

 Here's my current attributes and attached smart report, and diagnostics report

tower-smart-20210922-1610.zip

tower-diagnostics-20210922-1803.zip

Edited September 22, 20214 yr by imFrankis
Added Diagnostics ZIP file

Looks like you rebooted before getting diagnostics so syslog restarted and can't see anything that happened before that. If it happens again be sure to get diagnostics before rebooting. Or setup syslog server so you can get saved syslogs to post.

Will do, thank you

 

Here's a newtower-diagnostics-20210923-1444.zip log, the error occurred on my system at 0212, still trying to figure out this issue.

Sep 22 16:28:46 Tower kernel: ata1.00: ATA-9: WDC WD120EDAZ-11F3RA0, 5PH3E2VD, 81.00A81, max UDMA/133
Sep 22 16:29:05 Tower kernel: md: import disk4: (sdb) WDC_WD120EDAZ-11F3RA0_5PH3E2VD size: 11718885324 

Sep 23 02:01:13 Tower kernel: ata1.00: exception Emask 0x50 SAct 0x8000 SErr 0xb0802 action 0xe frozen
Sep 23 02:01:13 Tower kernel: ata1.00: irq_stat 0x00400000, PHY RDY changed
Sep 23 02:01:13 Tower kernel: ata1: SError: { RecovComm HostInt PHYRdyChg PHYInt 10B8B }
Sep 23 02:01:13 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Sep 23 02:01:13 Tower kernel: ata1.00: cmd 60/00:78:d0:d3:3c/01:00:84:01:00/40 tag 15 ncq dma 131072 in
Sep 23 02:01:13 Tower kernel:         res 40/00:00:d0:d3:3c/00:00:84:01:00/40 Emask 0x50 (ATA bus error)
Sep 23 02:01:13 Tower kernel: ata1.00: status: { DRDY }
Sep 23 02:01:13 Tower kernel: ata1: hard resetting link

and lots more like that.

 

Check connections, SATA and power, both ends, including splitters. Try another cable.

I'll check connections and replace all the sata cables to be safe. Any other known causes for this? only running 4 drives and all plugged direct into the MB

1 hour ago, imFrankis said:

Any other known causes for this?

Some controllers. Looks like you have 2 different controllers but I think they are both OK.

So just in case anyone has the same issues, I did some diagnosis over the weekend. The drives I'm currently using are shucked white label WD drives from Easy Store units. These units require one of two things to power on, either a 3rd pin (3.3v power) modification where this pin is covered in tape to prevent it making contact with the connector, or the use of a molex to sata connector. 

 

I opted for the prior, as I did not have a molex to sata adapter on hand. Upon taking all the drives out of the system, one of the three 12tb drives had the tape slide partially off of that connector, causing intermittent power and thus the drive to disconnect abruptly. Not quite sure how this would happen out of the blue, but none the less if you opt for this modification, double check the tape if you have any issues.

 

Thanks for the help trurl!