Smbios 0x16 ошибка - Не ошибается лишь тот, кто ничего не делает!

Question

I found the error in BIOS Event log whenever the X9DRL-IF motherboard boots. The error code is «SMBIOS 0X16». Please let me know what does this code mean?

Answer

Normally, you’ll see 0x16 & 0x17 at the system reboot. «0x16» means Log Area Reset; and 0x17 means System Boot. The «Severity» also says «N/A», which means these are just the message and nothing serious.

Was this FAQ helpful?

YES NO

Enter Comments Below:
Note: Your comments/feedback should be limited to this FAQ only. For technical support, please send an email to support@supermicro.com.

Enter your email address below if you’d like technical support staff to reply:

Please type the Captcha (no space)

FAQ Stats
FAQ ID	Related Category / Keyword	Date Posted	Code
13793	BIOS: — AMI BIOS	03/05/12	JC

Print Answer

Источник

Перейти к контенту

Здравствуйте.

В наличии есть рабочая станция на базе 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, все встало без проблем.

Спасибо.

#281

Ziferius, I’m getting some strange results from one of the modules I got from Superbiiz back in March (see below).

I ran Memtest86+ 5.01 for 17 hours on the default settings and it found no errors. However, when I looked at the Event Logs in the BIOS it showed (see below). I’ve only had the machine powered on fewer than 10 times (on for only 1 — 5 hours each time, except for the 17 hour memtest) since I put it together. Is this normal, or is DIMMA1 faulty?

Samsung DDR3-1600 ECC CL11
Mfr Part Number: M391B1G73QH0-YK0

#282

Where are you getting your memory, if you don’t mind me asking?

Thanks!

Sent from my iPad using Tapatalk

I have Kingston for my primary system. My secondary will run on Crucial ECC initially. Might exchange that later.

Have you checked CPU then? Bent pins?

#283

Thank you for the firmware flashing instructions Sir.Robin.

You’re welcome!

#284

Ziferius, I’m getting some strange results from one of the modules I got from Superbiiz back in March (see below).

I ran Memtest86+ 5.01 for 17 hours on the default settings and it found no errors. However, when I looked at the Event Logs in the BIOS it showed (see below). I’ve only had the machine powered on fewer than 10 times (on for only 1 — 5 hours each time, except for the 17 hour memtest) since I put it together. Is this normal, or is DIMMA1 faulty?

DATE: | TIME: | ERROR CODE: | SEVERITY: | DESCRIPTION:
05/05/14 | 01:20:30 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 03:08:27 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 06:48:06 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/05/14 | 09:34:40 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
05/18/14 | 11:48:03 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
06/15/14 | 11:32:58 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error
06/22/14 | 15:21:03 | Smbios 0x01 | DIMMA1 | Single Bit ECC Memory Error

Samsung DDR3-1600 ECC CL11
Mfr Part Number: M391B1G73QH0-YK0

Interesting… That seems like an aweful lot, but that’s why we run ECC….it catches and fixes that.
Cyber jock is definitely proved right (yet again) why ECC is so important.

Sent from my iPad using Tapatalk

#285

I have Kingston for my primary system. My secondary will run on Crucial ECC initially. Might exchange that later.

Have you checked CPU then? Bent pins?

CPU socket on first board had bent pins… I had a pentium G3220 for it…

Sent from my iPad using Tapatalk

#286

I’m glad I listened and got ECC. It does seem a little strange that all the errors are occurring on only one DIMM (that is if I’m reading the event log correctly). Good luck getting your board to work — sorry I can’t offer any help.

#287

It could be the DIMM or it could be the socket. To check though — trade sockets with that DIMM with one of the others. If the problem follows — then it’s the DIMM. If it doesn’t, then it’s the socket.

#288

It could be the DIMM or it could be the socket. To check though — trade sockets with that DIMM with one of the others. If the problem follows — then it’s the DIMM. If it doesn’t, then it’s the socket.

Thanks. I’ll switch them and see what happens. Hopefully it’s not the board.

#289

Thanks. I’ll switch them and see what happens. Hopefully it’s not the board.

I would say it’s more likely a bad dimm (memory stick).

#290

Awh crap!! They slashed the pricing of Samsung 8GB M391B1G73BH0-CK0 modules!! Just a tiny bit more than what i gave for the kingston’s

#291

Ran Memtest at the default settings again for another 18 hours — still no errors. I wonder if the errors are corrected by the ECC before Memtest can detect them. I was also thinking, since Memtest can read and write to the DIMM with no errors, would this definitely absolve the motherboard?

I would say it’s more likely a bad dimm (memory stick).

Thanks Sir.Robin. Also, if you get the Samsungs just don’t sit on them for a few months, like I did (see below).

Ziferius, I thought I’d get the ball rolling just in case it takes a few days to get a response… Don’t know if you’ve tried contacting Samsung yet about your memory, however, here is the response I received:
Unfortunately you’ve reached the Retail Memory department. The part number
you’ve provided is for a OEM unit meant to be sold together with Pre-built
systems (Dell, HP, ETC). You can try contacting your point of purchase or
system manufacturer for further assistance.

Contacted the system manufacturer and he’s pretty much clueless too.

Looks like getting a replacement from Samsung may be a little tricky.

#292

Ran Memtest at the default settings again for another 18 hours — still no errors. I wonder if the errors are corrected by the ECC before Memtest can detect them. I was also thinking, since Memtest can read and write to the DIMM with no errors, would this definitely absolve the motherboard?

There are tales that Memtest 86+ detects ECC-corrected (and detected) errors and logs them… I say tales because I’ve never seen proof and the whole figuring out if ECC is working business relies on blind faith that ECC is working, in many cases.

#293

There are tales that Memtest 86+ detects ECC-corrected (and detected) errors and logs them… I say tales because I’ve never seen proof and the whole figuring out if ECC is working business relies on blind faith that ECC is working, in many cases.

Ericloewe, thank you for enlightening (and frightening ) me.

Ziferius, just got a response from Superbiiz and it looks like they will let me RMA the module — I can post more info if you’d like.

#294

cool. Grep137 — has it been more than 30 days?
I went ahead and requested an RMA as well.

I’ve tried everything that I could have. I did order 32gb of Hynix last night … we’ll see if this works
I’m really looking forward to getting this system going!. (Though, I have to get 3 more 3 TB drives. . . .)

#295

Awh crap!! They slashed the pricing of Samsung 8GB M391B1G73BH0-CK0 modules!! Just a tiny bit more than what i gave for the kingston’s

Am I correct in assuming that the «they» who slashed the price on the Samsung modules is a European vendor? I don’t see a price drop by any of the US vendors.

#296

cool. Grep137 — has it been more than 30 days?
I went ahead and requested an RMA as well.

I’ve tried everything that I could have. I did order 32gb of Hynix last night … we’ll see if this works
I’m really looking forward to getting this system going!. (Though, I have to get 3 more 3 TB drives. . . .)

Where did you find your Hynix modules, and how much?

#297

Am I correct in assuming that the «they» who slashed the price on the Samsung modules is a European vendor? I don’t see a price drop by any of the US vendors.

Hehe… yeah. Norwegian/danish shop. The samsung sticks were cinda pricey before… but now that they are over 30% lower it’s abut the same price as i payed for the kingston sticks.

#298

cool. Grep137 — has it been more than 30 days?
I went ahead and requested an RMA as well.

I got mine back in March. Superbiiz’s response when I told them the purchase date: «Please note that because you are beyond the 30 day period, you are no longer eligible for a refund, only repair/replacement.» However, this response wasn’t from someone who actually works in the RMA dept.

Just found this too:
«Items received by SuperBiiz after the initial 30-day period are no longer eligible for refund and will be forwarded to the original manufacturer for repair or replacement only, the choice of which will be at the discretion of the manufacturer.»
http://www.superbiiz.com/rma.php

I believe that they may still do replacements beyond the 30 days because of Samsung’s policy on ECC memory (copied from the e-mail I received from Samsung): «You can try contacting your point of purchase or system manufacturer for further assistance.»

Which makes me wonder who we would contact in the future if Superbiiz goes out of business.

Also, I tried to get them to cross ship, but that seems like a no go so far; maybe you’ll have better luck.

#299

I just got my X10Sl7F mobo and have everything setup, updated all the firmware’s and installed the LSI IT Mode Firmware from here, ftp://ftp.supermicro.com/Driver/SAS/LSI/2308/Firmware/IT/ version 19… I can’t see my drives though, they aren’t showing up in the SAS configuration. Was version 19 the right one to use?

#300

I just got my X10Sl7F mobo and have everything setup, updated all the firmware’s and installed the LSI IT Mode Firmware from here, ftp://ftp.supermicro.com/Driver/SAS/LSI/2308/Firmware/IT/ version 19… I can’t see my drives though, they aren’t showing up in the SAS configuration. Was version 19 the right one to use?

Congrats on a great motherboard

No, FreeNAS is on the ver 16 driver level. And so your firmware also needs to be there.

I’m running ubuntu server 14.04 on Supermicro X10SLM-F / Xeon E3-1271 v3

Memory: SuperTalent 32GB DDR3 1600 ECC

About every 4 days, the logs on Ubuntu will show this:

{1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1
{1}[Hardware Error]: It has been corrected by h/w and requires no further action
{1}[Hardware Error]: event severity: corrected
{1}[Hardware Error]:  Error 0, type: corrected
{1}[Hardware Error]:  fru_text: CorrectedErr
{1}[Hardware Error]:   section_type: memory error
[Firmware Warn]: error section length is too small

Immediately after this the server reboots itself in a «power-cycle» fashion.

When I look in the BIOS event log, I see this:

DATE            TIME           ERROR CODE      SEVERITY
06/13/15      13:13:38      Smbios 0x02         P1-DIMMB2

And the description of the error is:

Single Bit ECC Memory Error

ipmitool in Ubuntu show this:

ipmitool sel elist
...
...
  1a | 06/13/2015 | 13:13:39 | Memory | Correctable ECC | Asserted | CPU 0 DIMM 8
  1b | 06/13/2015 | 13:13:39 | Memory | Uncorrectable ECC | Asserted | CPU 0 DIMM 8

A few questions:

If the ECC memory is self correcting, why does the machine reboot itself?
Am I, perhaps, missing some setting in the BIOS that will stop the box from rebooting itself?
Is this obviously a memory stick issue or can this be a slot issue or a CPU issue?
How to stop the server from rebooting?

Thank you for any advice.

4-56

Chapter 4: BIOS setup

DATE TIME ERROR CODE SEVERITY

01/01/2000 01:19:45 Smbios 0x16 N/A

Log OEM Codes [Enabled]

Enables or disables logging of EFI status codes as OEM codes (if not already converted to

legacy). Configuration options: [Disabled] [Enabled]

Convert OEM Codes [Disabled]

Enables or disables converting EFI status codes to Standard Smbios types (Not all may be

translated). Configuration options: [Disabled] [Enabled]

4.7.2

View Smbios Event Log

This menu displays all Smbios event logs.

DESCRIPTION

Log Area Reset

Main Advanced Event Logs Boot Monitor Security Tool Exit

Event Logs

Log OEM Codes [Enabled]

Enables or disables logging of EFI status codes as OEM codes (if not already converted to

legacy). Configuration options: [Disabled] [Enabled]

Convert OEM Codes [Disabled]

Enables or disables converting EFI status codes to Standard Smbios types (Not all may be

translated). Configuration options: [Disabled] [Enabled]

4.7.2

This menu displays all Smbios event logs.

Main

Advanced

DATE

01/01/2000

4-56

Event Logs

Boot

TIME

ERROR CODE

01:19:45

Smbios 0x16

Monitor

Security

Event Logs

SEVERITY

N/A

Tool

Exit

DESCRIPTION

Log Area Reset

Chapter 4: BIOS setup

Источник

gan34
Новичок

Зарегистрирован: 08.10.2019
Пользователь #: 172,307
Сообщения: 4

Источник

Профиль | Отправить PM | Цитировать

Перезагружался, т.к. устанавливал последние обновления от MS за сентябрь. ОС — 2008R2. Здесь аналогичная проблема, только память другая. Также натыкался ещё на несколько подобных случаев. Снёс все установленные обновы (кроме обновки для ie11), а именно: KB3184471, KB3177186, KB3175024, KB3184122, KB3185911. И всё ребутнулось успешно. Кто-н имел дело с похожим?

Судя по бипам — проблемы с памятью. »

——-
ВНИМАНИЕ ознакомьтесь, прежде чем создать тему! Процессор — мозг компьютера, блок питания — сердце и печень.

Это сообщение посчитали полезным следующие участники:

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

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

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

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

Источник

ECC memory errors causing random server reboots

I’m running ubuntu server 14.04 on Supermicro X10SLM-F / Xeon E3-1271 v3

Memory: SuperTalent 32GB DDR3 1600 ECC

About every 4 days, the logs on Ubuntu will show this:

Immediately after this the server reboots itself in a «power-cycle» fashion.

When I look in the BIOS event log, I see this:

And the description of the error is:

ipmitool in Ubuntu show this:

A few questions:

If the ECC memory is self correcting, why does the machine reboot itself?

Am I, perhaps, missing some setting in the BIOS that will stop the box from rebooting itself?

Is this obviously a memory stick issue or can this be a slot issue or a CPU issue?

How to stop the server from rebooting?

Thank you for any advice.

3 Answers 3

The system should not reboot upon correctable memory error. Do you see additional information/pattern via ipmitool sel elist ? The BMC watchdog could reboot the system, check if it is enabled via ipmitool mc watchdog get . As you already have the information on the location of the bad memory module, replace it and if the problem manifests again, the memory slot could be at fault.

X10SLM-F the RAM that you use is not on the list of tested RAM modules — if you have the possibility, replace all the memory bars in a ‘problem’ system with equivalent Supermicro-tested ones. Also, check the list of supported OS for you Ubuntu version.

Related to the CMOS settings, you could use Supermicro SUM , provided you have the SUM keys installed, to dump the BIOS settings from all the systems then vimdiff them to see if there is any CMOS parameter being different for the systems that regularly reboot compared to the system(s) that do not.

Источник

Smbios 0x16 error supermicro

Профиль | Отправить PM | Цитировать

Добрый день, появилась такая проблема.
Есть сервак, при перезагрузке из-под винды, сервак не хочет стартовать, пищит (5 коротких, 1 длинный), а на экране Intel Reference Code Execution с кодом 02. Судя по бипам — проблемы с памятью. Однако с кнопки ресета всё стартует норм., далее постоял 2 часа и завис. Конфигурация следующая:
— Supermicro X11SSL-F (2 PCI-E x8, 1 PCI-E x16, 4 DDR4 DIMM, Video, Dual Gigabit LAN);
— QuadCore Intel Xeon E3-1240 v5, 3700 MHz (37 x 100);
— 2хKingston 8GB DDR4 PC4-17000 [KVR21E15D8/8];
— Два зеркала на встроенном контроллере Intel.
Перезагружался, т.к. устанавливал последние обновления от MS за сентябрь. ОС — 2008R2. Здесь аналогичная проблема, только память другая. Также натыкался ещё на несколько подобных случаев. Снёс все установленные обновы (кроме обновки для ie11), а именно: KB3184471, KB3177186, KB3175024, KB3184122, KB3185911. И всё ребутнулось успешно. Кто-н имел дело с похожим? »

Добрый день. Что-нибудь решилось с проблемой памяти?

Абсолютно таже проблема на Supermicro X11SSH-LN4F с 2хKingston 8GB DDR4 PC4-17000.
Тесты ничего не выявили.
Началось тоже после перезагрузке при обновлениях.
Прошло после посещения БИОС и потыканья вроде ничего не значащих пунктов с последующим сохранением.
В View SMBIOS Event Log также было одно старинное сообщение smbios 0x16.

Источник

Adblock
detector

gan34
Новичок

Зарегистрирован: 08.10.2019
Пользователь #: 172,307
Сообщения: 4

Источник

Smbios 0x16 error supermicro

Профиль | Отправить PM | Цитировать

Судя по бипам — проблемы с памятью. »

Это сообщение посчитали полезным следующие участники:

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

Smbios 0x16 error supermicro

Профиль | Отправить PM | Цитировать

Судя по бипам — проблемы с памятью. »

Это сообщение посчитали полезным следующие участники:

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

Источник

SuperMicro X10SL7-F

grep137

Dabbler

Ziferius, I’m getting some strange results from one of the modules I got from Superbiiz back in March (see below).

Samsung DDR3-1600 ECC CL11
Mfr Part Number: M391B1G73QH0-YK0

Sir.Robin

Where are you getting your memory, if you don’t mind me asking?

Sent from my iPad using Tapatalk

I have Kingston for my primary system. My secondary will run on Crucial ECC initially. Might exchange that later.

Have you checked CPU then? Bent pins?

Sir.Robin

Ziferius

Dabbler

Ziferius, I’m getting some strange results from one of the modules I got from Superbiiz back in March (see below).

Samsung DDR3-1600 ECC CL11
Mfr Part Number: M391B1G73QH0-YK0

Interesting. That seems like an aweful lot, but that’s why we run ECC. it catches and fixes that.
Cyber jock is definitely proved right (yet again) why ECC is so important.

Источник

Supermicro BMC watchdog-caused reboots

I’ve recently acquired a SuperMicro X10SLL-F motherboard, which has a built-in BMC (Aspeed AST2400 chip). I want to use built-in watchdog controller when running linux on server (gentoo hardened).

I enabled watchdog function in bios then switched motherboard jumper from hard-reset to NMI (watchdog timeout action, for testing purposes to avoid rebooting). About soft — I installed and added to default runlevel watchdog program (sys-apps/watchdog) which is configured to ping watchdog device (/dev/watchdog, which is present) every 10 seconds. Watchdog timeout is set to 250 seconds.

Programs apparently see watchdog hardware (ipmitool with openipmi enabled):

However, after certain amount of time I get (with good «current countdown» values reported by programs above):

Which is NMI, apparently caused by watchdog timeout. Little less than a minute after that machine hard-reset happens.

Where is a problem and which direction should I dig to?

EDIT: kernel messages related to ipmi:

EDIT: I tried to use bmc-watchdog with configuration «-u 4 -p 2 -a 0 -F -P -L -O -i 300 -e 10». So only SMS/OS time is in use, pre-timeout interrupt is set to NMI, timeout action is set to NONE:

But this led to no change at all.

EDIT. Also when I trigger watchdog timer with echoing x00 to /dev/watchdog and then kept it untouched — system is correctly rebooted after default 10 second timeout. So watchdog works good but at exactly 350 seconds from startup system reboots.

EDIT. I checked BMC system event log (SEL) and found this after reboot:

What is interesting here — is that event marked as «status only». And even so, system is rebooted. When I trigger watchdog timeout intentionally, logs are different:

Источник

Adblock
detector

Источник

Здравствуйте.

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

Спасибо.

Источник

4-56

Chapter 4: BIOS setup

DATE TIME ERROR CODE SEVERITY

01/01/2000 01:19:45 Smbios 0x16 N/A

Log OEM Codes [Enabled]

Enables or disables logging of EFI status codes as OEM codes (if not already converted to

legacy). Configuration options: [Disabled] [Enabled]

Convert OEM Codes [Disabled]

Enables or disables converting EFI status codes to Standard Smbios types (Not all may be

translated). Configuration options: [Disabled] [Enabled]

4.7.2

View Smbios Event Log

This menu displays all Smbios event logs.

DESCRIPTION

Log Area Reset

Main Advanced Event Logs Boot Monitor Security Tool Exit

Event Logs

Источник