Void-installer - Configured partitions not shown in filesystem about void-docs HOT 3 CLOSED

did you [write] the partition table in cfdisk?

from void-docs.

Partitioning a Disk Using fdisk in Linux

1. Identify the disk:

   sudo lsblk
   

   This will list all the block devices connected to your system. Identify the disk you want to partition, e.g., /dev/sda or /dev/nvme0n1.

2. Enter the fdisk interactive prompt:

   sudo fdisk /dev/[DEVICE]
   

   Replace [DEVICE] with the disk you want to work with, e.g., /dev/sda.

3. Create a new partition table:
   Inside the fdisk prompt, type:

   o
   

   This will create a new empty DOS partition table.

4. Create a new partition:
   Inside the fdisk prompt, type:

   n
   

   Follow the prompts to specify the partition type (primary or extended), partition number, and the start and end sectors for the new partition.

5. Set the partition type (optional):
   Inside the fdisk prompt, type:

   t
   

   Then select the appropriate partition type code, e.g., 83 for a Linux native partition or 82 for a Linux swap partition.

6. Make the partition bootable (optional):
   Inside the fdisk prompt, type:

   a
   

   Then select the partition number you want to make bootable.

7. Write the changes and exit:
   Inside the fdisk prompt, type:

   w
   

   This will write the changes to the disk and exit fdisk.

8. Format the new partition:

   sudo mkfs.ext4 /dev/[PARTITION]
   

   Replace [PARTITION] with the name of the new partition you created, e.g., /dev/sda1.

Remember to replace [DEVICE] and [PARTITION] with the appropriate names for your system. Also, always double-check your work and back up any important data before making changes to the partition table.

from void-docs.

did you [write] the partition table in cfdisk?

Thanks for the tip on the GitHub issue. Your suggestion about cfdisk was exactly what I needed to fix the problem. As a newbie, I really appreciate you taking the time to provide that helpful feedback. I knew how to fix this bug and I also created an issue for others who may have encountered it.

from void-docs.