meep

A quick web search suggests corrupt disk. Glad it's not critical.

I've found that the most reliable way to get rid of obstinate files is via the command line. SSH into your unRaid system as root and navigate to the directory in question. To see all files, including invisible, with extended info, issue; ls -a -l Then, from within the directory; rm -r -f * (be super careful with that one, it's force remove all files in the current directory, including all files and folders within folders - issuing that in the wrong place can wipe drives) If that doesn't work, you may need more expert guidance that I can give.

Naughty Dockers! Naughty Meep for misconfiguring them!

unRaid can do that. The advantages of going unRaid are that you already know the OS, so the learning curve will be reduced. And you know how friendly and helpful the community can be, if you get stuck Going with something else such as Proxmox or other will also work for you, and you have the opportunity/challenge to learn a new system. If it were me, I'd go with unRaid, mostly because I'd be too lazy to learning something else, and it will just work, mostly. 'Better the devil you know'

Yes, I'll need to trudge through all my settings. I'd find it odd though, that a docker could actually create a share like that.

Bah! Fix common problems to the rescue. it seems I now have both a ‘media’ share and a ‘Media’ share, and that’s the root cause. I have zero idea how that happened though. Will need to conduct some further investigations as I have not created any new shares in quite some time.

Hi folks Stumped by this one. I've seen several similar threads in search, but none of the solutions seem relevant. Today, a significant quantity of files and folders have gone missing from my shares, in particular, my 'media' share (all my movies & music etc.). The files still exist on the disks, just no longer showing in shares. I have no apparent disk issues - all are present and green. I have checked share and global share settings, and no disks are excluded. I have run XFS check on all my array disks with no errors reported. I cannot be 100 percent certain, but I believe most/all of the missing files are located on Disk1. Diagnostics attached. What am I missing??? unraid-diagnostics-20210506-2144.zip

On Amzaon.co.uk, until 31st March

Perhaps you can disable docker? This would allow you to either adjust your unRaid network settings so they don't conflict, or delete the docker image (and force a reinstall) which will give you a window to reconfigure or remove Shinobi. There's a thread here that has info on how someone else did this (for a different reason;

Have you taken the time to edit your vm xml to ensure both the video and audio nodes of your gpu are set to the same virtual bus and slot? UnRAID borks this and can cause to problems like you are experiencing. have a look at the link in my sig for details on this and other things to try.

The behaviour sounds like a situation where the GPUs have been reserved. In this scenario, the boot sequence shows up to a point, but appears to stall. Have you a clean unraid install, or have you ever set any VFIO reservations for passthrough? (if you have, and the n shifted or added devices, the assignments can change and th wrong devices can become reserved).

That should be fine. I believe the recommendations are to give unRaid at least core 0, and alway include core 0 as there is some benefit in that (i'm not sure what). Remember, the above guidance is specifically around isolating cores for high performance VMs such as gaming. If you have a few dokers that are not computationally intensive, you can pin non-isolated cores to them, leaving a bit of headroom for unRaid to take as needed. Also, you don't need to isolate ALL the cores assigned to a VM. You can, say, assign 4x threads to a VM, but only isolate 2 of them. The VM then has two dedicated threads form its exclusive use and two others that may or may not have other tasks assigned. There's also a TON of esoteric analysis on here about performance benefits of assigning specific threads / cores to VMs based on how the CPU is constructed etc. Its as bit over my head, but some peeps seem to have eeked out a bit more horsepower by paying close attention to how core assignment is managed. based on CPU architecture.

@brainbudt , @sbo365web If you switch on the help in the GUI on the isolation page, you will find this; So, when you pin a core to a VM or Docker, that core is allocated to the VM/Docker, but the unRAID OS may still access it and use it for various tasks. When you isolate a core, it is no longer accessible even by unRaid for routine tasks and should therefore be 100% dedicated to wherever it's pinned. You can pin cores without requiring a system restart. You must restart your unRaid server to effect any isolation changes.

Nice. Perfect!

As the multi-lingual aspects get more popular, the activity feed is filling up with incomprehensible posts. Is there a way to add a filter to remove certain forums / languages from the feed?