The Drive letter on a volume is lost during a cluster failover following a reboot of the active node.

book

Article ID: 100005267

calendar_today

Updated On:

Description

Error Message

Application log error:

02/23/2011      10:21:10 PM   ERROR               801(0xe5090321)   VxSvc_mount            Failed to add drive letter E: to volume \Device\HarddiskDmVolumes\\

 

If this is a Microsoft Cluster FileShare, then you will receive an error when the FileShare resource tries to come online.

0000121c.000015e8::2011/02/24-03:21:15.541 WARN  [RES] File Server )()>: Failed to open path E:\. Error: 3. Maybe a reparse point...

Cause

- When a volume is assigned a drive letter, the volume/drive letter mapping is maintained by Windows in the Mount Manager database.
- The Mount Manager database contains all volumes (and drive letter mappings) for every volume that has ever been brought on line on this server.
- Whenever a volume arrives, Windows scans the MountManager database to determine if this is a volume that has been imported before, and if so, it checks the drive letter mapping and assigns the drive letter accordingly.
- If no drive letter is found, then the volume is not assigned a drive letter.

Resolution

Work around:

Use the following procedure to bring the Microsoft Cluster resource online.

1. Offline the VMDg resource in the cluster

2. Open VEA

3. Import the DG

4. Right click on the volume, and choose File System -> Change Drive Letter and Path

5. Assign the appropriate drive letter

6. Bring the VMDg resource online in the cluster

 

 

 

Issue/Introduction

Drive letter is lost during cluster failover after a reboot of the active node. The disk group is able to import with no issues, but the drive letter is not assigned. This results in resources that depend on the drive letter to fault when attempting to online.

Additional Information

ETrack: 1933048
Powered by Wolken Software