| 12 Jul 2024 |
 nrv | * So, sgdisk commands succeed, but then there is no cryptsetup in the log. It is in the script though, but refers to hardcoded random partlabels(?), dunno how that works, are they static and calculated at build time? They seem to exist | 10:02:30 |
| nrv | /tmp/secret.key is also created | 10:03:08 |
| nrv | i did actually forget that before and the error was different and intelligible of the issue | 10:03:33 |
| nrv | ..so it's failed to open keyfile | 10:16:55 |
| nrv | but cat /tmp/secret.key works | 10:17:08 |
| nrv | (and of course it's not in the logs, disabled explicitly for the cat but not for the cryptsetup so hmm) | 10:19:32 |
| nrv | * (and of course it's not in the logs, disabled with +x explicitly for the cat but not for the cryptsetup so hmm) | 10:19:44 |
| nrv | also, disko completely misses this error and proceeds with the zfs stuff | 10:20:44 |
| nrv | * ..so it's failed to open keyfile (the pipe substitution or whatever it's called in bash) | 10:22:28 |
| 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 |
