| 12 Jul 2024 |
 nrv | * At first i think i miscalculated the sizes. sgdisk would say cannot make partition and refuse going further. That is ok.
But then this, and also partprobe broke and said to reboot, and also sgdisk were spitting random numbers instead of ones that i give to it | 10:26:13 |
 lassulus | but you can also overwrite the labels there, if they are too long, they are changed to a hash | 10:33:30 |
| nrv | could it be that sgdisk --clear doesn't work properly and there's still partitions on the disk when i run disko multiple times? | 10:38:05 |
| nrv | even though it runs --clear and partprobe and everything | 10:38:17 |
| nrv | because now i see sgdisk failing again (though i tweaked the sizes) | 10:38:56 |
| nrv | In reply to @nevrv:matrix.org
could it be that sgdisk --clear doesn't work properly and there's still partitions on the disk when i run disko multiple times? sure it could. blkdiscard fixes that. | 10:42:08 |
| nrv | bug? | 10:42:31 |
| nrv | * bug on the disko part? | 10:42:43 |
| nrv | In reply to @nevrv:matrix.org
could it be that sgdisk --clear doesn't work properly and there's still partitions on the disk when i run disko multiple times? * sure it could. blkdiscard fixes that. success after blkdiscard, no changes to disko config | 10:43:26 |
| lassulus | what command are you running? | 10:43:51 |
| nrv | In reply to @nevrv:matrix.org
sure it could. blkdiscard fixes that. success after blkdiscard, no changes to disko config wait, abort | 10:44:47 |
| nrv | i got excited on one success message which was not the right one | 10:45:12 |
