Модераторы: Trinity admin`s, Free-lance moderator`s
-
vitya_vii
- member
- Сообщения: 22
- Зарегистрирован: 23 окт 2016, 12:16
- Откуда: Брянск
Проблемы с сервером SR1550ALSAS
здравствуйте подскажите при отключении сервера от питания на 5 10 минут сервер после этого не запускается пока не сбросишь bios
в биос выходит 2 ошибки
1. 8110 major 1
2. 5220 major n/a
пере прошил bios до последней версии Intel® Deployment Assistant
Данный пакет содержит:
BIOS : 101
BMC : 68
FRUSDR : 48
указал что корпус sr1550 все прошилось
но сервер все равно кидает такие ошибки и не стартует без сброса биос
да кстати сервер до пере прошивки вентиляторы крутились по максимум сейчас сам повышает, понижает обороты
-
Tert
- Advanced member
- Сообщения: 4233
- Зарегистрирован: 19 янв 2003, 08:09
- Откуда: Москва
- Контактная информация:
Re: Проблемы с сервером SR1550ALSAS
Сообщение
Tert » 24 окт 2016, 14:34
vitya_vii
А что вы после сброса выставляете в настройках BIOS?
-
vitya_vii
- member
- Сообщения: 22
- Зарегистрирован: 23 окт 2016, 12:16
- Откуда: Брянск
Re: Проблемы с сервером SR1550ALSAS
Сообщение
vitya_vii » 24 окт 2016, 14:49
выставляю дату время включаю raid и настраиваю boot загрузку
-
Tert
- Advanced member
- Сообщения: 4233
- Зарегистрирован: 19 янв 2003, 08:09
- Откуда: Москва
- Контактная информация:
Re: Проблемы с сервером SR1550ALSAS
Сообщение
Tert » 24 окт 2016, 15:09
vitya_vii
Вы BIOS сбрасываете с помощью вытаскивания батарейки с платы?
Или по инструкции с помощью джампера J1D3?
-
Tert
- Advanced member
- Сообщения: 4233
- Зарегистрирован: 19 янв 2003, 08:09
- Откуда: Москва
- Контактная информация:
Re: Проблемы с сервером SR1550ALSAS
Сообщение
Tert » 24 окт 2016, 15:55
vitya_vii
У вас проблема с первым процессором.
Попробуйте вынуть его из гнезда и вставить обратно (возможно, что окислился контакт). Или поменять местами два процессора.
И посмотрите на результат.
Коды ошибок:
8110 — Processor 01 internal error (IERR) on last boot.
При сбрасывании BIOS сбрасывается и эта ошибка. Сервер включается.
Когда сервер выключается штатными средствами, то BMC уже не включает его из-за наличия такой ошибки.
-
vitya_vii
- member
- Сообщения: 22
- Зарегистрирован: 23 окт 2016, 12:16
- Откуда: Брянск
Re: Проблемы с сервером SR1550ALSAS
Сообщение
vitya_vii » 27 окт 2016, 10:15
Tert писал(а):vitya_vii
У вас проблема с первым процессором.
Попробуйте вынуть его из гнезда и вставить обратно (возможно, что окислился контакт). Или поменять местами два процессора.
И посмотрите на результат.Коды ошибок:
8110 — Processor 01 internal error (IERR) on last boot.При сбрасывании BIOS сбрасывается и эта ошибка. Сервер включается.
Когда сервер выключается штатными средствами, то BMC уже не включает его из-за наличия такой ошибки.
снял оба процессора почистил поставил результат тот же
запустил на одном процессоре он вывел ошибки
1, 5220 major n/a
2, 9268 minor n/a
-
vitya_vii
- member
- Сообщения: 22
- Зарегистрирован: 23 окт 2016, 12:16
- Откуда: Брянск
Re: Проблемы с сервером SR1550ALSAS
Сообщение
vitya_vii » 27 окт 2016, 16:32
есть еще какие идеи? пока сервер стоит уже весь его перечистил батарейку поменял нечего
-
gs
- Сотрудник Тринити
- Сообщения: 16650
- Зарегистрирован: 23 авг 2002, 17:34
- Откуда: Москва
- Контактная информация:
Re: Проблемы с сервером SR1550ALSAS
Сообщение
gs » 27 окт 2016, 16:35
Машина снята с производства в 2010 году. Может бобик просто сдох?
-
turboprop
- Advanced member
- Сообщения: 244
- Зарегистрирован: 18 июн 2010, 11:22
- Откуда: C.Петербург
Re: Проблемы с сервером SR1550ALSAS
Сообщение
turboprop » 28 окт 2016, 11:14
я бы ещё посоветовал отключить BMC джампером (если он есть). это, конечно, лишит возможности мониторить сервер, но может он будет грузиться и работать.
-
Tert
- Advanced member
- Сообщения: 4233
- Зарегистрирован: 19 янв 2003, 08:09
- Откуда: Москва
- Контактная информация:
Re: Проблемы с сервером SR1550ALSAS
Сообщение
Tert » 28 окт 2016, 14:15
vitya_vii
9268 — Local Console component encountered an output error.
Вернуться в «Серверы — Решение проблем»
Перейти
- Серверы
- ↳ Серверы — Конфигурирование
- ↳ Конфигурации сервера для 1С
- ↳ Серверы — Решение проблем
- ↳ Серверы — ПО, Unix подобные системы
- ↳ Серверы — ПО, Windows система, приложения.
- ↳ Серверы — ПО, Базы Данных и их использование
- ↳ Серверы — FAQ
- Дисковые массивы, RAID, SCSI, SAS, SATA, FC
- ↳ Массивы — RAID технологии.
- ↳ Массивы — Технические вопросы, решение проблем.
- ↳ Массивы — FAQ
- Майнинг, плоттинг, фарминг (Добыча криптовалют)
- ↳ Proof Of Work
- ↳ Proof Of Space
- Кластеры — вычислительные и отказоустойчивые ( SMP, vSMP, NUMA, GRID , NAS, SAN)
- ↳ Кластеры, Аппаратная часть
- ↳ Deep Learning и AI
- ↳ Кластеры, Программное обеспечение
- ↳ Кластеры, параллельные файловые системы
- Медиа технологии, и цифровое ТВ, IPTV, DVB
- ↳ Станции видеомонтажа, графические системы, рендеринг.
- ↳ Видеонаблюдение
- ↳ Компоненты Digital TV решений
- ↳ Студийные системы, производство ТВ, Кино и рекламы
- Инфраструктурное ПО и его лицензирование
- ↳ Виртуализация
- ↳ Облачные технологии
- ↳ Резервное копирования / Защита / Сохранение данных
- Сетевые решения
- ↳ Сети — Вопросы конфигурирования сети
- ↳ Сети — Технические вопросы, решение проблем
- Общие вопросы
- ↳ Обсуждение общих вопросов
- ↳ Приколы нашего IT городка
- ↳ Регистрация на форуме
- Remove From My Forums
-
Question
-
How to rectify
Do i need Agent and controller on my machine to run load test
Error 8110. Could not connect to the specified controller machine or access the controller object. The service may not be running, firewall settings may be blocking the connection request, or the installing
user does not have permissions to connect to the controller machine. Verify the spelling of the controller machine, ensure the executing user is an administrator on the controller machine and the controller machine is configured to allow remote connections.
Refer to the log for details.
Answers
-
Hello Partner.
Based on my understanding if you do not need to generate simulated load for testing, you don’t need to set
up test controllers or test agents to run load test. For better understanding Controllers, Agents, and Rigs, please see:http://msdn.microsoft.com/en-us/library/ms182634(VS.90).aspx
The Error 8110 you got is caused by installing the controller on a computer that has more than one network adapter.
To fix this error, you must bind the controller to one of the network adapter. For further information, please refer to the Binding a Controller to a Network Adapter part of this article:http://msdn.microsoft.com/en-us/library/ms404660(VS.90).aspx
Thanks,
Vicky Song [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.-
Marked as answer by
Monday, February 21, 2011 10:41 AM
-
Marked as answer by
- Remove From My Forums
-
Question
-
How to rectify
Do i need Agent and controller on my machine to run load test
Error 8110. Could not connect to the specified controller machine or access the controller object. The service may not be running, firewall settings may be blocking the connection request, or the installing
user does not have permissions to connect to the controller machine. Verify the spelling of the controller machine, ensure the executing user is an administrator on the controller machine and the controller machine is configured to allow remote connections.
Refer to the log for details.
Answers
-
Hello Partner.
Based on my understanding if you do not need to generate simulated load for testing, you don’t need to set
up test controllers or test agents to run load test. For better understanding Controllers, Agents, and Rigs, please see:http://msdn.microsoft.com/en-us/library/ms182634(VS.90).aspx
The Error 8110 you got is caused by installing the controller on a computer that has more than one network adapter.
To fix this error, you must bind the controller to one of the network adapter. For further information, please refer to the Binding a Controller to a Network Adapter part of this article:http://msdn.microsoft.com/en-us/library/ms404660(VS.90).aspx
Thanks,
Vicky Song [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.-
Marked as answer by
Monday, February 21, 2011 10:41 AM
-
Marked as answer by
I have a very important server that just locked up solid on me. When I rebooted it by the button, I came up with two error codes: 8110 and 8111. I did research and it has to do with the processors. Does it mean that both my processors are bad? What do I do? The motherboard model is s5000vsa.
I attached a picture of the error screen when it rebooted.
DSC-2281.JPG
ComponentsServer Hardware
SQL Server Error Message — Errors 8001 to 8500 A message number uniquely identifies each error message and the error message Some error messages are self-explanatory and can easily be fixed, such as |
Error | Severity | Description |
8101 | 16 |
An explicit value for the identity column in table «Table Name» can only be specified when a column list is used and IDENTITY_INSERT is ON. s |
8102 | 16 | Cannot update identity column «Column Name». |
8103 | 16 | Table ‘%.*ls’ does not exist or cannot be opened for SET operation. |
8104 | 16 | The current user is not the database or object owner of table ‘%.*ls’. Cannot perform SET operation. |
8105 | 16 | ‘%.*ls’ is not a user table. Cannot perform SET operation. |
8106 | 16 | Table ‘<Table Name>’ does not have the identity property. Cannot perform SET operation. |
8107 | 16 | IDENTITY_INSERT is already ON for table ‘<Table Name>’. Cannot perform SET operation for table ‘%.*ls’. |
8108 | 16 | Cannot add identity column, using the SELECT INTO statement, to table ‘<Table Name>’, which already has column ‘<Column Name>’ that inherits the identity property. |
8109 | 16 | Attempting to add multiple identity columns to table ‘%.*ls’ using the SELECT INTO statement. |
8110 | 16 | Cannot add multiple PRIMARY KEY constraints to table ‘<Table Name>’. |
8111 | 16 | Cannot define PRIMARY KEY constraint on nullable column in table ‘<Table Name>’. |
8112 | 16 | Cannot add more than one clustered index for constraints on table ‘%.*ls’. |
8114 | 16 | Error converting data type %ls to %ls. |
8115 | 16 |
Arithmetic overflow error converting numeric to data type numeric. Arithmetic overflow error converting numeric to data type varchar. |
8116 | 16 | Argument data type %ls is invalid for argument %d of %ls function. |
8117 | 16 | Operand data type %ls is invalid for %ls operator. |
8118 | 16 | Column ‘%.*ls.%.*ls’ is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause. |
8119 | 16 | Column ‘%.*ls.%.*ls’ is invalid in the HAVING clause because it is not contained in an aggregate function and there is no GROUP BY clause. |
8120 | 16 | Column ‘%.*ls.%.*ls’ is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. |
8121 | 16 | Column ‘%.*ls.%.*ls’ is invalid in the HAVING clause because it is not contained in either an aggregate function or the GROUP BY clause. |
8122 | 16 | Only the first query in a UNION statement can have a SELECT with an assignment. |
8123 | 16 | A correlated expression is invalid because it is not in a GROUP BY clause. |
8124 | 16 | Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression. |
8125 | 16 | An aggregated expression containing an outer reference must be contained in either the select list, or a HAVING clause subquery in the query whose FROM clause contains the table with the column being aggregated. |
8126 | 16 | Column name ‘%.*ls.%.*ls’ is invalid in the ORDER BY clause because it is not contained in an aggregate function and there is no GROUP BY clause. |
8127 | 16 | Column name ‘%.*ls.%.*ls’ is invalid in the ORDER BY clause because it is not contained in either an aggregate function or the GROUP BY clause. |
8128 | 10 | Using ‘%s’ version ‘%s’ to execute extended stored procedure ‘%s’. |
8129 | 16 | The new disk size must be greater than %d. Consider using DBCC SHRINKDB. |
8130 | 16 | The device is not a database device. Only database devices can be expanded. |
8131 | 10 | Extended stored procedure DLL ‘%s’ does not export __GetXpVersion(). Refer to the topic «Backward Compatibility Details (Level 1) — Open Data Services» in the documentation for more information. |
8132 | 10 | Extended stored procedure DLL ‘%s’ reports its version is %d.%d. Server expects version %d.%d. |
8133 | 16 | None of the result expressions in a CASE specification can be NULL. |
8134 | 16 | Divide by zero error encountered. |
8135 | 16 | Table level constraint does not specify column list, table ‘%.*ls’. |
8136 | 16 | Duplicate columns specified in %ls constraint key list, table ‘%.*ls’. |
8138 | 16 | Duplicate columns specified in %ls constraint key list, table ‘%.*ls’. |
8139 | 16 | Number of referencing columns in foreign key differs from number of referenced columns, table ‘%.*ls’. |
8140 | 16 | More than one key specified in column level %ls constraint, table ‘%.*ls’. |
8141 | 16 | Column %ls constraint for column ‘%.*ls’ references another column, table ‘%.*ls’. |
8142 | 16 | Subqueries are not supported in %ls constraints, table ‘%.*ls’. |
8143 | 16 | Parameter ‘%.*ls’ was supplied multiple times. |
8144 | 16 | Procedure or function <Procedure of Function Name> has too many arguments specified. |
8145 | 16 | %.*ls is not a parameter for procedure %.*ls. |
8146 | 16 | Procedure %.*ls has no parameters and arguments were supplied. |
8147 | 16 | Could not create IDENTITY attribute on nullable column ‘<Column Name>’, table ‘<Table Name>’. |
8148 | 16 | More than one column %ls constraint specified for column ‘%.*ls’, table ‘%.*ls’. |
8149 | 16 | OLE Automation objects are not supported in fiber mode. |
8150 | 16 | Multiple NULL constraints were specified for column ‘%.*ls’, table ‘%.*ls’. |
Error | Severity | Description |
8151 | 16 | Both a PRIMARY KEY and UNIQUE constraint have been defined for column ‘%.*ls’, table ‘%.*ls’. Only one is allowed. |
8152 | 16 | String or binary data would be truncated. |
8153 | 0 | Warning: Null value is eliminated by an aggregate or other SET operation. |
8154 | 15 | The table ‘%.*ls’ is ambiguous. |
8155 | 15 | No column was specified for column <Column Index> of ‘<Object Name>’. |
8156 | 15 | The column ‘%.*ls’ was specified multiple times for ‘%.*ls’. |
8157 | 15 | All the queries in a query expression containing a UNION operator must have the same number of expressions in their select lists. |
8158 | 15 | ‘<Object Name>’ has more columns than were specified in the column list. |
8159 | 15 | ‘<Object Name>’ has fewer columns than were specified in the column list. |
8160 | 15 | A grouping function can only be specified when either CUBE or ROLLUP is specified in the GROUP BY clause. |
8161 | 15 | A grouping function can only be specified when either CUBE or ROLLUP is specified in the GROUP BY clause. |
8162 | 16 | Formal parameter ‘%.*ls’ was defined as OUTPUT but the actual parameter not declared OUTPUT. |
8163 | 16 | The text, ntext, or image data type cannot be selected as DISTINCT. |
8164 | 16 | An INSERT EXEC statement cannot be nested. |
8165 | 16 | Invalid subcommand value %d. Legal range from %d to %d. |
8166 | 16 | Constraint name ‘%.*ls’ not permitted. Constraint names cannot begin with a number sign (#). |
8168 | 16 | Cannot create two constraints named ‘%.*ls’. Duplicate constraint names are not allowed. |
8169 | 16 | Syntax error converting from a character string to uniqueidentifier. |
8170 | 16 | Insufficient result space to convert uniqueidentifier value to char. |
8171 | 16 | Insufficient result space to convert uniqueidentifier value to char. |
8175 | 10 | Could not find table %.*ls. Will try to resolve this table name later. |
8176 | 16 | Resync procedure expects value of key ‘%.*ls’, which was not supplied. |
8177 | 16 | Cannot use a column in the %hs clause unless it is contained in either an aggregate function or the GROUP BY clause. |
8178 | 16 | Prepared statement ‘%.*ls’ expects parameter %.*ls, which was not supplied. |
8179 | 16 | Could not find prepared statement with handle %d. |
8180 | 16 | Statement(s) could not be prepared. |
8181 | 16 | Text for ‘%.*ls’ is missing from syscomments. The object must be dropped and re-created before it can be used. |
8183 | 16 | Only UNIQUE or PRIMARY KEY constraints are allowed on computed columns. |
8184 | 16 | Error expanding ‘*’: all columns incomparable, ‘*’ expanded to zero columns. |
8185 | 16 | Error expanding ‘*’: An uncomparable column has been found in an underlying table or view. |
8186 | 16 | Function ‘%.*ls’ can be used only on user and system tables. |
8190 | 16 | Cannot compile replication filter procedure without defining table being filtered. |
8191 | 16 | Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements. |
8192 | 16 | Replication filter procedures cannot have parameters. |
8193 | 16 | Cannot execute a procedure marked FOR REPLICATION. |
8194 | 16 | Cannot execute a USE statement while an application role is active. |
8196 | 16 | Duplicate column specified as ROWGUIDCOL. |
8197 | 16 | Windows NT user ‘%.*ls’ does not have server access. |
8198 | 16 | Could not obtain information about Windows NT group/user ‘%ls’. |
8199 | 16 | In EXECUTE <procname>, procname can only be a literal or variable of type char, varchar, nchar, or nvarchar. |