Linux cannot install vdmx root not found
- Linux cannot install vdmx root not found update#
- Linux cannot install vdmx root not found Pc#
- Linux cannot install vdmx root not found iso#
- Linux cannot install vdmx root not found windows#
"Rescue" mode puts you in chroot, so I had to modify paths and removed few steps that aren't needed.
Linux cannot install vdmx root not found iso#
It is similar, practically same, but I modified it to fit the workflow of "Rescue" mode available from stock 16.04 boot ISO image. You can also force creation of grub.cfg file on Ubuntu with following command: grub-mkconfig -o /boot/grub/grub.cfg Linux /vmlinuz-x.x.x-xx-generic root=/dev/mapper/ubuntu-vg-ubuntu-lvĪfter this you should end up in your normal OS instance, just sudo as root again, and repeat the grub-install and update-grub as explained above. # if above didn't start boot, try manually like this, instead "-x.x.x-xx-generic" enter your current kernel version, use tab to autocomplete In case of trouble do not despair! If your first attempts go wrong and you end up in grub > prompt, you can fix it by doing something roughly like this: # if you reboot to grub rescue prompt, you can still fix everything, no need to return to original export/backup files ! I tried installing new kernel after this procedure, and after update-grub and reboot, I could see new entries.
Grub-install /dev/sda -efi-directory=/boot # if you had to manually fix boot, first fix whatever was wrong (like fstab, or whatever), then do this
Linux cannot install vdmx root not found update#
# after successful reboot, install and update grub, to have correct and fresh system with current mounts etc # now we can shut down VM, unmount DVD/ISO, and get it ready for normal boot # keep other entries (eg swap) as is, or if you know what you're doing change them in similar way, or find new UUIDs, etc. dev/ubuntu-vg/ubuntu-lv / ext4 defaults 0 0
# also /boot needs to be changed from ext2/ext4/whatever to "vfat", so like this # change UUIDs to what says in comments above them like "was on. Grub-install -force -target=x86_64-efi -boot-directory=/mnt/boot -efi-directory=/mnt/boot /dev/sda # copy files from old (BIOS) /boot2 backup, one you made before formatting
Mount /dev/mapper/ubuntu-vg-ubuntu-lv /mnt/root/ Mount /dev/ubuntu-vg/ubuntu-lv /mnt/root/ # if you boot in Server installer, pick Help, Enter shell # boot LiveCD, or server install + shell, or similar, it's important to boot in Gen2/EFI mode # Add DVD drive and make it first device, attach same ISO image you used to install this OS # create new Gen2 VM with same settings, and attach existing VHDX file(s) # delete old VM in Hyper-V Manager, but keep the VHDX file(s) (also, remember to export/backup before trying this all) # make /boot2 folder and copy everything from /boot to /boot2 (for backup, safe keeping, later use) # install grub efi version for later use, just in case note: it will remove other version on install # note: all steps done as root, so sudo su first Note #3: I recommend to backup whole VM before this procedure, for example using "Export" function in Hyper-V Manager Ubuntu 20.04įollowing is instructions based on my Ubuntu 20.04 VMs (installed fresh for this purpose, default install settings): # boot your Gen 1 VM Note #2: As always, your partitioning scheme and disk names will probably be different than in my examples, PLEASE modify accordingly, I am in no way responsible for data loss if you format wrong partition! You can check partitions while in your original OS using fdisk -l and/or cat /etc/fstab Note #1: I did this with Ubuntu 20.04, Ubuntu 16.04 and Centos 7, I need to repeat this with Ubuntu 18.04, if it differs in important ways I'll edit answer.
Linux cannot install vdmx root not found Pc#
So in short - answer is same as converting BIOS PC to UEFI PC. (btw in old comments is no longer available so couldn't say if it was helpful or not) Intro & notesĪnyway, the real issue is BIOS vs UEFI, while IDE vs SCSI didn't throw anything extra my way. Since this was top result when I tried to find an answer, I'm posting my own solution, even though it's 6+ years since question. The installing and migration for this particular server (it's a Gitlab server running on Ubuntu 14.04) is pretty cumbersome and we'd prefer not to reinstall and migrate if at all possible. We have upgraded to a 2012 R2 host and can run Gen2 now, but every source I've found says you have to reinstall linux for it (I haven't been able to figure out why, but I'm sure there should be a reason).
Linux cannot install vdmx root not found windows#
The original VM was running on a Windows Server 2008 host. I'm having some problems running on HyperV (machine stops responding for a while, etc.), that for the most part I've seen are greatly improved on Gen2 (we follow all Microsoft recommended practices for running Linux on Hyper-V but it's still not there, at least on Gen1).
I know the Convert-VMGeneration cmdlet for PowerShell (this one: ) but that won't work with Linux VMs. Is there any way I can easily (and without reinstalling) convert a Linux Hyper-V (gen 1) VM to a gen2 one?