| 12 Jul 2024 |
 lassulus | maybe the start of it is inside or on the end of it | 11:45:52 |
| lassulus | trying to read the code now :) | 11:46:02 |
 nrv | 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 |
| nrv | In reply to @lassulus:lassul.us
trying to read the code now :) mine or generated?:P | 11:46:50 |
| nrv | it 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 fine | 11:48:36 |
| 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 |
| lassulus | it should be start=0, not 0M, but you should be able to leave it out | 11:54:44 |
| nrv | hmm, it isn't | 11:54:55 |
| nrv | apparently that's mine | 11:55:04 |
| nrv | examples just have size and no start | 11:55:15 |
| lassulus | yeah, start = 0 makes sgdisk automatically choose the next startpoint | 11:55:44 |
| lassulus | so size is usually enough to set | 11:56:35 |
| nrv | ...but it's not 0 | 11:56:40 |
| nrv | it's 0M | 11:56:42 |
| lassulus | yeah, that seems to be confusing to sgdisk | 11:57:05 |
| lassulus | maybe a bug in there? | 11:57:12 |
| nrv | it's worked. Thank God | 11:59:35 |
| nrv |
changed 0M to 1M
| 11:59:45 |
 [0x4A6F] | AFAIK "34s" is the first usable start point for partions on gpt table. | 11:59:45 |
