| 12 Jul 2024 |
nrv | 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 |
nrv | 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 |
nrv | Seems that the first 1M one gets created incorrectly | 11:49:58 |
nrv | But why? | 11:50:02 |
nrv | it's --new=1:0M:+1M | 11:50:24 |
nrv | 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 |
nrv | Then i happily changed some datasets & mount settings and it broke again | 11:52:46 |
nrv | * Then i happily changed some datasets & mount settings expecting that i can finally purge & rebuild it until i'm happy and it broke again | 11:53:19 |
lassulus | hmm, I guess the start=0M confuses sgdisk | 11:53:59 |
lassulus | Could not create partition 1 from 8594128896 to 8594130943 | 11:54:00 |
nrv | But isn't it straight from example? | 11:54:21 |
lassulus | uh I hope not | 11:54:31 |