| 29 Nov 2024 |
 lassulus | can't you mount it in a tmpdir for the first mount and mount it with veritysetup for the mount step? | 15:52:58 |
 Mic92 | lassulus: no, because mounted veritysetup devices are read-only | 15:54:38 |
| Mic92 | The idea is to have immutable filesystems that can be verified and not tempered with. | 15:55:18 |
| lassulus | ah, well the mount command from disko is just used for installation anyway | 15:57:35 |
| lassulus | so you just define the /dev/sda in there and the verity thingie in the config? | 15:57:51 |
| lassulus | type would be similiar to the luks type | 15:58:11 |
| lassulus changed their profile picture. | 18:30:30 |
 netpleb | In reply to @joerg:thalheim.io
netpleb: there is a format mode that should not destroy your existing disk and add missing partitions disks etc. But I am not sure this works for raid conversion yet. Thanks for your reply. Ok, let's ignore the raid1 complication for now and just assume I want to add a second disk to my existing btrfs fileystem. So I would:
- update my
disks.nix file in my flake repo to include the additional disk
nixos-rebuild switch --flake . --target-host <user@target_ip>- on target system run
disko -m format ...
And hope for the best. Is that about right?
| 23:50:38 |
| netpleb | In reply to @joerg:thalheim.io
netpleb: there is a format mode that should not destroy your existing disk and add missing partitions disks etc. But I am not sure this works for raid conversion yet. * Thanks for your reply. Ok, let's ignore the raid1 complication for now and just assume I want to add a second disk to my existing btrfs fileystem. So I would:
- update my
disks.nix file in my flake repo to include the additional disk
nixos-rebuild switch --flake . --target-host <user@target_ip>- on target system run
disko -m format ...
And hope for the best. Is that about right?
| 23:50:50 |
| netpleb | I guess maybe steps #2 and #3 might be reversed? | 23:51:42 |
| 30 Nov 2024 |
| Mic92 | netpleb: that format command has to be used with caution. We only test basic transition, so your migration might have been not properly tested. You can use the --dry-run command and inspect if the commands makes sense. | 07:40:57 |
|  42398234iuodfhjkdsfjdsfsdffgs joined the room. | 10:35:34 |
|  @jappie3:matrix.org left the room. | 20:24:44 |
| 1 Dec 2024 |
|  @tanvir:hackliberty.org removed their profile picture. | 17:39:28 |
| @tanvir:hackliberty.org removed their display name ππππππ. | 17:41:50 |
| @tanvir:hackliberty.org left the room. | 17:47:24 |
| 2 Dec 2024 |
|  SΓ‘vio joined the room. | 03:40:06 |
| 8 Dec 2024 |
 blimbus | Does disko support unlocking a LUKS drive via crypttab after boot? | 01:53:23 |
| blimbus | * Does disko support unlocking a LUKS drive via crypttab after boot?
Edit: Either I was stupid or this has been fixed | 01:54:24 |
| blimbus | * Does disko support unlocking a LUKS drive via crypttab after boot? | 01:54:38 |
| blimbus | * Hi yall, not sure if I'm just stupid and missing something but disko in disko mode is failing to setup luks on an empty drive. If the drive aleady has partitions or anything else on it it works but otherwise just fails somewhere after partitioning. It makes a luks device with password "password" even though it is set to prompt and then doesnt open the volume so creating filesystems fails.
Edit: Either I was stupid or this has been fixed | 01:55:12 |
| blimbus | * Does disko support unlocking a LUKS drive via /etc/crypttab after boot? | 01:59:11 |
| blimbus | was also wondering if I have to specify drive names when using disko-install or if I can make it just use the ones in my config | 02:11:12 |
| blimbus | * Does disko support unlocking a LUKS drive via /etc/crypttab after boot?
Seems there used to be a way to disable auto unlocking a specific drive at boot, maybe that's what I'm looking for? | 02:40:59 |
| blimbus | * Does disko support unlocking a LUKS drive via /etc/crypttab after boot?
Seems there used to be a way to disable auto unlocking a specific drive at boot, maybe that's what I'm looking for?
Edit in case anyone ever searches for this: options.intirdUnlock = false | 02:50:34 |
|  @jj:envs.net joined the room. | 06:58:32 |
| @jj:envs.net | hello! wondering if someone could look over my configuration. i pieced it together from the existing examples, but had (and still am having) a very hard time understanding what they all do. | 06:59:56 |
| @jj:envs.net | Download disk-configuration.nix | 06:59:56 |
| @jj:envs.net | there is one explicit issue: disko is not mounting /, which i understand it's supposed to do. so i definitely have some problems in the config. | 07:00:36 |
| @jj:envs.net | generally also i have not been able to find documentation! for exactly what options disko.devices is expecting, and what all sorts of everything are doing. like zpool is a separate disk from the main disks for some reason, but i have no idea why this is, or what i would read to find out why this is. same goes for what datasets etc are doing. any pointers in this area would be appreciated. | 07:03:39 |
