DaFr0n

Where do I identify the culprit in the diagnostic files please? It also looks like my CCTV_Pool HDD is dying, would you agree as it keeps going read only and the allocated share is a 'invalid path'

Docker within the UnRaid WebUI. Again, this is for various dockers all created within the WebUI. This is using the below App. https://github.com/willfarrell/docker-autoheal/issues

Could someone please help with how I'm meant to set a docker container up to use Autoheal? Autoheal is set as AUTOHEAL_CONTAINER_LABEL=heal My dockers containers I want to watch have: AUTOHEAL_CONTAINER_LABEL=heal I'm not sure if this is correct as the Github states AUTOHEAL_CONTAINER_LABEL: autoheal-app Logs for auto heal show: AUTOHEAL_CONTAINER_LABEL=heal AUTOHEAL_START_PERIOD=0 AUTOHEAL_INTERVAL=5 AUTOHEAL_DEFAULT_STOP_TIMEOUT=10 AUTOHEAL_ONLY_MONITOR_RUNNING=false

Problem solved... I'm not sure how this happened but my Pelican-Wings changed to pulling ghcr.io/mainfrezzer/pelican-panel:latest I have changed this back to wings:latest & all is well. Thanks for the help

Just tried the above, same issue mate

Yes updated wings and panel, still the same issue.

laravel-2025-04-06.log Logs attached

Has anyone else's updated and after no longer able to connect to their node. I have changed the Pelican owner to 'nobody' as suggested above but no node connection. Assume something in a update has changed as it worked great previously with multiple servers "Failed to load resource: the server responded with a status of 404 (Not Found)"

Hi all, I have tried multiple solutions without success. My aim is to have the below~: Bedrockconnect (running in docker, needs port 19132) I have installed this and I can see user IDs etc. so I know its working Run a Geyser Bedrock server within Pelican Docker (Pterodactyl) Again I can get this working fine, but it needs port 19132, which doesn't respect changes in the server.properties for port changes. Therefore, how would I go about getting these 2 instances to run allowing both to access port 19132 & be connectable. As you would expect at the moment, if I start one, I get a port reservation error on the other. I was thinking macvlan or ipvlan, but I will be honest that side of things is new to me 😁

They are on the same SATA power cable, also the same cable splitter on the LSI HBA. But then again so are a few other disks, I have just moved some cables around, waiting for it to reboot

Looks like there is also a possible issue with disk 2 according to the notifications

Hi all, looks like the parity issue is back. Is it time to replace the drive? Unraid just threw a bunch of errors, need to go through them now unraid-diagnostics-20241205-1739.zip

Thanks, I will have another look, as its done this on multiple occasions, however always resyncs

Hi all, would someone help me read my diag file to understand if my parity disk is faulty. I have tried, removing, restarting array, stopping, readding disk, to force a parity sync. However it keeps disabling so I guess there is a error somewhere. Thanks in advance unraid-diagnostics-20240927-1852.zip

Does anyone know if this method still works, I'm struggling to get it up and running.

Hi all, I'm having a few problems with unraid behind OPNsense. OPNsense is setup as a VM within unraid. The issues I have at the moment mainly relates to dockers, looking at their address's they are correct 192.168.4.3:32400 e.g. for Plex. However if I try to open the Plex webui it doesn't load and the actual webui Ip is 169.254.126.151:32400 If you go into a docker template, delete the last letter of the name & re-add it to enable the save button it recreates the docker and the webui works again. Is there anything you can recommend?

**UPDATE** Looks like the Pizero hasnt yet got its static IP during boot, therefore before OPNsense is running I need to use host instead of the IP: wget --user=USER --password='PASSWORD' ftp://[email protected]/files/keyfile -O /root/keyfile The file does transfer to unraid, however the server wont start, inspecting the transferred file in nano its actually blank. If I do a wget with the system already up and running it pulls fine, therefore why is the keyfile coming over blank during boot? ***UPDATE*** Scratch the file transferring I had -O which was creating a blank log file. I also tried --tries=0 but it doesn't make a difference. I'm at a loss

Ok so far I have done the below: Headless Raspbian install on Pizero connected via LAN Installed vsftpd Saved a keyfile on the Pizero SSH directly into Pi from unraid console to generate keypair Tested the wget from the Pizero to unraid, trial and error but I got the transfer to work successfully, though its only ftp, everything else SFTP, curl, threw errors: wget --user=USER --password='PASSWORD' ftp://192.168.4.28/keyfile -O /root/keyfile Amended the go file: #!/bin/bash # get keyfile wget --user=USER --password='PASSWORD' ftp://192.168.4.28/keyfile -O /root/keyfile # Start the Management Utility /usr/local/sbin/emhttp & This is where I'm struggling, if I put the wget to the bottom of the go file, then it boots but it wont auto start however the keyfile is there in 'MAIN' , assume its auto starting before it fully pulls the keyfile. If I put the wget as per the above, before /usr/local/sbin/emhttp &, then it wont show the webgui or fully boot. Any ideas?

As per the title, as of the latest unraid version 6.12, what's the best way to auto start an encrypted array? I never used to mind entering the passphrase, however I have since installed OPNsense, therefore I need the system to auto boot if it ever goes down & automatically start the OPNsense VM. My thinking is to have a Pi Zero (lan adapted) hidden somewhere is the house attached to the network, if the unraid server goes down then it automatically pulls the keyfile and starts the array, therefore in the unfortunate instance of the server being stolen, it would not find the pi/keyfile and therefore not start the array leaving the data encrypted. If anyone is doing this, instructions would be great please.

Does anyone know how would you install the DEV branch on unraid?

The only part I added to avoid conflict was: # path to the configuration directory (must be writable by motionEye) conf_path /etc/motioneye

That did the trick, thank you

Hi all, does anyone know where the config file is to check if a user is actually assigned, there is nothing in the settings list of user(s) >>>

I will have a look at the LSI connectors in that case. Thanks for the help

I have used unbalance to pull my IronWolf 2TB from the array as it has been disabled multiple times throughout the past few months, a extended SMART has been ran and the results are attached. My question is, looking at the data do you believe the HDD is actually faulty? unraid-smart-20230625-1110.zip