Post reply

The disk is off line because of a policy set by an administrator

  • January 17, 2011 at 10:43 am

    #230268

    Howdy,

    I am having a vexing problem with a SQL Server 2005 cluster on a Windows 2008 R2 cluster.

    Problem is, on node A I can see the SAN disks in Windows Explorer and Disk Management, but I cannot see all the SAN disks in Windows Explorer on Node B. On Node B Disk Management shows Disk 1 and Disk 4 as "Reserved" but without drive letters. I can access no properties of the disks, because "The disk is offline because of a policy set by an administrator".

    The SAN disks in question are the disks that contain the MDF and LDF files. I can see the SAN disks for the quorum and DTC on both nodes.

    The SQL Server cluster resource fails over just fine, SQL Server comes on line and I can read in the properties of the master database that SQL Server is having no trouble accessing the files. I just can't access the disks in Windows Explorer and Disk Management

    I tried to fix this using diskpart.

    DISKPART> select disk 4

    Disk 4 is now the selected disk.

    DISKPART> rescan

    Please wait while DiskPart scans your configuration...

    DiskPart has finished scanning your configuration.

    DISKPART> attributes disk clear readonly

    DiskPart failed to clear disk attributes.

    DISKPART> attributes disk

    Current Read-only State : Yes

    Read-only : Yes

    Boot Disk : No

    Pagefile Disk : No

    Hibernation File Disk : No

    Crashdump Disk : No

    Clustered Disk : Yes

    DISKPART>

    Now why can't I clear the read only state? This has me vexed. I have found pretty much the same instruction on many web sites but no advice about what to do when the instruction fails. Restarting both nodes, running diskpart from the gui "as administrator" is not helping. My user is a member of the local administrator group anyway ... can't figure out what to do.

    Thanks for any advice.

  • January 23, 2011 at 6:11 pm

    #1277017

    Gaius,

    In a Windows cluster, the disk will only be available where the disk is currently active. Since the disks are part of the SQL Server application within the cluster, the disks will only be available within explorer on the node that SQL Server is currently running.

    If SQL is running on node A of the cluster, only node A will see the disks locally within explorer.

    You can access them via the UNC path by using the SQL Server network name (for example, if you have a G:\ drive under SQL Server, \\sqlservernetworkname\G$\).

    Hope that clarifies what you are seeing.

    Regards,

    Steve

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply