Page MenuHomeSolus

Cannot assign mount points for boot, swap, root partitions of prepared virtual hard drive when installing the MATE .ISO
Closed, ResolvedPublicBUG

Description

MATE installer fails to assign prepared partitions to mount points.

When I prepare a 32 GB virtual hard drive for a VM, I create a 1.0 GB boot partition, a 6.0 GB swap partition, and that leaves 25 GB for the root file system. The Budgie and GNOME installers assigned the mount points, and the installations completed without any issues. The MATE installer did not.

  1. In the VirtualBox manager, create a 32 GB virtual disk drive and assign the Solus 4.4 GNOME .ISO to it. Assign settings as usual, including creating a shortcut icon on the desktop.
  1. In the "live" session, before starting the installer, use the GParted editor to create a 1.0 GB boot partition, a 6.0 GB swap partition, and a 25.0 GB partition for the root file system.
  1. Proceed to launch the OS installer and step through the wizard until you get to the choice of letting the installer partition the disk automatically or having it use the partitions you've prepared. Select the latter.
  1. The following page is where you assign mount points to the prepared partitions. Normally here is where you assign the swap partition to the swap mount point, and the root file system partition to the / mount point.

Expected result: After assigning these partitions to their respective mount points, the [Next] button becomes enabled and the remain installation steps can be completed.

Actual result: Clicking to select mount points does nothing. The [Next] button remains disabled, and installation can't continue.

  1. Environment: This problem occurs during attempted installation of the testing .ISO, so no update has occurred yet. I have no idea what repo is involved. The DE is MATE.

Event Timeline

Apparently this can be ignored. When I returned to the VM, I was able to assign the mount points normally. I have no idea why it didn't work the first time I tried. I had already created the Budgie and GNOME VMs, where I didn't run into this problem. I'll continue with the installation and testing.

EbonJaeger claimed this task.
EbonJaeger added a subscriber: EbonJaeger.

Since this seems to have resolved itself, I'll close this one out.