| 27 Apr 2025 |
 l0b0 | You do have device = "/dev/vdb"; in your configuration though. Not sure how that interacts with the CLI. | 08:56:50 |
| l0b0 | Why do I have to specify--disk NAME PATH when those are already in the configuration? | 08:57:49 |
| l0b0 | * Why do I have to specify--disk NAME DEVICE when those are already in the configuration? | 08:57:57 |
| l0b0 | * Why do I have to specify --disk NAME DEVICE when those are already in the configuration? | 08:58:03 |
 @realhotgirlshit:envs.net | Oh okay, I’ll take a look at that | 08:58:56 |
| @realhotgirlshit:envs.net | Alright I fixed that in the disko configuration, but I’m still getting the error | 09:04:36 |
| @realhotgirlshit:envs.net | Probably a good start though | 09:04:41 |
| @realhotgirlshit:envs.net | I’ll see if I can mess with the GRUB configuration | 09:05:02 |
| @realhotgirlshit:envs.net | I doubt nodev will work | 09:05:50 |
| @realhotgirlshit:envs.net | Yeah, same thing | 09:07:55 |
| @realhotgirlshit:envs.net | Got it to go through!
boot.loader.grub.enableCryptodisk = true | 09:15:19 |
| @realhotgirlshit:envs.net | Now I probably just have to load a kernel module | 09:18:23 |
|  mkg20001 joined the room. | 14:15:25 |
|  musjj joined the room. | 14:43:05 |
