 | disko | 354 Members |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 89 Servers |
| disko | 354 Members |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 89 Servers |
| Sender | Message | Time |
|---|---|---|
| 12 Jul 2024 | ||
 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 |
| 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.orgsure 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* 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.orgwait, abort | 10:44:47 |
| nrv | i got excited on one success message which was not the right one | 10:45:12 |
| nrv | In reply to @lassulus:lassul.usgive me a sec | 10:45:16 |
| nrv | In reply to @lassulus:lassul.us this is dicko.nix https://0x0.st/XMUo.txt the command that i'm running is what i'm getting:
...for some reason | 11:37:03 |
| nrv | This is btw when it now decided to switch back to not liking my sgdisk. I don't know if it is sgdisk, linux, disko or i'm stupid and blind and there's wrong numbers again. The cryptsetup issue had another log | 11:39:21 |
| nrv | * This is btw when it now decided to switch back to not liking my sgdisk. I don't know if it is sgdisk, linux or disko misbehaving or i'm stupid and blind and there's wrong numbers again. The cryptsetup issue had another log | 11:39:50 |
| lassulus | ah this is if you run the formatScript multiple times, the errors are expected there, if you want disko to wipe the drives before retrying, you should run --mode disko | 11:43:14 |
| nrv | thing is that i tried to do --zap and --clear and blkdiscard --force multiple times | 11:43:57 |
| nrv | and rebooting | 11:43:58 |
| nrv | it just changes behavior randomly | 11:44:08 |
| nrv | and i did mode disko, it just spits more errors or something so i decided to stick to format | 11:44:50 |
| nrv | i'll try it, sec | 11:44:54 |
| lassulus | also it seems your luks partitions conflicts with your grub-mbr partition | 11:45:41 |