• Content Count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About HectorG

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Bit more insight into this issue and a fix for startup.nsh uefi shell appearing constantly :
  2. 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.
  3. Ok I fixed the issue (I have same issue as yourself) Rachid told me to use a special bootloader modded bios (clover) iso file as the primary vdisk instead of it being set to none(space invader made it in his video and shows same thing), then you can tick the nvme drive in other pci devices as normal and also click the + sign under primary disk to add 2nd vidsk such as unassigned disk or other drives as normal. This forces windows 10 template to boot off the nvme drive using the modded clover iso, startup.nsh is gone now. Here is the link to info: Hopefully this
  4. Thank you very much rachid596 ! (and to space invader) it worked with that modded clover bios bootloader iso file. Instead of adding primary vdisk location = none, I chose manual and selected the clover bootloader.iso (download link in space invaders vid above) then I clicked + sign to add my 2nd vdisk location and selected my unassigned disk as normal (or add any other hdd or device) Booted it up several times to make sure but no more startup.nsh error. Unraid does save the bios savings what I found was setting primary vdisk to none (to pass through the nvme drive
  5. thanks I did see this video a while back but noticed maybe this is relevant to older unraid builds, the ytube comments suggested using a clover bios was not required anymore since the ovmf bios can support uefi and nvme boots (although I think its buggy since it wont save after a reboot). Still I will give it a try since this issue still exist as noted also over here these guys modded the xml to tell it to boot directly off the nvme drive but some had issues with passing through other unassigned devices. https://forums.unraid.net/topic/83515-forcing-boot-order-w-nvme-pass
  6. Hi did you have any joy with this issue ? I still have this issue sadly to me it feels like the bios is not saving the boot order, when you get startup.nsh shell error and type exit and change boot order and save it, it 100% saves since if you click resume/continue it boots to your nvme drive but..... if you shut down and restart it defaults the original incorrect bios. To me it almost feels like a bug in the vm virtual bios regardless of q35 or i440 etc I posted here also: Some suggested using a clover modded bios, never heard of this but will also tr
  7. 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 edite
  8. I have a strange issue with VM windows 10, I am running VM directly off an internal nvme ssd (with windows 10 already) Nvidia gpu pass through all works well but I get the startup.nsh bios message each time I start the vm. I can type exit, select boot manager and select my uefi nvme intel ssd and it boots fine to windows and runs well but obviously it's not nice to do this every single time I switch on Windows 10vm. I have already tried to delete the boot order entries and leave just my uefi nvme intel ssd as the only boot device or like the first or only boot device to
  9. 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.
  10. 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
  11. 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
  12. 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.
  13. 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.
  14. pretty good video here: I currently am having usb controller issues (its possible but bit tricky to isolate and pass through-needs some work) since I am new to unraid I may actually just get a usb 3.0 pciexpress card there cheap and since it's an separate device should be more headache free, I too have issues with my usb soundcard dac/amp sometimes does not get detected even despite being listed in device manager or no power. I recommend getting one with additional power to help drive powerful usb devices.
  15. 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 ?