nlash

I'm unable to run DBRepair.sh without forcing the PMS media server to stop manually. The script doesn't seem able to do it for me. Any ideas?

@binhex Sorry, how can I stop the PMS service manually to run the other options in the script? EDIT: Managed to figure it out—kill -15 $(pidof 'Plex Media Server') Thank you for including the script!

Sorry, last questions (hopefully). What's the best sequence of steps to protect the data on the cache from corruption when this happens? I've moved my cache-only shares to the array and I have appdata backups happening nightly. I'm not familiar enough with how the cache pool system works to know what NOT to do in this scenario. Can I simply power down, replace the cable, and scrub?

Getting cache pool errors again after replacing the cable. Pre-reboot diags attached. Any advice is much appreciated. unraidserver-diagnostics-20220925-0750.zip

Got it—thank you for the help. I'll swap the cable and see how it shakes out.

Ah, the reset errors was the step I was missing—thank you. Would sbd dropping offline be due to cables or some other something else?

Just moved everything off of the cache to the array, removed the offending disk, formatted and added back to the cache pool. Cache is still empty. I rebooted and get the errors again. Bad drive?

Yes, cache pool errors on one device.

The last two times I've rebooted, the server has started a parity check and reported cache pool errors upon start-up. The first time was after an OS upgrade (months ago), the most recent time (today) was after a CPU pin reassignment. I have a script that I grabbed from here that does hourly BTRFS checks and reports when it finds them. Nothing was reported since the last time this happened and I rebuilt my pool. I also have monthly BTRFS scrubs scheduled. Diagnostics attached. Any help as to why this is happening would be appreciated. unraidserver-diagnostics-20220825-1704.zip

I actually had it/them as Prefer (when mover wouldn't move) before finally using Unbalance to move everything to the cache. After that, I set it to cache only.

unraidserver-diagnostics-20220119-0938.zip

I just added a second SSD to my existing cache to create a cache pool. Mover moved everything off of cache to the array. I installed the second drive to the pool, formatted. Switching the shares back to Prefer, then running mover yields these errors: I can move things back to the cache manually using Unbalance, but I don't understand why Mover won't do it.

If I wanted to delete the old (pre Home and Hearth update) server world and start fresh, what's the best way to do that?

It was set to "Yes", but I did a No > Apply, then Yes > Apply and it seems to be working. Thanks!

It was working for a while, but now I cannot seem to get remote access working. Port is forwarded. The check passes. It shows that it's connected to the mothership and I've since rebooted the server. Any ideas?