My one server takes too long to startup and I am wondering if anyone sees anything odd in the syslog

 

I tried to add a couple new drives and the server would not start at all. So I removed one and it still would not start

So I removed both and then it came back up

 

Do u see anything odd?

 

Thanks

tower3-diagnostics-20201004-1556.zip

Edited October 4, 20205 yr by Blade

Might we assume that your Diagnostics file is from the setup where it is booting normally.   If this is the case, you will have to provide more information.  By "start at all", if you mean you can not access the GUI and/or have access to the files, you are going to have to reinstall those drives, connect up a monitor and keyboard.  Now try to boot the server and look at what is happening.  Tell us what you see going on while the boot process is taking place.

How many drives work, and how are they connected?   Some BIOS’s seem to get upset if you have more than 12 drives in the system unless you disable the options for all of them to be treated as potentially bootable.

Yes the diagnostic was from system coming up OK with drives not hooked up

 

I will check the bios and see if there is an issue there

Will hook up monitor as well

Edited October 5, 20205 yr by Blade

I removed the bios on my LSI SAS board and that seemed to fix the issue

 

sas2flsh.exe -o -e 5

 

Thanks

9 hours ago, Blade said:

I removed the bios on my LSI SAS board and that seemed to fix the issue

 

sas2flsh.exe -o -e 5

 

Thanks

That would work   It has the added advantage that the system should now boot slightly faster.

Yes it boots much faster too so a win-win