Everything posted by Macj72x
-
Containers deleting and failing when updating
Yes it does. That thread seems to be my situation. I'll try to run through some of those troubleshooting steps.
-
Containers deleting and failing when updating
Anyone have any recommendations? I'm not sure where to start and my troubleshooting has been turning up empty
-
Containers deleting and failing when updating
For the past few months, a many if not all of my containers will fail to update. They will leave a orphaned image and I need to redownload them and then they work properly. I recently noticed it still is doing it, but not leaving an orphaned image any more. The container just drops off my system. Can anyone point me in the right direction or see any issues with my diagnostics? chunkymonkey-diagnostics-20241212-1255.zip
-
Server Lockup
My server has been having intermittent issues where the gui and ssh will become no longer accessible until I reboot the server. I received a notification that it froze at around 11ish today 4/17. I set up a remote sys log server and attached the results. Could someone provide me some guidance on what may be happening or how I can troubleshoot this? I don't see anything in the logs that stick out to me. syslog-192.168.3.7.log
-
Why won't docker.img unmount?
I am having trouble getting the array to stop. I keep getting these errors continuously: Feb 7 15:52:11 ChunkyMonkey emhttpd: Unmounting disks... Feb 7 15:52:11 ChunkyMonkey emhttpd: shcmd (310): /usr/sbin/zpool export cache-system Feb 7 15:52:11 ChunkyMonkey root: cannot unmount '/mnt/cache-system': pool or dataset is busy Feb 7 15:52:11 ChunkyMonkey emhttpd: shcmd (310): exit status: 1 Feb 7 15:52:11 ChunkyMonkey emhttpd: Retry unmounting disk share(s)... Feb 7 15:52:16 ChunkyMonkey emhttpd: Unmounting disks... I followed this link: and ran losetup to receive these results: NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/cache-system/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 I ran umount /dev/loop2 to force the array to stop. Are there any diagnosing steps to prevent this from happening again? I've attached my diagnostics. chunkymonkey-diagnostics-20240207-1556.zip
-
Easy, like really easy, backup of unraid to synology?
Did you ever find a solution to this? I have a synology nas that I setup a point to point tunnel to that I wish to run backups to. Trying to find an easy and secure solution.
-
New Server Not Pulling up Disks
So I solved it. I was thinking you change the setting at the RAID controller configuration to go to HBA mode, but that didn't work and caused me more issues. After lots of tinkering and get my drives to show again, I found the best solution. I had to go into the configuration of each individual drive and change it to non-raid mode then click go.
-
New Server Not Pulling up Disks
Hey I have a new Dell R430 Poweredge server running Unraid. I can get it to boot fine, but the disks are not loading. I have another server with a similar configuration that pulled up these same disks with no issue. Can anyone tell me what I'm doing wrong? impairedbear-diagnostics-20240111-1823.zip
-
/var/log is getting full
Hey All, I'm getting the error message /var/log is getting full. I've looked through them and fixed the cron issue with userscripts, but other than that, I'm not sure what else to do or where to start. Any advice? I've attached my diagnostics. chunkymonkey-diagnostics-20240111-1018.zip
-
Can't stop containers or VMs through GUI menu
That was it. Thank you!
-
Can't stop containers or VMs through GUI menu
When I try to start, stop, restart, pause, force stop, hibernate, remove VM, or remove VM and Disks a container or VM it doesn't do anything and will just sit there with the menu highlighted. Without clicking everything, most all the other menu items seem to work find including start with console(VNC) for the vms. I've tried using different browsers. This seems to be a relatively new development maybe in one of the last few updates. I have no clue where to start with diagnosing this. Please see my attached diagnostics. chunkymonkey-diagnostics-20231207-1449.zip
-
Kernel Panic
I redid the flash drive. I didn't get a boot error the two times I tried booting it so fingers crossed that is fixed, but my appdata share ownership keeps changing to unknown. Any advice on how to diagnose that?
-
Kernel Panic
I lately have been having this kernel panic pop up when I need to restart unraid: Sometimes I can restart and it will go past it and sometimes it takes several restarts. Can anyone decode this for a layman? Once I get Unraid to boot, sometimes I will be missing some of my cache nvme drives. This probably happens 1 in 10 boots and I will need to restart for them to appear again. Then once I get it going with all the drives, I will have all my appdata owership change from nobody to unknown. This causes all my docker containers to not work until I run a script a few times switching it back. The appdata share is on a different cache pool than the nvme drives that disappear. I feel like this may all be related and a hardware issue, but I'm not sure where to start to diagnose this. Any help? chunkymonkey-diagnostics-20230809-1143.zip
-
Appdata keeps changing ownership to Unknown
As the title says, I keep having ownership changes with my entire appdata share and only that share. It causes issues with all my containers. I happen to catch it in the middle of a change and copied the attached diag file. It started changing sometime around 11-12am today(6/21). I don't see anything that stands out in my log file. Can someone more experienced look through and see if anything stands out that may be causing this? chunkymonkey-diagnostics-20230621-1158.zip
-
[Plugin] CA Appdata Backup / Restore v2.5
My appdata share keeps changing owner from nobody to unknown when appdata backup runs. Any ideas what’s happening and what steps I may need to do to fix it?
-
Appdata keeps changing ownership to Unknown
I haven't tried it. Should I leave it in safe mode for a week and see what happens?
-
Appdata keeps changing ownership to Unknown
As the title says, I keep having ownership changes with my entire appdata share and only that share. Obviously it causes issues with all my containers when this happens and I have to run a Fix Appdata Permissions script to fix it. I currently have to run that several times a week. The last time it happened (some time right before 2023-04-05 14:57:46) this is the only message I saw before it changed: Apr 5 14:56:53 ChunkyMonkey kernel: docker0: port 13(vethf0ca75c) entered disabled state Apr 5 14:56:53 ChunkyMonkey kernel: veth3e9fb99: renamed from eth0 Apr 5 14:56:53 ChunkyMonkey avahi-daemon[14646]: Interface vethf0ca75c.IPv6 no longer relevant for mDNS. Apr 5 14:56:53 ChunkyMonkey avahi-daemon[14646]: Leaving mDNS multicast group on interface vethf0ca75c.IPv6 with address fe80::54a2:2aff:fe29:9011. Apr 5 14:56:53 ChunkyMonkey kernel: docker0: port 13(vethf0ca75c) entered disabled state Apr 5 14:56:53 ChunkyMonkey kernel: device vethf0ca75c left promiscuous mode Apr 5 14:56:53 ChunkyMonkey kernel: docker0: port 13(vethf0ca75c) entered disabled state Apr 5 14:56:53 ChunkyMonkey avahi-daemon[14646]: Withdrawing address record for fe80::54a2:2aff:fe29:9011 on vethf0ca75c. This doesn't seems like something that would cause that to my untrained eye, but is all I see. I've also noticed it seems to happen around the time that appdata backup runs. This is exhausting as I'm fairly new to Unraid and want to get this thing to be stable, but I'm about to give up. Please help me get this thing running properly. chunkymonkey-diagnostics-20230406-0829.zip
-
Mover not Moving
It looks like that is causing the share floor to be set at about 164gb. I removed that, but how would that help mover move the files?
-
Mover not Moving
Hopefully I don't need to make a new tread, but I'm still having trouble with mover. Since I made this post, I have built a separate cache pool for my default shares and those are set to prefer. All my media and basically everything else is goes into a separate media cache pool and is set to Yes:cache-media. That media pool keeps getting completely full and I have to shut everything down and wait a few hours for it to start emptying. Can someone tell me what is going on here or where I can search the logs to find out why stuff isn't moving? chunkymonkey-diagnostics-20230319-1922.zip
-
Mover not Moving
Since I'm moving files from cache to array, I also need to remove "use hardlinks instead of copy" option in the 'arr settings, correct?
-
Mover not Moving
Gotcha. I like that. How do you move to a new share for the post processing, a script? If so, do you mind DMing it to me?
-
Mover not Moving
Could you break this down a little more? You use two cache pools for your media downloads or just one of the two? What is the path that your media downloads take because that obviously is my issue. Sounds like a great recommendation to break up my cache pool into two.
-
Mover not Moving
Will do. Any recommendations going forward? Should I not use cache for media downloads?
-
Mover not Moving
It finally kicked into gear and has almost cleared out all of the media files. It seemed like it started working after about fours hours after that last post.
-
Mover not Moving
Scratch that. It moved about 100gb then stopped. It says mover is still running but I haven’t seen a change in about 15 minutes and the data rate dropped significantly.