HectorG

Hi I am new to unraid was trying to get my GMKtec G9 nas (Intel N150 with 2x intel i226 ethernet) wattage down since its currently 25 watts idle. I tried the commands from page 1 here Ran the commands from inside unraid terminal, and ran: powertop --auto-tune &>/dev/null This just causes my system to hang, have to hard reset the GMKtec G9 nas. I am just wondering do I need to do some bios tweaking or enable some bios features before running that powertop command? tuntables option shows bad states still. The only one that worked was the setting powersave on the cpu governer, but that did nothing for saving power.

thanks much appreciated for the quick replies😀

Thanks, so just for an example if I tried raidz1 I would have to use 1 NVME drive for an parity drive and than have 3 NVMEs left for storage? I am wondering how the speed difference would be in general usage between the ZFS pool vs the RaidZ1, but I guess I can set them both up and give them a bit of testing and find out copying some large video files over maybe with nvmes the speed difference might not be much difference.

Hi I have an cwwk mini nas box, which comes with 4 x nvme slots. I have just purchased 4x WD Red nvme NAS drives and plan to install unraid on it. I have watched several YT videos and read some of the installation set ups/guides but am a tad confused with the general set up (never used unraid) I would like encryption to keep my data secure, its for general storage of documents, movies/music, pictures and downloads and family back ups. The data will be backed up regularly with a portable hard drive and the data is not critical if it gets lost, so not really concerned about back up more about using the full space available to all the 4 x nvme drives. I have read since its an all NVME drive setup, I should use an ZFS pool, is this the best method? Since its not an unraid array, can I skip the parity and cache drive and stick with the ZFS pool with 4x nvmes? Are there any other recommendations to use with an all nvme setup unraid setup? thanks

probably not of much help but usb controllers seem to be hit and miss for many (espeically amd ryzen owbers) and even then it feels usb controllers even when in seperate groups appear to still be sharing from the other usb controllers on the mobo causing other issues and instability. I see why space invader vid he just bought a usb controller card and passed that through so reduced the headache, gonna do same shortly.

These may not work since I am new to unraid but I did have the error 43 myself, try these: I had to disable Legacy bios or CSM in the motherboard bios then the error 43 went away and my Nvidia card worked fine. GPU pass through does not work with those it has to be UEFI bios only, also when creating your VM template in unraid do not use seabios since its legacy/csm mode (so wont pass through gpus) it has to be set to OVMF only since that supports UEFI bios and GPU pass through. You should also use your correct gpu bios of your gpu card and make sure it's been edited correctly, otherwise if it's not been edited it won't work either for pass through. Ytube space invader has the vids for that and shows you how to edit the rom file. also this may not help but I did all the above and had a blank screen when my VM started I followed jt rippers instructions here: and applied a script fix, this allowed my gpu to display and work also. Again not sure if it helps but maybe worth a look.

Had this exact error and then figured since the nvme drive is enabled and checked within the vm template to just go back to that busted or bad VM template and then uncheck NVME drive in the other pci devices section or just uncheck any usb or pci express devices and hit apply. Now you should be able to simply delete the vm without any error message. Unraid is so logical that if you try to 'Windows' it, it won't forgive you for being stupid and it will just tell you off, but if you think like spock unraid just works.

Well was just about to post my cure to the deadful nvidia code 43 error but Dangerous above posted it. I too have an 3800x AMD system and Nvidia card, I had switched to CSM to fix unraid gui getting a blank screen but when I ran the VM win10 it came up with code 43 and a giant screen. Luckerly I recalled I changed that bios setting since it was working last week fine so knew switching CSM in my bios to OFF was perhaps going to fix it and it did. Something to note however is not all bios of mainboards call it UEFI mode or Legacy mode anymore, my motherboard calls it CSM which I believe is legacy mode. Looking back on the last 4 pages id bet the whole UEFI, Legacy, CSM mode is causing the code 43 error so give it a try I believe its due to Windows 10 and gpus being installed via UEFI mode and not legacy/CSM.

It 100% is for myself, I have watched probably 20 space invader vids and read many pages on the forum (probably overkill in terms of newbie) and just feel I have spent more time trying to get the flash stick set up correctly then using unraid itself. Even with the above hackery to rename to UNRAID it did not work for me, but then I noticed it is my fault or the unraid wiki is not fully clear, the Manual method of creating the unraid stick (copying over the zip etc) only works if you are in legacy bios mode, my bios does not have any legacy mode written anywhere but then I found its also known as CSM. So I disabeled CSM and the stick boots fine. The only issue is I can't have CSM enabled since when I pass through my GPU on my VM I discovered I get the dreaded Code 43 gpu fault but switching off CSM in bios my gpu can pass through the nvidia card fully without error (I will update the code43 thread with my findings may help others) So I still remembered others on here used a old pc, tried it on a 10 year pc and unraid creator created it perfectly on a sandisk usb stick and the corsair! So only took 3-4 weeks to fully get a usb stick running. I also read usb2.0 flash are more reliable but I used a magazine freebie one and while it passed multi write read/write test, I think its a dodgy stick maybe the cheap or free ones are a reason ! so ill digress and say cough up get a good quality flash drive. Its perhaps a bit of old guides getting out of date, seems UEFI, Legacy/CSM and usb3.0 flash are also problematic, maybe its better to flash on an stick on an usb 2.0 port on a 10 year old computer. Really at this point I just want to see if unraid is stable enough to move full time, which I believe it is.

ran into this issue also but sure enough as it hangs on sync I went back to windows explorer renamed pen drive to UNRAID and it began copying correctly. I ran the unraid usb creator as admin also but still had to do the above.

Oh thanks I must be mistaken, thought I heard of hotter temps with AMD cpus and unraid good to hear this is not the case.

Hello I am new to unraid and just read this excellent post, I own a AMD 3800x and Asrock 570x mobo so think I have spotted some of these issues (mainly trying to vfi onboard sound to win10 vm crashing it and crashing unraid), I think I can avoid the onboard audio (I use an usb external soundcard) and can get a usb controller seperate card to solve any usb pass through issues. Is there a problem with unraid and AMD cpus/X570 with hot cpu temps or is this false temp readings ?

big thank you to Endy, I have a AsRock X570 mobo and these settings will be handy since am very new to unraid. I, too, noticed after doing further bios updates the iommu grouping was better asrock are doing a good job of releasing newer bios so far. But I think I still ran into sam usb controller issue you mentiioned and had tried all 3 but the other 2 did not work (just hanged the vm and crashed unraid) the separate one works better but has been a bit iffy sometimes does not detect my usb soundcard rarely (creative X3), and since the other 2 usb controllers hanged vm when I used the vci plugin I think I may just get a usb 3 separate card instead to reduce headache. I noticed you used machine Q35 and also a non uefi unraid pen flash, does this give better stability ? Either way I will re-read your guide, I currently have a VM running Win10 successfully but think once I got the seperate usb controller sorted and I use a usb sound card I should be more solid. Also, worth mentioning it's a good idea to enable "VFIO allow unsafe interrupts" under VM advanced tab settings, this solves the usb issue if you are hot swopping devices and won't hang the vm and crash the unraid server.

Query for CS380 owners : did owners consider trying to use 140mm > 120mm fan adaptor converters on the inside of the hdd cage (2 fans)and even maybe on the outside of it (bottom (intake) and one on back(external) you could mount the fan on the outside maybe. 140mm fans have better air flow and the improved silence, so this maybe worth a mod.