Andrew Z

Bear in mind that this has never once been reported before. That throws a monkey wrench into it, along with recycle bin being active, and the possibility that a script or a docker container or something is modifying the permissions on you (due to misconfiguration?) Under ideal circumstances, I'd love for you to upgrade to 6.10-rc4+ The way any bugs get handled on any version of the OS that it's the current (6.9.2 is the current "stable", but not the "current" version) is that they are then duplicated against the current (as of right now rc4 which is public and rc4i which is private). If the issue cannot be replicated under the current, then it is technically already solved. The one thing I'm actually surprised at is that no replies asked you to "prove" the ownership issue (that I see) ls -ail /mnt ls -ail /mnt/user ls -ail /mnt/cache

The problem with the original diagnostics is that there was also an issue in them with the filesystem (which you've now fixed) I would however like you to uninstall the Recycle Bin plugin (and reboot after removing) While I agree with @dlandon that this technically shouldn't be an issue, removing it would help isolate the problem since it removes the recycle bin functionality from Samba

The syslog in the posted diagnostics are basically nothing but the Now that you've fixed that issue, can you reboot replicate your issue again and then post a clean set of diagnostics

Thanks I see it. I've pinged @SpencerJ to look into this (I don't have access to the billings / activation code side of things)

Should be there. Check junk / spam folders. If not, contact us.

Did the email arrive with the activation? Here is a video on activating: https://wiki.unraid.net/Articles/Frequently_Asked_Questions#How_to_Redeem_a_License_Activation_Code: If the email didn't arrive, then contact support https://unraid.net/contact with the details (attach invoice etc) Andrew

All done @dRuEFFECT

Please do not directly post links to copyrighted material here in the forum. Your post has been edited to remove the link as this violates the terms and conditions of the forum Andrew

I think the above posts could have been handled (or worded) a bit better and that it's primarily just some frustration that leaked into the posts. But, in the future just bear in mind that the wording which was used isn't particularly acceptable in this venue.

Trial keys cannot be transferred (Paid keys do not have this limitation) After setting up the new key you will have to assign your disks etc and restart your trial period

https://unraid.net/contact We'll be able to tell you exactly why (Include a copy / paste of Tools - Registration after you boot up with a Trial licence on that device)

No request have ever come through -> I saw the conversation and looked you up. Usual time to do this (depending upon time of day) is 15 minutes to 12 hours Set up the replacement key. If you can't use the automated method, https://wiki.unraid.net/Manual/Changing_The_Flash_Device then unraid.net/contact with a copy & paste of Tools - Registration. No screenshots

What do you mean by "Waiting ...." Have you already transferred a key or are waiting for support to transfer it?

Easiest method is to use the MyServers plugin to automatically create backups as the flash drive changes. Then to get the backup you just log into the forum, MyServers page and download the backup. Via the Automated key transfer system the key could get done in a matter of seconds. If the automated system doesn't work for you (eg: too many transfers done in a year), then Limetech support needs to get involved to transfer it for you. Depending upon the time of day, the response can vary between a few minutes to a couple of hours though (but it is getting faster all the time)

One other thing to look at would be the TDP limits in the BIOS. Most motherboard manufacturers on the 10th Gen series set the TDP limits for the CPU to be 4096W or "auto" which is effectively an unlimited amount of power. For best stability you should set the TDP in the BIOS appropriately: 65Watts Also you should look at running memtest from the boot menu for at least a full pass or two

Is there a forum posting detailing what issues you were having?

The one thing I see right away in your diagnostics is that "macvlan" is being listed as a module being run. Some users have issues (crashing etc) when using macvlan for asigning static IP to docker containers and for this reason, Unraid 6.10+ support ipvlan (Settings - Docker) as it is a more stable solution. These crashes could have resulted in the corruption that you're also seeing on the drives If / when you decide to try 6.10 again if issues happen try switching the network driver A

Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz With the 10th Gen series and Intel's new features relating to turbo boost, the motherboards all started playing games with how they set up the defaults in the BIOS in order to gain them a slight edge in benchmarks performed by the various reviewers. They did this by instead of following the specifications of the chips for thermals, they would have the BIOS setup to assume that you're running a perfect cooler that can keep everything absolutely perfect under all circumstances etc. TLDR: It's probably a very safe bet that Asus has set up the BIOS for the TDP's to indicate "Auto" This setting *implies* that it uses what the chip says it is (in your case 65W). In actual practice, the Auto setting here indicates an "Unlimited" TDP setting (or 4096W). They do this because it gives the motherboard a very slight edge in benchmarks and they count on the CPU being able to appropriately throttle itself in order to protect the system from inevitable China Syndrome. The net result however is that you're inherently running a massive overclock on on the CPU when under load (such as shutting down VMs), Many users have found with the 10th Gen series that stability is terrible (across all platforms), with very similar symptoms as what you're seeing. Go into the BIOS and set the TDP thermals accordingly (ie: set it to 65 Watts or less) and then see how things go. See here (and the video) for some more information

Was the new VM pointed to the original VDisks or created by copying and pasting an xml or was it basically a stock VM as a test?

Huh. Try just leaving the name alone and switch the share that it's in. (It seems to work changing the name occasionally. I have to investigate why on that one)

I wonder if you can try something. Can you stop the VM service via Settings - VM Manager. Once it's stopped, switch to Advanced View and change the name of the libvirt.img file (ie: call it test.img instead) Restart the service and see if you can't add a VM now (NOTE that none of your existing VMs will appear because we've set the libvirt image to be something else) It's not going to solve you problem, but it will narrow it down. A

All done!

Done

Or email support if the forum isn't given you the answers you need.

All done