| 12 Jul 2024 |
 nrv | * ..so it's failed to open keyfile (the pipe substitution of cat or whatever it's called in bash) | 10:22:40 |
| nrv | * ..so it's failed to open keyfile (the process substitution of cat) | 10:23:34 |
| nrv | * ..so it's failed to open keyfile (the process substitution of cat /tmp/secret.key) | 10:23:44 |
| nrv | * (and of course it's not in the logs, disabled with +x explicitly for the cat but not for the cryptsetup so hmm, maybe the big ( ) subshell captures it?) | 10:24:56 |
 lassulus | hmm, weird, I don't see any code that ignores the cryptsetup error. like it should fail if cryptsetup fails. The partlabels are calculated inside the gpt type and are used onwards from there | 10:26:11 |
| 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 |
