| 30 May 2024 |
 lassulus | and the zap should after the partprobe | 11:38:02 |
| lassulus | this could be another issue | 11:38:08 |
 waltmck | yep, issue just persisted under another full reboot. Reboots wipe all of the rescue system state so the problem is either in my config file or in the disk state | 11:38:14 |
| lassulus | https://github.com/nix-community/disko/pull/654 | 11:40:41 |
| lassulus | ah forgot to rebase | 11:41:23 |
| waltmck | ahh, I will try running sgdisk --zap-all | 11:41:25 |
| waltmck | I think it worked | 11:43:10 |
| waltmck | the output for sgdisk --zap-all /dev/md/raid1 was
Warning! Disk size is smaller than the main header indicates! Loading
secondary header from the last sector of the disk! You should use 'v' to
verify disk integrity, and perhaps options on the experts' menu to repair
the disk.
Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: OK
Main partition table: OK
Backup partition table: ERROR
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
| 11:43:32 |
| waltmck | great that fixed everything | 11:46:36 |
 lillecarl | lassulus: Out of curiosity, would changing the size of partitions resolve this? Since /dev/md/raid1 header would be at a different location.... right? | 12:37:49 |
| lassulus | not sure, probably | 12:38:46 |
| 1 Jun 2024 |
|  relichunter joined the room. | 21:46:01 |
| 2 Jun 2024 |
|  bumperboat (UTC+2) changed their display name from bumperboat (UTC+7) to bumperboat (UTC+1). | 05:28:59 |
| 4 Jun 2024 |
|  raitobezarius changed their display name from raitobezarius (DECT: 7248) to raitobezarius. | 11:15:39 |
|  Tanja (she/her) changed their display name from Tanja (☎️ 6920 at GPN22, she/her) to Tanja (she/her). | 18:51:48 |
|  netpleb joined the room. | 21:52:57 |
| 6 Jun 2024 |
|  Sebastian joined the room. | 18:47:34 |
| 8 Jun 2024 |
|  wieldable9080 joined the room. | 14:55:35 |
| wieldable9080 | hello to all fellow disko dancers/lovers
the drive is encrypted, and every time i boot it waits for this swap, but it's not there
content = {
type = "btrfs";
extraArgs = ["-f"];
subvolumes = {
"/@SWAP" = {
mountpoint = "/.swapvol";
swap.swapfile.size = "(people will start asking why so much swap)G";
};
};
};
| 14:58:37 |
| lassulus | maybe you want to set swap.swapfile.path instead of mountpoint? | 15:14:36 |
| lassulus | but there is also a default value for that | 15:17:06 |
| lassulus | so maybe you don't need mountpoint? | 15:17:12 |
| wieldable9080 | In reply to @lassulus:lassul.us
maybe you want to set swap.swapfile.path instead of mountpoint? this is the easy way of doing this :D | 15:18:37 |
| wieldable9080 | In reply to @lassulus:lassul.us
so maybe you don't need mountpoint? btrfs subvolume swap has its pros, also it just looks nice | 15:19:05 |
| lassulus | hmm, ok, reading the code again, it should also work with a mountpoint set | 15:20:24 |
| wieldable9080 | doing btrfs swapfile outside of a separate volume is probably a bad idea (has something to do with compression i think) | 15:20:26 |
| wieldable9080 | In reply to @lassulus:lassul.us
hmm, ok, reading the code again, it should also work with a mountpoint set i think i took this code from the main repo :D | 15:20:55 |
| wieldable9080 | i mean, except the subvolume naming | 15:21:12 |
| lassulus | whats the error you see on boot? | 15:24:17 |
| wieldable9080 | In reply to @lassulus:lassul.us
whats the error you see on boot? timeout waiting for the device which somewhere shows as this swap swap | 15:25:34 |
