You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just ran az vm repair run -g xxx-rg -n xxxvm-1 --run-id win-chkdsk-fs-corruption --verbose
as well as
az vm repair run -g xxx-rg -n xxxvm-1 --run-id win-sfc-sf-corruption --verbose
Both commands did not work and gave me the follwing error message.
The vm was still bootable and usable but had a disk error.
error
Running script on VM: xxxdvm-1
Log file is too large and has been cutoff at the start of file. Please locate the log file within the VM using the logFullpath to check full logs.
Can you confirm your version of vm-repair with az extension show --name vm-repair? If it is 0.5.8, can you try updating to 0.5.9 and retrying: az extension update --name vm-repair
If that fails, can you try downgrading to 0.5.7 and retrying:
az extension remove --name vm-repair
az extension add --name vm-repair --version 0.5.7
Hello,
I just ran
az vm repair run -g xxx-rg -n xxxvm-1 --run-id win-chkdsk-fs-corruption --verbose
as well as
az vm repair run -g xxx-rg -n xxxvm-1 --run-id win-sfc-sf-corruption --verbose
Both commands did not work and gave me the follwing error message.
The vm was still bootable and usable but had a disk error.
error
Script returned with error:
I cannot check the logs status is SUCCESS but i doubt that it worked because
win-chkdsk-fs-corruption
took just 70 seconds for 512 GB disk.Any help appicieated.
The text was updated successfully, but these errors were encountered: