!oNSIfazDqEcwhcOjSL:matrix.org

disko

171 Members
disko - declarative disk partitioning - https://github.com/nix-community/disko55 Servers

Load older messages

SenderMessageTime
12 Jul 2024
@nevrv:matrix.orgnrvbecause now i see sgdisk failing again (though i tweaked the sizes)10:38:56
@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. 		10:42:08
@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
@nevrv:matrix.orgnrvthing is that i tried to do --zap and --clear and blkdiscard --force multiple times11:43:57
@nevrv:matrix.orgnrvand rebooting11:43:58
@nevrv:matrix.orgnrvit just changes behavior randomly11:44:08
@nevrv:matrix.orgnrvand i did mode disko, it just spits more errors or something so i decided to stick to format11:44:50
@nevrv:matrix.orgnrvi'll try it, sec11:44:54
@lassulus:lassul.uslassulusalso it seems your luks partitions conflicts with your grub-mbr partition11:45:41
@lassulus:lassul.uslassulusmaybe the start of it is inside or on the end of it11:45:52
@lassulus:lassul.uslassulustrying to read the code now :)11:46:02
@nevrv:matrix.orgnrv
In reply to @nevrv:matrix.org
i'll try it, sec

the same;

Could not create partition 2 from 4096 to 1258295295
Unable to set partition 2's name to '06445541fb4bfc49161c5e8c7b7b431ea6c8'!
Could not change partition 2's type code to 8300!
Error encountered; not saving changes.
11:46:07
@nevrv:matrix.orgnrv
In reply to @lassulus:lassul.us
trying to read the code now :)
mine or generated?:P 		11:46:50
@nevrv:matrix.orgnrvit looks fine. start offset is 1M/2048 sectors and the main partition is from 2M/4096 sector and on, after which there is nothing currently so it's fine11:48:36
@nevrv:matrix.orgnrv
In reply to @nevrv:matrix.org

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

The resulting disk state is this btw 		11:49:38
@nevrv:matrix.orgnrv
In reply to @nevrv:matrix.org

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

* The resulting disk state is this though 		11:49:53
@nevrv:matrix.orgnrvSeems that the first 1M one gets created incorrectly11:49:58
@nevrv:matrix.orgnrvBut why?11:50:02
@nevrv:matrix.orgnrvit's --new=1:0M:+1M11:50:24
@nevrv:matrix.orgnrv
In reply to @nevrv:matrix.org
The resulting disk state is this though
It's this, and the fact that it worked before once, all the way in with all zfs stuff mounted & fine 		11:52:13

Show newer messages

Back to Room ListRoom Version: 10