Explaining and Troubleshooting WriteCache Disk Drive Letter Assignment

Explaining and Troubleshooting WriteCache Disk Drive Letter Assignment

book

Article ID: CTX133476

calendar_today

Updated On:

Description

This article explains the process involved on drive letter assignments for target devices and how to troubleshoot writecache drive letter changes.

Background

Mount Manager is the component responsible for managing volume names and drive letter assignments on windows. It has a database that is recorded on the registry under the HKLM/SYSTEM/MountedDevices key. When a new disk is installed on the system, the Mount Manager Creates a new unique ID for the disk and saves it into the registry with the "\??\Volume{GUID}\ naming scheme, this is unique and persistent for this system. If the disk is plugged on another system, a new unique ID is created. The uniqueid key is stored as a binary registry and has on its data the MBR Disk Signature, which is unique to the disk and will persist among all the systems where the disk will be plugged, for example:

User-added image

After the volume is formatted and a drive letter is assigned, one new key is created with the letter assignment, it has the \DosDevices\{Letter}\ naming scheme, and is stored as binary registry with the same contents as the uniqueid key, as displayed:

User-added image

For consistency, one \DosDevices\{Letter}\ registry is created for each letter, therefore if a new disk with different signature is added to the system, windows overwrites the registry and assign the letter for the new disk. You come across this behavior when a target device starts as standard on a new target (physical or virtual) that was not cloned from the golden image. To ensure that the new system will be consistent with the drive letter assignment, you must change the unique id for the writecache disk to match the master target device disk.


Instructions

Complete the following procedure to troubleshoot the writecache disk drive letter:

  1. On the Golden Image (running as private), assign the letter based on the requirement.

    For test purposes, let us use W.

    User-added image

  2. Open a command prompt and run the command “diskpart”, on the diskpart command line and run list disk.

    User-added image

  3. Select the writecache disk using the command “Select disk {writeCache disk}”.

    User-added image

  4. Run the command “uniqueid disk” and note the result.  For this example, the unique Disk ID = 917E9869

    User-added image

  5. Log on the target device that is starting with the different drive letter, as displayed in the following screen shot.

    User-added image

  6. Open command prompt and run the same commands used on the Golden Image.

    User-added image

    Note: Note that the Disk ID is different.

  7. Using the Disk ID from step 4 above from the Golden image, run the command “uniqueid disk ID=GoldenDiskID”.  In the example, the command would be "uniqueid disk ID=917E9869.  This changes the disk id to match the id from the golden image. 
Re-run the command "unqueid disk" to check the id is changed.
  1. Restart the target device.

  2. The WriteCache Drive letter should be the same in the target device as in the master disk.

    User-added image

Issue/Introduction

This article explains the process involved on drive letter assignments for target devices and how to troubleshoot writecache drive letter changes.

Additional Information

http://msdn.microsoft.com/en-us/library/windows/hardware/ff567603(v=vs.85).aspx

http://technet.microsoft.com/en-us/library/cc770877(v=ws.10)

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc730793(v=ws.11)