Link to home
Create AccountLog in
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Avatar of getzjd
getzjd🇺🇸

MSiSCSI Timeout - Event ID 103 - 2003 server hanging connected to CX4-120
We have an EMC CX4-120 iSCSI SAN currently connected to one host as a file server on 2008 storage server that is working fine.  We recently purchased another server and due to our current SAP environment, had to load Windows 2003 x64 Enterprise on it.

I loaded v 2.08 of the MS iscsi initiator, navisphereCLI, Navisphere agent, and powerpath administrator.   I have 5 raid5  LUNS being attached which correspond to F: 70GB, G: 70GB, H: 70GB, I:, 1000GB, Z: 20 GB.

If I attach them while the server si running, everything appears to function correctly, but if I reboot, I the server will usually hang after login and the drives either slowly appear or not at all.  For example, right now,  PowerPath administrator shows all 5 drives, but the disk manager hangs when I try to view them and In explorer, it only shows 4 of the 5.  The 1000GB was missing for about 10 minutes until it finally appeared.

Event Viewer shows a few errors that only appear if I have iSCSI drives attached.  If I disconnect them and reboot, all is well, no system hangs.

Powerpath shows all paths up and active.

I have tried “iscsicli ClearPersistentDevices"

I do not understand the event id relating to 192.168.1.3 as a target.  That target is up and active and we do not receive these errors on the Windows 2008 server.


Ideas?


Event1.JPG
Event113.JPG
Event103.JPG
LUN.JPG

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of dovidmicheldovidmichel🇺🇸

Update storport.sys
http://support.microsoft.com/kb/950903

Make sure the latest NIC driver is installed.

If that does not help, check for an iSCSI initiator from the manufacturer of the NIC rather than using the MS version.

ASKER CERTIFIED SOLUTION
Avatar of getzjdgetzjd🇺🇸

ASKER

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account

Avatar of getzjdgetzjd🇺🇸

ASKER

Was a few registry settings for timeouts

Avatar of Paul SPaul S🇺🇸

Can you please share which registry settings? It was not the dependency settings?

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of getzjdgetzjd🇺🇸

ASKER

Sorry, I misspoke when I said "registry" settings.   The changes specified in the article I originally posted solved the issue.  http://support.microsoft.com/kb/870964

Avatar of Andres BravoAndres Bravo🇺🇸

I'm no longer able to see the solution

Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).