1 Rookie
•
6 Posts
0
935
September 28th, 2022 07:00
T420 3 hour boot time
Hi! I just got a T420 from my work and it has around 17T storage installed, 192gb ECC Ram installed and 2x 2.20 GHz Quad-core intel xeon installed, now it worked fantastic at work but now when i try to boot it at home it takes around 3 hours just to get passed the initilasation screens where you see whats on the system (bios boot i think people call it). and even after 3 hours when it enters me flash drive where i have my bios (unraid) on it says auto launching in 5 seconds... and tics down 1 second maybe after 2 minutes so takes around 10 minutes for that to fully launch and then nothing happens (and yes i have timed every boot), any idea what could cause this? i also had an error saying "BAT0015 Low perc battery" and could that be the reason why the boot is so insanly slow and non functioning?
AceBoyden
1 Rookie
•
6 Posts
0
October 10th, 2022 05:00
After alot of fiddling around and testing hardware i came to the conclusion it was a faulty raid controller, i changed it out with one of my old ones and boom boot took around 3 minutes with no errors.
AceBoyden
1 Rookie
•
6 Posts
0
September 28th, 2022 07:00
It has been on this page alone now for 28 minutes
DELL-Chris H
Moderator
•
9.6K Posts
0
September 28th, 2022 12:00
AceBoyden,
We don't normally support performance issues, but I don't believe it is the perc battery, as its function is to supply power to the controller long enough to save the cache data to the controller during a power outage or such.
What I would look at is if the server is up to date on the BIOS, iDrac, Raid controller, and drives.
Also, in order to possibly help speed up booting, you may want to access the iDrac and disable Collecting System Inventory on Restart.
Lastly, have you run any diagnostics on the server yet?
Let me know what you see.
AceBoyden
1 Rookie
•
6 Posts
0
September 28th, 2022 19:00
Hello,
I disabled Collecting System Inventory on Restart in lifecycle controller (couldn't find it in Idrac 7), i checked all software versions and all of my stuff is all up to date, ran system diognostics (the really in depth one aswell as the basic) and no errors came up and everything was fine and good.
After all that i did another boot and same is still happening
DELL-Shine K
4 Operator
•
3K Posts
0
September 28th, 2022 20:00
Did you start seeing this boot time issue after adding any components to the server? You can configure the server minimum to POST and check the boot behavior. Minimum to POST configuration is the configuration that has the minimum components required to complete POST. Typically, the minimum to POST configuration is PSU1, CPU1, memory module in A1 slot, and the default riser without expansion cards. If this boot is normal then you can add component ne by one and check which component causing the boot time. Sometime bad hardware can impact boot time.
AceBoyden
1 Rookie
•
6 Posts
0
September 30th, 2022 02:00
Hello, i've tried to post to minimum of 1 component each and changing out components but its all the same results, could it be caused by the motherboard maybe?
DiegoLopez
4 Operator
•
2.7K Posts
0
September 30th, 2022 05:00
Hello @AceBoyden,
If the problem persist on a Minimum to post. Yes, that can be caused for a BIOS configuration on the motherboard. I would not say it's a faulty hardware, but a configuration that is taking all that time to boot. Are you sure in the Minimum to post you disconnected everything but the components that Shine K mentioned? Including storage?
Regards.
OldSchoolAdm1n
1 Rookie
•
16 Posts
0
September 30th, 2022 14:00
Hi AceBoyden,
So the machine worked perfectly at your work, but what happened the very first time you booted it up at home? Did it boot up normally to "something", or did it immediately start doing what you're describing?
Also, did you actually install Unraid on the flash drive while it was installed in this machine or did you move the installation on the flash drive from another machine to this one?
We are missing some helpful info here. My first thought is that the machine is fine, but something is so far out of whack now that it just can't get around it. Do you happen to know "How" and "What" this machine booted to when it was on your work network?
Any other history or info you have about the machine would be helpful for everyone.
Also, look in your Lifetime Controller setting and see if you have a setting that says "Retire or Repurpose", just in case you end up needing to reset the machine, but don't do it yet.