FQs19

Sorry. I did know that folders could be excluded. I just don't know Plex's folder structure. Maybe @Dalarielus isn't able to exclude a folder because it has multiple different file types and some of those files are needed in the backup. I'll let Dalarielus continue this discussion.

Since my backup wasn't that large, I've never dug into what files aren't necessary. Of course, being able to exclude folders from backing up would be a great addition.

I use this plugin to backup my Linuxserver Plex Docker to a separate backups share I have on the same unRAID server. I've spent too much time on my Plex metadata to not backup. I also take screenshots of the Plex docker container for reference. This helps if I have to re-install the docker container since some of the settings won't re-populate correctly when re-installing the container from the Previous Apps tab in CA.

I pulled the USB flash drive and edited the boot selection to boot into the GUI. I haven't had time to check to see if I'm able to change boot selection so I'm marking this as solved.

First, thank you KluthR for taking over this plugin. I would love for you to change this setting: "Delete backups if they are this many days old:". For me, this setting is the reverse of what I would like to have. I would prefer to "Keep this many backups:". The reason for this is in this forum post. I had several disk failures and it took me over a month to fix everything, but by that time, my appdata backups had been deleted because I was only keeping 15 days of backups. Even if you just added "Keep this many backups" without removing the current setting, that would be awesome!

My backup, including Plex, is 102GB. I don't exclude any files/folders. I have over 1700 movies in Plex. There's no way I would want to go through an update every poster or some other metadata just to save GB's of space on my server. The whole point of a backup is to backup data, so that you can restore easily and quickly.

The new dynamix stats update did fix the Stats graph from not showing anything, but it broke the CPU stats on the Dashboard page. My CPU dashboard was showing 50% load on my Ryzen Threadripper 3960x. The graph was showing gray bars, which was odd to me, cause the bars are usually colored when usage is that high. I removed the Dynamix Stats plugin and the CPU Dashboard graph went back to the normal load of just 3% when idle.

You were forgetting to start the array after you unassign the old data disk. This commits the change to unraid so that the drive will be emulated. Then stop the array and assign the new data disk. I'm doing the same thing with my server next week. Here is the link to the unraid manual you should follow and the steps I'm taking in my dual parity setup: unRAID Storage Manual Parity Upgrade Section 1. Preclear new disks 2. Make backups of flash drive, dockers, VM'S, and appdata. 3. Take screenshots of Disk Assignments and Shares. 4. Run a Parity Check. Verifying 0 sync errors. 5. Disable Dockers and VM's. 6. Disable Mover and any other scheduled tasks. 7. Turn off auto-start for array. 8. Stop array and unassign parity disks. 9. Power down server. 10. Remove parity disks and store in safe place until parity is built on new disks. (In case you lose a data drive in the process) 11. Install new parity disks. 12. Start server. Verify new disks are the correct ones by looking at serial numbers. 13. Assign new disk/s to Parity slot/s. (Unraid suggests to replace one parity disk at a time, in dual parity, which will keep the array in a protected state during parity build). I will be replace both parity disks at the same time to save time. 14. Start array in maintenance mode (so nothing can be written to array while building parity) or normal mode (to access data while building parity). 15. Wait for parity build to finish. Then reboot server to verify unraid boots correctly, with all the correct disk assignments. Data Upgrade Section 16. Start array. Verify all your data is still there. 17. Take another set of backups and screenshots (same as in Parity section). 18. Stop array. Unassign data disk to be replaced. 19. Start array to commit change to unraid. You may have to check a box at the bottom of the page stating that disk will be emulated. (Necessary to start array for missing disk to be emulated). 20. Stop array and power down server. 21. Remove the data disk you just unassigned and keep safe until data is rebuilt onto new disk. 22. Install new data disk. (You can now use the old parity disk since your server has built parity on the new parity disks). 23. Start server and verify new data disk is shown by looking at the serial number. 24. Assign the new data disk to the empty slot you created when you removed the old data disk. 25. Start array. (You may need to check a box at the bottom of the page stating that unraid will rebuild the data on the new disk using parity). 26. Once the data disk is rebuilt, verify all your data is there. 27. Reboot your server to verify there are no issues and all data is still there after starting the array. 28. Take new backups and screenshots of everything for future use. 29. Change settings back to normal, like array auto start, re-enabling dockers, VM's, Mover, etc. Enjoy your larger array!

It would help if I actually started my array. Attached is the diagnostics after starting my array and running the first script with Run then Run in Background. Here's the output of "cat /etc/cron.d/root": threadripper19-diagnostics-20221107-2020.zip

I'm having an issue with my scripts not showing the logs after clicking on Run Script. The logs will show after clicking on Run in Background. I believe my NTP server settings weren't correct. I fixed that, but I still can't get two of my scripts to work at all. Could anyone tell me what is going on? Here are the two scripts I need help with: -first "arraycache errors": -second "plexcache errors": Here's the output of "cat /etc/cron.d/root": I'm also attaching my unRAID diagnostics for your review. Any help is appreciated. Thanks threadripper19-diagnostics-20221107-2014.zip

I just installed this update and for the first time, since I was on 6.9.2, it worked! Thank you both, @jbartlett and @IZSkiSurfer, for working together on fixing the issue. I'm sorry I wasn't able to help besides saying it wasn't working for me. Cheers! Also, here's the logs from the working DiskSpeed docker on my 6.11.1 unRAID.

I've got 64GB. HyperX Predator Black 4x16GB 3333MHz

I'm still unable to get this plugin to work just like @IZSkiSurfer Looking forward to getting it working again. Here's the error from the webgui: Here's the logs from DiskSpeed:

I was able to get my Plex docker to work after updating unRAID to 6.11.1. After rebooting my server for the 6.11.1 update, I had to go into the nvidia drive plugin page and update & download the driver, then reboot my server again. Once I did all that, I started my Plex docker and it worked perfectly.

Hi all. I'm having a problem updating unRAID from 6.10.3 to 6.11.1. After doing the unRAID update, I get the following error: The first time I tried to update unRAID, I rebooted and started the array. My Plex docker didn't start, so I tried to start it and it errored out, then the docker became abandoned. I restored unRAID back to 6.10.3 from my backup and restored my Plex docker. I tried updating unRAID to 6.11.1 again and got the same Nvidia Driver plugin error. Has anyone else gotten this error? This time I will try going into the Nvidia plugin settings page, after rebooting for the update, and updating the plugin. Hopefully that's all it takes. I've attached my diagnostics file for your review. Any help is appreciated. threadripper19-diagnostics-20221102-1728.zip

I haven't even tried to install that plugin again. Hopefully you can figure out what is going on. Goodluck.

Driver Update Notification now works! Thank you for the quick fix and help.

AHHH... Sorry, I just expected there to be a Save button. The Update & Download button seemed like it was going to download and update even I was already up to date. I clicked Update & Download and it saw that I was already on the Production branch and just finished without updating. The Production Branch is also now selected. Thanks for the help.

Glad to see its not just me. About the Select Preferred Driver Version, I don't want it to keep updating to the latest, which is why I'm trying to select the Production Branch and not Latest Production Branch. Unfortunately, I'm unable to keep the Production Branch selected.

This plugin hasn't been working normally for a month on my server. I noticed that it never notified me of a driver update. It never downloaded and installed the update even after rebooting my server. I had to update the driver manually and reboot my server. I've always kept the plugin up to date. So I deleted the plugin, rebooted, and re-installed the plugin. Now I can't change the Notification setting from Enabled to Disabled. I don't see any Save button on the plugin page. I also can't change Select Driver Preferred Version setting. I usually select Production Branch, but I can't change it from Latest Branch. Fortunately this plugin is still working for local gui access and my plex docker. Does anyone have any idea what is causing these issues? Thanks for the help. threadripper19-diagnostics-20220927-1329.zip

I deleted the DiskSpeed directory, edited the docker image and saved it. It did create a new DiskSpeed directory. I then opened the webgui and the same error popped up: I'm attaching diagnostics. threadripper19-diagnostics-20220927-1314.zip

I updated DiskSpeed then applied those lines of code. After starting the docker, it still won't start. Here is the error: Here is the docker logs: I also attached the diagnostics. I did not restart my unRAID server during this. If that needs to be done, let me know. Thanks for the help. threadripper19-diagnostics-20220926-1925.zip

I'm unable to use this docker after changing my appdata default location from mnt/user/appdata to mnt/arraycache/appdata. I've uninstalled and reinstalled the docker, including deleting its appdata folder in unraid. When starting the docker, it stays on the 'Scanning Hardware Spinning Up Hard Drives' screen for a long time then displays this error: DiskSpeed - Disk Diagnostics & Reporting tool Version: 2.9.5 Scanning Hardware 22:32:41 Spinning up hard drives Lucee 5.3.7.47 Error (application) Message Error invoking external process Stacktrace The Error Occurred in /var/www/Spinup.cfm: line 137 135: <CFFILE action="write" file="/tmp/DiskSpeedTmp/spinup.sh" mode="766" output="#spinup#" addnewline="NO"> 136: </cflock> 137: <CFEXECUTE name="/tmp/DiskSpeedTmp/spinup.sh" timeout="0" /> 138: <CFELSE> 139: <cflock name="FileWrite" type="exclusive" throwontimeout="true" timeout="10"> called from /var/www/ScanControllers.cfm: line 257 255: </CFOUTPUT> 256: <CFFLUSH> 257: <CFINCLUDE template="Spinup.cfm"> 258: 259: <CFIF FileExists("#PersistDir#/storage.json")> called from /var/www/ScanControllers.cfm: line 250 248: <cfexecute name="/bin/ls" arguments="-l /sys/block" variable="BlockDevices" timeout="90" /> 249: <CFFILE action="delete" file="#PersistDir#/ls_sysblock_exec.txt"> 250: <CFFILE action="write" file="#PersistDir#/ls_sysblock.txt" output="#BlockDevices#" addnewline="NO" mode="666"> 251: 252: <CFOUTPUT> Java Stacktrace lucee.runtime.exp.ApplicationException: Error invoking external process at lucee.runtime.tag.Execute.doEndTag(Execute.java:259) at spinup_cfm$cf.call(/Spinup.cfm:137) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:945) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:837) at lucee.runtime.PageContextImpl.doInclude(PageContextImpl.java:818) at scancontrollers_cfm$cf.call_000005(/ScanControllers.cfm:257) at scancontrollers_cfm$cf.call(/ScanControllers.cfm:250) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:945) at lucee.runtime.PageContextImpl._doInclude(PageContextImpl.java:837) at lucee.runtime.listener.ClassicAppListener._onRequest(ClassicAppListener.java:64) at lucee.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:43) at lucee.runtime.PageContextImpl.execute(PageContextImpl.java:2416) at lucee.runtime.PageContextImpl._execute(PageContextImpl.java:2406) at lucee.runtime.PageContextImpl.executeCFML(PageContextImpl.java:2381) at lucee.runtime.engine.Request.exe(Request.java:43) at lucee.runtime.engine.CFMLEngineImpl._service(CFMLEngineImpl.java:1170) at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:1116) at lucee.loader.engine.CFMLEngineWrapper.serviceCFML(CFMLEngineWrapper.java:97) at lucee.loader.servlet.CFMLServlet.service(CFMLServlet.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:747) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:374) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:834) Timestamp 9/23/22 10:37:45 PM EDT Here is the log: My Plex docker works completely fine with zero issues after changing the appdata default location. Could anyone tell me what the problem is. I'm attaching my diagnostics and a screenshot of the docker edit screen. Thanks threadripper19-diagnostics-20220923-2249.zip

Glad to hear swapping m.2 slots won't affect the cachepool. And yes, I only do File System checks as read only. Thanks again.

Thanks again for your help JorgeB. I'm going to pull both nvme disks out, make sure all contacts are clean, verify the heatsinks are secured and that the thermal pads are in the correct location, then install the nvme disks. I might swap which m.2 slot they go back in. Would that affect the cachepool? I'm thinking it will change the name associated with each nvme disk like nvme0n1 will now be nvme1n1. Also, to get my nvme disk back online, are these the steps to take (these are the steps I did the first time): -reboot server -verify all nvme disks are online -start array in maintenance mode -run a file system check -if no errors are found, start array in normal mode, then run a correcting scrub. After those steps, I'll shut my server down and do the steps I laid out earlier. I'm also going to change my memory speed to its default of 2666 from the 3000 it is set to now.