Goldmaster

First off, I never suggested replacing forums with Discord.
Forums are excellent for long posts, guides, detailed troubleshooting, and anything that benefits from being searchable years later. They’re structured, persistent, and much better for in‑depth support than a fast‑moving chat.
The only point I was making is that forums aren’t ideal for quick, simple questions or situations where the conversation shifts rapidly. In those cases, real‑time chat on Discord can be more practical — but it comes with the downside that information isn’t easily searchable and sits behind an invite link and an account.
A possible middle‑ground is using a Matrix client with bridging. For example, Fedora and MusicBrainz both run Discord, Matrix, and IRC, all bridged together. That way there’s no single point of failure or reliance on one platform, and people can use whichever system they prefer.
That was the spirit of my post — not replacing anything, just discussing resilience and accessibility.

Ok this is interesting as i had created a new vm from scratch and it works fine. If i enable windows sandbox or nested virtualisation, then the open teracopy, the VM crashes. I have found out the issue is due to enabling virtual machine platform in features. Tuned it off and teracopy works fine.

It turns out that windows sandbox is basically a vm and as i have Windows 11 vm running, then enabling sandbox, creates basically a vm inside a vm ie nested virtualisation and teracopy does not like that. It's similar here https://forums.unraid.net/topic/138451-hyperv-nested-virtualization-on-amd-threadripper-pro/ I do wonder if it's kernel thing that needs to be fixed and updated in, however, many months time. In which case I can wait it out.

Well here is something strange and that is after binding the m.2 drive, the array decided to then work and start successfully. However, issues then seamed to start when I tried to tick to add the drive to the VM. but I did notice some additional devices ticked under other pci devices, such as something relating to Matisse and something to do with tpm2 security. So it may be that upon binding, those devices were getting bonded as well as the m.2 drive. It was only upon removing them. That the system decided to work. The only devices that should be showing up under other pci devices is the hard drive, disc drive and Bluetooth module.


So for anyone else with similar issues, ensure there are no other random devices to begin with in the other pci devices and remove them. Then try binding again. Not sure how this came to be, but hopefully a bug fix could be done to prevent such an issue like this.

Well sods law was that I sorted it AFTER posting. I have used the file manager plugin and just deleted the docker folder bit by bit until I had btrfs and another folder, then just deleted them. it was a bit by bit kind of situation. so now my cache drive has gone from around half full to just under a 5th fall on my cache drive. Im marking as solved.

I have tried 6.11 and I am still getting issues. its deafeningly the m.2 drive. I don't know why or how.