February 16, 20242 yr So I thought it would be a simple process to increase the size of my VM disk from 50G to 100G as I was running low on space inside my Windows environment. Increasing the vdisk size in UnRAID was no problem. The issues started as I tried to extend my Windows 10 VM C:. First issue was the recovery volume being adjacent to the C:. Easy enough fix - used the built in Windows disk manager to delete this partition and then I was able to extend the size of my Windows 10 C drive to the full 100GB. Everything looked good until I had to reboot my vm. Now I'm presented with this screen: I'm assuming I need to create a bootable Win 10 USB drive but I'm unclear how to make this the boot device for my vm so I can repair the vm disk with the Win 10 repair utility (assuming that even works)? VM Log.txt
February 16, 20242 yr Put the windows install ISO back into the list of drives and set the VM to boot off the iso first.
February 16, 20242 yr Author 4 minutes ago, JonathanM said: Put the windows install ISO back into the list of drives and set the VM to boot off the iso first. Thanks for the response. Sorry, but I'm a little confused by the first part - "Put the windows install ISO back into the list of drives"? I've added the Windows 10 ISO as a share via unassigned devices in UnRAID: But I'm unclear how to point the vm to Windows 10 iso as the boot device in the vm settings? As far as boot devices, all I can see is connected USB devices:
February 16, 20242 yr Community Expert 3 minutes ago, betaman said: Thanks for the response. Sorry, but I'm a little confused by the first part - "Put the windows install ISO back into the list of drives"? I've added the Windows 10 ISO as a share via unassigned devices in UnRAID: But I'm unclear how to point the vm to Windows 10 iso as the boot device in the vm settings? As far as boot devices, all I can see is connected USB devices: you shou!d be able to select file path in the os iso drop down nearer the top. you dont need to share via UD
February 16, 20242 yr Author 5 minutes ago, SimonF said: you shou!d be able to select file path in the os iso drop down nearer the top. you dont need to share via UD Yeah, that's where I have the Windows 10 ISO selected: However, it doesn't boot into the repair tool screen. I just get the first screen I posted above:
February 16, 20242 yr Community Expert 2 minutes ago, betaman said: Yeah, that's where I have the Windows 10 ISO selected: However, it doesn't boot into the repair tool screen. I just get the first screen I posted above: use boot order 1 and change disk to 2. You should then get press any key to boot from cd. also set bus to sata
February 16, 20242 yr Author 4 minutes ago, SimonF said: use boot order 1 and chnage disk to 2. You should then get press any key to boot from cd. also set bus to sata Ok, setting the ISO to boot order 1 got me into the tool. As expected, it says it couldn't repair my drive. When I went to the reset options (keep my files), it says my drive is locked?
February 16, 20242 yr 16 minutes ago, betaman said: it says my drive is locked? Is it asking for your bitlocker code?
February 16, 20242 yr Author 8 minutes ago, JonathanM said: Is it asking for your bitlocker code? No, it just says it's locked. I used the command prompt to try rebuilding the BCD but it doesn't find a partition with Windows on it. Not a good sign. I could just rebuild the vm but I'm pretty sure I used a Win 8 license to upgrade to Win 10. I'll have to see if that license will work on a Win 10 iso for install but I'm not optimistic...
February 16, 20242 yr If you are experienced with recovery procedures you can substitute your favorite recovery iso into the windows iso slot.
February 17, 20242 yr Author Ok, so I just went ahead and reinstalled the Windows 10 VM. Everything is good except my Redhat virtio ethernet adapter has the wrong IPv4 address configuration. My router should be assigning the address in the 192.168.1.xxx range but virtio is showing 192.168.122.xxx range. Same issue with the default gateway (192.168.122.1 instead of 192.168.1.1). I tried assigning a fixed IP address in the proper range but then I lose all connection (media disconnected). Any idea why the dhcp isn't assigning correctly? Edited February 17, 20242 yr by betaman
February 17, 20242 yr Community Expert 2 minutes ago, betaman said: Ok, so I just went ahead and reinstalled the Windows 10 VM. Everything is good except my Redhat virtio ethernet adapter has the wrong IPv4 address configuration. My router should be assigning the address in the 192.168.1.xxx range but virtio is showing 192.168.122.xxx range. Same issue with the default gateway (192.168.122.1 instead of 192.168.1.1). I tried assigning a fixed IP address in the proper range but then I lose all connection (media disconnected). Any idea why the dhcp isn't assigning correctly? Which interface have you selected in the template, sounds like virtbr0 which will nat the connection
February 17, 20242 yr Author 6 minutes ago, SimonF said: Which interface have you selected in the template, sounds like virtbr0 which will nat the connection yeah, it's set to virbr0. Should I set it to vhost0? Edited February 17, 20242 yr by betaman
February 17, 20242 yr Community Expert Solution Just now, betaman said: yeah, it's set to virbr0. Should I set it to vhost0? yes
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.