Problem and solution when the number of LUNs mapped to a Windows application server exceeds 26 but the system fails to automatically allocate drive letters for creating a partition

1

When the number of LUNs mapped to a Windows application server exceeds 26, the system fails to automatically allocate drive letters for creating a partition. To solve the problem, perform the following steps:
On a Windows application server, the operating system uses 26 letters from A to Z to automatically allocate drive letters. If the number of mapped LUNs exceeds 26, the system cannot allocate more drive letters. You need to change the drive letter to a New Technology File System (NTFS) folder. The procedure is as follows:
1. Create a folder on a disk that has created partitions.
For example, the test folder on disk H.
2. Right-click My Computer and choose Manage from the shortcut menu. The Computer Management dialog box is displayed.
3. In the left navigation tree, choose Storage > Disk management. Right-click Disk Management and choose Rescan Disk from the shortcut menu. The system scans for newly mapped LUNs.
4. Right-click the disk to be initialized and choose Initialize Disk from the shortcut menu. After the initialization is complete, the disk status changes to Unallocated.
5. Right-click an initialized disk and choose New Partition. Select the type and size of the partition.
6. Specify the drive letter.
In the Assign Drive Letter or Path dialog box, select Mount in the following empty NTFS folder and click Browse to select the path of the created folder. For example, select H:\test.
7. Click Next until the partition is created successfully.

Other related questions:
Problem and solution when some LUNs fail to be mapped when LUNs are mapped in batch
After LUN mappings are canceled in batch in a storage system, the LUNs generated on a host still exist. As a result, the storage system returns "Unmapped" with error code 0x05/0x25/0x00 due to I/Os sent using these LUNs. The interface protocol indicates that the error code performs a LUN switchover but the storage system uses a system lock for the LUN switchover. As a result, LUN mapping fails because no system lock can be obtained. To solve this problem, map the LUNs again. Then check whether the number of LUNs that are successfully mapped is correct.

Problem and solution when port mapping on the USG6330 fails
If port mapping fails, check first whether the policy is correct and then view the session table information.

For V3 series unified storage V300R001, how can I query the mapping relationship between LUNs and hosts?
For V3 series unified storage systems V300R001, you can obtain the information about LUNs and its mapped hosts from the mapping view. You can identify the corresponding relationship between storage systems' hosts and their connected application servers in the live network through parameters such as host names and host operating systems. You are advised to use a host name that is easy for you to recognize the host's corresponding application server. For details about how to view mapping views, see Viewing Mapping View Information.

Method to query the mapping relationship between LUNs and hosts on T series V100R005 devices
On the T series V100R005 storage system, you can view information about mapped LUNs by checking the host information. You can identify the corresponding relationship between storage systems' hosts and their connected application servers in the live network through parameters such as host names and host operating systems. You are advised to use a host name that is easy for you to recognize the host's corresponding application server. For details about how to check the host information, see Viewing Host Information.

The application server connected to the OceanStor V3 storage system fails to detect LUNs
Refer to Revelations of Troublesolving cases on the right.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top