cloudyhome

Ok, I remembered I had Unraid connect running. I downloaded the last backup from yesterday morning. Imager tool did not work (opened shell), however, manually copying all files to the formatted stick worked flawlessly. System booted, GUI is available and all seems to be working properly. Ufff. Thanks a lot again for your continuous help. I think this is the third time already you are helping me out. Thanks a lot! Best regards Jan

Will try, luckily, its Saturday, I have some time on my hand. Thanks for the hints. I will provide an update once I tested it.

Here you go! Thanks a lot! tower-diagnostics-20250222-0903.zip

Hi everoyne, running Unraid 7 after a reboot I receive an 500 Internal Server Error. I can still access the server via keyboard/connected monitor and it boots to the point where it says login and here is your ip4/ip6. However, the gui is not reachable (500 internal server error). Last changes I remember doing was installing the Powertop plugin (now realizing that is seems to be made for 6.11). Before rebooting I noticed some error while mounting an external drive and running userscripts for backing up to it - it never finished mounting the external drive. Any help is appreciated. The log file is from the automatic log creation during shutdown as well as after the initial reboot yesterday evening. Thanks a lot! tower-diagnostics-20250221-2304.zip tower-diagnostics-20250222-0806.zip

Ok, thanks @JorgeB! I tried to look through my syslog. It appears that frigate starts a ffmpeg process, but can't stop it. Maybe it's related to appdata backup, which is starting around the same time. I will dig into it Right now, I am just happy, that I can access the server again and it's a fixable problem. Thanks again!

Hey, I could use some help again regarding a reappearing out of memory issue. System is Unraid 6.12.13. Last time it was a Frigate issue. I am not sure what causes it this time, so maybe some can have a look. I feel it might be related again to frigate in connection with appdata backup closing it. Any help is appreciated. I am not at home and the server was unreachable for 11 hours now and I just could login again with tailscale to download the diagnostics. Thanks a lot everyone! tower-diagnostics-20241105-1122.zip

Thanks a lot for your feedback. Appreciate it! I was not aware of that I'll update the guide above accordingly with a hint to the chosen device name.

Hey, Thank you for the wonderful script! Saved me a lot of time. I tried to figure out how I can ensure that the backed up data is not acessible anymore once the backup is done. My understanding is that spinning it down and detaching it will do the trick. This can be achieved by using the unassigned device plugin as mentioned by OP. Here is a short manual which works for me. Any feedback is appreciated. Updating Unassigned Devices Default Script 1. First, you want to adapt the unassigned devices script by uncommenting the sections of the default script. Click on the settings button in the unassigned devices section (Main tab). 2. Copy Disk Serial and Disk Name to a notepad. You will need them later. My Disk Serial in this example ends at "74". Do not copy blank space or the brackets. Note: @dlandon pointed out: Do not use "devX" device names. Assign a unique name to the 'Disk Name' field as an alias and use that in your script. Take the time to update it here and save the change before proceeding to the next steps. 3. Scroll down to find the script section. Click on "Default". It will load the default script to the Device Script content. At this stage, the script does nothing. 4. Uncomment the "remove" section activities by removing the hashtag. Effect: Once unmounted, the disk spins down and deattaches. Click on Save. 5. Scroll up and select the device script. Yours will have a different name, but there is probably only one to select. -------------------------------------------------- Switch to the User Scripts: 6. Open the script which you created for the backup based on OPs script. 7. Add lines at the beginning and the end of the script to attach, mount and unmount the usb device. You will need the saved information from the first step: Disk Serial and Device Name. Note: I am using different devices than at the beginning here, do not let this confuse you. Just copy & paste the information you saved before. ### mount external USB drive /usr/local/sbin/rc.unassigned attach 'device serial number' /usr/local/sbin/rc.unassigned mount name='device name' # unmount the usb device /usr/local/sbin/rc.unassigned umount name='device name' You can test the command without processing the full script by copy and pasting them in the command line of your unraid system. Note that attaching and mounting will take some time (~10 seconds for me). Just wait and see if it pops an error or hopefully just works. Source:

Quick update after some testing with frigate: It looks like it is fixed after a switch to vaapi instead of qsv for all reolink cams. Also updated the input profile for the h265 cam according to this link https://github.com/blakeblackshear/frigate/discussions/7859 I will monitor the situation and keep this thread updated in case the problem reappears.

Thanks a lot @Michael_P! I will give it a try. My nvr is frigate, I will dig into this and update this thread accordingly. My first guess regarding frigate is that it is maybe caused by the car as a non-moving object within frigate. I saw some "car"-event with 20 hours recording. Let's see.

Hello dear community, I got an error in the morning from the fix common issues plugin. This is the first time, I am experiencing this kind of issue. I had some "unknown" red flagged errors in the last weeks, but they disappeared after a reboot and I could not really see anything from the GUI not working. I am running plenty of docker containers one VM. The VM was stopped when this issue appeared and was not online for several days. On a side note: I am one of the people who need to use macvlan because of their ubiquiti setup. While the update notes recommend to enable "host access to docker", I can't enable this. Once enabled, GUI becomes unavailable, all dockers, however, remain accessible. Please find attached the diagnostics. Any help is appreciated. I would really like to fix this rather sooner than later tower-diagnostics-20240303-0824.zip

Hey, is there any chance you could share some screenshots of your setup? I have the same gpu. It appears in the device manager as correctly installed, but the intel driver setup tells me that the installations failed and I should reinstall the drivers. Subsequently, Fusion 360 and also the Orcaslicer, which I would like to use tell me that they cannot use my GPU. Any hint would be appreciated.

Hi everyone, I have a strange issue my unraid setup. After the upgrade to 6.12, everything was fine. Now, after some days, it looks like it the GUI is no longer reachable. It timeouts. In the morning, I could still access it, now it is gone. All container's website are still reachable, just the Unraid GUI is not. I tried different browsers and I tried reaching it from a different PC. Same results: Browser loads endlessly without result. Any suggestions are welcome! Yesterday I experienced the same issue and I reset the PC. Afterwards, the GUI was available again. Thank you!

quick feedback: switched to the official jellyfin docker as proposed. Did not change anything with the go file, just installed intel-gpu-top, added the parameter to the jellyfin docker and selected quicksync for hardware decoding. Works for intel 12500 Read this from the intel-gpu-top app information: "This plugin adds the tool 'intel_gpu_top' to your unRAID server and also enables your Intel iGPU from the installation of this plugin on, so no editis to the 'go' file or creation of other files are necessary." So it seems with installing the app from the app store, the go file is already updated, no manual update needed. Thanks for pointing this out, really helped me out

oh my god... should have tried this before losing my mind. Thank you very much for the hint. Not sure what the difference between the both installations are, but I was able to install unraid in no-time. Thanks again.