- Remove From My Forums
-
Question
-
Hi
We are deploying a VDI environment.
There are few iSCSI error event occurring on Windows 2012 R2 server.
EventID 9: Target
did not respond in time for a SCSI request. The CDB is given in the dump data.
EventID 39: Initiator sent a task management command to reset the target. The target name is given in the dump data.
EventID 7: Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
EventID 20: Connection to the target was lost. The initiator will attempt to retry the connection.
EventID 1: Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.Do you have any idea about these error event. Please let me know if you have any solution/workaround for this issues.
-
Moved by
Friday, January 15, 2016 3:50 PM
-
Moved by
Answers
-
-
Proposed as answer by
Mary Dong
Monday, January 25, 2016 8:52 AM -
Marked as answer by
Mary Dong
Thursday, January 28, 2016 1:09 AM
-
Proposed as answer by
We are experiencing severe slowness with applications with databases stored on our SQL server 2008 R2 machine. These are all VMs running on physical host machines running HyperV and stored on SAN machines. This past Saturday, we installed new switches in our datacenter (we didn’t reboot the hosts afterwards since we verified connectivity). Fast forward to Wednesday afternoon, I receive multiple complaints from various locations regarding the slowness and it hasn’t stopped since. Yesterday evening, I increased the RAM on our SQL server machine significantly and increased the maximum allocation by SQL server accordingly (yes, I left some for the OS). This did nothing to help. I checked to see that indexing and statistics rebuild operations were occurring nightly, and they are. I have checked various logs (SQL Server, the VM it runs on, the host it runs on, etc.) and have seen the following samples:
— On the SQL Server
SQL Server has encountered N occurrence(s) of I/O requests taking longer than X seconds to complete on file …
— On the Physical host machine
Event 9, iScsiPrt: Target did not respond in time for a Scsi request. The CDB is given in the dump data.
I’m not a DBA and this is a bit over my head. Does anyone have an idea where to begin on this? I have looked at Resource Monitor and am seeing high disk usage, but no process in particular is standing out.
Thanks in advance!
We have a three node W2012 R2 Fail over cluster that has been running spotless for years with the HPE P4300 SAN but after adding the HPE Storevirtual SV3200 as a new SAN we are having iScsiPrt errors that HPE Support cannot fix, crashing VMs and also two
of the three fail over nodes.
At first everything seemed to work, but after adding additional disks on the SAN a SAN controller crashed. That has been replaced under warranty but now when moving our servers and especially SQL 2008 Servers to the SAN, problems
start to occur. The VHDX volumes of the SQL servers are thin provisioned.
Live moving of the storage worked fine for none SQL servers. For some SQL servers the servers frooze and operation was halted, so we needed to perform an offline move. Then during high disk IO and especially during backups W2012 R2 FOC started
to behave erratic eventually crashing VMs and in one instance rebooting two fail over nodes, as a result of a flood of iScsciPrt errors in the eventlog:
System iScsiPrt event ID 27 error Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.
System iScsiPrt event 129 warning The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the
component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DeviceRaidPort4
the message resource is present but the message is not found in the string/message table
System iScsiPrt event ID 39 error Initiator sent a task management command to reset the target. The target name is given in the dump data.
System iScsiPrt event ID 9 error Target did not respond in time for a SCSI request. The CDB is given in the dump data.
System iScsiPrt event 129 warning The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the
component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DeviceRaidPort4
the message resource is present but the message is not found in the string/message table
System iScsiPrt event ID 27 error Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iSCSI header.
System FailOverClustering event id 5121 Information Cluster Shared Volume ‘Volume4’ (‘NEMCL01_CSV04’) is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network to the node that owns the
volume. If this results in degraded performance, please troubleshoot this node’s connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished.
After a 2 hour period of these events the FailOver Cluster services started to give errors, VMs failed and finally 2 nodes of our 3 node failover cluster rebooted because of a crash.
Sofar HPE has not been able to fix this. The SV3200 logs has occasional ISCSI controller errors but the error logging in the SVMC is minimal.
HPE support blamed using a VIP and using Sites (a label). Both are supported according to the HPE product documentation. This has been removed and ISCSI initiator has been set to the Eth0 bond IP adresses directly. As problems persist they blamed that we are
using the Lefthand DSM MPIO driver on the initiator connections to the SV3200 which is not the case. Standard MS DSM. Yes the Lefthand driver is on the system for our old SAN but not configured for the SV3200 initiator sessions, which is round robin
with supset.
We are currently facing a legal warranty standoff.
Any pointers or other comparable experiences with the HPE Storevirtual SV3200 SAN?
TIA,
Fred
I am using MS ISCSI initiator to connect to a Promise VTRAK 610i and the server is sending these errors when I start the connection to the ISCSI target. I deleted the LUN’s from the target so that I could increase the size of the volume space and this started after I did this. I looked in the registry and the old lun’s are still showing up but I cannot delete the old registry entries
HKEY_LOCAL_MACHINESYSTEMControlSet001EnumSCSI
I think that if I can clear these out then it will start working again — it seems like the iscsi initiator is trying to connect to the old luns and it is causing the errors. I get an error cannot delete when I attempt to remove them from the registry. Any help will be appreciated. Promise has not been any help with this.
StorageServer HardwareWindows Server 2003
Обновлено 15.01.2017
Всем привет сегодня расскажу как решается и что значит ошибка Не удается установить портал инициатора. Состояние ошибки содержится в данных дампа в Windows Server 2012 R2. Ошибка имеет код 5 источник iScsiPrt, что уже должно вас наталкивать на вектор направления, так как мы с вами знакомились с темой систем хранения данных и там фигурировали диски такого формата подключения, но если вы вдруг не успели еще прочитать данную статью, то чуть ниже вы поймете, о чем речь.
Ошибка код 5 источник iScsiPrt
Для начала, давайте, посмотрим как она выглядит в логах просмотра событий Windows.
Ошибка Не удается установить портал инициатора. Состояние ошибки содержится в данных дампа в Windows Server 2012 R2
Ошибка сыпалась каждые 3 секунды так что весь журнал уже был забит этим мусором (Советую почитать Как почистить все журналы windows с помощью скрипта). Причин может быть несколько рассмотрим их ниже.
Причина 1
Конечное устройство iSCSI, перечисленных на вкладке Избранные конечные объекты iSCSI инициатора больше не доступен. Это может произойти, если имя целевого устройства iSCSI изменяется при изменении IP-адреса или если целевое устройство iSCSI, удаляется из сети.
Причина 2
Целевое устройство iSCSI достигнут предел для числа входящих подключений.
Причина 3
Проблема временное состояние сети временно запретить подключения к целевому устройству iSCSI.
Причина 4
Сетевой стек не полностью подготовлен при инициатор пытался подключиться к постоянных конечных объектов.Инициатор будет пытаться подключиться. Когда сетевой стек полностью подготовлены, подключение должно быть установлено успешно.
В моем случае уже давно на сервере был отключен диск по протоколу ISCSI и в инициаторе ISCSI осталась фантомная запись подключения к диску, удаляем ее и все. Инициатор ISCSI можно найти в Пуск-Панель управление-Администрирование. У вас там либо не должно быть ничего либо только того что уже не существует.
Ошибка Не удается установить портал инициатора. Состояние ошибки содержится в данных дампа в Windows Server 2012 R2-01
Вот так вот просто решается Ошибка Не удается установить портал инициатора. Состояние ошибки содержится в данных дампа в Windows Server 2012 R2.
Материал сайта pyatilistnik.org
Янв 15, 2017 21:08