R620 takes forever to boot. Slow at the BIOS screen.

Hello

Did you see any messages on the screen prior to slow down? Enter the BIOS set up using F2 and check to makew sure that Memory Testing is disabled under Memory Settings. Memory testing can slow down the boot process

Doesn't the memory check happen during the part that says Checking Memory?  That's not what I'm posting about.  See the screenshot.

The best way you can figure out this issue, quickly, is by taking a boot trace using the free Microsoft troubleshooting tool (Windows Performance Toolkit) https://developer.microsoft.com/en-us/windows/hardware/... Here is a tutorial on how to take a boot trace. https://zinetek.wordpress.com/2015/12/16/how-to-use-wpr...

Share the boot trace, and I'll help you analyze it. there is a big chances we can find exactly what is causing this issue..

I use this tool every time when I encounter Windows Perfomance issue, it's very powerfull. https://zinetek.wordpress.com/2015/12/19/windows-7-slow-logon-troubleshoot/

Just found that our Memory Testing is already disabled.  I'll look into the above program.  I just rebuilt a second R620 and it too takes forever to get past the Bios screen.

It involves re-installing the operating system and as such you will need to backup your data first and restore after OS is installed. It is a tradeoff, you can still wait a little while for the server to boot and post instead of going the other route.

OK, so when I get stuck at the Dell screen, if I press the Spacebar, it then tells me: Memory tests terminated by keystroke.

This response is typical of Windows Server 2016, which I presume you are running because it manually overrides the memory settings specifically Memory Testing defined at BIOS level while searching for secure  Memory Overwrite Request (MOR). MOR  feature is not available in 12 Gen servers including R620 and as a result causes the memory testing to proceed. Switch to UEFI mode in order to keep memory testing disbaled.

OK, so when I get stuck at the Dell screen, if I press the Spacebar, it then tells me:

Memory tests terminated by keystroke.

However, when I go into BIOS, it says that the memory tests are disabled.  Is there somewhere else to turn off these mysterious Memory tests?

Are there any other differences that we'd need to be concerned with if we change to UEFI mode?  If the only thing we'd gain is to save 5 minutes during a boot it may not be worth it.  If there are other things we'd gain, then we'd consider it.

Also, do we need to do anything else in order to change modes?  Does it require rebuilding the machines or anything like that?

Thanks!

I have 4 R820's and all of them do this exact same thing.  I found this post after installing the first two, so when I did a cluster upgrade to 2016 I decided to change to UEFI. 

I can tell you that the two new servers have this exact same issue, so I would not recommend changing to UEFI just to fix this issue. 

As soon as I can I will take a screenshot and provide it, but for now it appears that this solution WILL NOT work. 

We're rebuilding some additional servers and are doing everything with UEFI now and still have the memory checks running at every boot.  Anyone ever get this figured out?  I don't know how the server OS would have anything to do with this since the memory tests fire up before Windows is anywhere near loading...

I know this was posted a while ago but I need to bring it up again.  We are installing Server 2016 on a number of servers and they are no longer skipping the memory test at book like we have them set to do in System Setup.

The first one I did we were using BIOS instead of UEFI and someone here said that was the cause.  Well, now we're using UEFI and have the exact same problem.  It adds 5-10 minutes onto rebooting a server because of the long wait.  If I press the spacebar it will tell me the Memory test was cancelled and will boot normally but for remote servers, that's a pain to do every time.

Does anyone know why this happens and if there's a way to make it skip the test like we tell it to?

Not sure why the response saying to switch to UEFI mode was marked as the solution when I specifically states we are using UEFI mode now and still have the memory test running.  Is there simply no solution for this at all?

Hi,

Please send a private message with your service tag to ensure we have all appropriate information on your system.

Thank you,

Hi,

Please send a private message with your service tag to ensure we have all appropriate information on your system.

Thank you,