Closed allentiak closed 5 years ago
Current partitioning:
root@sysresccd /root % gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 1000215216 sectors, 476.9 GiB
Model: SAMSUNG SSD SM84
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): BAF22793-BCD9-8349-A200-0C0773CF380B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1000215182
Partitions will be aligned on 2048-sector boundaries
Total free space is 227949 sectors (111.3 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 1026047 500.0 MiB EF00 EFI Boot
2 1026048 98682879 46.6 GiB 8301 rootfs
3 98682880 161183743 29.8 GiB 8200
4 161183744 897814527 351.3 GiB 8301 homefs
5 897814528 999989247 48.7 GiB A504
still an issue
My hypothesis (unchecked for now) is that this is related with rEFInd's startup scripts.
I am still not sure whether this bug is to Trident's or to TrueOS', though.
still an issue
@RodMyers Do you mean release 19.07?
With the move to Void Linux this is no longer an issue. New installer, procedures, and environment.
(Waiting for #47 to generate the corresponding logs.)