markc99

Looks like it's finished... Restarted array in normal mode, and the disk is back! Thank you everyone.

I got this:

The filesystem type is set to xfs though, so I'm not sure what's going on with btrfs...

Sometime last night, when attempting to play some TV from my Plex server, I noticed my libraries were missing. I checked the server, and somehow it was powered off... It wasn't power related as I have a UPS, and we never lost power. I'm thinking some other "failure" or a cat walked on the power button of my server. 🤷‍♂️ Regardless, I brought the server up, started up the array and one of my disks is unmountable. I saw some other forum posts about this issue, but I wanted to make sure to start a thread about my issue, and not hijack someone elses... I have been seeing odd things with Plex recently, where it will play some media fine for awhile, and then the screen will either freeze, or glitch out, the sound will continue playing, but sometimes I see the video come back, but it's from a totally different media file (show or movie). I was thinking about doing a error check on my drives, but I'm not sure how to do that... Mark tower-diagnostics-20240916-1040.zip

So, I have Unraid USB stick backups... Is that what you are referring to, or Plex container specifically?

Greetings... I had an power outage yesterday, and realized that during some troubleshooting, I had disabled my battery backup on Unraid and forgotten to enable it again... Needless to say, my Unraid server powered off, and now I'm having issues with Plex. I'm using the Official Plex Docker Image, and although I'm able to start Plex, I'm getting the following message in the logs. /config/Library/Application Support/Plex Media Server/Preferences.xml:1.1: Document is empty ^ Failed to load preferences at /config/Library/Application Support/Plex Media Server/Preferences.xml Failed to load preferences at /config/Library/Application Support/Plex Media Server/Preferences.xml /config/Library/Application Support/Plex Media Server/Preferences.xml:1.1: Document is empty ^ Failed to load preferences at /config/Library/Application Support/Plex Media Server/Preferences.xml Failed to load preferences at /config/Library/Application Support/Plex Media Server/Preferences.xml I've googled around, and it seems like some of my options are deleting or renaming the Preferences.xml so it gets rebuilt. Is that the best course of action?

I'm not sure what they are either... I did power off the server and put the two disks experiencing errors on SATA cables attached to the mobo, instead of the SATA card, and it's running a parity check. The interesting thing is it's running WAY faster. It's been running a half an hour, and it's already 10% complete, with 5 or so hours left... The last one that ended up erroring out, was estimated to take almost 2 days. My gut is thinking one of my breakout cables may be going bad.

Attached. tower-diagnostics-20230126-1436.zip

Well, I thought I was in the clear, but I have errors on two disks again. One is brand new, and the other is a bit older. I'm thinking the first step may be to replace the SATA breakout cable. I haven't used any SATA connections on my motherboard however, so maybe I switch them to there to make sure it's the cable? Thoughts?

So far, so good.

Understood. I stopped everything, powered the server off, checked the cables again, and the parity is rebuilding. Finger crossed... Only 1 day and 19 hours to get through without issue.

Running a "read-check" and now I'm chasing errors on another disk. I guess the next step is switching cables around, but it's so odd that it's been multiple disks in the system, and as of now, I haven't changed any of the cables, just reseated them.

New diag attached. This is after I shutdown the server, reseated all the cables and powered it back on. Parity drive is still offline. tower-diagnostics-20230124-1044.zip

Diag uploaded. tower-diagnostics-20230124-0849.zip

I thought the same thing, but when I did the disk swap in the GUI, I didn't open the case. The original "bad" disk is still connected to the same cable it was before, and the new "bad" disk is on the cable which wasn't having problems before... The server currently has my parity disk disabled and is running a "Read-Check". Based on the percentage done, it's probably going to take another day or two.