| 17 Sep 2025 |
mprasil | It seems to be some effort to not overwrite pre-existing partition. | 14:29:15 |
mprasil | But I found it to be quite a footgun. For example it's pretty common that EFI partition is 1GB (or 500M) an due to that if statemen disko silenty didn't format my EFI partition because previously there was also EFI partition with same size. (so when disko recreated GPT, EFI "adopted" contents of previous vfat there) | 14:31:45 |
mprasil | disko does prompt whether it should destroy data on the disk and --mode destroy,format,mount is also pretty explicit about what the user expects/wants. So this effort to preserve data feels quite a bit surprising. | 14:33:38 |
| 19 Sep 2025 |
| bl1nk changed their profile picture. | 15:21:46 |
| bl1nk changed their profile picture. | 15:24:43 |
| mkg20001 changed their profile picture. | 17:20:47 |
| 21 Sep 2025 |
| rocky ((λ💝.💝)💐) (she/they; ask before DM please) changed their display name from ((λ💝.💝)💐) (she/they; ask before DM please) to rocky ((λ💝.💝)💐) (she/they; ask before DM please). | 16:45:39 |
| 22 Sep 2025 |
| lillecarl changed their display name from LilleCarl (Salsa9) to lillecarl. | 10:36:51 |
| 23 Sep 2025 |
| sinan changed their profile picture. | 02:47:54 |
| Chris P Bacon joined the room. | 09:46:59 |
| kenji changed their display name from a-kenji to kenji. | 10:37:21 |
| @epk123:matrix.org left the room. | 20:08:04 |
| @freexploit:trafkin.com | 20:37:04 |
| @freexploit:trafkin.com | 20:37:30 |
| @freexploit:trafkin.com left the room. | 20:38:09 |
cdata | I ended up filing an issue. Thanks in advance if anyone here has any insights: https://github.com/nix-community/disko/issues/1133 | 20:53:54 |
cdata | * I ended up filing an issue with a minimal test case demonstrating the problem. Thanks in advance if anyone here has any insights: https://github.com/nix-community/disko/issues/1133 | 20:54:38 |
| 29 Sep 2025 |
| Pol joined the room. | 10:06:33 |
no-mood | Could you help me understand what the problem is with this config? I would like to have bcachefs with tiered storage between hdd and nvme, but after deploying with nixos-anywhere, the system won't boot.
{ inputs, ... }:
{
imports = [
inputs.disko.nixosModules.disko
];
# Enable bcachefs support in kernel
boot.supportedFilesystems = [ "bcachefs" ];
disko.devices = {
disk = {
# NVMe SSD - Fast tier for metadata and caching
nvme = {
type = "disk";
device = "/dev/disk/by-id/nvme-SAMSUNG_MZVLB256HAHQ-000H1_S425NX2M363531";
content = {
type = "gpt";
partitions = {
ESP = {
priority = 1;
name = "ESP";
size = "512M";
type = "EF00";
content = {
type = "filesystem";
format = "vfat";
mountpoint = "/boot";
mountOptions = [ "umask=0077" ];
};
};
# NVMe partition for bcachefs (fast tier)
main = {
size = "100%";
content = {
type = "bcachefs";
filesystem = "main_bcachefs";
label = "nvme.main";
extraFormatArgs = [ "--discard" ];
};
};
};
};
};
# HDD - Bulk storage tier
hdd = {
type = "disk";
device = "/dev/disk/by-id/ata-WDC_WD5000AAKX-60U6AA0_WD-WCC2EU003365";
content = {
type = "gpt";
partitions = {
# HDD partition for bcachefs (storage tier)
main = {
size = "100%";
content = {
type = "bcachefs";
filesystem = "main_bcachefs";
label = "hdd.backup";
};
};
};
};
};
};
bcachefs_filesystems = {
main_bcachefs = {
type = "bcachefs_filesystem";
extraFormatArgs = [
"--compression=zstd"
"--background_compression=zstd:15"
# Tiering configuration
"--background_target=hdd"
"--foreground_target=nvme"
"--promote_target=nvme"
"--metadata_target=nvme"
];
subvolumes = {
# Root filesystem - equivalent to @root
"@root" = {
mountpoint = "/";
mountOptions = [
"noatime"
];
};
# Nix store - equivalent to @nix
"@nix" = {
mountpoint = "/nix";
mountOptions = [
"noatime"
];
};
# Persistent data - equivalent to @persist
"@persist" = {
mountpoint = "/persist";
mountOptions = [
"noatime"
];
};
# Backups directory
"@backups" = {
mountpoint = "/var/backups";
mountOptions = [
"noatime"
];
};
};
};
};
};
}
| 11:56:03 |
lassulus | good question, what happens during boot? | 11:58:06 |
no-mood | First, Now I've noticed that during the deploy I get:
Caution! After loading partitions, the CRC doesn't check out!
Warning: Invalid CRC on main header data; loaded backup partition table.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Main header: ERROR
Backup header: OK
Main partition table: ERROR
Backup partition table: ERROR
Invalid partition data!
Information: Creating fresh partition table; will override earlier problems!
Warning! Mismatched GPT and MBR partition! MBR partition 1, of type 0x82,
has no corresponding GPT partition! You may continue, but this condition
might cause data loss in the future!
The operation has completed successfully.
+ rm -rf /tmp/tmp.Befxfm9cFt
Connection to 192.168.68.103 closed.
| 12:08:24 |
no-mood | * First, Now I've noticed that during the deploy I get:
Caution! After loading partitions, the CRC doesn't check out!
Warning: Invalid CRC on main header data; loaded backup partition table.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Main header: ERROR
Backup header: OK
Main partition table: ERROR
Backup partition table: ERROR
Invalid partition data!
Information: Creating fresh partition table; will override earlier problems!
Warning! Mismatched GPT and MBR partition! MBR partition 1, of type 0x82,
has no corresponding GPT partition! You may continue, but this condition
might cause data loss in the future!
The operation has completed successfully.
+ rm -rf /tmp/tmp.Befxfm9cFt
Connection to 192.168.68.103 closed.
Back to your answer, It just hangs. No boot screen or anything
| 12:08:53 |
lassulus | ok, so it sounds like the EFI partition is not detected then or you didn't set efi.canTouchVariables (or whatever the exact name was). The other error you just posted also seems pretty critical | 12:10:09 |
no-mood | It could be the EFI partition since it doesn't show "Linux boot manager" (or whatever was it) in the boot menu. That option is already set:
boot.loader = {
systemd-boot.enable = true;
efi.canTouchEfiVariables = true;
};
| 12:26:22 |
no-mood | Is it necessary to have boot.supportedFilesystems = [ "bcachefs" ]; on the target image? | 12:51:25 |
| 30 Sep 2025 |
| ruby left the room. | 01:50:30 |
| @lotte:chir.rs changed their profile picture. | 10:58:41 |
| 1 Oct 2025 |
| @realsnick:matrix.org joined the room. | 07:15:15 |
| jarppiko joined the room. | 21:04:58 |
| 2 Oct 2025 |
| -> @oli:catgirl.cloud changed their display name from olivia [she/it] 🏳️⚧️ to olivia floof company edition [she/it] 🏳️⚧️. | 07:04:32 |