RoninTech

/dev/sdg is now 30% remaining, up from 60%, and the original offender, /dev/sdj is at 90% up from 10%. I'll let them finish and see what the extended tests say.

So neither of the drives are progressing in their smart tests and there's nothing going on with the array. WTH?? EDIT: I've taken the array offline just to see if that helps the tests move along.

So should I have taken the array offline to do this?

Is it my main CPU that runs the self-test or an embedded controller on the drive itself? I kicked off another extended test yesterday on /dev/sdg for which the smartctl output said it should take 587 mins. It is still running almost 24 hours later and says: The original "bad" drive is also still running its test.

Almost 24 hours later and it is still running the test.

I'm positive I pushed the "SMART extended self-test" START button. If/when it finishes, how will I know it's done? Inside the SMART report dump is a line that reads: Its read this for about 3 hours but hopefully this means that the extended test is still running?

Thanks JorgeB. I can now communicate with the bad disk 7 after rebooting. Here are my new diags. Hopefully just a SAS card blip? I used to get more of these years ago but the newer kernels/drivers drastically reduced their occurrence. unraid-diagnostics-20210728-1149.zip

I've attached the diagnostics and am wondering what next? Unfortunately I am a thousand km's away from the machine. Can I just try a reboot and see what happens or do I need to disable all dockers and not do any more writes until I can physically check cables and/or replace the drive? The machine has been running solidly for years. Thanks unraid-diagnostics-20210727-1312.zip

There's a new version of videosort that supports Python3. It fixes the post-processing error I've been getting from videosort.py due to the Python2 deprecation. "git clone https://github.com/nzbget/VideoSort" and then recursively copy the contents to your nzbget scripts folder.

FTL wasn't working either for me which was fixed by writing to the port file. SHIFT+F5 in Brave fixed the display problem for me.

Had to clear my browser cache for the pi-hole and "echo 4711 > /var/run/pihole-FTL.port" in the pi-hole docker console.

Pi-hole was working great with version 5.0. I just updated to version 5.1 and now I see this permanently on the dashboard. Anyone else seeing this? Ad-blocking appears to still be working, so the issue is just a reporting one vs. core functionality.

Thank you for this plugin! Is there a way to access a "Run Script" button via a URL? Would love to add links on our phones that we can trigger with a single press rather than opening a browser, going to the user scripts page and then pressing one.

I use AI Reader on Android and it allows specifying a password when adding an OPDS library as I did for COPS: http://unraid:6060/feed.php. I haven't tried using a password with COPS because my security is via openvpn or ssh tunnels but the underlying tech appears to support it.

Enable ssh tunneling on your unraid box open sshd server. Recent versions all come with sshd baked in. Then forward a firewall port to your unraid server's ssh port which is 22 by default. Then when you ssh into your unraid box from anywhere in the world you use ssh port forward tunnels to access any web interface or other ports like COPS. Might require a bit of googling but it works well and is very secure as ssh is highly encrypted.