Solved Issue installing Korora
-
@momurda said in Issue installing Korora:
My guess, as suggested by others, the 1MB partition is throwing the installer off, or it is actually an MBR setup and you cant install because youll have too many primary partitions afterwards.
The 1MB partition problem can be mitigated by moving the 1MB unallocated to the right of the sda2 partition. Move is a function in gparted.Yes - Yes it is. But not possible. Tried that...
-
Well anyways, to my original post... I resolved it by installing Fedora instead of Korora.
-
It was quick and easy to get things running in Fedora Cinnamon Desktop.
No issues setting up a Win10 VM in Fedora... PXE booted to the WDS server and got a fully loaded Win10 image deployed to it in about 10 or so minutes, and was up and running.Screen capture is not great quality because I was TeamViewering into my laptop to take the screenshot:
-
@gjacobse on a live (or even in the installer, pressing ctrl+alt+Fx, x=1,2,3... try one) issue the following:
fdisk -l /dev/sda
Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 8ADBCAE5-504D-4019-9CFD-4E827DF67876 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 8390655 7340032 3.5G Linux filesystem /dev/sda3 8390656 16775167 8384512 4G Linux swap
as you can see here:
Disklabel type: gpt
MIND TO PASS JUST A LOWER CASE "L" AS A FLAG! FDISK IS USED TO KILL YOUR DOG, ALSO!
-
The Win10 VM I'm running on KVM in Fedora shows up in WSUS like this:
That one update needed is the 1703 upgrade. I didn't push that yet.
All seems well so far!