jbrown705

I am having an issue with getting any backup to complete. I have been trying for about 2 weeks without success. I keep getting messages about "tar creation failed ..." and usually something about a file within a docker changing before it was read, then a the end it tell me at the end: "[23.08.2023 05:15:44][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." I have also uploaded my logs. Here is my log ID: c1b978de-a3a4-4d79-82e4-3dd8a46290ca

Yes, I first updated from macvlan to ipvlan and left run for a few days. All was fine. Then I updated to latest version and left run for a few days. All seems to be ok but I had one error that cause me all my dockers to say unavailable but they still worked. I did a force update and that fixed them one by one. I am having issues getting the new appdata backup to complete tho, but that’s my only issue so far.

@JorgeB, So I should switch to ipvlan then do the upgrade immediately or so i need to check anything before the upgrade?

@JorgeB I had to format and reinstall my main cache drive (I have 3 cache drives, nvme for all appdata, and other one for downloads only and a 3rd for just vm and the other stuff). The main nvme is the one I had to reformat. Seems ok now but if there is anything else you can share about it, I’ll try to fix. I reverted back and everything has been fine for about 2 weeks now. as for the ipvlan, I did try switching that but it was after I did the upgrade and i don’t know if that was what was causing the crashes. Should I switch that give it a day then try the upgrade or just switch the immediately so the upgrade? Was there something in the diag files indicating the issue with with that?

Hi all, hopefully this is in the right place because it's related to my docker crashing and causing issues with being able to shutdown the docker, restart it, remove it etc. After upgrading to 6.12.3 from the last version of 6.11, my docker crashes after a few hours (most I have gotten was about 12hrs after updating). I have tried 4x and the same thing keeps happening. As soon as I downgrade, it works and remains stable. I have checked and removed anything the compatibility check flags and all works perfectly fine for hours then just one after the other the dockers crash and become unresponsive. I have attached the diagnostic file it prompts you to download when downgrading and am hoping can someone can take a look and let me know what the problem might be or how to fix it? deathstar-diagnostics-20230729-0330.zip deathstar-diagnostics-20230728-1318.zip

Hi all, hopefully this is in the right place because it's related to my docker crashing and causing issues with being able to shutdown the docker, restart it, remove it etc. After upgrading to 6.12.3 from the last version of 6.11, my docker crashes after a few hours (most I have gotten was about 12hrs after updating). I have tried 4x and the same thing keeps happening. As soon as I downgrade, it works and remains stable. I have checked and removed anything the compatibility check flags and all works perfectly fine for hours then just one after the other the dockers crash and become unresponsive. I have attached the diagnostic file it prompts you to download when downgrading and am hoping can someone can take a look and let me know what the problem might be or how to fix it? deathstar-diagnostics-20230729-0330.zip

Hello- Here you go. I put several from the last few in case it helps. Thank you! backup (1).log backup (2).log backup.log

Hello- I too am also seeing the error notifications and '-error" extension on the filename but do see what appears to be a full sized backup. I am not sure if I should tick the box to ignore the errors and nothing I have found in this thread seems to inform me. How can I tell if the errors that are registering are able to be ignored? The last one in the log says "A error occurred somewhere. Not deleting old backup sets of appdata" but i do see 2 other in there that say "tar verify failed! "and "tar creation/extraction failed!" however the tar file is still created. Any help is appreciated!

I am posting this here because it seems that I am having a similar issue. I am not sure what could be holding it up but it looks like my /usr/ will not unmount during a shut down. I have the logs mirrored to the flash because I have been doing some troubleshooting possibly around bad memory slot. Would someone mind maybe taking a look and seeing if they can help? Logs attached here. Also, I have had some issue with the system crashing and going into kernel panic, so if there is anything else in here you can see I would appreciate the feedback, not too good at understanding the logs. Thanks! deathstar-diagnostics-20220215-1236.zip

Anyone around to help?

Would you mind posting how you did that I have wondered that too, but don't know how to as I am not super familiar with linux or cli?

Hello, I am hoping I can get some help troubleshooting and some issues I am having. I recently moved to some new hardware but have some random issues that seem to keep popping up. I am currently only an ASRock z690 steel legend, with an i7 12.7K, Dell H310 6Gbps SAS HBA w/ LSI 9211-8i, and 64gb corsair vengeance pro ram. There are times when it seems Plex will lock up all of a sudden and cause the docker server to get stuck which prevents me from doing a clean shut down and reboot (i think). There also seems to be times when I can't stop the docker and can't get the system to reboot. I set the syslog server to mirror the logs to the flash and have attached a few of them here that happened when I was trying to shut down (ones from 4th and 5th). Any help is appreciated. deathstar-diagnostics-20220201-0909.zip deathstar-diagnostics-20220204-2234.zip deathstar-diagnostics-20220204-2246.zip deathstar-diagnostics-20220205-0131.zip

I checked there first and the processing tab and the temp file dir match statuses. However, I was trying to check to see if the verifying step had hung. It did finish but took nearly 10 hours for some reason this time. I was just looking to see if there was a way to see what was happening during that verification stage. Not sure if it’s possible based on how the code works but do you think it’s realistic to ask that maybe in the status tab for a progress bar to be added for each step? They people would be able to see if the bar is not progressing or just moving slowly?

I realize this is an old post, but I have a backup that is going on 6 hours now and it normally does not take anywhere near that. I see the backupinprocess and verifyinprocess file in that temp dir but is there any way to see if it hung or there are any other issues? UI is saying verifying still too... Logs align with that as well.

I’m on 6.9.2. I didn’t know there was a newer version.

I updated this and then just edited the docker config so it would pull it and so far so good. I will update this post once there is an official update to the image and report back but it looks like you helped me solve it!! Thank you! I also noticed the path to the template was actually in the URL on the page which i never noticed before.

I do that to fix and and get the docker started again but the next time there is an update (or if I remove it and try reinstalling it from a template) it adds all those parameters in again. It’s almost like the commands that are written or generated (in the XML file maybe?) are messed up and add a bunch of /path/to/device parameters to every re-run of the command.

Hello- I am having an issue with a docker for Home Assistant that seems to have an issue with the command to pull the new files on update or reinstall. I have googled for days, posted in both the LS and UnRaid Discord with no luck. I tried looked for a way to maybe edit the docker command but I am not great with Linux. It seems to add a lot of /path/to/device lines with no values every time I update or reinstall and it won't start until I remove all the empty ones. Any know how to fix or maybe go in and edit the command it's using to see if those extra parameters can be removed?

Hello- I have been having some issues with Netdata. The docker log is full of errors and I also get some sock errors in the main log. Can anyone help me out? I tried Googling and looking online but some of the things to try make me nervous as they are over my head and I don't want to follow blindly for fear of making it worse. Here is a pic of the 2 log files: Docker Log: Main Log: Thanks for any help! -Jason

Sorry, apparently after I replied and attached it didn't post correctly and I was sitting here waiting to a notification. I can still see it right below this message now. Is it not showing for you? deathstar-diagnostics-20190112-1546.zip I already know there is a weakness in the small exhaust port...

I'm sorry, I am not sure which one you need (and possibly how to get it). Did you want the main log file from the log tab or something else? Do you need it when the the issue is actually happening? Thanks!

I'm having and issue with UA. It seems to work fine for a bit then locks up and maxes out a few of my cores but never actually loads. I have a left over WD MyBook attached via USB. I leave it go and after a day or so and it seems to get stuck trying to mount the drive. As soon as i unplug it the cpu usage drop and the UA network mounted locations pop up. I'm not seeing anything in the SMART reports for the drive to indicate it is failing. Any thoughts from anyone on how to troubleshoot? Thanks!

would you recommend using static or bridge? **Update** That got me in but with bridge and 8443 or static and 443, it doesn't come thru as secure for some reason (chrome on mac)?

I switched the port back to the default 8443 and tried again. Here is a screenshot of my settings and what happens when I click WebUI.

I am not using 8443 for unraid, but I am using it for a WDMyCloud on different IP. I have tried changing the port and still can't get in. I set a bunch of different port and forwarded them all as well. I installed using the app via CA. Should i be using a different one?