HP X1000/3000 G2 Network Storage System Upgrade to Microsoft Windows Storage Server 2012 (B7D88-96059, December 2012)

\\?\Volume{94b58beb-7d7a-438f-9ed3-1b19920e8e5d}\
F:\
\\?\Volume{12eb4f84-8c62-4259-8582-3110271cb738}\
G:\
\\?\Volume{83c0005b-4f33-49ba-9c88-2d69b7339b00}\
H:\
\\?\Volume{38199cb1-1332-11e2-9409-806e6f6e6963}\
S:\
\\?\Volume{38199cb2-1332-11e2-9409-806e6f6e6963}\
C:\
PS C:\Windows\system32>
In this example, if the volume that is not mounted at any drive
letter had failed the cluster validation test, then its volume name
(\\?\Volume{ee4014fa-2310-4b34-8fd9-c6f402669b9c}
) may be used.
For each volume that failed the cluster validation test, run
chkdsk /f on the volume. For example:
PS C:\Windows\System32> chkdsk /f D:
PS C:\Windows\System32> chkdsk /f
“(\\?\Volume{ee4014fa-2310-4b34-8fd9-
c6f402669b9c}”
Enter Y if you receive the following message:
Chkdsk cannot run because the volume is in use
by another process. Chkdsk may run if this
volume is dismounted first. ALL OPENED HANDLES
TO THIS VOLUME WOULD THEN BE INVALID. Would
you like to force a dismount on this volume?
(Y/N)
After repairing disks with chkdsk, retry the cluster validation,
and create the cluster.