Squid

One quirk with the OS is that in case of filesystem corruption strange things can happen. I think that after the file system check does its repair that it will come back. If not, then continue on with a new set of diagnostics etc.

Disk 10 needs to be replaced 1 Raw_Read_Error_Rate POSR-K 193 193 051 - 8478 On WD drives, this value should always be 0 But that brings up a problem. The parity drive is currently invalid so I'd check the cabling to it and then replace disk 10 followed by running the filesystem checks against disk 10 (https://wiki.unraid.net/Check_Disk_Filesystems) as it's corrupted, . There may however be corrupted files on the rebuild at the end of this. You should also enable notifications so you'd be alerted to the problems on disk 10 (make sure attribute 1 is monitored)

@SpencerJ @ljm42

32 bit binaries won't work at all with UEFI boot because it requires 64 bit. The same reason why MemTest on the unraid boot menu doesn't work if you boot via UEFI

It does You mentioning 25% and 80% usage suggests that you're confusing what the % that is listed reflects. It is the total CPU usage that the container is utilizing subject to it's CPU constraints

There's currently an issue already reported with the plugin that it will stop working if you have installed an update to the MyServers plugin. Rebooting is the fix

Bad memory Aug 26 18:29:11 unraid kernel: mce: [Hardware Error]: Machine check events logged Aug 26 18:29:11 unraid kernel: EDAC sbridge MC0: HANDLING MCE MEMORY ERROR Aug 26 18:29:11 unraid kernel: EDAC sbridge MC0: CPU 0: Machine Check Event: 0 Bank 7: 8c00004000010090 Aug 26 18:29:11 unraid kernel: EDAC sbridge MC0: TSC 17b040b44b483 Aug 26 18:29:11 unraid kernel: EDAC sbridge MC0: ADDR 1abf19d00 Aug 26 18:29:11 unraid kernel: EDAC sbridge MC0: MISC 50020286 Aug 26 18:29:11 unraid kernel: EDAC sbridge MC0: PROCESSOR 0:306f2 TIME 1630016951 SOCKET 0 APIC 0 Aug 26 18:29:11 unraid kernel: EDAC MC0: 1 CE memory read error on CPU_SrcID#0_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x1abf19 offset:0xd00 grain:32 syndrome:0x0 - area:DRAM err_code:0001:0090 socket:0 ha:0 channel_mask:1 rank:1) The system event log in the BIOS will hopefully identify the stick further

No .sh filename must be the exact name of the container

Problem with putting vdisks onto a parity protected array is that performance will be limited to the write speed of the HDD. If you set up the drives as a cache pool and a single data drive instead then while you would lose redundancy (you'd have to do backups like any other system) you would gain the full speed of the SSD. Alternative would be to use 2x 2TB SSD set up in a redundant cache pool and then use something like a small flash drive as a data drive (every Unraid system requires at least one data drive regardless of how small). Then you would still remain redundant but gain all of the speed.

Wow. TBH I had no idea that torrents were still that popular. It's a testament to how well your VPN containers work.

It would appear that somehow the backup is deleting the contents of /usr/local/emhttp/state

You actually shouldn't need to change the permissions The update script runs the scripts like this /bin/bash /boot/config/plugins/ca.update.applications/scripts/starting/$containerScript This does however require that the script be a valid bash script. For python or something else your starting script then has to call python to execute the script.

Personally, I consider the schema to be an internal data structure as filling out the template will always create a proper xml file. But, I do keep this thread up to date with changes etc. Reasons for fatal errors are either invalid syntax, or something that CA enforces. In your case, (from Template Errors in CA's statistics section) knex666's Repository atlassian/confluence-server: No category entry present No Support Link Present knex666/mopidy:3-experimental: No Support Link Present nextcloud:latest: No Registry entry set. Created from Repository setting knex666/prpdf: No Registry entry set. Created from Repository setting Fatal: Incorrect characters in name No Support Link Present knex666/rssnotipy: No category entry present No container port set. Set to 3247 (Container Port: 3247) alqutami/rtmp-hls: No Support Link Present knex666/shortipy: No Support Link Present kevineye/snapcast: No category entry present No Support Link Present doudou34/tor-server: No Registry entry set. Created from Repository setting No container port set. Set to 9030 (Container Port: ) No container port set. Set to 9001 (Container Port: ) No Support Link Present prpdf has invalid characters within the <Name> entry. Since this is passed directly through to the docker command, CA enforces that the default name will work so as to lessen the support requests because the template as is requires the user to rename the app for it to even install For speedtest, the template duplicated another existing app from the identical docker repository so I flip a coin as to which to remove since there is zero need to have exact duplicated apps present

Still works for me

Yeah, that's actually a bug (minor) in the OS itself which I also noticed about 2 weeks ago and reported it via an internal reporting system. Basically, if an update is listed as being available when you delete / recreate the image (or folder), then the update still shows as being available until the next check for updates. EDIT: This is fixed for the next release of the OS

Any and all port mappings are ignored (by docker itself) when on a custom IP You need to adjust the appropriate settings within the application itself

Aug 7 07:11:05 TheVoid kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Aug 7 07:11:05 TheVoid kernel: EDAC sbridge MC1: CPU 0: Machine Check Event: 0 Bank 7: cc00060000010090 Aug 7 07:11:05 TheVoid kernel: EDAC sbridge MC1: TSC 116fa3060a0e0 Aug 7 07:11:05 TheVoid kernel: EDAC sbridge MC1: ADDR 63182b240 Aug 7 07:11:05 TheVoid kernel: EDAC sbridge MC1: MISC 1401a9a86 Aug 7 07:11:05 TheVoid kernel: EDAC sbridge MC1: PROCESSOR 0:306f2 TIME 1628338265 SOCKET 0 APIC 0 Aug 7 07:11:05 TheVoid kernel: EDAC MC1: 24 CE memory read error on CPU_SrcID#0_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x63182b offset:0x240 grain:32 syndrome:0x0 - OVERFLOW area:DRAM err_code:0001:0090 socket:0 ha:0 channel_mask:1 rank:1) Bad memory

The plugin only supports a single appdata share

Since I'm Canadian, I'll go with this 😀

Not necessarily your problem, but GSkill doesn't list the memory as being compatible with the Prime X470-PRO (I'm a big fan of always buying off of the QVL). Also, regardless of what the aforementioned link states, you should try the speed at 2133 this that's the actual speed of the memory. Also try it without the nvidia plugin installed.

Legacy boot *should* give a stock resolution of 800x600 IIRC. UEFI boot will tend to use the highest resolution your monitor says it supports.

Where did you get the idea that stuff was being stored in the cloud? Only thing being "stored" is a flash backup which is completely optional. The rest of it is to allow easy access remotely to your server (basically a no-brainer reverse proxy to your server) which is also completely optional.

Look in /config/plugins/user.scripts/scripts on the flash drive and change the folder names to avoid special characters and see if that makes a difference

Not sure if it would help, but try setting static DNS addresses (208.67.222.222 / 208.67.220.220) in settings - Network Settings

The big difference between bridge and host/br0 is that you can map any given port to one you decide. Not to say that there isn't value in putting containers onto a dedicated IP but in most cases its not required at all.