Windows Server TechCenter > Windows Server Forums > File Services and Storage > Getting Device Not Ready for SAN drives (HBA QLA 2462)
Ask a questionAsk a question
 

Proposed AnswerGetting Device Not Ready for SAN drives (HBA QLA 2462)

  • Friday, October 12, 2007 4:51 PMYashmeet Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi ,

      I am trying to get the SAN luns detected by the Windows 2008 Operating system. I can see the disks in the Logical Disk Manager. But when I try to bring the disks online or when I try to Initialize the disks I get the "Device Not Ready" error message. Any help or insight would be helpful.

    Thanks......

All Replies

  • Sunday, October 21, 2007 6:21 PMChuck Timon [MSFT]MSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Is this only happening in Disk Management or is the same true if you use diskpart CLI?

     

  • Monday, March 03, 2008 9:16 PMKJLitman Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am having the same issue. Have you have any luck with this yet?

     

  • Friday, March 07, 2008 5:08 PMMalu MenezesMSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi, KJLitman

     

    Can you tell us if this is only happening in Disk Management or is the same true if you use diskpart CLI?

     

  • Monday, March 10, 2008 11:55 AMKJLitman Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    This is only happening in Disk Management. I am using MPIO with the Microsoft DSM.

     

  • Monday, March 10, 2008 10:06 PMrajsyd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    I am experiencing exactly the same issue.If I dont use MS MPIO then it shows every attached lun 4 times (4 paths) however it shows up properly in windows explorer and works. Is there any risk in not using MPIO at all - like corrupt volume etc

    Any help would be greatly appreciated.

  • Monday, March 10, 2008 10:42 PMJLMALB Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    I am getting the same error also.  In the System's event log I have this error.

     

    "VDS fails to write boot code on a disk during clean operation. Error code: 80070015@02070008"

     

    Dell 2850 with a PCI-X QLA-200 hba directly attached to an EMC AX-100 running Server 2008 STD x86.

    • Proposed As Answer byrajsyd Friday, July 11, 2008 4:33 AM
    •  
  • Tuesday, March 11, 2008 12:21 AMJustinMS Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    All who are experiencing this issue,

     

    Could you please post which version of Windows Server 2008 you are running (i.e. Beta, RC0, RC1, RTM, etc).

     

    Thanks!

     

    - Justin

     

  • Tuesday, March 11, 2008 1:01 AMrajsyd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I think the solution is:

     

    Go into Disk Management right click on the gray area on the disk that says 'unknowm or 'not intialised' - properties -- MPIO tab -  by default the first path is Active/Optimised - if you have more then 1 path (as in our case) change this path to standby and try make one of the other paths Active/Optimised and tick the 'Preferred'  check box and rescan - And one of the other paths should work.

  • Tuesday, March 11, 2008 1:01 AMKJLitman Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    OS: Windows Server 2008 Datacenter x64 RTM.

    Server: 2 x Dell R900

    HBA: QLogic QLE2462

    SAN: EMC CX300

  • Tuesday, March 11, 2008 1:08 AMKJLitman Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    rajsyd,

     

    I have tried this and it works until you reboot or in my case when you are running Failover Clustering. When I fail over to node 2 then back to node 1 the path I changed in the MPIO tab is back to it's default setting. When this happens my disk becomes unavailable and I will get the message "Device Not Ready".

  • Tuesday, March 11, 2008 1:40 AMrajsyd Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    make sure you check the 'Preferred' check box where you change the standby path.
  • Thursday, March 13, 2008 7:16 PMJLMALB Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    2008 STD x86 (6.0.6001).

    Qlogic QLA-200 using built in windows drivers.

    EMC AX-100 direct attatch fiber.
  • Friday, April 25, 2008 1:49 AMfsteinb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Having similar issue with Emulex adapters on McData ED-64M switch with DMX3-24 array mwith 5772 microcode.  Both paths are RW zoned, device is RW_enabled and Ready down both paths.  I believe the initial issue was the device was not ready at the point MPIO detected it.  Then after it was claimed into MPIO the device was readied and marked RW_enabled and even after reboot the device state from OS perspective is not updated.  I added a total of 8 LUN's and 2 were marked not_ready.  Of the 2 only 1 is having the issue.  From the frame perspective I readied the device marked it RW_enabled down all paths.  I then unmasked it, ran rescan from within diskpart, then re-masked it, rescanned, no joy.  Rebooted server again and it was fixed.  It just took a while for the new RW state on the device to be "detected".

     

    Having said all this I don't believe it is a MPIO related issue, this should only track pathing nothing else.  Server 2008 was just slow to detect the RW status.

     

     

    I have attempted the suggestion above about using the other path as active, this also did not work and even if it did you lose redundancy on the one path marked write protected.  If the working path(s) fail you are toast on the last one.