I was surprised to see that, even after deletion and re-add of the disk, the disk remained with a status of “offline” and would not come online. To make it even stranger, the only option I saw when right-clicking on the disk in Disk Management, was “Help”.
Say what?! The user and server had no policies set on them; none whatsoever!
Open a command prompt and type “diskpart.exe”.
You will now receive a diskpart-prompt:
Now type “san”. This will provide you with the current configured SAN policy:
So this means that the system was right… there was a policy configured… but I didn’t configure it, did I? Anyway, back to solving the issue.
In the diskpart-prompt, type “san policy=OnlineAll”.
This will result in the following message:
Diskpart successfully changed the SAN policy for the current operating system.
Disk ### Status Size Free Dyn Gpt
Disk 0 Online 30 GB 0 B
Disk 1 Offline 50 GB 1024 KB
In my case, disk 1 was offline so I typed “select disk 1” which provided:
Disk 1 is now the selected disk
Disk attributes cleared successfully.
This will give an output something like:
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
After the last check has been successful, type “online disk” to bring the disk online.
The disk should be available right away in Disk Management. If not the case, close and re-open Disk Management.
After I’ve found the solution I started searching on the internet. It seems that Microsoft has decided to change how disks are handled as of Windows Server 2008 Enterprise/DataCenter. The default SAN disk policy is now VDS_SP_OFFLINE_SHARED, with an exception for the boot-disk.