| 12 Jul 2024 |
 nrv | Then i happily changed some datasets & mount settings and it broke again | 11:52:46 |
| nrv | * Then i happily changed some datasets & mount settings expecting that i can finally purge & rebuild it until i'm happy and it broke again | 11:53:19 |
 lassulus | hmm, I guess the start=0M confuses sgdisk | 11:53:59 |
| lassulus | Could not create partition 1 from 8594128896 to 8594130943 | 11:54:00 |
| nrv | But isn't it straight from example? | 11:54:21 |
| lassulus | uh I hope not | 11:54:31 |
| lassulus | it should be start=0, not 0M, but you should be able to leave it out | 11:54:44 |
| nrv | hmm, it isn't | 11:54:55 |
| nrv | apparently that's mine | 11:55:04 |
| nrv | examples just have size and no start | 11:55:15 |
| lassulus | yeah, start = 0 makes sgdisk automatically choose the next startpoint | 11:55:44 |
| lassulus | so size is usually enough to set | 11:56:35 |
| nrv | ...but it's not 0 | 11:56:40 |
| nrv | it's 0M | 11:56:42 |
| lassulus | yeah, that seems to be confusing to sgdisk | 11:57:05 |
| lassulus | maybe a bug in there? | 11:57:12 |
| nrv | it's worked. Thank God | 11:59:35 |
| nrv |
changed 0M to 1M
| 11:59:45 |
 [0x4A6F] | AFAIK "34s" is the first usable start point for partions on gpt table. | 11:59:45 |
| nrv | * > changed 0M to 1M | 11:59:53 |
| nrv | In reply to @lassulus:lassul.us
yeah, that seems to be confusing to sgdisk fuck sgdisk then | 12:00:09 |
| [0x4A6F] | If you don't care about alignment. | 12:00:20 |
| lassulus | well if you find a better cli tool to format disks I'm happy to integrate it :D | 12:00:29 |
| nrv | parted? fdisk? | 12:00:42 |
| nrv | i don't know their downsides | 12:00:49 |
| lassulus | fdisk is interactive | 12:00:52 |
| nrv | but parted seems simpler | 12:00:54 |
| nrv | though i know it has problems with alignment | 12:01:04 |
| lassulus | parted we had before, but parted is weird with gpt | 12:01:05 |
| lassulus | and the cli was ambigious in some cases | 12:01:16 |
