installer saves partition layout after exit about void-mklive HOT 13 OPEN

I would like to add I was not once given the option to choose between: gpt, dos, etc.

this would suggest your disk already had a partition table, so cfdisk did not prompt you to create one. wipefs would be able to remove that for you (or cfdisk -z)

from void-mklive.

the installer seemed to save changed done within the installer even after exiting or removing the install medium, USB stick, and would even run

if you did not reboot, the installer would have saved the settings to a file in /tmp. If you did reboot, then the saved changes you saw are probably from writing the partition table to disk in cfdisk.

from void-mklive.

I would like to add I was not once given the option to choose between: gpt, dos, etc.

this would suggest your disk already had a partition table, so cfdisk did not prompt you to create one. wipefs would be able to remove that for you (or cfdisk -z)

But should it not anyway? Backing out of an installer to run commands and then re-entering is a bit strange. If I find this issue again, I will recall, but should the cfdisc not override existing partitions?

from void-mklive.

the installer seemed to save changed done within the installer even after exiting or removing the install medium, USB stick, and would even run

if you did not reboot, the installer would have saved the settings to a file in /tmp. If you did reboot, then the saved changes you saw are probably from writing the partition table to disk in cfdisk.

The changes did not persist between reboot.

from void-mklive.

But should it not anyway? Backing out of an installer to run commands and then re-entering is a bit strange.

This has been a requested feature in the past, so yes, it should, it seems

If I find this issue again, I will recall, but should the cfdisc not override existing partitions?

it should not, as some people don't want their disks erased before installing void (dual boot, for example)

from void-mklive.

it should not, as some people don't want their disks erased before installing void (dual boot, for example)

So, is the solution for now to always run the above commands before entering the void-installer?

Will future iterations fix this issue?

from void-mklive.

You'll have to give more info about what the problem is, because from what you've said so far I don't see an issue

from void-mklive.

To abridge the issue:

1. Boot from Installer USB
2. Run Void Installer as root
3. Go through the installer
4. Installer failed to create bootable system
5. Persisted across multiple attempts

from void-mklive.

In relation to this issue, I plan to install on my desktop and dual boot with Arch.
Would the recommend course of action be to wipe the disk beforehand?

from void-mklive.

i'm not sure why you would need to or want to wipe the disk

from void-mklive.

When I run a cfdisc and write my partitions, select root, boot, etc.
I would expect it to wipe and write the drive as set in the cfdisc, but it seems to not be functioning as such.

Should the installer not simply install the OS on the disk, following the partitions as set by the cfdisc?

from void-mklive.

if you wiped and wrote the partition table to the disk in cfdisk it will do that. all the installer does is shell out to cfdisk, then read the partition tables in the filesystem configuration section.

from void-mklive.

Yes. This was the core root of my issue.

The cfdisc, no matter how many attempts or what it indicated, would not properly install.
It simply ran the installer with said settings, but did not actually install or create a bootable system.

Only when I manually created an fstab, saved, and did not open the drive partition option within the installer, did the system actually install.

from void-mklive.