Squid

You've wound up with a duplicated docker.img somehow (its hard for me to replicate that circumstance) To solve, Settings - Docker. Disable the service Check off and delete the image From the command prompt (or terminal button) rm /mnt/user/system/docker.img Settings - Docker. Re-enable the service Apps Tab, Previous Apps Section, check off all of your apps you had installed previously, and then hit the Install Multi. A minute or two later, and you're back in business

Nope. It only ran as often as you had FCP scheduled to run (in this case it was weekly) I would guess that when you originally set up your system you did not have a cache drive, started playing around with docker apps, and then added a cache drive afterwards. My reasonable guess is that your docker.img file is sitting on disk 1 (currently sdc) DOCKER_IMAGE_FILE="/mnt/cache/system/docker/docker.img" # Share exists on cache,disk1 Stop the docker service (settings / docker) and the VM service (settings VMs). Then go to Main, Array Operations, Move Now. Refresh the page every once in a while and when mover stops running, re-enable docker and vms

Feb 02 14:08:06 CREATE => /mnt/disk2/1114683235.tmp Feb 02 14:08:06 OPEN => /mnt/disk2/1114683235.tmp Feb 02 14:08:06 OPEN => /mnt/disk2/1114683235.tmp Feb 02 14:08:06 DELETE => /mnt/disk2/1114683235.tmp This is from Fix Common Problems running a scan. You can have it set to avoid spin ups to stop the tests on drives which are spun down.

delete that file on the flash drive

It's not installed. I just tried a reinstall on my system, and there's no problem. Maybe try a reboot.

https://forums.unraid.net/forum/53-feature-requests/

I would also post a feature req for LT to add in the appropriate drivers to unRaid

Preferably an Intel

Doesn't look like unRaid has the driver for the ethernet. 07:00.0 Power PC [0b20]: Freescale Semiconductor Inc MPC8308 [1957:c006] (rev 10) Subsystem: Bigfoot Networks, Inc. Killer E2100 Gigabit Ethernet Controller [1a56:1201] Not sure if it supports the "Killer" NICs You have another add-on card you can try instead?

Log in as root, and then diagnostics power down powerdown and then put the flash drive into a desktop / laptop and post the diagnostics file (logs folder from the flash drive) that you just generated

I'd consider replacing disk 2 197 Current_Pending_Sector -O--C- 100 100 000 - 48 198 Offline_Uncorrectable ----C- 100 100 000 - 48 As for the flash, as mentioned try a different port, preferably USB2

yes

Looks like your flash drive is dropping offline. Try a different port. Ideally USB2 Looks like your disk 2 is dropping offline, causing the read errors (and presumably it being disabled). Could simply be a crappy connection to the drive / port / power As @Frank1940 said, we'd like to see your diagnostics.

Did you hit "exclude selected"? IE: Works for me. BTW, if you're just looking at fixing the media share, you can just go to Tools - New Permissions and run that strictly against the media share.

Normally, I don't pump out an update for something this minor, but since I don't have anything else queued up for updates on the plugin, I've already done so.

I think the point is that nowhere does it say that it's a cron entry it's looking for in the field.

Semi-recurring issue throughout the 6.x series *IF* the webUI is busy doing something else, this will happen.

Thought about a generic backup plugin, and ultimately decided that something like Duplicati is better for that.

0 * * * * for the top of the hour, every hour But, hourly is extreme overkill, and daily should be sufficient

You can get rid of that "ubooquity/admin" in ubooquity's settings, which winds up solving your problem.

Jan 21 10:49:02 Tower kernel: EDAC MC0: 1 CE memory read error on CPU_SrcID#0_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x1173e8 offset:0xc00 grain:32 syndrome:0x0 - area:DRAM err_code:0001:0090 socket:0 ha:0 channel_mask:1 rank:1) You've got a bad memory stick. The event log in your BIOS will probably help you narrow down which one

No. Workarounds though would be limiting the share to only exist on a specific drive and/or an unassigned device.

I *think* I have that test in there due to what happens on a restore. A fail-safe because when restoring, any excess files from the source are deleted. (and also to prevent a source and destination overlap)

Ok. Looks like I lied. Must've had a reason that I set the plug-in like that, but can't think of why right now. 🤔

Try the ControlR app available in the Appstore on your tablet (and the companion plugin for unRaid)