nearcatch

No luck, had another MCE today: Dec 10 09:59:27 UnraidServer kernel: vfio-pci 0000:08:00.0: vfio_ecap_init: hiding ecap 0x26@0x410 Dec 10 09:59:27 UnraidServer kernel: vfio-pci 0000:08:00.0: vfio_ecap_init: hiding ecap 0x27@0x440 Dec 10 13:19:10 UnraidServer kernel: mce: [Hardware Error]: Machine check events logged Dec 10 13:19:10 UnraidServer kernel: [Hardware Error]: Corrected error, no action required. Dec 10 13:19:10 UnraidServer kernel: [Hardware Error]: CPU:1 (19:21:2) MC8_STATUS[-|CE|-|-|-|-|-|-|-]: 0x80000001b23bd063 Dec 10 13:19:10 UnraidServer kernel: [Hardware Error]: IPID: 0x0000000000000000 Dec 10 13:19:10 UnraidServer kernel: [Hardware Error]: Bank 8 is reserved. Dec 10 13:19:10 UnraidServer kernel: [Hardware Error]: cache level: L3/GEN, tx: INSN Dec 10 13:40:14 UnraidServer emhttpd: spinning down /dev/sdm Dec 10 17:55:39 UnraidServer emhttpd: spinning down /dev/sdd Can anyone help figure out what's happening?

Thanks, I changed that in my bios and I'll update the thread if no further MCE happen.

Experienced twice, diagnostics are from the most recent occurrence. I recently upgraded the CPU on this server. Nov 7 08:40:53 UnraidServer kernel: mce: [Hardware Error]: Machine check events logged Nov 7 08:40:53 UnraidServer kernel: [Hardware Error]: Deferred error, no action required. Nov 7 08:40:53 UnraidServer kernel: [Hardware Error]: CPU:1 (19:21:2) MC27_STATUS[Over|-|-|-|PCC|-|Deferred|Poison|-]: 0xc35b9aeb5bdf8948 Nov 7 08:40:53 UnraidServer kernel: [Hardware Error]: IPID: 0x0000000000000000 Nov 7 08:40:53 UnraidServer kernel: [Hardware Error]: Bank 27 is reserved. Nov 7 08:40:53 UnraidServer kernel: [Hardware Error]: cache level: RESV, tx: GEN Nov 29 16:07:02 UnraidServer emhttpd: read SMART /dev/sdw Nov 29 16:07:02 UnraidServer emhttpd: read SMART /dev/sdp Nov 29 16:09:47 UnraidServer kernel: mce: [Hardware Error]: Machine check events logged Nov 29 16:09:47 UnraidServer kernel: [Hardware Error]: Corrected error, no action required. Nov 29 16:09:47 UnraidServer kernel: [Hardware Error]: CPU:1 (19:21:2) MC27_STATUS[-|CE|-|-|-|-|-|-|-]: 0x80000001ae5b9163 Nov 29 16:09:47 UnraidServer kernel: [Hardware Error]: IPID: 0x0000000000000000 Nov 29 16:09:47 UnraidServer kernel: [Hardware Error]: Bank 27 is reserved. Nov 29 16:09:47 UnraidServer kernel: [Hardware Error]: cache level: L3/GEN, tx: INSN Nov 29 16:27:17 UnraidServer emhttpd: spinning down /dev/sdw Nov 29 16:27:17 UnraidServer emhttpd: spinning down /dev/sdp unraidserver-diagnostics-20221130-1145.zip

This works for me. You need the style tags to trick Theme Engine into inserting custom javascript this way. Probably a security hole, tbh. You could also use a browser extension like Violentmonkey or Tampermonkey to load it as a userscript. </style> <script type="text/javascript"> document.addEventListener("DOMContentLoaded", () => { let fansTds = document.querySelectorAll(".fan_view td"); let fansTdsArray = Array.from(fansTds); for (const td of fansTdsArray) { switch (td.innerText) { case "FAN 0": td.innerText = "fan0name"; break; case "FAN 1": td.innerText = "fan1name"; break; case "FAN 2": td.innerText = "fan2name"; break; case "FAN 3": td.innerText = "fan3name"; break; case "FAN 4": td.innerText = "fan4name"; break; case "FAN 5": td.innerText = "fan5name"; break; case "FAN 6": td.innerText = "fan6name"; break; case "FAN 7": td.innerText = "fan7name"; break; case "FAN 8": td.innerText = "fan8name"; break; case "FAN 9": td.innerText = "fan9name"; break; case "FAN 10": td.innerText = "fan10name"; break; default: break; } } }); </script> <style>

something like this should work even when you want FAN1 to be different from FAN10. I don't have 10 fans so I can't test it and confirm. @BreakfastPurrito EDIT: go to this post for the code

Don't know what else to do. After I installed the IT87 plugin (and maybe after unloading drivers and re-detecting/re-saving, I don't remember), my plugin looks like this, and I haven't had to do anything else since then, even after reboots:

You can just search for ITE IT87 in the Community Apps in your server dashboard.

I had success with my GB X570 AORUS PRO WIFI by installing the ITE IT87 Driver plugin. It adds some modified IT87 drivers for newer chipsets, after which unraid detected my fans.

Yeah I would welcome an update to the current compose version. The last couple of releases have added extra features for docker secrets.

The other thing I've done is disable "IPv4 custom network on interface br0 (optional):", which is only visible after stopping the docker service. Iirc this, combined with "Docker custom network type: macvlan", creates a macvlan network via unRAID, but unRAID recreates it on every boot. This means the network id changes even if the network seems the same. I instead manually create a new docker macvlan network, and that gets preserved with the setting I mentioned in my previous post. I used something like this to create it months ago, and haven't had to recreate it since, even after more than a dozen reboots: docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 --ip-range 192.168.1.160/28 -o parent=br0 --aux-address="host=192.168.1.160" lan_macvlan Use this in the compose file to make it available to your containers: networks: lan_macvlan: external: true name: lan_macvlan Sorry for the guesswork here. I set this up almost a year ago now and don't quite remember how I got past the problem.

You could try setting "Preserve user defined networks" to "Yes" in docker settings. I remember having the issue you're experiencing and I *think* changing this setting fixed it.

For the system temp statusbar display, can the span#temp be added to div#footer? Currently it's added to span#copyright which doesn't make sense. I want to hide the span#copyright with css but that would hide the temp too.

to elaborate on this, docker-compose is no longer a separate program but is a plugin to docker itself. So that's why it's `docker compose` now - you're passing the compose option to docker.

There isn't good official documentation afaik, but I gave an example in a comment here.

If you're moving a folder named "/mnt/user/media" that has hardlinks to "/mnt/user/downloads", then Unbalance (which uses rsync) will not touch the "/mnt/user/downloads" files, even if there are hardlinks to files in there. The preservation of hardlinks will only happen for files within "/mnt/user/media". Also, hardlinks in general act pretty weird on Unraid and they're not recommended, iirc.

I do agree, but I've run into an unintended effect from the above setting. I didn't realize that was happening until yesterday, and unfortunately my previous posts weren't specific enough for you guys to realize what I was doing. I use this folder structure because I also have a /mnt/user/appdata/docker/compose I use to keep track of yamls, and a /mnt/user/appdata/docker/secrets for docker secrets. Presumably this plugin is hardcoded to exclude any folder named docker, regardless of whether it's the system docker directory, which is why my appdata/docker isn't backed up. Can that be changed so that the hardcoded exclude uses /mnt/user/system/docker/, and not just docker? Or ideally, read the exclude path directly from the unraid docker settings, in order to catch any differences in user settings, rare as they might be.

The point of backing up the docker folder is to backup persistent data that is generated by the containers, not to backup the simple container instructions. You can reinstall a mariadb container from the Apps page, but it won't recreate the database you had previously. The entire reason this plugin stops your containers is so that it can backup the containers' persistent folders in appdata. It even has an advanced option to ignore certain containers that you want to keep running and not backup.

I've noticed that my backups are not including the docker folder. The CA backup command in the logs is odd - it excludes the docker folder with single quotes instead of the double quotes used for folders I've specified. Where is the settings file for CA Backup located? It seems like it has somehow decided to exclude docker but not tell me in the gui. CA Backup/Restore: Backing Up appData from /mnt/user/appdata/ to /mnt/user/backups/appdata/[email protected] CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -cvaf '/mnt/user/backups/appdata/[email protected]/CA_backup.tar.gz' --exclude "mergerfs" --exclude 'docker' * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress CA Backup/Restore: Backup Complete CA Backup/Restore: Verifying backup CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar --diff -C '/mnt/user/appdata/' -af '/mnt/user/backups/appdata/[email protected]/CA_backup.tar.gz' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress

Maybe put in a way for people to choose whether to use the stable version of docker-compose or pre-releases. Stable is 2.0.1 right now, but pre-release is 2.1.0.

I got it to work with local files: labels: - "net.unraid.docker.icon=$DOCKERDIR/czkawka/czkawka-unraid.png" - "net.unraid.docker.webui=https://czkawka.$DOCKERHOSTNAME"

I've installed and rebooted but all I get is the following when I try running "docker compose" or "docker-compose": docker: 'compose' is not a docker command. I see this when I run "docker" [...] Management Commands: builder Manage builds compose* Docker Compose (Docker Inc., v2.0.1) config Manage Docker configs container Manage containers context Manage contexts [...] EDIT: Nevermind, got it working. I'd earlier manually created the cli-plugins folder in my ~/.docker in an attempt to install Compose v2 manually, and it seemed to cause some issues. Deleted it and everything works now.

FYI, the current version of Docker Compose supports both v2 and v3. The recommended way to write compose files is to omit the "version" tag at the top entirely. Compose will then read the yml and interpret all v2 and v3 features.

Thanks. I wish unraid allowed user installation of docker plugins but this will do for now.

Docker Compose v2 is now primarily a plugin for docker instead of a standalone application. The directions on compose's github are as follows: How would I do this in unraid? None of these locations exist in unraid. I see a "plugins" folder in my docker folder but putting docker-compose there and then chmod +x does nothing (I also tried the "plugins/storage" folder and the "plugins/storage/ingest" folder). I also tried creating the "cli-plugins" folder in $HOME/.docker (which is linked to /boot/config/plugins/dockerMan/), but that didn't work either.

I'm trying to set up a registry proxy for the docker daemon. According to the instructions here, it is normally set using a systemd file. I have found that in unraid, simply setting the environment variables in a shell window and then using '/etc/rc.d/rc.docker restart' will properly get docker using the registry proxy. My question is: How can I set the environment variables globally on boot so that the docker daemon recognizes them upon startup? Setting the variables in my go file or in profile.sh does not work. After a reboot, the variable is set (from profile.sh only), but docker doesn't use it until I manually restart it from the command line. EDIT: For anyone else who ever wants to do this, I figured it out. There's a file on the flash drive at /boot/config/docker.cfg. Add the below lines to that file and your docker daemon will use a proxy. export HTTP_PROXY="http://proxy.example.com" export HTTPS_PROXY="https://proxy.example.com"