!oNSIfazDqEcwhcOjSL:matrix.org

disko

358 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko89 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
4 Jun 2025
@rob.sliwi:matrix.orgrobsliwi changed their display name from Robert Sliwinski to robsliwi.18:30:13
5 Jun 2025
@s:consortium.chatshelvacu joined the room.21:48:38
@s:consortium.chatshelvacu

https://github.com/nix-community/disko/blob/d74db625a5cf3f46cf8fa545d6ef10bd3463ea07/lib/types/gpt.nix#L259

if ! blkid "${config.device}" >&2; then
  sgdisk --clear "${config.device}"
fi

I can't tell if I found a bug or if I'm just not understanding this; blkid exits with code 2 when run on a blank (all 00) block device, in which case it... clears the gpt label? that isn't there?

21:55:56
@s:consortium.chatshelvacu
In reply to @pink_rocky:tchncs.de
Okay, right now I’ve gotten it to error on the build with:
"Unable to read fragment cache entry"
"Unable to read page"
"unknown filesystem type 'btrfs'"
what exactly are you building? Do you mean nixos-rebuild build? Could send the full output in a pastebin or smth?
22:03:21
@s:consortium.chatshelvacu
In reply to @pink_rocky:tchncs.de
configuration.nix
Separately, I highly recommend switching to a flake-based config in a git repo. That would make it possible to link to a specific commit and then everyone else can run the exact same build.
22:05:09
@s:consortium.chatshelvacu Also I strongly recommend not using /dev/sdb as the device; the ordering can change between boots and when you add/remove thumb drives. Instead look for your drive in /dev/disk/by-id/ 22:06:24
@s:consortium.chatshelvacu also I can't build your config because it's missing hardware-configuration.nix 22:09:11
6 Jun 2025
@creepinson:matrix.org@creepinson:matrix.org left the room.00:18:44
@francesco:zanini.mefrancesco joined the room.07:06:03
@pink_rocky:tchncs.derocky ((λ💝.💝)💐) (she/they; ask before DM please)@shelvacu Thank you for the help! I will give you that info later07:35:28
@francesco:zanini.mefrancesco

Hey folks, quick question: I'm trying to setup a bind mount that points to a file system part of a disk managed by disko. I am unable to build the disk image because the order of operation is wrong:

  1. disks and filesystems created
  2. (a file-system irrelevant to this issue is mounted)
  3. bind mount tried, but source fs not mounted
  4. (I assume here it would mount the source fs)

Is there anything I can do to influence the order? I tried messing around with _meta.deviceDependencies but without much success.

11:59:29
@s:consortium.chatshelvacuyou should be able to look at the script produced by disko and confirm #412:01:32
@s:consortium.chatshelvacuwhich would be good to check since its a very different issue if its mounted nowhere12:02:08
@francesco:zanini.mefrancescoThanks let me check that.12:03:07
@francesco:zanini.mefrancescoMy assumption was correct: the issue starts here: https://github.com/nix-community/disko/blob/17d08c65c241b1d65b3ddf79e3fac1ddc870b0f6/lib/default.nix#L970 Basically I have root (tmpfs), a writable partition at /system, and a bind mount /nix -> /system/nix.12:06:37
@francesco:zanini.mefrancesco

the mount order is currently:

  • root
  • /nix (bind)
  • /system/nix

I guess a possible work-around would be to call system anything that is lexicographically before nix?

12:08:00

Show newer messages


Back to Room ListRoom Version: 10