disko

Sender	Message	Time
7 Apr 2024
n3v3r_a9a1n	[root@nixos:~]# ls /mnt/ home log nix persist root swap [root@nixos:~]# ls /mnt/root bin boot dev etc home lib lib64 nix persist proc root run srv sys tmp usr var [root@nixos:~]# btrfs subvolume list /mnt ID 256 gen 29 top level 5 path home ID 257 gen 33 top level 5 path log ID 258 gen 33 top level 5 path nix ID 259 gen 29 top level 5 path persist ID 260 gen 36 top level 5 path root ID 261 gen 18 top level 5 path swap ID 262 gen 29 top level 260 path root/srv ID 263 gen 30 top level 260 path root/var/lib/portables ID 264 gen 31 top level 260 path root/var/lib/machines ID 265 gen 33 top level 260 path root/var/tmp	10:47:53
n3v3r_a9a1n	In reply to @xxxcrow:matrix.org then mount /dev/mapper/nvme-crypt /mnt or i shouldn't do it at all?	10:50:02
lassulus	Perchun Pak: I created this PR to fix the gpt behaviour: https://github.com/nix-community/disko/pull/595	10:51:22
n3v3r_a9a1n	In reply to @xxxcrow:matrix.org or i shouldn't do it at all? if i mount the way tutorials on impermanence+btrfs say, everything looks fine,but how do i take the snapshot	10:54:15
n3v3r_a9a1n	In reply to @perchun:matrix.org Vimjoyer did config for btrfs + impermanence, don't know about other things https://youtu.be/YPKwkWtK7l0?feature=shared also, sorry if it's not true, but i think the way way he implements everything is not really ok 1st. https://discourse.nixos.org/t/what-does-impermanence-add-over-built-in-functionality/27939/16 2nd. it doesn't work with some stuff (can't remember what exactly either lanzaboote, or clevis, or something like that) 3rd. something else i forgot exactly what	11:22:11
@perchun:matrix.org	In reply to @xxxcrow:matrix.org also, sorry if it's not true, but i think the way way he implements everything is not really ok 1st. https://discourse.nixos.org/t/what-does-impermanence-add-over-built-in-functionality/27939/16 2nd. it doesn't work with some stuff (can't remember what exactly either lanzaboote, or clevis, or something like that) 3rd. something else i forgot exactly what Yeah, it deleted all of my data if there wasn't something correct in the setup. Like no /persist/system or wrong permissions on /persist/home (in second scenario, home manager just failed to start completely). Though it is probably the fault of impermanence. But for now, it works on my machine™. Feel free to send your final setup, I will happily steal it ;)	11:57:22
lassulus	whoops, I accidently ran sgdisk -o isntead -p on my main disk :D	12:52:35
lassulus	luckily I could recover it with disko	12:52:46
lassulus	but why are those 2 parameters (-p pronts, -o wipes) so close together on the keyboard :D	12:53:07
lassulus	* but why are those 2 parameters (-p prints, -o wipes) so close together on the keyboard :D	12:53:14
n3v3r_a9a1n	Quick questiono about disko and nixos-anywhere! How do I skip disko in nixos-anywhere?	16:01:36
lassulus	Hmm you can't really. Maybe we should add a --stop-after-kexec parameter	16:29:37
8 Apr 2024
	l0b0 joined the room.	00:55:29
	@palo:xaos.space changed their display name from palo to palo moved to @mrvandalo:terranix.org.	13:03:24
	palo joined the room.	13:06:37
	@palo:xaos.space left the room.	13:06:51
	palo changed their display name from mrvandalo to palo.	13:12:45
n3v3r_a9a1n	is disko working with clevis?? error: … while evaluating attribute 'nodes' at «string»:4:25: 3\| (deploy // { 4\| nodes = { \| ^ 5\| inherit (deploy.nodes) "immortal"; … while evaluating attribute 'immortal' at «string»:5:49: 4\| nodes = { 5\| inherit (deploy.nodes) "immortal"; \| ^ 6\| }; (stack trace truncated; use '--show-trace' to show the full trace) error: Failed assertions: - No filesystem or LUKS device with the name /dev/disk/by-uuid/9119a486-5702-4af7-bce8-5bb7e513ea6f is declared in your configuration. - No filesystem or LUKS device with the name /dev/disk/by-uuid/e85aa7c5-5926-434c-8142-0ede397a6369 is declared in your configuration. 🚀 ❌ [deploy] [ERROR] Failed to evaluate deployment data: Evaluation resulted in a bad exit code: Some(1)	15:07:54
@perchun:matrix.org	afaik, disko doesn't use uuids to manage paritions, but labels `~ ❯ ls /dev/disk/by-partlabel/  disk-main-ESP  disk-main-luks  disk-main-swap`	15:13:19
@perchun:matrix.org	In reply to @perchun:matrix.org afaik, disko doesn't use uuids to manage paritions, but labels `~ ❯ ls /dev/disk/by-partlabel/  disk-main-ESP  disk-main-luks  disk-main-swap` or i should probably say "doesn't use uuids to reference partitions"	15:13:51
lassulus	not sure if we can precalculate the UUIDs somehow, but afaik they are randomly generated	15:13:53
lassulus	I guess we could override them with some hash if we really wanted to	15:14:11
n3v3r_a9a1n	same for partlabel: warning: Git tree '/home/egor/my-little-flake' is dirty error: … while evaluating attribute 'nodes' at «string»:4:25: 3\| (deploy // { 4\| nodes = { \| ^ 5\| inherit (deploy.nodes) "immortal"; … while evaluating attribute 'immortal' at «string»:5:49: 4\| nodes = { 5\| inherit (deploy.nodes) "immortal"; \| ^ 6\| }; (stack trace truncated; use '--show-trace' to show the full trace) error: Failed assertions: - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-nvme0n1-luks is declared in your configuration. - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-sda-luks is declared in your configuration. 🚀 ❌ [deploy] [ERROR] Failed to evaluate deployment data: Evaluation resulted in a bad exit code: Some(1)	15:17:54
n3v3r_a9a1n	In reply to @xxxcrow:matrix.org same for partlabel: warning: Git tree '/home/egor/my-little-flake' is dirty error: … while evaluating attribute 'nodes' at «string»:4:25: 3\| (deploy // { 4\| nodes = { \| ^ 5\| inherit (deploy.nodes) "immortal"; … while evaluating attribute 'immortal' at «string»:5:49: 4\| nodes = { 5\| inherit (deploy.nodes) "immortal"; \| ^ 6\| }; (stack trace truncated; use '--show-trace' to show the full trace) error: Failed assertions: - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-nvme0n1-luks is declared in your configuration. - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-sda-luks is declared in your configuration. 🚀 ❌ [deploy] [ERROR] Failed to evaluate deployment data: Evaluation resulted in a bad exit code: Some(1) Solved with boot.initrd.luks.devices	15:26:01
	@lychee:lefishe.club changed their display name from lychee to kay.	17:11:04
9 Apr 2024
matthewcroughan @fosdem	lassulus: just wondering, have you seen the systemd-repart stuff in nixos?	16:24:18
matthewcroughan @fosdem	https://nixos.org/manual/nixos/unstable/#sec-image-repart	16:24:36
matthewcroughan @fosdem	it is just super fancy	16:24:45
lassulus	Yes	16:24:49
matthewcroughan @fosdem	If you had to compare it in terms of feature parity to disko, what would you say?	16:25:16

[root@nixos:~]# ls /mnt/
home  log  nix  persist  root  swap

[root@nixos:~]# ls /mnt/root
bin  boot  dev  etc  home  lib  lib64  nix  persist  proc  root  run  srv  sys  tmp  usr  var

[root@nixos:~]# btrfs subvolume list /mnt
ID 256 gen 29 top level 5 path home
ID 257 gen 33 top level 5 path log
ID 258 gen 33 top level 5 path nix
ID 259 gen 29 top level 5 path persist
ID 260 gen 36 top level 5 path root
ID 261 gen 18 top level 5 path swap
ID 262 gen 29 top level 260 path root/srv
ID 263 gen 30 top level 260 path root/var/lib/portables
ID 264 gen 31 top level 260 path root/var/lib/machines
ID 265 gen 33 top level 260 path root/var/tmp

10:47:53

n3v3r_a9a1n

In reply to @xxxcrow:matrix.org
then mount /dev/mapper/nvme-crypt /mnt

or i shouldn't do it at all?

10:50:02

lassulus

Perchun Pak: I created this PR to fix the gpt behaviour: https://github.com/nix-community/disko/pull/595

10:51:22

n3v3r_a9a1n

In reply to @xxxcrow:matrix.org
or i shouldn't do it at all?

if i mount the way tutorials on impermanence+btrfs say, everything looks fine,but how do i take the snapshot

10:54:15

n3v3r_a9a1n

In reply to @perchun:matrix.org
Vimjoyer did config for btrfs + impermanence, don't know about other things
https://youtu.be/YPKwkWtK7l0?feature=shared

also, sorry if it's not true, but i think the way way he implements everything is not really ok
1st. https://discourse.nixos.org/t/what-does-impermanence-add-over-built-in-functionality/27939/16
2nd. it doesn't work with some stuff (can't remember what exactly either lanzaboote, or clevis, or something like that)
3rd. something else i forgot exactly what

11:22:11

@perchun:matrix.org

In reply to @xxxcrow:matrix.org
also, sorry if it's not true, but i think the way way he implements everything is not really ok
1st. https://discourse.nixos.org/t/what-does-impermanence-add-over-built-in-functionality/27939/16
2nd. it doesn't work with some stuff (can't remember what exactly either lanzaboote, or clevis, or something like that)
3rd. something else i forgot exactly what

Yeah, it deleted all of my data if there wasn't something correct in the setup. Like no /persist/system or wrong permissions on /persist/home (in second scenario, home manager just failed to start completely). Though it is probably the fault of impermanence.

But for now, it works on my machine™. Feel free to send your final setup, I will happily steal it ;)

11:57:22

lassulus

whoops, I accidently ran sgdisk -o isntead -p on my main disk :D

12:52:35

lassulus

luckily I could recover it with disko

12:52:46

lassulus

but why are those 2 parameters (-p pronts, -o wipes) so close together on the keyboard :D

12:53:07

lassulus

* but why are those 2 parameters (-p prints, -o wipes) so close together on the keyboard :D

12:53:14

n3v3r_a9a1n

Quick questiono about disko and nixos-anywhere!
How do I skip disko in nixos-anywhere?

16:01:36

lassulus

Hmm you can't really. Maybe we should add a --stop-after-kexec parameter

16:29:37

l0b0 joined the room.

00:55:29

@palo:xaos.space changed their display name from palo to palo moved to @mrvandalo:terranix.org.

13:03:24

palo joined the room.

13:06:37

@palo:xaos.space left the room.

13:06:51

palo changed their display name from mrvandalo to palo.

13:12:45

n3v3r_a9a1n

is disko working with clevis??

error:
       … while evaluating attribute 'nodes'

         at «string»:4:25:

            3|                       (deploy // {
            4|                         nodes = {
             |                         ^
            5|                           inherit (deploy.nodes) "immortal";

       … while evaluating attribute 'immortal'

         at «string»:5:49:

            4|                         nodes = {
            5|                           inherit (deploy.nodes) "immortal";
             |                                                 ^
            6|                         };

       (stack trace truncated; use '--show-trace' to show the full trace)

       error:
       Failed assertions:
       - No filesystem or LUKS device with the name /dev/disk/by-uuid/9119a486-5702-4af7-bce8-5bb7e513ea6f is declared in your configuration.
       - No filesystem or LUKS device with the name /dev/disk/by-uuid/e85aa7c5-5926-434c-8142-0ede397a6369 is declared in your configuration.
🚀 ❌ [deploy] [ERROR] Failed to evaluate deployment data: Evaluation resulted in a bad exit code: Some(1)

15:07:54

@perchun:matrix.org

afaik, disko doesn't use uuids to manage paritions, but labels

~ ❯ ls /dev/disk/by-partlabel/
 disk-main-ESP
 disk-main-luks
 disk-main-swap

15:13:19

@perchun:matrix.org

In reply to @perchun:matrix.org
afaik, disko doesn't use uuids to manage paritions, but labels
~ ❯ ls /dev/disk/by-partlabel/
 disk-main-ESP
 disk-main-luks
 disk-main-swap

or i should probably say "doesn't use uuids to reference partitions"

15:13:51

lassulus

not sure if we can precalculate the UUIDs somehow, but afaik they are randomly generated

15:13:53

lassulus

I guess we could override them with some hash if we really wanted to

15:14:11

n3v3r_a9a1n

same for partlabel:

warning: Git tree '/home/egor/my-little-flake' is dirty
error:
       … while evaluating attribute 'nodes'

         at «string»:4:25:

            3|                       (deploy // {
            4|                         nodes = {
             |                         ^
            5|                           inherit (deploy.nodes) "immortal";

       … while evaluating attribute 'immortal'

         at «string»:5:49:

            4|                         nodes = {
            5|                           inherit (deploy.nodes) "immortal";
             |                                                 ^
            6|                         };

       (stack trace truncated; use '--show-trace' to show the full trace)

       error:
       Failed assertions:
       - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-nvme0n1-luks is declared in your configuration.
       - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-sda-luks is declared in your configuration.
🚀 ❌ [deploy] [ERROR] Failed to evaluate deployment data: Evaluation resulted in a bad exit code: Some(1)

15:17:54

n3v3r_a9a1n

In reply to @xxxcrow:matrix.org

same for partlabel:

warning: Git tree '/home/egor/my-little-flake' is dirty
error:
       … while evaluating attribute 'nodes'

         at «string»:4:25:

            3|                       (deploy // {
            4|                         nodes = {
             |                         ^
            5|                           inherit (deploy.nodes) "immortal";

       … while evaluating attribute 'immortal'

         at «string»:5:49:

            4|                         nodes = {
            5|                           inherit (deploy.nodes) "immortal";
             |                                                 ^
            6|                         };

       (stack trace truncated; use '--show-trace' to show the full trace)

       error:
       Failed assertions:
       - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-nvme0n1-luks is declared in your configuration.
       - No filesystem or LUKS device with the name /dev/disk/by-partlabel/disk-sda-luks is declared in your configuration.
🚀 ❌ [deploy] [ERROR] Failed to evaluate deployment data: Evaluation resulted in a bad exit code: Some(1)

Solved with boot.initrd.luks.devices

15:26:01

@lychee:lefishe.club changed their display name from lychee to kay.