disko | 353 Members | |
| disko - declarative disk partitioning - https://github.com/nix-community/disko | 88 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 May 2024 | ||
| Redacted or Malformed Event | 09:59:23 | |
| waltmck: Updated PR, missed that you're double declaring the disks | 10:00:21 | |
| Updating the ESP partitions as you suggest gives a similar error
| 10:12:41 | |
I also tried setting the boot partition to start="0"; end="1M"; | 10:14:37 | |
LilleCarl (Salsa9): could you also elaborate on why you think switching to start= end= would help? Has the interface changed and the example files not been updated? | 10:23:42 | |
| waltmck: I might just be using "the old way". I've ran disko for awhile and a half. If it didn't work then I don't know | 10:25:33 | |
| If you revert the changes, does the device appear as /dev/md127 after disko fails? | 10:25:53 | |
In reply to @lillecarl:matrix.orgIt appears as /dev/md/raid1. Here more logs for context. By the way, the /boot array is starting fine | 10:30:00 | |
In reply to @lillecarl:matrix.org* It appears as /dev/md/raid1. By the way, the /boot array is starting fine | 10:30:09 | |
| * It appears as
| 10:31:25 | |
I am getting a warning at the beginning: trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the mdmon service to crash. | 10:33:15 | |
* I am getting a warning at the beginning: trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the mdmon service to crash. | 10:33:26 | |
| There is a bug about that, it doesn't look like it should actually cause this issue. But who knows | 10:34:43 | |
| Nah I've got that same thing on my desktop | 10:35:02 | |
| waltmck: https://github.com/Lillecarl/nixos/blob/master/hosts/shitbox/disko.nix You can compare with mine. I don't raid my bootloader though, I mirror with grub. Don't use my thing as a reference for "this is right". What happens if you run the erroring command (as root) yourself? | 10:38:19 | |
In reply to @lillecarl:matrix.orgSame thing happens. I am actually running this entire thing as root (sshing to root@hostname) | 10:57:41 | |
| waltmck: ```bash
| 11:12:16 | |
| Invalid argument during seek for read on /dev/md/raid1 seems like a corrupt partition table. can you try printing it with fdisk -l or parted -l? | 11:12:31 | |
* Invalid argument during seek for read on /dev/md/raid1 seems like a corrupt partition table. can you try printing it with fdisk -l or parted -l? | 11:12:42 | |
*
| 11:12:46 | |
In reply to @lillecarl:matrix.org
| 11:13:04 | |
In reply to @lassulus:lassul.us
| 11:14:45 | |
| huh dos | 11:18:08 | |
| that doesn't see right | 11:18:13 | |
| maybe there was already a partition table which got mixed up somehow and the cleanup script failed to delete it | 11:18:44 | |
| how did you run disko? | 11:19:24 | |
| Interesting. That means that disko isn't actually totally reproducible/declarative? | 11:19:29 | |
| I am running it through nixos-anywhere | 11:19:40 | |
| I have a rescue system booted from a network drive so I have access to the disks | 11:20:06 | |
| it should be, but removing existing partitions is sometimes a bit lagging :) | 11:20:14 | |