| 11 Mar 2025 |
 food style edible product | Anyone have a btrfs/disko/impermanence config I can peep? Having trouble getting conflicting definitions for filesystems."/foobar" or having stage1 failures due to mounts not working. | 21:47:38 |
| food style edible product changed their display name from Department Store Crust-Punk-Chic to FORWARD TO EXTINCTION. | 21:54:13 |
| food style edible product changed their display name from FORWARD TO EXTINCTION to Like/Share/Subscribe. | 21:54:53 |
| 12 Mar 2025 |
|  cornfused joined the room. | 01:00:21 |
 Mic92 | @dantefromhell:matrix.org: is this where I added the change for swap? | 04:25:45 |
| food style edible product changed their display name from Like/Share/Subscribe to KFC is All I See. | 05:25:10 |
 dantefromhell | In reply to @joerg:thalheim.io
@dantefromhell:matrix.org: is this where I added the change for swap? yes. sorry for the mangled message, editor on the phone displays the code highlights properly, but f*** it up once I hit save/ send | 12:52:57 |
| 13 Mar 2025 |
 waltmck | I have a ZFS mirror running as root that was formatted with disko. If I replaced both drives one at a time (i.e. with zpool offline and zpool replace), would the initramfs know where to look to mount the root partition next time I boot? | 15:58:40 |
| waltmck | in my disko config the drives are referred to as /dev/disk/by-id identifies, so I want to make sure that there is no hard-coded fstab entry or anything that uses those | 15:59:56 |
| waltmck | * in my disko config the drives are referred to as /dev/disk/by-id identifiers, so I want to make sure that there is no hard-coded fstab entry or anything that uses those | 16:00:27 |
| food style edible product changed their display name from KFC is All I See to That's "Mr. Anarchist" to you. | 17:48:08 |
| 14 Mar 2025 |
 phaer | In a typical zfs setup, fstab doesn't reference the underlying devices but only the datasets (i.e. rpool/root, not /dev/disk/by-id/...) here.
the initrd pretty much does a zpool import on boot, so you should be good after zpool replace. (but no warranty and all ;)) | 15:46:25 |
| phaer | * In a typical zfs setup, fstab doesn't reference the underlying devices but only the datasets (i.e. rpool/root, not /dev/disk/by-id/...) here.
the initrd pretty much does a zpool import on boot, so you should be good after zpool replace. (but no warranty as usual ;)) | 15:46:32 |
| waltmck | I see. So I understand that it works roughly like: ZFS scans all storage devices for zfs disks, and then makes the pools it finds available which can be referred to by name in the legacy mount scripts? | 15:48:01 |
| phaer | Yes, exactly | 15:48:34 |
| phaer | Had missed that one before: but that's exactly how it is. It should be safe to re-run but as the license says: this software comes without warranty of any kind. So better check your backups ;) | 15:51:09 |
| phaer | Not a btrfs user myself, but the conflicting definitions do sound solvable. Do you have your config online somewhere? | 15:55:08 |
| 16 Mar 2025 |
|  mprasil joined the room. | 21:18:49 |
|  digitaltwin joined the room. | 22:38:51 |
| food style edible product changed their display name from That's "Mr. Anarchist" to you to iLovePsyOps. | 23:41:31 |
| 17 Mar 2025 |
|  Sylvie (They/She) 🏳️⚧️ left the room. | 04:38:41 |
|  nicoty joined the room. | 17:46:50 |
| food style edible product changed their display name from iLovePsyOps to Ghost of Corporate Future. | 18:59:58 |
| 18 Mar 2025 |
 matthewcroughan | Any opposition to renaming installTest to diskoInstallTest ? | 18:06:55 |
| matthewcroughan | or in putting disko attrs into a disko set? like system.config.build.disko.installTest? | 18:07:23 |
| matthewcroughan | It has always annoyed me when trying to find installTest, because I ignore this attribute believing it to be a nixpkgs one, not realising disko introduced it | 18:07:48 |
| matthewcroughan | [root@nixos:/home/nixos/nixcfg]# nix run .#nixosConfigurations.p4.config.system.build.diskoScript
warning: Git tree '/home/nixos/nixcfg' is dirty
error: unable to execute '/nix/store/i1v0hbscb3m3bib3f90dsm479d6aisk8-disko/bin/disko': Not a directory
| 18:36:34 |
| matthewcroughan | Did not realise before that the disko script was not runnable | 18:36:41 |
| 19 Mar 2025 |
|  erahhal joined the room. | 03:05:37 |
| erahhal | Hi! I've used disko with nixos-anywhere on a few machines and now on a newer machine having some trouble. Not sure if I broken something in the config or something changed out since NixOS has been bumped since then. I'm seeing this error and no idea what it means:
error: flake 'git+file:///home/erahhal/Code/nixcfg' does not provide attribute 'packages.x86_64-linux.nixosConfigurations."msi-linux".config.system.build.diskoScript', 'legacyPackages.x86_64-linux.nixosConfigurations."msi-linux".config.system.build.diskoScript' or 'nixosConfigurations."msi-linux".config.system.build.diskoScript'
Does it mean that it can't find the disk device so it's not able to build a script? Perhaps I've provided the wrong device? I triple checked it though and it seems to be correct.
| 03:09:45 |
