muffinman1604

Well, I tried restoring and it is not working with the successful backup. Restore is treating the tar as a gzip file ab.debug-failed-restore.log

I just upgraded to Unraid v 6.12.0 and I got this plugin from the Apps tab. When I tried to do my backup I got an error: [15.06.2023 03:22:54][Main][warning] An error occurred during backup! RETENTION WILL NOT BE CHECKED! Please review the log. If you need further assistance, ask in the support forum. and my folder is titled ab_20230615_025310-failed, so it will not let me restore from that folder. Attached is my log. Any idea what is happening? The 2.5 CA backup plugin was working in the previous version of Unraid 6.11.5 Edit: I had rebooted my server for something and tried the backup again and this time it worked. Not sure what happened, but I'll leave this here anyway. ab.debug.log ab.log succes-ab.debug (1).log

That would be awesome if someone could provide that for a hint.

Is the option to verify backups very necessary? It seems to add a good bit of time to the process (currently been verifying for 18 minutes). And is there anything from Plex that could be removed to speed up the process? Like any info if missing that would just get grabbed from the internet again?

What does "Create separate archives (one per folder)?" mean? Is yes or no going to be faster? Also, does the scheduled backup always stop the docker containers, or is it just the first time that the backup is run that the docker containers are stopped?

I had been fine for a while and thought I was in the clear, but I guess not. Just happened again at 10/29/2021 00:00 in the logs and it doesn't seem to show anything telling. https://pastebin.com/V1vNsrKm

I had another hang up after lowering RAM speeds and verifying power settings. Any other ideas? Logs in the previous comment I just left. I didn't see anything obvious as to what went wrong.

I noticed again today (10/18/2021) that the server was unresponsive. I powered back on at 14:29 in the logs. Here they are again: https://pastebin.com/3M7fA7BY

Hey, I'm pretty sure that I have C states set correctly already - I think I did that when I first set the Threadripper server up. My RAM is running at 3600 using the DOCP settings that came on the RAM. So I can try lowering that down to 2677. It is just weird that everything was fine for quite a while and now started having issues.

The problem: I had noticed yesterday that my Unraid server seemed to be unresponsive/crashed/frozen. I went to go and watch something on Plex on a different device and it said my media server was unreachable. I have the server running in a Docker container on Unraid so I went to investiage, but noticed that I could not get to the server how I normally do (entering the IP or TOWER/ as a url in chrome). So I tried pinging the server and also got no response. So I rebooted the server using the buttons on the case. Then everything started up fine. A few hours later I was watching a TV show on Plex and all of a sudden it stopped and the media server was showing as unreachable. So I tried the same steps as before and ended up powering the server off and back up. Then I went to look at logs and realized they didn't persist. So I set up the logging server so they log to a share on my cache drive. So then today the server did the same thing again. After getting it powered back up and starting the array, I went and got the logs and put them in pastebin. Pastebin link to the syslogs: https://pastebin.com/847K9gX8 Oh, I did add a note in there (line 205-213) System Info: OS: Unraid OS Pro 6.9.2. Motherboard: ASUSTeK COMPUTER INC. ROG STRIX TRX40-E GAMING, Version Rev 1.xx American Megatrends Inc., Version 0602 BIOS dated: Mon 18 Nov 2019 12:00:00 AM EST CPU: AMD Ryzen Threadripper 3970X 32-Core @ 3700 MHz RAM: G Skill Trident Z NEO 64GB 3600 CL16 (4x16) x2 (128gb total) PSU: EVGA SuperNOVA 1200 P2 14 HDDs, 2 WD SN750 1TB cache drives, and 2 Intel 650p unassigned drives. If you need more specifics on system info or if there is a command I can run to get something, let me know. Additional info: Because of the crond crontab error that was happening in the logs, I went and looked quickly. I went to "Auto Update Applications" in Settings. I saw that the plugin update schedule had a custom cron expression that I didn't remember ever setting. So I removed that and changed it to one of the built in options for daily/weekly/hourly/etc. After doing that and applying, I ran the following commands: cat /etc/cron.d/root pastebin link: https://pastebin.com/cd2y7SdW crontab -l pastebin link: https://pastebin.com/7e0iBYGw I'd really appreciate any help with this. Thanks in advance! Let me know if you need any other info.