Unable to get Supermicro X10SRH-CF mobo to power on/post properly

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

whitey

Moderator
Jun 30, 2014
2,766
868
113
41
Afternoon everyone, busy stranger popping back into the fray seeking help :-D

I've been focused heavily on the software side of the house (PaaS/Kubernetes) the last few years so I may be rusty WRT my hardware chops but this just has me feeling silly.

So a few weeks back picked up a X10SRH-CF from ebay, arrived in good shape shipping-wise but mobo has slight (hope I am right abt this) damage to the front panel header pins (reset pin 3 to be exact)...I ended up bending that back and saying hell w/ it. Well today I got to throw together my new build and I can't get it to POST. Front pwr/reset button doesn't light up/work at all, Tried shorting pins 1/2 on FPH w/ small screwdriver/paperclip. I must be doing something silly.

Tried populating dimm slots DIMMA1/DIMMC1 and have backed off that to just 1 stick in DIMMA1. When I plug PSU's in all I get is a quick pwr up for roughly 3-4 seconds, front chassis slots blink red, motherboard green lights solid, then 20-25 secs later that starts blinking green on and off.

Appreciate if someone can give me another idea or two. Still shaking off the 'out of the HW game rust' and RTFM troubleshooting sections of pdfs/manuals.

System specs are as follows:

CSE-846 chassis w/ BPN-SAS3-846EL backplane and PWS-1K28P-SQ dual pwr supplies
X10SRH-CF mobo (mobo came w/ a 2620v4 so I don't think it needs a BIOS update AKA the old mobo needs a v3 chip to flash v4 compat bios to use v4 procs)
Xeon E52667v4 proc
Samsung DDR4 2133 RDIMM's (M393A2G40DB0-CPB) borrowed from a Xeon-D build

Here's a video showing issue (sorry for shaky/blurry spot, dim in basement and camera was fighting w/ me)


Kind regards, whitey
 

whitey

Moderator
Jun 30, 2014
2,766
868
113
41
Fairly certain I have a dead mobo, I can access the IPMI via an isolated test vlan/subnet and see it pickup a DHCP addy, acces it and I see this nonsense (old system build info/NO sensors reading) WTF

Toast would you all concur? Start w/ a new/replacement/non-damaged mobo?

1614905761804.png

1614905782962.png
1614905799902.png
1614905816099.png
1614905827295.png
1614905840862.png
1614905852075.png
1614905861651.png
1614905876911.png
1614905884501.png
 

mbosma

Member
Dec 4, 2018
76
58
18
I've had instances before where I was able to access IPMI but the system just wouldn't power up.

In some cases I wasn't getting any error messages while trying to power up the system, it simply wouldn't do anything.
Pressing the powerbutton wasn't giving any response either.
These got solved swapping the power supplies.

Other cases were related to the motherboard, IPMI showed an error stating the CPU overheated but actually the VRM for CPU 1 died.
The system also wouldn't power up anymore but the power led was on when trying to power up the system.

If you have a psu (can be a simple ATX one) available I'd start out with that but my guess is that your mobo is indeed dead.

FYI, all sensors are set to "Not Present!" until the system is powered up and is past POST so those aren't really related to your issue.
 

zack$

Well-Known Member
Aug 16, 2018
701
315
63
Had an identical issue with a X10SRW-F board. Tried CMOS clear, swapped psu, cpu and ram. Nothing worked to get the MB to boot via power button or IPMI power on.

Saw a couple people have a similar issue on the forum, which was also never resolved.

Called it quits and just got a new board.
 

Fritz

Well-Known Member
Apr 6, 2015
3,371
1,375
113
69
Wow, I have 2 of these boards and they're both flawless. Both are running with 3rd party PSU's but one will be going into a SM chassis this coming week.
 

pricklypunter

Well-Known Member
Nov 10, 2015
1,708
515
113
Canada
Get it out the case and give it a close visual with a magnifying glass for any obvious damage to CPU pins, components and tracks etc, then bench test it with a known good power supply, stick of RAM and CPU :)
 

zer0sum

Well-Known Member
Mar 8, 2013
849
473
63
I had something like this happen recently and it was my power supply.
It didn't like a sata power cable I was using, and it wouldn't fire up, but ipmi worked perfectly.

Try unplugging everything from the psu except for just the power for the big 24 pin plug motherboard and see if it fires up.
Or try a different psu if you have one around
 

whitey

Moderator
Jun 30, 2014
2,766
868
113
41
OK, so I got a new MB in, resolved issue, posting cleanly now. Glad to know it was a faulty mobo, figured from the initial damage I should have known better and not held out hope.

Anyone know what the latest Supermicro LSI SAS3 download page is at these days? I seem to have misplaced the url and google-fu is weak ATM apparently. Forget if I use a generic driver or one specifically for this mobo, sure it's a 3008 chipset but still digging into the details.

EDIT: Found it 'I think'


Are these the proper files to flash LSI sas HBA with or is there a 'more proper' source for this mobo?
 
Last edited:
  • Like
Reactions: Fritz

zack$

Well-Known Member
Aug 16, 2018
701
315
63
They are the proper files. Seems this firmware is up to date as of March 3, 2021 as well!

NB: running the included Supermicro script to update/flash the HBA makes life simple.
 

whitey

Moderator
Jun 30, 2014
2,766
868
113
41
All updated, order of update operations I took was BCM/IPMI firmware (IPMI web UI), BIOS (BIOS boot mode via freedos usb...ummm yeah they forced my hand), LSI 3008 HBA (UEFI boot mode using freedos usb) and YES SMC3008T.nsh is quite nice :-D

vSphere 6.7 and 7.0 tested so far via satadom install. TrueNAS Core was NOT impressed w/ me trying to place AIO NAS VM on the free space datastore on that same hypervisor satadom.

1615267314780.png

Thought that would work as satadoms are orders of magnitude better perf/build-wise than USB flash media for install destination but I'm over it and threw my Optane 900P 280GB AIC at it and installed TrueNAS there on top of VMFS and setup boot and left l2arc/zil vdisks there for future pool usage.
 
Last edited:
  • Like
Reactions: Fritz