Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a Windows Server 2003 machine using Microsoft iSCSI Initiator that connects to a Fujitsu DX80. I've added a target that uses mutual CHAP and works wonderfully until I reboot. I have set the target to be persistent and bound the volume properly, but upon reboot it fails to successfully mount the drive. I see a few events in the System log that are of particular interest.

Early on in the boot process I see this

Event Type: Error
Event Source: dmboot
Description: dmboot: Failed to start volume Volume51 (M:)

Later on, I see this a couple of times

Event Type: Error
Event Source: iScsiPrt
Description: Initiator Service failed to respond in time to a request to encrypt or decrypt data.

Lastly, and probably most importantly, I see this

Event Type: Error Event Source: MSiSCSI Description: Timeout waiting for iSCSI persistently bound volumes. If there are any services or applications that use information stored on these volumes then they may not start or may report errors.

Armed with the knowledge of that last event, I tried to tweak the timeouts to be a bit longer. I modified the VolumeRetryCount to 720 and the VolumePostDiscoveryTimer to 90000. These had no effect on the outcome other than extending what is already a very slow boot process.

I've read this article, KB870964, but it doesn't apply to my situation since I'm not even getting to the point where I could be expecting a network share to map.

Any ideas?

EDIT: I've tried it without any CHAP authentication and it still doesn't work.

share|improve this question
add comment

1 Answer

up vote 2 down vote accepted

OK, I found the problem. This is a quote from the Microsoft iSCSI Initiator Version 2.X Users Guide.

Dynamic disks on Windows Server 2003, Windows XP and Windows 2000
Configuring volumes on iSCSI disks as Dynamic disk volumes using the Microsoft software iSCSI initiator is not currently supported. It has been observed that timing issues may prevent dynamic disk volumes on iSCSI disks from being reactivated at system startup.

The use of dynamic disk volumes with Windows Vista and Windows Server 2008 is supported.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.