On Thu, 12 Dec 2024 at 08:23, Toomas Soome via openindiana-discuss < [email protected]> wrote:
> > I’m not quite sure why size would be an issue there - unless installer is > insisting to use MBR+VTOC and will fail there, but if so - thats bug for > sure. IMO the GPT should be default and MBR+VTOC should use annoying > confirmations if the user is really-really sure to use it;) > so, this is how linux sees them: root@test:~# sfdisk -l Disk /dev/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: KINGSTON SNV2S4000G Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 14BF5E17-A9F7-4015-82A2-AB9CA09CCA80 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1953791 1951744 953M EFI System /dev/nvme0n1p2 1953792 7814035455 7812081664 3.6T Linux filesystem Disk /dev/sdb: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM008-2FR1 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: 2236D5C7-DCED-DB4E-84DC-7F3266A0EB8A Device Start End Sectors Size Type /dev/sdb1 256 524543 524288 256M EFI System /dev/sdb2 524544 3907012750 3906488207 1.8T Solaris /usr & Apple ZFS /dev/sdb9 3907012751 3907029134 16384 8M Solaris reserved 1 Partition 9 does not start on physical sector boundary. Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM006-2DM1 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: DAB7E9F4-0C55-4A7B-B530-71462AC6017C Disk /dev/sdc: 18.19 TiB, 20000588955648 bytes, 39063650304 sectors Disk model: TOSHIBA MG10ACA2 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: 6DAE86F3-CB47-4815-B3EE-E3E7734D2F47 They seem to be all gpt, and all supporting 512 bytes sectors. > There currently is one limit, however. We are still completing the support > for 4kn sector size for boot (that is, to create ESP with FAT32 on 4k > sector size), if those disks do have 4kn sector size (no 512B support), > then manual work and external tools are needed. > They are currently all set at 512. The nvme support 4096 for sure, the 20G spinner I'm not sure what's the right command to check. side question: what's the equivalent of "lsblk" in OI ? root@test:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 1.8T 0 disk sdb 8:16 0 1.8T 0 disk ├─sdb1 8:17 0 256M 0 part ├─sdb2 8:18 0 1.8T 0 part └─sdb9 8:25 0 8M 0 part sdc 8:32 0 18.2T 0 disk sr0 11:0 1 1024M 0 rom nvme0n1 259:0 0 3.6T 0 disk ├─nvme0n1p1 259:1 0 953M 0 part /boot/efi └─nvme0n1p2 259:2 0 3.6T 0 part / -- Pierfrancesco Caci, ik5pvx _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
