Storage migration for virtual machine failed with error 'Unspecified error ' (0x80004005)

Question

Hello,

On Standalone S2D (not Azure Stack) cluster after shut down cluster (gracefully with all procedures) before power outtage happen while i run all envirtment i can't do storage migration. VM has shared vhdx (vhdx set) with another VM. I tried do storage migration from vm 1 and vm 2, from Failover Cluster MMC, from AdminCenter all time with the same error. In web i only found information about problem with replication between 2 nodes, or connected iso, but affected vm are not replicated and iso are disconnected and removed. At this moment shutdown vm and re-attach disks in not allowed. This is SQL cluster vm. Can someone help with this issue?

Regards

Answer 1

Hi Xu Gu,

Hope you’re doing well.

i don't have green light to restart vm-01. First maintenance window will be on 1st week of January. I meantime i changed in vm-02 (this server i can restart) compatibility and tried to run storage migration but problem was the same. Can we try something more before January?

Best Regards

Answer 2

Hello Xu Gu,

Hope you’re doing well.

Thank you for update. Restart vms is planned for tommorow. I will add the option to both vms and i will update you.

Best Regards

Answer 3

Hope you’re doing well.

Thanks for your update.

Based on the information provided, I have summarized the following possible reason for your reference:

According to the screenshot you attached, It is possible that VM -01 has a configuration problem. You can select the options below and try storage migration again to check whether it is feasible:

Please let me know whether it is feasible.

Best Regards

Answer 4

Hello Xu Gu,

Thank you for interest the case. Below is answers for your questions:

Is the account logged into the cluster a domain account?

Yes

Please check the following configuration, right-click question machine, select “settings”, and check the “Processor -> Compatibility”:

All vms in cluster have the same compatibility

Please check the system and application logs from Event Viewer to see if there are any related errors. If exist, please provide us the screenshot.

I found only:

I checked vm on host-03 and all vm don't have attached .iso. host-03 is also not have connected .iso. Fires screenshot happen while i try run storage migration.

At the same time, please check “Microsoft-Windows-SmbClient%4Connectivity” log under path C:\Windows\System32\winevt. Check whether the network issue exists.

All logs is with info level. No errors in mentioned time.

(Compare-VM -Name xx -DestinationHost xx).Incompatibilities | fl *

I have only error with 1 host

What’s more, we suggest you update the driver, patches, and firmware to the latest.

That is a case. This is the last host from i must evacuate vms for update firmware task. Live migration works fine but i have problem only with storage migration. The affected vm have files on host-03.

Best Regards

Answer 5

Hi Bartosz,

Hope you’re doing well.

Is the account logged into the cluster a domain account?

Please check the following configuration, right-click question machine, select “settings”, and check the “Processor -> Compatibility”:

Please check the system and application logs from Event Viewer to see if there are any related errors. If exist, please provide us the screenshot.

At the same time, please check “Microsoft-Windows-SmbClient%4Connectivity” log under path C:\Windows\System32\winevt. Check whether the network issue exists.

Due to possible compatibility issues, please open PowerShell and then input the following command:

Compare-VM -Name xx -DestinationHost xx

---

(Compare-VM -Name xx -DestinationHost xx).Incompatibilities | fl *

Please provide us the screenshot. Thanks.

What’s more, we suggest you update the driver, patches, and firmware to the latest.

Hope my answer can help u!

Best Regards,

Xu Gu