markc99

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.

So, I was able to build a new config, remove a data drive, and replace the erroring Parity disk with it. It got probably 8 hours through a rebuild, and now the NEW parity drive is doing the same thing. The new data drive was already pre-cleared, and only has a month or two of service so far. I'm perplexed as to what to do next.

I'm having errors on my parity drive, and it keeps going disabled. I've tried resetting it, and running through another parity check, and its not helping... I have at least two data drives which aren't being used yet, and I thought I would be able to shrink the array to pull a data drive out to be able to replace the parity drive, but I can't figure out how to do it. I've googled around, and not able to find the right answer. Could someone point me in the right direction? I'm running Unraid 6.11.5. Mark

After enabling Pi-hole on my network, and distributing DNS settings via my router, I'm getting a Privacy Warning on my Wifi network, and some iphones are saying they need to turn off Private Relay. I saw there is a way to fix that by disabling something in the config. I was wondering if there is something different I need to do in the docker config since I'm not running this on a Raspberry.

So, I powered everything off and sure enough, the drive with read errors was on SAS Cable 1, Port 2, which I feel like I had problems with before. I had a free Port on the other SAS cable, so I swapped it to that and booted everything up. Ran an SMART test on that drive and it passed. Followed the instructions in another thread about unassigning the drive, starting the array and then stopping and reassigning the drive to kick off rebuild. That is running and I'll report back on my results.

I had my server on my desk while I was configuring it, today since everything seemed fine, moved it to my network closet and booted everything back up. Even though I used the shutdown command before moving it, it came up and said Unclean Shutdown Detected. I started the array and it kicked off a parity check. The last one completed fine, without errors. Now I'm getting read errors on a disk, and it disabled it. My gut tells me it's probably a loose connection to my SAS card. I was going to power it down again and reseat/check all the connections. Is there a way to re-enable the drive? tower-diagnostics-20220201-0923.zip

I replaced the disk and everything came up clean. I really appreciate all the help!

In browsing Disk1 with midnight commander, the only thing on there now is two empty media folders, and the libvert.img and docker.img. I was actually going to move those two off to a cache pool anyway, so Disk1 is essential empty as this point.

Here you go. I stopped and started the array and as an FYI, it came up and said "Array turned good...0 disks with read errors." Thanks again, Mark tower-diagnostics-20220129-1618.zip

The copy did finish, and then I got a notification that all the pending sectors went away. My new disk arrived today, so I'm ready to swap. Is it just a matter of switching them at this point?

Roger that, I'll keep an eye on it. Thanks for all the help.

Thanks for that! I'm running a copy from Disk1 to Disk3 now, hopefully the damage isn't too bad. Once the copy is complete, what are the next steps? Am I able to offline that drive until the replacement arrives on Monday, and then just swap them?

Greetings, built my Unraid server this past weekend, and spent a lot of time moving all my files off an aging QNAP. Finally got everything moved, and then decided I need to switch around the folder structure a tiny bit, so I was moving media files from one directory to another, and got a bunch of notifications about one of my drives reporting errors. It's the drive where the majority of my files are sitting at the moment. I did setup parity and it finished syncing last evening. Is it as easy and powering off and pulling the drive and letting parity rebuild the files on the other drives, or should I attempt to move them myself? I did order a new 4 TB Ironwolf, but it won't be here until Monday. Hardware: Unraid 6.9.2 Intel i5 10400 16 GB DDR4 RAM Gigabyte B560 HD3 (4) 4 TB Seagate Ironwolf NAS Drive (1) 3 TB Seagate Barracuda Drive (1) 2 TB WD Red NAS Drive (1) 1 TB Seagate Barracuda Drive (1) 256 GB Crucial SSD (1) 1 TB Sandisk SSD tower-diagnostics-20220128-1111.zip