Gragorg

You could always try another plex container like the one from linuxserver which is the most popular one. Just to clarify your mapping. Do you have a Tv and Movies directory in a share called data like this /data/media/movies/(files stored here?) or is the actual media in the media folder /data/media/(files stored here?)

Read errors wont break parity only write errors. If you want one of the experts to look at your drive post your diagnostics. Although Current pending sectors is usually not good.

Try and boot in safemode with gui. Looks like disklocation plugin is causing an issue.

Not sure if the picture of your array is old from August or not. If your drive is passing extended SMART and has been stable. You can hit the "CLEAR STATS" button on the main tab to flip your drive back to showing healthy (thumbs up). That way you will get the thumbs down again if the problem happens again.

1. I would preclear both drives that way it will confirm that you dont have any connection issues or a disk that is DOA. After success full preclear add them to the array. Your parity sync will start after you add them. One parity drive allows you to have one bad drive and recover it. Keep in mind parity is not a backup. 2. Under the shares tab you can determine where your data goes by setting the split level. Hit the ? in the top right hand corner of the screen to read up about your split level choices. 3. Yes always backup critical files

Under your plex settings go to " remote access" does it show enabled? By default it uses Upnp to open a port if your router supports it and it is enabled. If you have "manually select a public port" selected than you need to forward that port in your router to your new plex server.

If you are using ZFS Master plugin try setting "Refresh interval" to "no Refresh"

Thank you for all your work. Upgrade from 6.12.13 went smoothly.

You appear to have a cabling issue on ATA3 (ST2000DM008-2UB102). Check/replace cables and try again.

You could try the unassigned devices plugin from the app store.

So I uninstalled erased my appdata. Re installed and restored from backup and seem to be all up to date with the exception of Node.js which is running 18.17.1. I don't seem to have issue with that and I have till April till its not supported. Out of curiosity what version of Node.js are you running?

I get this in my log when I restart Homebridge [11/21/2024, 4:39:17 PM] [Homebridge UI] Running Command: sudo -E -n npm install -g [email protected] [11/21/2024, 4:40:11 PM] [Homebridge UI] Error: Operation failed with code 217. You can download this log file for future reference. See https://github.com/homebridge/homebridge-config-ui-x/wiki/Troubleshooting for help.

Did you update within the GUI?

Has anyone been able to update Homebridge to version 1.8.5 from 1.8.1? I get an error when I try to.

Add your diagnostics for the gurus.

Just go into the plugin on the configuration tab and pick any boxes to be displayed from "Visible Frontpage Information" be sure to save to take effect.

My dashboard is back. It looks like by drive data is there under information but they show blank on the tray screen.

Was this you? Oct 26 16:42:52 Erebor webgui: Successful login user root from 68.49.155.148

Agreed

Yes this update also killed my dashboard and wont let me look in the plugin settings. Is there any way to roll back a plugin?

How do I fix missing channel logos?

Has anyone notice the "More Info" that takes you to the docker hub is broken?

Nothing really obvious in there. The only thing I noticed is you are using a depreciated OVPN file. Should be 256 not 128 you should download the updated files from PIA. PIA can use wireguard instead of OVPN if you change the it in the template. It is also much faster than OVPN. It wasn't and option when Spaceinvader made that video. If it doesn't work you can always change it back. It will at least rule out an OVPN problem. You can also temporarily set VPN_ENABLED to 'no' to rule out all vpn issues. Be aware that any torrents that are currently in deluge will start without VPN. The kill switch in the container seems to be the most common issue. You should also post this to Binhex support forum as he provides excellent support for his containers.

You likely have an issue connecting to your end point which will not allow you to go to gui. This post would be best in support channel for delugevpn. If you restart Deluge-VPN you can look at the log for the conntainer and you should see the error or connection that is stopping you. One thing you could try in the docker template is change "Container Variable: VPN_CLIENT" to wireguard.

Looks like your files may be corrupted. Have you tried putting you USB into a windows computer and see if it detects errors? Do you have a backup?