Possible Causes
After the local storage system is recovered, it detects the third-party LUN and reports the eDevLUN to the host. I/Os from the host to the eDevLUN fail before the eDevLUN is recovered. As a result, the file system created based on the eDevLUN cannot be read, and the host detects the eDevLUN as a raw disk.
Fault Diagnosis
Figure1 Flowchart for troubleshooting an eDevLUN detected as a raw disk

Procedure
Check whether the third-party LUN corresponding to the eDevLUN is connected.
Check whether the local storage system is reset.
Disconnect the cable between the host and local storage system (or disable the host's optical port that connects to the switch).
Wait until no physical drive letters can be detected on the host.
Connect the cable between the host and local storage system (or enable the host's optical port that connects to the switch).
Check whether the fault is rectified, the file system created based on the eDevLUN is recovered, and original files remain.
If yes, no further action is required.
If no, keep the fault environment intact and contact technical support engineers.