| 30 May 2024 |
 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 |
