0x1e mrcunsupportedtechnology supermicro ошибка

Проблема с Supermicro X9DAi (SYS-7037a-i)

Проблема с Supermicro X9DAi (SYS-7037a-i)

Сообщение SciMan » 10 янв 2017, 22:57

В наличии есть рабочая станция на базе Supermicro X9DAi, в корпусе SYS-7037a-i, версия BIOS = 3.0а

Сама станция подключена к бесперебойнику, до недавнего времени все было хорошо (полгода с запуска), а сегодня внезапно начался следующий глюк: включаю питание с передней панели — стартуют кулеры, шумят секунд 5, и мигает красный индикатор «i» — «информация». Потом станция внезапно прерывает запуск и выключается, не показав ничего на экране. Через несколько секунд (примерно 3 сек.) внезапно включает питание и продолжает запуск с нуля. В мане об индикации LED «i» не сказано ничего, там вместо него обозначен индикатор температуры, означает проверить помещение на перегрев, или мешает ли что-то вентиляторам. Разобрал корпус, прочистил его, собрал обратно, проблема осталась.

Некоторое время погуглив, нашел еще вариант источника проблемы — возможно, ошибки в памяти: на борту 128 ГБ Reg-ECC, работал на Force speed 1600, сейчас в BIOS переставил на Auto (стало 1333). Проблема не исчезла. На ночь поставлю Memtest, в нем, кстати, ECC=off. В логах BIOS есть ошибка Smbios 0x01 SINGLE ECC-BIT ERROR. Но в логах она уже очень давно, а проблема началась сегодня.

Подскажите пожалуйста, в чем может быть проблема. Прошивку BIOS обновлял летом, по способу в readme с офсайта Supermicro, все встало без проблем.

Источник

Supermicro X9SCM-F & Kingston Memory Error

Quinnx

Dabbler

So after going though the Kingston Memory configuration memory finder it recommend the following memory. (And yes I have read the FAQ’s to stay away from Kingston Memroy)

Once installed in DIMM 1A & DIMM 2A I get the 5 short beeps + 1 long beep Memory error thus meaning No memory detected in the system. So i remove slots 1A & 2A and the system boots with only the slots in 2A & 2B.

I tried just using slots 1A and 2B with the same memory and the system does not boot, again 5 short beeps + 1 long. Again I tried with all four slots filled and I get the same memory beep error.

Does this mean that the motherboard slots for the 1A & 2A are faulty?

I really hope not as this board came from the USA & I Live in the UK, so it will be a pain to return and thus leaving me with no FreeNas system for a while.

Many thanks for your audience!

Quinnx

Dabbler

Ericloewe

Not-very-passive-but-aggressive

Assuming you moved the DIMMs around, yes.

It could be the CPU IMC itself (unlikely), CPU socket with bent pins (very likely) or a real PCB flaw (not very likely).

Quinnx

Dabbler

Mirfster

Doesn’t know what he’s talking about

Perhaps you simply have a bad memory stick somewhere in the mix?

I would suggest trying out each stick of memory itself in DIMM2A, then if all of them work move on to two sticks in DIMM2A & DIMM2B. If that works, then progress onward increasing the number of sticks and using the recommended installation order (3 sticks = DIMM2A, DIMM2B and DIMM1A).

Perhaps you will find out that one of the sticks are bad (from the first test) or you will get to a point where you can deduce one of the memory slots are bad.

Side notes:

• I have not checked with SuperMicro to see if this memory is supported by them (perhaps you did?)
• In the manual it also notes (not sure what CPU you are using. ):

Quinnx

Dabbler

Perhaps you simply have a bad memory stick somewhere in the mix?

I would suggest trying out each stick of memory itself in DIMM2A, then if all of them work move on to two sticks in DIMM2A & DIMM2B. If that works, then progress onward increasing the number of sticks and using the recommended installation order (3 sticks = DIMM2A, DIMM2B and DIMM1A).

Perhaps you will find out that one of the sticks are bad (from the first test) or you will get to a point where you can deduce one of the memory slots are bad.

Side notes:

• I have not checked with SuperMicro to see if this memory is supported by them (perhaps you did?)
• In the manual it also notes (not sure what CPU you are using. ):

All memory modules are matched. When I swap any from 1A or 2A to 2A & 2B the system boots no problem.

• Q: I have not checked with SuperMicro to see if this memory is supported by them (perhaps you did?)
• A: Contacted directly Kingston support who have confirmed this memory does work with this system board. Whilst I can appreciate Supermicro (1.99BN Company) cannot test all memory modules, Kingston (11.9BN Company) have confirmed this memory is 100% compatible.
• Q: In the manual it also notes (not sure what CPU you are using. ):
• A: It is a V2 Intel Xeon

I will attempt to follow the suggestion of installing the dims in order as suggested, not sure how that will help if the system is off. How does it know the order of the dimms placement?

Anyway, the dude from the USA is going to send me a new board and ensure that all memory slots are working.

Источник

0x1e mrcunsupportedtechnology supermicro ошибка

Этот форум закрыт. Спасибо за участие!

Лучший отвечающий

Вопрос

Ответы

Все ответы

копайте в направлении интерпритации Dump файлов

после того как рсшифруете, выложите сюда, будем искать решение.

сила в справедливости

В dmp-файлах запись об ошибке ntkrnlmp.exe и упоминание, видимо, одной из служб Exchange:

Probably caused by : ntoskrnl.exe ( nt+2c121f )

Crash date: Thu Jul 30 11:15:24.837 2009 (GMT+4)
Stop error code: 0x1E
Process name: Microsoft.Excha
Probably caused by: ntkrnlmp.exe ( ntPspGetSetContextInternal+203 )

kd.exe выдает следующее:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [Q:minidumpMini073009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:symbols
Executable search path is: C:symbols
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer
Built by: 3790.srv03_sp2_gdr.090319-1204
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Thu Jul 30 11:15:24.837 2009 (GMT+4)
System Uptime: 0 days 16:22:15.402
Loading Kernel Symbols
.
.
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

Probably caused by : ntkrnlmp.exe ( nt!PspGetSetContextInternal+203 )

а при анализе ( !analyze -v ) вывод такой:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800012c121f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000001ba8000, Parameter 1 of the exception

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 —

FAULTING_IP:
nt!PspGetSetContextInternal+203
fffff800`012c121f 488b58f8 mov rbx,qword ptr [rax-8]

EXCEPTION_RECORD: fffffadcb8f3db90 — (.exr 0xfffffadcb8f3db90)
ExceptionAddress: fffff800012c121f (nt!PspGetSetContextInternal+0x0000000000000203)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000008
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000001ba8000
Attempt to read from address 0000000001ba8000

TRAP_FRAME: fffffadcb8f3dc20 — (.trap 0xfffffadcb8f3dc20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000001ba8008 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800012c121f rsp=fffffadcb8f3ddb0 rbp=fffffadcb8f53b10
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!PspGetSetContextInternal+0x203:
fffff800`012c121f 488b58f8 mov rbx,qword ptr [rax-8] ds:0010:00000000`01ba8000=.
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001080e86 to fffff8000102e890

STACK_TEXT:
fffffadc`b8f3d498 fffff800`01080e86 : 00000000`0000001e ffffffff`c0000005 fffff800`012c121f 00000000`00000000 : nt!KeBug
CheckEx
fffffadc`b8f3d4a0 fffff800`0102e6af : fffffadc`b8f3db90 fffff980`05100698 fffffadc`b8f3dc20 fffffadc`de3c81c8 : nt!KiDis
patchException+0x128
fffffadc`b8f3daa0 fffff800`0102d521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExc
eptionExit
fffffadc`b8f3dc20 fffff800`012c121f : fffffa80`005e7088 00000000`00000000 fffffadc`b8f3ec70 fffffadc`b8f535c0 : nt!KiPag
eFault+0x1e1
fffffadc`b8f3ddb0 fffff800`0104236b : fffffadc`dbaf6bf0 00000000`00000000 fffffadc`dbaf6c38 00000000`00000000 : nt!PspGe
tSetContextInternal+0x203
fffffadc`b8f3e300 fffff800`01027eb1 : fffffadc`de920000 fffffadc`0000000c fffffadc`de920060 00000000`000003b0 : nt!PspGe
tSetContextSpecialApc+0xab
fffffadc`b8f3e410 fffff800`0103bf97 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDel
iverApc+0x215
fffffadc`b8f3e4b0 fffff800`0102828e : 00000000`00000000 00000000`00000000 fffffadc`dbaf6c88 fffffadc`dbaf6bf0 : nt!KiSwa
pThread+0x3e9
fffffadc`b8f3e510 fffff800`0101f88c : 00000000`00000000 00000000`00000005 00000000`00000000 fffffadc`def70e00 : nt!KeWai
tForSingleObject+0x5a6
fffffadc`b8f3e590 fffff800`0101f51b : fffffadc`b8f3e8c0 00000000`00000000 fffffadc`de920070 00000000`00000000 : nt!KiSus
pendThread+0x2c
fffffadc`b8f3e5d0 fffff800`01027abd : ffffffff`80000718 00000000`00000000 fffff800`0101f860 fffffadc`dabed000 : nt!KiDel
iverApc+0x2d3
fffffadc`b8f3e670 fffff800`011a4a66 : fffffadc`daf80240 00000000`00000000 00000000`00000001 fffffadc`b8f3e861 : nt!KiApc
Interrupt+0xdd
fffffadc`b8f3e800 fffff800`011a99d1 : fffffadc`dabed000 00000000`44536d45 fffff800`011ce1c0 00000000`05da6490 : nt!MiFre
ePoolPages+0xfa1
fffffadc`b8f3e890 fffffadc`dc5feea4 : 00000000`00000000 fffffadc`daf80270 fffffa80`00f17878 fffffa80`00f17860 : nt!ExFre
ePoolWithTag+0x3a3
fffffadc`b8f3e950 00000000`00000000 : fffffadc`daf80270 fffffa80`00f17878 fffffa80`00f17860 fffffadc`dae056a0 : 0xfffffa
dc`dc5feea4

FOLLOWUP_IP:
nt!PspGetSetContextInternal+203
fffff800`012c121f 488b58f8 mov rbx,qword ptr [rax-8]

Источник

SOLVED SuperMicro X10 Motherboards + i3 4th Gen Proc Boot Issues?

Faluzure

Explorer

Ericloewe/cyberjock/Fraoch: Thanks your your input. I completely understand their stance on it. I did take Eric’s advice and call personally and the guy on the phone had a much different stance than the guy I was emailing. After explaining everything, he said if I tried 2 different power supplies & verified they are working and double-checked the memory & CPU, he thinks it must be a motherboard issue.

Then I asked him, even with a CPU incompatibility with the 1.X version of BIOS, shouldn’t the fans at least spin to indicate power when the power button is pressed? He agreed with me and just said to either RMA through them or return the motherboard to the reseller. I’ve already returned it to Newegg for an exchange, but if the replacement acts the same, I’ll just RMA it back to SuperMicro.

Will keep you guys posted.

Faluzure

Explorer

Well. I got my new motherboard today. and now I get an ORANGE LE6 LED. According to Supermicro’s page, it’s: Orange means standby power is OK but not power on yet.

Now that I have the motherboard connected to the PSU & the IPMI on the network, I can verify I can access IPMI but it can’t power on the motherboard. I get this message: «Performing power action failed. Please check The feature connector cables.»

On the Summary section, I verified I have the 2.00 firmware:

Firmware Revision : 01.42IP address : 192.168.001.107
Firmware Build Time : 04/18/2014BMC MAC address : 0c:c4:7a:0c:d4:40
BIOS Version : 2.00System LAN1 MAC address : 0c:c4:7a:0c:d6:d0
BIOS Build Time : 04/24/2014System LAN2 MAC address : 0c:c4:7a:0c:d6:d1

I’m kind of at a loss now. Now the only things left is the PSU/CPU/Memory. But if the CPU/memory was bad, it should still power up. Now I’m wondering if the Seasonic is bad. I’m using the SSR-550RM that Ericloewe is using.

Faluzure

Explorer

FML. I just tried my PSU from my gaming PC and it powers up just fine via the power switch and in IPMI. via IPMI, I saw the Supermicro splash screen in the console preview.

When I tried that with the 1st motherboard, it had a red LED with both PSUs. Now it’s orange on both but the Seasonic is bad. I even did the PSU paperclip fan test failed. Fan won’t even spin.

What the heck are the chances that I ended up with a bad motherboard AND a PSU?! I should buy a lottery ticket tonight.

Sheesh. RMA’ing the PSU now.

Ericloewe

Not-very-passive-but-aggressive

FML. I just tried my PSU from my gaming PC and it powers up just fine via the power switch and in IPMI. via IPMI, I saw the Supermicro splash screen in the console preview.

When I tried that with the 1st motherboard, it had a red LED with both PSUs. Now it’s orange on both but the Seasonic is bad. I even did the PSU paperclip fan test failed. Fan won’t even spin.

What the heck are the chances that I ended up with a bad motherboard AND a PSU?! I should buy a lottery ticket tonight.

Sheesh. RMA’ing the PSU now.

Damn, that’s unlucky. And a Seasonic at that.

Fortunately, it should be smooth sailing from now on, since Seasonic should just rubber stamp your RMA.

Glad the motherboard got fixed.

Fraoch

Patron

Starpulkka

Contributor

cyberjock

Inactive Account

Starpulkka

Contributor

pschatz100

I had a similar situation with a bad power supply. I went through two motherboards and two cpu’s before identifying the power supply as my problem. In my case, the power supply had not failed completely, so it was difficult to diagnose. On an older motherboard with the same power supply, the board would boot.

I didn’t RMA the boards or cpu’s as I feel it is inappropriate to RMA equipment that is not failing. However, next time I troubleshoot a system, when the problem does not have an obvious cause, I’ll check out the power supply a lot sooner.

By the way, you do have a UPS. Right?

Faluzure

Explorer

Just wanted to come back here and give everyone a big thanks for helping me out. I got the replacement PSU on Saturday. Just to be 100% safe, I cardboard boxed it and powered it up. No issues whatsoever. Still hard to believe that both the motherboard & the PSU were faulty. I know it’s more common nowadays with the architecture, but that’s some pretty bad luck.

I spent all day Saturday & Sunday to get FreeNAS set up and running based on the documentation & other people’s recommendations. All hardware testing turned out fine and I spent Sunday night setting up FreeNAS. Got the cron job for backing up the DB going, got periodic snapshots se tup, got email alerting set up, LACP setup for the NAS, and just got my UPS cable this morning (it works)!

To pschatz100, yeah. i was quick to RMA both parts. I just hate the process, because it costs you money & time. Had that not happened, the NAS would have been set up over 2 weeks ago. I do have a UPS. it was one of the things I had in the closet (no battery) when my work decided to dump a ton of hardware at the electronics recycling dump. I got a Cisco router & a gig C3750 on my network.

Again, thanks for all the help and the forums/documentation are an excellent resource.

Источник

I’ve bought new( not used ) SuperMicro MBD-X11DPI and

• x2 — Intel Xeon Silver 4210R OEM
• Micron [MTA72ASS8G72PSZ-2S6E1] 64Gb
• Samsung [M393A8G40MB2-CTD] 64Gb

When I’m booting, 10 different combinations of 2xCPU and different RAM modules give me always such picture:

System Initializing...
P1-DIMMA1:DIMM Mapped Out
P1-DIMMA1(runtime)Failing DIMM: DIMM location
MAP Failure
All channels are disabled due to memory test failures

In the right / bottom corner blinks codes: AF — BB — B7 — BB — 53

https://www.supermicro.com/manuals/other/AMI_BIOS_POST_Codes_for_Grantley_Motherboards.pdf

• 0xAF Exit Boot Services event

• 0xB8 – 0xBF Reserved for future AMI codes — …

• 0xB7 Configuration Reset (reset of NVRAM settings)

• 0x53 Memory initialization error. No usable memory detected

Google said, that I shall update BIOS to use gen2 Xeon on this board, seems.

Moreover, I’ve gained IMPI access via LAN / browser, but I can not log-in with default ADMIN/ADMIN

Invalid Username or Password

From the manual, I have understood that IMPI shall be enabled from BIOS. So, by default it should not even answer me by http. But it answers… Strange…

Ssh — connected to 22 with ADMIN@192.168.10.12, but «ADMIN» — is incorrect password it’s said. admin/admin, ADMIN/admin, admin/ADMIN, root/toor — everything is not valid…

# ssh ADMIN@192.168.10.12 
ADMIN@192.168.10.12's password: 
Permission denied, please try again.
ADMIN@192.168.10.12's password: 

ipmitool the same:

# ipmitool -H 192.168.10.12 -U ADMIN  -P ADMIN
Activate Session error: Command response could not be provided
Error: Unable to establish LAN session
Error: Unable to establish IPMI v1.5 / RMCP session

USB Keyboard inserted in USB0 — does not seems to response also. So, I can not enter to BIOS. I’m only seeing this blue on black SupermicrO ascii label and

All channels are disabled due to memory test failures
System Initializing...                                     53

Is it right, that I can not enter to BIOS without installed proper Processor and RAM module, or BMC module shall give me VGA via controller even without CPU installed and pass me to the BIOS?

Is the buying older gen1 Intel Xeon — to boot, to update BIOS is only way to launch this setup for me, or there exist bypass?