ISCSI in windows 20008

I'm using rocket iscsi with a virtual disk image set up on another server.  I have a production server that connects to this iscsi drive using windows 2008 iscsi initiator.  When either server reboots, or loses power and the other one doesn't, it creates some wacky halt condition where the SQL server still runs, but in a very limited way (The SQL DB is not on the ISCSI volume, FYI-- nothing system related should be, no page, no index, etc) It won't run any maintenance plans and it won't gracefully shutdown.  I'm assuming there is some system patrol writing to this iscsi volume when the condition occurs, because the windows event viewer is plague with bad sector warnings.  

I've tried round-robin and failover, but the problem still occurs.  Is this native to ISCSI in 2008?  Is there a way to make it content with being removable?  Can I make it pause or increase a timeout value to 500 seconds?
LVL 16
Chris HInfrastructure ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Davis McCarnOwnerCommented:
iSCSI treats the storage device as if it were a local, block driven I/O device and you should never have direct access to it from two different PC's.  Doing so is asking for data corruption.
M$ reccomends using a dedicated pair of NICs for access to the iSCSI device and then you should share it to other systems that need access:
Chris HInfrastructure ManagerAuthor Commented:
I understand that.  There is one server connected to one iscsi share.  When either the storage server reboots or the 2008 server reboots, the 2008 server acts really stupid.  I need this to stop.  There is nothing system related, other than system volume information, which would have a lock on the drive.  I only have this issue with 2008 iscsi Initiator.  Vmware is much more graceful....
Davis McCarnOwnerCommented:
There must be something open on the storage server from the other server and assuming the iSCSI is a mapped drive, it could be the system volume information which you could disable on the 2nd server.  Its in the advanved system properties on the system restore or system protection tab.
If that ain't it, we need to figure out what is open.
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Chris HInfrastructure ManagerAuthor Commented:
Interesting...  2008 sp1 (Not 2008 R2) does not contain system protection, but I think you're on to something.
Chris HInfrastructure ManagerAuthor Commented:
I started down the path you were going and found a lot of people trying to resolve the issue are using a program from MS called Handle.  This is a list of handle locks on the drive.  

 3F4: File  (R--)   F:\$Extend\$RmMetadata\$TxfLog\$TxfLog.blf
  538: File  (R--)   F:\$Extend\$RmMetadata\$TxfLog\$TxfLogContainer00000000000000000001
  580: File  (R--)   F:\$Extend\$RmMetadata\$TxfLog\$TxfLogContainer00000000000000000002
  58C: File  (RWD)   F:\$Extend\$RmMetadata\$Txf
  1FC: File  (RWD)   F:\$Extend\$ObjId
  204: File  (R--)   F:\System Volume Information\tracking.log

Any idea how to free these so the system doesn't halt if the drive disappears?
Davis McCarnOwnerCommented:
Your entry for F:\$Extend\$RmMetadata\$TxfLog\$TxfLog.blf only occurs if the drive is mounted locally (meaning, most probably, that iSCSI has been initiated.
It needs to be a normal network share with no iSCSI involved, at all.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris HInfrastructure ManagerAuthor Commented:
I gave up and went with unstoppable copier, some registry edits and a network share.  Pray for me...
Chris HInfrastructure ManagerAuthor Commented:
The downfall of 2008 ISCSI is that it must be persistent or redundant, otherwise a locally mapped drive with a windows volume will always demand access to the drive.  Bummer...  I believe the problem is resolved in windows 2008R2, in which the user is able to disable all the locking features on the drive, such as indexing and recovery.  Thanks for the suggestions!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.