Hi, guys!
Do you know what can I do if a LUN cannot be accessed or data is abnormal? Don't worry, the post will share with you!
Question：
The LUN cannot be accessed or data is abnormal.
Answer：
The solution is as follows:
1. Log in to DeviceManager and check whether the storage system is normal, whether the front-end link is normal, and whether intermittent disconnection occurs.
2. If multiple hosts are connected to the same storage system, check whether the host configuration is incorrect. If the ports of the two hosts are configured in the same host configuration, the two hosts access LUNs at the same time, causing data damage.
For example:
The two ports of the HBA on host 1 are as follows:2000707be87fb4da 2100707be87fb4db
The two ports of the HBA on host 2 are as follows：2100707be87fb4e0 2100707be87fb4e1。
Create LUN 1 on the storage device for host 1.
In normal cases, two ports of the same host should be allocated to the same host configuration, and LUNs should be mapped to the host configuration, that is, 2000707be87fb4da and 2110707be87fb4db should be mapped to host configuration 1. Map LUN 1 to host configuration 1 so that host 1 can see LUN 1 through two paths.；However, if the configuration is incorrect,，Map 2000707be87fb4da and 2110707be87fb4e0 to host configuration 1. After LUN 1 is mapped to host configuration 1, LUN 1 can be viewed on both host 1 and host 2. In a non-cluster environment, data on LUN 1 may be damaged.
In this case, reconfigure the port. If the data has been damaged, the host can only attempt to restore the data.
3. Check whether the multipathing software is installed and runs after the multipathing software takes effect.
You can view the entered _tmain file in the InstallationLog.txt file to determine the UltraPath installation time
as shown：
To view the time for loading the multipathing driver, check the Trigger opening for log.cfg file in UPLOG_0.txt.
as shown：
This is my solution, how about yours? Go ahead and share it with us!
