Hello

 

I think my cache drive has gone bang, or at least is in the process of going bang.
I use it to support my Plex docker.
I discovered that Plex had stopped working last Saturday.
I had a look at UnRaid syslog, and see ATA14 (my cache drive) throwing various errors on boot up.

Q1) can anyone clarify what has happened ??
Q2) can i re-format the cache drive, and continue as normal ??

I'm attaching the Diagnostics.ZIP

Meantime i removed/re-installed Plex, and told it to use one of my data disks for support.
The webgui fires up no problem now, and i'm re-building my libraries.

 

thanks
Richard
 

tower-diagnostics-20241125-1327.zip

Answers to Questions

Q1: Can anyone clarify what has happened?

Your cache drive is either:

Experiencing physical issues (e.g., bad sectors or degraded media).

Facing connectivity issues due to a faulty cable, port, or power connection.

Given the persistent media error and UNC logs, it is likely the drive itself is failing.

 

Q2: Can I reformat the cache drive and continue as normal?

Reformatting may temporarily alleviate issues but is unlikely to resolve underlying hardware failures. If the drive is failing, reformatting won't restore its reliability.

 

looks like sdi is problematic:
 

Findings and Recommendations:

1. Cache Drive (sdi) SMART Report

The SMART report for your cache drive (WDC WD10EACS-00ZJB0) shows significant concerns:

Reallocated Sector Count: 131

Indicates that sectors on the drive have been marked as unusable and replaced with spare sectors. This suggests surface degradation.

Current Pending Sector Count: 21

These are sectors awaiting reallocation but have not yet been successfully rewritten. This indicates unstable sectors.

Offline Uncorrectable Errors: 5

Data could not be read from some sectors during an offline test.

Power-On Hours: 132,330 hours (~15 years of use)

The drive has far exceeded its typical lifespan.

Device Error Log: 45,844 errors recorded, highlighting severe instability.

Conclusion: The drive is failing and should be replaced immediately. It is not reliable for critical tasks like supporting Docker containers or caching frequently accessed data.

Ok, i here ya. 

Thank you for your guidance.