- Veeam Support Knowledge Base
- "Failed to detach SCSI lun" errors in vSphere after finishing Instant Recovery or File-level restore from storage snapshots
"Failed to detach SCSI lun" errors in vSphere after finishing Instant Recovery or File-level restore from storage snapshots
| KB ID: | 2805 |
| Product: | Veeam Backup & Replication |
| Version: | 9.x |
| Published: | 2018-11-29 |
| Last Modified: | 2020-08-13 |
| Languages: | DE |
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
You might see "Failed to detach SCSI lun" errors in vSphere during the unexport phase when restoring items (file-level restore) from storage snapshot or doing an Instant Recovery from storage snapshot because of certain VMware behaviour. Both types of the restores include a step when storage snapshot clone is presented as a temporary datastore which should be unmounted or detached when the restore is finished.
Cause
By default when the device is detached, it stays in an unmounted state even if the device is re-presented (that is, the detached state is persistent). That positively means that it's possible to exhaust the limit of 512 detached devices which can lead to aforementioned error message
Solution
To clean up the list please refer to this kb article: https://kb.vmware.com/s/article/2004605
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
