!oNSIfazDqEcwhcOjSL:matrix.org

disko

402 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko108 Servers

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


SenderMessageTime
12 Jul 2024
@nevrv:matrix.orgnrvbug?10:42:31
@nevrv:matrix.orgnrv * bug on the disko part?10:42:43
@nevrv:matrix.orgnrv
In reply to @nevrv:matrix.org
could it be that sgdisk --clear doesn't work properly and there's still partitions on the disk when i run disko multiple times?
* sure it could. blkdiscard fixes that. success after blkdiscard, no changes to disko config
10:43:26
@lassulus:lassul.uslassuluswhat command are you running?10:43:51
@nevrv:matrix.orgnrv
In reply to @nevrv:matrix.org
sure it could. blkdiscard fixes that. success after blkdiscard, no changes to disko config
wait, abort
10:44:47
@nevrv:matrix.orgnrvi got excited on one success message which was not the right one10:45:12
@nevrv:matrix.orgnrv
In reply to @lassulus:lassul.us
what command are you running?
give me a sec
10:45:16
@nevrv:matrix.orgnrv
In reply to @lassulus:lassul.us
what command are you running?

this is dicko.nix https://0x0.st/XMUo.txt
this is it's output https://0x0.st/XMUT.txt built by nix run .#disko -- --dry-run --mode format --arg disks '[ "/dev/disk/by-id/nvme-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" ]' ./disko.nix

the command that i'm running is sudo --preserve-env=NIX_PATH nix run .#disko -- --mode format --arg disks '[ "/dev/disk/by-id/nvme-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ]' ./disko.nix
disko rev is 786965e1b1ed3fd2018d78399984f461e2a44689

what i'm getting:

  • command log https://0x0.st/XMUQ.txt
  • the disk state after it is this:
Device                                                            Start     End Sectors Size Type
/dev/disk/by-id/nvme-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-part1 4194304 4196351    2048   1M BIOS boot

...for some reason

11:37:03
@nevrv:matrix.orgnrv This is btw when it now decided to switch back to not liking my sgdisk. I don't know if it is sgdisk, linux, disko or i'm stupid and blind and there's wrong numbers again.
The cryptsetup issue had another log
11:39:21
@nevrv:matrix.orgnrv * This is btw when it now decided to switch back to not liking my sgdisk. I don't know if it is sgdisk, linux or disko misbehaving or i'm stupid and blind and there's wrong numbers again.
The cryptsetup issue had another log
11:39:50
@lassulus:lassul.uslassulusah this is if you run the formatScript multiple times, the errors are expected there, if you want disko to wipe the drives before retrying, you should run --mode disko11:43:14

Show newer messages


Back to Room ListRoom Version: 10