ich777

I just switched my build toolchain over to my repository, you now shouldn't need to put that one file into place (Unraid 6.12.10+). If Unraid is detected it will automatically disable the chip check.

Bitte nochmal eine Mail schreiben, evtl ging die Mail nicht durch. Was heißt das on und off? Hast du mal Diagnostics oder irgendwas? Ich benutz mittlerweile das hier: https://www.amazon.de/gp/product/B01N4EUXCU und https://www.amazon.de/gp/product/B077H276GQ Läuft perfekt und die GUID ist eine mischung aus der Seriennummer vom Gehäuse und verbauten SATA M2 SSD. Sollte natürlich auch mit jeder anderen beliebigen SATA M2 SSD funktionieren. Das Gehäuse (in kombination mit der SATA M2 SSD) hat dann immer eine GUID.

I only made a little change to the module itself. When the module/driver is run on Unraid it set's the detect_chip automatically to off/false. This is a global fix for all users and will be working on 6.12.10+ (except for the closed beta so far but I will be recompiling the driver for the latest closed beta too).

Sorry, I completely overlooked your post... I tried it now and it seems to have some kind of issue now, sadly enough I made this game on request and I don't own the game so I really can't test what's wrong... Sorry to have bad news but I'll deprecate the container since it's really hard to troubleshoot for me without owning the game.

Please uninstall the plugin, then remove the .conf file that you've created with: rm -f /boot/config/modprobe.d/qnap_ec.conf then install the plugin again, reboot and see if it is working.

Hmm unfortunate... I'll keep you updated, give me 15 minutes and I think I can upload a custom version.

Please put the attached binary on your server, navigate to it in the terminal, make it executable if not already and execute it: cd /path/to/file chmod +x check_chip ./check_chip Please post the output. check_chip

If possible yes, I‘m curious what Intel-GPU-TOP does on boot.

Can you please do me a favor? Please issue this command form a Unraid terminal: mkdir -p /boot/config/modprobe.d echo "blacklist i915" > /boot/config/modprobe.d/i915.conf After that make sure that Intel-GPU-TOP is installed, reboot, pull the Diagnostics after the reboot and post it here please?

A more recent one, that should support your CPU.

I just read that ASUS for example released a new BIOS where they now improved stability. Don't know if Gigabyte has/will also release a new BIOS. Please also check if you have a option to improve performance from the CPU in the BIOS and disable it.

I'm not 100% sure because this is a game specific question but couldn't you connect through the in game console or via filtering LAN games only or simply by connecting through your servers LAN IP?

I'm not sure if I agree with that since otherwise you shouldn't be forwarding containers. In my opinion it should be safe to put this one VM with it's own dedicated DMZ VLAN on the DMZ (as long as you only put the VM in this VLAN) since the forwarding is done on the Router/Firewall/Switch and as long as your VM running the Mailserver is up to date it should be fine. Sure the VLAN filtering is done on Unraid but that happens on the Kernel level and is part from the Linux network layer which should be considered also safe. That should be in it's own pretty hard since you don't use the Hosts Kernel and is isolated from the Host, but you know nothing is safe, nether VLANs are 100% safe... In my opinion it should be pretty safe and many people run Mail servers in VMs or even Docker containers (which shares the Kernel from the host). This is my opinion on that...

I do that also with User Scripts. Something like: docker container stop CONTAINER1 CONTAINER2 … will do the job just fine... If you need to stop the container for example in 45 minutes you can do: echo "docker container stop CONTAINERNAME" | at now + 45 minutes

Just in case are you sure that your CPU is stable? I heard a lot of things in regards that 13th and 14th gen are really unstable and even crashing on Windows quiet frequently… Please make sure that your BIOS is up to date and ensure that your power limits are under control.

This is caused because you have the WebUI from TVHeadend on the same IP running as SABnzbd. You have two (or maybe more) options: Make sure that TVHeadend and SABnzbd are not running on the same IP address Don't open the WebUI from TVHeadend and SABnzbd on the machine where you manly access the WebUI from SABnzbd (Open TVHeadend in a Private Browser window) (Open TVHeadend in another Browser that you don't user for SABnzbd) ... This is nothing weird this is a known issue.

Anytime.

It can happen but shouldn‘t. Please try the slot that you used before.

Please see here: I think this is a pretty step by step tutorial.

Sorry but I don't see a Nvidia GPU on your PCIe bus. Are you sure the card isn't defective. Please try to reseat the card and make sure that it plugged in properly if it needs auxiliary power.

Also welche USB Sticks verwendest du denn das würde mich interessieren hab hier ein System von einem Kumpel und das läuft schon ca 8 Jahre mit ein und dem selben USB Stick. Mein development system, das bei jeder Unraid version die neue version automatisch installiert für die Plugin packages hat sicher schon 100 mal die Unraid version gewechselt und läuft auch noch immer. Bitte beachte aber hier das ich nur USB2.0 Sticks verwende der Marke Transcend. Welche Sticks kaufst du denn? Das hört sich sehr nach gefälschten USB Sticks an.

Ich nutze den container nicht also kann ich dir da nicht weiter helfen. Ich würde mich aber an den Entwickler selbst wenden wenn im Docker container was fehlt. Google translate, ChatGPT oder Google Gemini hilft.

Bleeding edge hardware on Linux in general is never the best choice, at least when it was just released. I think so, maybe @SpencerJ can put you on the list of testers, would be also interesting to me if everything is working properly. Also check back from time to time in the Announcements subforums or subscribe to the newsletter.

Can you please post your Diagnostics, I'm looking currently into a way to ignore the chip.

You can do it either way and it doesn't matter much. I'm more comfortable pulling it from the source machine to the destination since it feels a bit more safe to me since you can write a script that is running on server start that starts the backup, shuts down the machine automatically if needed and if this machine is only powered on for a backup. Please don't use the root directory, you always have to use the id_rsa from the /luckybackup/.ssh directory not root because otherwise it will be wiped on a container update. Please post a screenshot from your Docker template. Then you selected the wrong keys. BTW You don't have to create new keys, please use the existing ones which are located in /luckybackup/.ssh since they are individually created for each installation and as said above, please don't use the keys from /root/.ssh