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

Updating README for Disk Mounting #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Cojacfar
Copy link

Added instructions to mount the disk inside of the OS, as the Powershell script does not do that.

Added instructions to mount the disk inside of the OS, as the Powershell script does not do that.
@@ -54,7 +54,9 @@ The VM recovery script is most applicable when a VM is not booting, as seen on t

9. RDP to the rescue VM to resolve the issue with the OS disk of the problem VM.

10. To swap the problem VM's OS disk back to the problem VM, run the Restore_<problemVmName>.ps1 script located in the same folder as the recovery scripts.
10. You will need to attach the new disk from within the OS using either [diskmgmt.msc](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/attach-managed-disk-portal#initialize-a-new-data-disk) for Windows or [fdisk](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/attach-disk-portal#connect-to-the-linux-vm-to-mount-the-new-disk) in Linux.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it necessary to run diskmgmt.msc? After the script is completed, the rescue VM, already has the disk attached and can be accessed without having to run diskmgmt.msc. Am I missing something? Are you thinking of any specific scenario?

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

Successfully merging this pull request may close these issues.

2 participants