Hello all,

 

I've upgraded my Gigabyte Z490m motherboard to an MSI Z490.

 

Everything was working fine, however since the change whenever I reboot, I get a blank screen, no flashing cursor, no bios, nothing. If I restart and enter the bios however, make no changes and then exit and continue to boot, UNRAID starts with no issues.

 

I have checked the bios and UEFI boot is selected (I've tried without also however makes no difference). My UNRAID usb is set to boot via UEFI.

 

On a side note, I did have an MSI GTX 760 passed through to a VM, however as the new MB does not have any video out capability, I have moved the card to a bottom slot and will use for bios access. I have an MSI 3090 coming tomorrow and would really like to iron out this minor setback beforehand. 

 

I've looked on several pages with similar issues, however nothing seems to fix it. Would changing my UNRAID USB from UEFI to Legacy help, and if so is it a simple matter of putting "-" after EFI in the folder name on the USB? 

 

Any ideas would be greatly appreciated. 

 

 

 

Edited January 15, 20215 yr by LoneTraveler

sorry have not got an answer for the issue, I am having the same issue with my recent built on B460, first reboot-unraid is fine subsequent reboots shows a blank screen and unraid server does not come up, unless until I go into BIOS do nothing save and exit

 

what i can add is i had initially set USB to non UEFI and it ddin't boot into unraid at all, i had to change it to UEFI to atleast get first unraid boot but reboot same problem occurs

Edited January 14, 20215 yr by unraid_2021

1 hour ago, unraid_2021 said:

sorry have not got an answer for the issue, I am having the same issue with my recent built on B460, first reboot-unraid is fine subsequent reboots shows a blank screen and unraid server does not come up, unless until I go into BIOS do nothing save and exit

 

what i can add is i had initially set USB to non UEFI and it ddin't boot into unraid at all, i had to change it to UEFI to atleast get first unraid boot but reboot same problem occurs

 

I'm sure I read that both the bios needs to be put into non-UEFI mode (in my case CSM) as well as the UNRAID USB being altered by way of editing the "EFI" folder on the stick to "EFI-", however I am yet to try this until someone can confirm. 

 

On a side note, UNRAID will boot for me if I physically power off the machine and switch it back on, I don't need to enter the bios, which beforehand I believed I needed to do. Unfortunately however, rebooting still brings me to a blank screen and no UNRAID. 

so I tried some settings on my MSI B460 Torpedo motherboard which looks like fixed the issue i have tried multiple reboots from webUI and unraid is starting up correctly without going to BIOS. 

 

1. click settings 
 

 

2 Access Advanced

 

 

3 Power Mgmt Setup

 

 

4. DTM - I changed it to Enabled

 

 

 

5 Save changes and reboot

 

 

 

this did the trick for me. Why this approach work I don't know may be someone can throw some light on it

I'm glad you were able to sort the problem out on your system, unfortunately for me I do not have a D.T.M option. Even using the search feature does not bring it up. 

 

Oh well, looks like I'll keep looking. 

 

 

will a BIOS update help ?

https://www.msi.com/Motherboard/support/MEG-Z490-GODLIKE

1 minute ago, unraid_2021 said:

will a BIOS update help ?

https://www.msi.com/Motherboard/support/MEG-Z490-GODLIKE

 

I was just wondering that myself, especially as this board hasn't been updated in several months. 

 

Many thanks, I'll give it a try. 

21 hours ago, unraid_2021 said:

will a BIOS update help ?

https://www.msi.com/Motherboard/support/MEG-Z490-GODLIKE

 

It worked! 

 

A bios update gave me the D.T.M option. Once enabled, the machine can restart and boot into UNRAID. 

 

Many thanks for the help! 

Edited January 15, 20215 yr by LoneTraveler

Excellent

Thanks @unraid_2021, The DTM setting save my MSI MEG Z590 Ace.  Had same problem on reboot.

Just an FYI, if anyone has issues with VMs possible IOMMU groups may have changed. May have to rebuild it using the same vdisk