30 May 2024 |
lassulus | hmm, not sure I have the time to debug that further :) also not sure if the issue would happen if disko is run again? | 11:31:07 |
waltmck | I've restarted the server a few times and the issue persists | 11:31:45 |
waltmck | I'll restart a few more times and hopefully that will fix the issue. If not, I'll let you know | 11:33:01 |
lassulus | hmm, it also fails after the partprobe | 11:37:56 |
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 (Salsa9) | 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 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 |
| @swendel:curious.bio joined the room. | 18:47:34 |
8 Jun 2024 |
| 🎈 Always joined the room. | 14:55:35 |
🎈 Always | 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 |
🎈 Always | 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 |
🎈 Always | 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 |
🎈 Always | doing btrfs swapfile outside of a separate volume is probably a bad idea (has something to do with compression i think) | 15:20:26 |