Squid

Try lowering your split level on the media share (TBH, split levels confuse the hell out of me )

Didnt space invader one do a video on that for a joke.

Not unless linux server creates a template for it (which they have not)

You're allow 6 attached storage devices on basic, and you've got 8 excluding the flash drive Oct 19 10:36:16 Zeus emhttpd: WDC_WD30EZRZ-00Z5HB0_WD-WCC4N0LF45L1 (sdh) 512 5860533168 Oct 19 10:36:16 Zeus emhttpd: Samsung_SSD_860_EVO_250GB_S3Y9NF0K222430B (sdg) 512 488397168 Oct 19 10:36:16 Zeus emhttpd: ST8000DM004-2CX188_WCT3J3A7 (sdd) 512 15628053168 Oct 19 10:36:16 Zeus emhttpd: ST6000VN0033-2EE110_ZAD7N41T (sde) 512 11721045168 Oct 19 10:36:16 Zeus emhttpd: WDC_WD50EZRX-11NWHB1_WD-WX31DC45TNU3 (sdf) 512 9767541168 Oct 19 10:36:16 Zeus emhttpd: ST6000VN0033-2EE110_ZAD7MFKF (sdc) 512 11721045168 Oct 19 10:36:16 Zeus emhttpd: ST3000DM008-2DM166_Z503J4HA (sdi) 512 5860533168 Oct 19 10:36:16 Zeus emhttpd: TOSHIBA_TOSHIBA_USB_DRV_07087A1EAD549849-0:0 (sda) 512 30285824

Try clearing your browser's cache

You edit the app on the docker tab, and select a new IP address for it

Assuming you've named it the exact same, then no.

Probably because fragmentation isn't a real huge problem on modern file systems, and the speed of drives lessens the degree of the impact. People are so used to "You have to defrag your drives to solve Windows problems" which was always completely false.

Don't see any problems there. Can you also add in your diagnostics

You need to post your diagnostics and attach the complete file here

Post the applicable xml from /config/plugins/dockerMan/templates-user on the flash drive for the app you're trying to adjust

Fixed next release

It isn't fixed. Simply that it will now use whatever you set on beta30.

Open up a new thread in General Support and include your diagnostics file (Tools - Diagnostics). This is not related to CA, but rather an issue you're having with either the docker image or the cache drive.

Oct 13 02:02:40 BB-8 kernel: EDAC MC0: 1 CE memory scrubbing error on CPU_SrcID#0_Ha#0_Chan#0_DIMM#1 (channel:0 slot:1 page:0x941686 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:0 ha:0 channel_mask:1 rank:4) Bad memory. Your BIOS' event log will probably have more information beyond Channel 0, Dimm 1

Oct 16 20:17:20 UnRaid kernel: EDAC MC1: 1 CE memory read error on CPU_SrcID#1_Ha#0_Chan#1_DIMM#0 (channel:1 slot:0 page:0x87fa42 offset:0xcc0 grain:32 syndrome:0x0 - area:DRAM err_code:0001:0091 socket:1 ha:0 channel_mask:2 rank:0) Bad memory. You BIOS' event log will probably have more information on which one other than Channel 1, Dimm 0

The more info link always goes to the dockerHub page. From there you can get to the GitHub page if need be. (IIRC, the GitHub link on the dockerHub page is generated by a script running on the page and cannot be scraped at all) Same thing with your base image link. Even if the dockerfile appears, its generated by a script and cannot be scraped to get the base image.

It does in 6.9-beta29+

It's from a docker container. Stop one at a time to see when it disappears.

Actually, when the notification is on screen (with the Clear All), those icons don't work then either....

Not related to Fix Common Problems, and ideally belongs in the CA thread, but odds on Pf-Sense is blocking the server from hitting GitHub.com. If you want to help me diagnose why you're seeing that particular message instead of the one you're supposed to see (ie: I can't replicate that message coming up in the same circumstances), see this: https://forums.unraid.net/topic/38582-plug-in-community-applications/page/128/?tab=comments#comment-899908

No reason what so ever that it should be gone. Try a reboot?

Top of my head, I'd say those errors are from custom networks you had defined. What I would do is stop the service, delete the image again, apply. Reboot then try it again.

I'm not a VM guy, but have you tried "stubbing" the card so that Unraid won't use it? (install the VFIO plugin to make things easier on 6.8)

The probable reason is that your image is filling up. BTRFS doesn't handle that situation very gracefully (luckily is rather immaterial for docker). There's multiple entries for the image filling up in the docker FAQ here.