When you use dynamic disks to create logical volumes by striping or spanning, in a SAN environment, you may experience the subject behavior.
This problem is caused by the host bus adapter miniport driver not reporting storage devices to the server in time.
NOTE: If the volumes don't eventual come online, you can use a Diskpart.exe script to do it manually.
Contact the SAN vendor to insure that the firmware, drivers, and configuration are current and correct.
NOTE: Your event log may contain:
Event Type: Error
Event Source: dmboot
Event Category: None
Event ID: 2
Date: MM/DD/YYYY
Time: HH:MM:SS
User: N/A
Computer: <ComputerName>
Description: dmboot: Failed to start volume Volume3 (no mountpoint)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00000000 004e0002 00000000 c0500002
0010: 00000000 00000000 00000001 00000000
0020: 00000000 00000000
NOTE: I would use the Freeware Disk Manager Diagnostics tool which queries the dynamic disk database and redirects the output to a text file.
NOTE: See Disk Manager Diagnostics (Dmdiag.exe) Command-Line Tool.
