Heh, I also just sacrificed a chicken:) Anyway, what do the logs say on the target? Nothing? If it were me, I would boot a Linux disc, like a centos install disc, and discover the target, then try and login to that thing and make an fs to see if it's a windows issue or if the san is farked. At least you will know where to spend your time. If you need some help with that, email me offlist.
Since you are using HBA's and SANSurfer, there are many other failure points. I'm not clear on whether or not you tried over a simple nic using the MS ini? jlc -----Original Message----- From: S Conn. [mailto:[email protected]] Sent: Tuesday, April 14, 2009 9:53 AM To: NT System Admin Issues Subject: iSCSI and Initialize Disk issues Guys, I have an IBM DS3300 iSCSI SAN and I'm having issues with Windows 2003 servers initializing the LUNs as drives. The setup: Server A: Windows 2003 SP2, Microsoft iSCSI Initiator, mapping to a 500gb LUN. Has a Qlogic fiber card attaching to different SAN using SANSurfer. Server B: Windows 2003 SP1, Microsoft iSCSI Initiator, mapping to a 400gb LUN. Both LUNs are on the same IBM DS3300 The error: Both servers see their disks in Disk Manager and in diskpart. Disk Manager even asks if I'd like to initialize the disk. Trying from diskpart, I get the error "The disk management services could not complete the operation." when trying to do the command "create partition primary align=64" (even if I leave the align out, same error). In Disk Manager, I choose "Initialize Disk", I get the error "The operation did not complete. Check the System Event Log for more information on the error." The event log shows nothing. I have two other Windows 2003 servers using the Microsoft iSCSI Initiator to connect to this very DS3300 (using their own LUNs) and have had no issues. I cannot find much of anything on the Internet about these errors (unless I was doing PE or dynamic disks, which I'm not). Now, I had another 2003 server at another site that had this error connecting to a different DS3300 via a Qlogic iSCSI HBA using SANSurfer. I installed Microsoft Hotfix 948699 (http://support.microsoft.com/default.aspx?scid=kb;en-us;948699) and it worked. This hotfix, however, did not work on the two servers listed above. I've tried: VDS registry entry from this article: (http://windowsitpro.com/article/articleid/81899/jsi-tip-8514-windows-server-2003-diskpartexe-reports-the-disk-management-services-could-not-complete-the-operation-when-you-attempt-to-perform-storage-management.html) Microsoft Hotfix 948699 Upgrading SANSurfer (on the machine that has SANSurfer) Using the latest iSCSI initiator software Destroying/recreating the LUNs, connections, etc Following IBM's setup guide regarding MS iSCSI Initiator step-by-step Multiple reboots Also tried hotfix 949001 on one of the servers (http://support.microsoft.com/kb/949001) Chicken sacrifice (didn't help, but was tasty) Screaming profanities at the servers via rdp sessions Has anyone run across this issue or have any ideas? Thanks for ANY help you guys have, Seth ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
