Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script returned with error: win-sfc-sf-corruption and win-chkdsk-fs-corruption #68

Open
LeonardSchwenk opened this issue Dec 9, 2023 · 3 comments

Comments

@LeonardSchwenk
Copy link

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

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.

Script returned with error:

{
  "log_full_path": "",
  "logs": "",
  "message": "Script completed with errors.",
  "output": "",
  "resource_group": "xxx-rg",
  "script_status": "ERROR",
  "status": "SUCCESS",
  "vm_name": "xxxvm-1"
}

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.

@rymccall
Copy link
Contributor

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

@LeonardSchwenk
Copy link
Author

@rymccall

Version is 0.5.9

So should I downgrade to 0.5.7 ?

@rymccall
Copy link
Contributor

Yes, try that out and confirm if successful, if so there may be an issue with 0.5.9 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants