Squid

Try the upgrade (Plugins, Check for Updates) 2025.05.30 Cause is that 7.x includes a proxy configuration where as 6.12 doesn't. All my dev work is always done on the absolute latest version of the OS.

K. 6.12.x isn't on my usual test regimen, especially if I don't think that anything would affect it. Downgrading a test server right now...

Fixed. Sorry guys

Assuming you've already rebooted to fix, if it happens again from the console can you grab the diagnostics (they'll be saved on the flash drive) and also the output of this command: ls -ail /usr/local/emhttp/plugins/dynamix/scripts

On the flash drive, edit this file: /config/docker.cfg. Remove the last line that's causing problems: DOCKER_OPTS="--runtime=nvidia"

My guess would be unbalanced. Inadvertent setting the source / destination wrong. Or improperly entering in a command that wound up copying them from RAM to the cache pool. Those shares all look like part of the webUI. Only way to really check is to delete them manually (you have to do this anyways), and then reboot and see if they come back and then work backwards as to what created them

Sure. I've been absolutely swamped with real life and other work commitments / issues and am behind on my PMs

It's a folder.view2 plugin issue. If you expand the folder (not sure the correct word), then it should work via clicking on the container's icon

You should post your diagnostics

folder.view.plg - 2025.01.11.1 (Unknown to Community Applications) May 25 04:32:16 Tower root: Fix Common Problems: Warning: The plugin folder.view.plg is not known to Community Applications and is possibly incompatible with your server There's a reason why Fix Common Problems was telling you about this. Uninstall folder view and install folder view2 from Apps Reason for your slowdown is that there's a container which is constantly restarting itself every second (presumably when this happens) Via Unassigned Devices and the settings for the device / network mount, you can run a script for when it connects and disconnects. this is the sample script that UD has as a starting point #!/bin/bash # # Available variables: # # ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # DEVICE - partition device, e.g. /dev/sda1 # UD_DEVICE - unassigned devX designation # SERIAL - disk serial number # LABEL - partition label # LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1 # FSTYPE - partition filesystem # MOUNTPOINT - where the partition is mounted # OWNER - "udev" if executed by UDEV, otherwise "user" # PROG_NAME - program name of this script # LOGFILE - log file for this script case $ACTION in 'ADD' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Device mounted" -i "normal" if [ "$OWNER" = "udev" ]; then # do your hotplug stuff here sleep 1 else # do your user initiated stuff here sleep 1 fi ;; 'UNMOUNT' ) # do your stuff here /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Device unmounting" -i "normal" ;; 'REMOVE' ) # do your stuff here # Spin down disk - uncomment this if you want the disk to be spun down after the disk is unmounted # /usr/local/sbin/rc.unassigned spindown $UD_DEVICE # Detach the disk - uncomment this if you want the USB disk to be detached after it is unmounted # /usr/local/sbin/rc.unassigned detach $UD_DEVICE /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Device unmounted" -i "normal" ;; 'ERROR_MOUNT' ) # do your stuff here /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Error mounting device" -i "alert" ;; 'ERROR_UNMOUNT' ) # do your stuff here /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Unassigned Devices" -d "Error unmounting device" -i "alert" ;; esac

Definitely require you to post your diagnostics, etc

Quick skim through the previous posts, and the underlying issue is likely fixed in 7.1.x

Yup. Reinstalling (not from Previous Apps) would overwrite the template. Depending upon your upgrade path on the OS, and how long the templates were installed, if you look in /config/plugins/dockerMan/templates-user there may be a backup of the file (my-NameOfContainer.bak). That backup however would have been from updating the OS and it adjusted a particular setting on the templates and created a backup before it made the change. Deleting the existing .xml file and renaming that backup's extension to be .xml instead of .bak would give you the version at the time of that template adjustment. YMMV -> Backup would only exist if the template was originally created prior to where the .xml specification changed slightly and the OS adjusted it when it installed the OS update

I tried it on Firefox on a Mac and no issues...

I'd say RAM. Run memtest for at least a couple of passes from the boot menu

@grayraven I could replicate this no problems originally. But, after I added [GLOBAL] map archive = no to smb extras, stopped / started the array, and also disconnected the server from the Mac, the executable bit isn't being set on the server when copying a file from the Mac, and when copying it back to the Mac, the executable bit remains off I replicated your issue on a private share, and it's fixed on the same private share. (I haven't tried on a public, but I don't see that it would make any difference)

If you guys see this again, can you post the output of ls -ail /usr/local/emhttp/plugins/dynamix/scripts

Reply back with your diagnostics

Your /config/flash.cfg file is corrupted Delete that file from the flash drive and reboot Also, if everything is indeed working awesome, then you're continually being spammed by some error message (corrected) Go To Main, Boot Device, click on flash, then syslinux configuration, switch to form view and in the menu default section add pci=noaer to the append line. File should look something like this: (But yours may differ slightly) default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot pci=noaer label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest

There was a spurious issue with at least one of the Dynamix plugins in and around then where it did get marked as blacklisted, uninstall it. This was due to a spurious GitHub issue, and the reason why it happened on the GH issue has been addressed.

Nope. Permanent unless you've got a backup. Hence why all the Use at own risk CYA's everywhere

It adds everything which the docker file specifies. All ports, all paths all variables if they are specified in the file. If the author didn't bother to include them in the dockerfile, not much I can do as the docker system will let you add in additional paths, ports, variables without them having to be exported from the dockerfile

What do you mean by "went down"? Was it off? GUI etc non responsive? Diagnostics were from after the reboot, so can't really discern what happened, but it never hurts after the kids finish the movie to run memtest for a couple of passes from the boot menu

What was the issue?