[New Motherboard - Won't boot from Unraid USB]

On 10/1/2022 at 7:20 PM, Hoopster said:

In the BIOS boot order is your flash drive called UEFI:{brand of flash drive} or something similar?

 

Some recent ASRock (and other brands as well) boards will only boot UEFI and not legacy.  On your flash drive, if there is a folder named EFI- that means it wants to boot in legacy mode.  To tell it to boot UEFI, rename the folder to EFI (remove the trailing - character).

 

OMG Thank You!!!  This needs to be put SOMEWHERE in an upgrade sticky.

 

THANKS!!!!!!

[[Support] selfhosters.net's Template Repository]

On 3/11/2022 at 10:26 AM, Douglas_D said:

Hey,

 

Hopefully you were able to figure this problem out, but in case you haven't, or others are searching for a fix, I had this same problem when I started up with zwavejs2mqtt. I found out I didn't have the appdata and zwavejs log folders set in my docker image. Make sure you go to advanced view and expand out the "more settings" section to get the appdata section to show. If it doesn't show up, click "Add another path, port, variable, label, or device" and add a new path as shown below. 

 

Good luck.

OMG Thank you so much!!!!!!!!!!!!!!!!!!!!!!!

[Nvidia mapping multiple BARs reported in LOG.]

Those log entries have ceased.  So one of those things above fixed it.  Either an update or turning on the iommu. 

[Nvidia mapping multiple BARs reported in LOG.]

I haven't. I actually forgot about it as I finally got the system to stop freezing.  However just this week I encountered another freeze.  Can't get to it tonight but I'll try to see if it's still posting those to the log tomorrow. 

 

Things I've done since though that may have changed things - updated the nvidia driver. Updated the gpustat addon.  Turned on iommu in the bios (that was a pain to find) and passed through the GTX 950 to plex docker for transcoding. 

 

I have no idea what the lockup was about this time but it had been up over a week this time.  

[Nvidia mapping multiple BARs reported in LOG.]

Wow. Thanks for the in depth answer.  I HAVE been experiencing lock ups.  Which is the reason for the updated BIOS.  I have been searching for the low power idle setting and just can't find it. Updated the BIOS trying to see if the option was added.  I guess that was a mistake.  Just found that same thread yesterday.  I did disable the global c state control.  

 

I hear you on the advice that it is not necessary.  However I am just going to see if I get the lockup again.  Hard to try and wait each change since it takes so long for the lockup.  I am on the road all week and just have to deal with it bit by bit when I get through to the house. 

[Nvidia mapping multiple BARs reported in LOG.]

Occurs every second or so.  Trying to catch why my Ryzen system is crashing.  Noticed this.  Is this a concern?