mirror of
https://github.com/nix-community/disko
synced 2024-09-20 05:51:54 +00:00
Update table-to-gpt migration guide
- Generalize examples to be independent of ZFS - Reduce indent of examples to focus on the relevant bits - Add explicit migration steps, pre- and postconditions
This commit is contained in:
Martin Weinelt
mergify[bot]
parent
9d5c673a66
commit
0274af4c92
1 changed files with 96 additions and 86 deletions
|
|
@ -1,10 +1,10 @@
|
||||||
# disko table to gpt migration guide
|
# Migrating to the new GPL layout
|
||||||
NixOS on ZFS with latest disko
|
|
||||||
## Error
|
|
||||||
|
|
||||||
WHen deploying NixOS the following trace occurs
|
## Situation
|
||||||
|
|
||||||
```clean=
|
When evaluating your NixOS system closure the following trace appears:
|
||||||
|
|
||||||
|
```
|
||||||
trace: warning: The legacy table is outdated and should not be used. We recommend using the gpt type instead.
|
trace: warning: The legacy table is outdated and should not be used. We recommend using the gpt type instead.
|
||||||
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
|
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
|
||||||
If you encounter errors similar to:
|
If you encounter errors similar to:
|
||||||
|
|
@ -12,106 +12,116 @@ If you encounter errors similar to:
|
||||||
this is likely due to the use of the legacy table type.
|
this is likely due to the use of the legacy table type.
|
||||||
```
|
```
|
||||||
|
|
||||||
## Before
|
The solution is to migrate to the new `gpt` layout type.
|
||||||
Configuration in question
|
|
||||||
|
|
||||||
```nix=
|
## Precondition
|
||||||
{ disk ? "/dev/nvme0n1", ... }:
|
|
||||||
|
Disko was set up with
|
||||||
|
|
||||||
|
- `type = "table"` and
|
||||||
|
- `format = "gpt"`,
|
||||||
|
|
||||||
|
for example like this:
|
||||||
|
|
||||||
|
```nix
|
||||||
{
|
{
|
||||||
boot.supportedFilesystems = [ "zfs" ];
|
disko.devices.disk.example = {
|
||||||
|
type = "disk";
|
||||||
disko.devices = {
|
device = "/dev/nvme0n1";
|
||||||
disk = {
|
content = {
|
||||||
nvme = {
|
type = "table";
|
||||||
type = "disk";
|
format = "gpt";
|
||||||
device = disk;
|
partitions = [
|
||||||
content = {
|
{
|
||||||
type = "table";
|
name = "ESP";
|
||||||
format = "gpt";
|
start = "0";
|
||||||
partitions = [
|
end = "512MiB";
|
||||||
{
|
fs-type = "fat32";
|
||||||
name = "ESP";
|
bootable = true;
|
||||||
start = "0";
|
content = {
|
||||||
end = "512MiB";
|
type = "filesystem";
|
||||||
fs-type = "fat32";
|
format = "vfat";
|
||||||
bootable = true;
|
mountpoint = "/boot";
|
||||||
content = {
|
};
|
||||||
type = "filesystem";
|
}
|
||||||
format = "vfat";
|
{
|
||||||
mountpoint = "/boot";
|
name = "root";
|
||||||
};
|
start = "512MiB";
|
||||||
};
|
end = "100%";
|
||||||
{
|
content.format = "ext4";
|
||||||
name = "zfs";
|
}
|
||||||
start = "512MiB";
|
];
|
||||||
end = "100%";
|
|
||||||
content = {
|
|
||||||
type = "zfs";
|
|
||||||
pool = "tank";
|
|
||||||
};
|
|
||||||
}
|
|
||||||
];
|
|
||||||
};
|
|
||||||
};
|
|
||||||
};
|
|
||||||
zpool = {
|
|
||||||
...
|
|
||||||
};
|
};
|
||||||
};
|
};
|
||||||
}
|
}
|
||||||
|
|
||||||
```
|
```
|
||||||
# Migration
|
|
||||||
|
|
||||||
|
## Remediation
|
||||||
|
|
||||||
|
The new GPT layout (`type = "gpt"`) uses partlabels to realize the partiton numbering. For this reason you have to manually set up partition labels, if you want to resolve this issue.
|
||||||
|
|
||||||
|
### Create GPT partition labels
|
||||||
|
|
||||||
|
For each partition involved, create the partition label from these components:
|
||||||
|
|
||||||
|
- The partition number (e.g. /dev/nvme0n**1**, or /dev/sda**1**)
|
||||||
|
- The parent type in your disko config (value of `disko.device.disk.example.type = "disk";`)
|
||||||
|
- The parent name in your disko config (attribute name of `disko.devices.disk.example`, so `example` in this example)
|
||||||
|
- The partition name in your disko config (attribute name of `disko.devices.disk.content.partitions.*.name`)
|
||||||
|
|
||||||
The new gpt layout uses partlabels to unify the partiton numbering. for this reason you have to set the partition labels manually if you want to upgrade.
|
|
||||||
```bash
|
```bash
|
||||||
sgdisk -c 1:disk-nvme-ESP /dev/nvme0n1
|
# sgdisk -c 1:disk-example-ESP /dev/nvme0n1
|
||||||
sgdisk -c 2:disk-nvme-zfs /dev/nvme0n1
|
# sgdisk -c 2:disk-example-zfs /dev/nvme0n1
|
||||||
Warning: The kernel is still using the old partition table.
|
Warning: The kernel is still using the old partition table.
|
||||||
The new table will be used at the next reboot or after you
|
The new table will be used at the next reboot or after you
|
||||||
run partprobe(8) or kpartx(8)
|
run partprobe(8) or kpartx(8)
|
||||||
The operation has completed successfully.
|
The operation has completed successfully.
|
||||||
```
|
```
|
||||||
|
|
||||||
1 is the partition number (in system `/dev/nvme0n1p`**`1`**)
|
### Update disko configuration
|
||||||
disk is the parents type (in config: `disko.devices.disk.nvme.type = `**`"disk"`**)
|
|
||||||
nvme is the parents name ( in config: `disko.devices.disk.`**`nvme`**)
|
|
||||||
ESP is the name of the partition (in config: `disko.devices.disk.content.partitions.`**`ESP`**)
|
|
||||||
|
|
||||||
usually it's okay to fuck this up, since booting an old generation should still be possible as the previous setup used disk numbering instead. When booting the new system you will see that systemd is waiting for the device with the respective partlabel.
|
Make the following changes to your disko configuration:
|
||||||
# After
|
|
||||||
|
|
||||||
```nix=
|
1. Set `disko.devices.disk.example.content.type = "gpt"`
|
||||||
disko.devices = {
|
1. Remove `disko.devices.disk.example.format`
|
||||||
disk = {
|
1. Convert `disko.devices.disk.example.partitions` to an attribute set and promote the `name` field to the key for its partition
|
||||||
nvme = {
|
1. Add a `priority` field to each partition, to reflect the intended partition number
|
||||||
type = "disk";
|
|
||||||
device = disk;
|
Then rebuild your system and reboot.
|
||||||
content = {
|
|
||||||
type = "gpt";
|
### Recovering from mistake
|
||||||
partitions = {
|
|
||||||
ESP = {
|
If you made a mistake here, your system will be waiting for devices to appear, and then run into timeouts. You can easily recover from this, since rebooting into an old generation will still use the legacy way of numbering of partitions.
|
||||||
size = "512MiB";
|
|
||||||
type = "EF00";
|
## Result
|
||||||
priority = 1; # instead of "start" the priority is used, otherwise the partitions are created alphabetically (ESP before zfs)
|
|
||||||
content = {
|
The fixed disko configuration would look like this:
|
||||||
type = "filesystem";
|
|
||||||
format = "vfat";
|
```nix
|
||||||
mountpoint = "/boot";
|
{
|
||||||
};
|
disko.devices.disk.example = {
|
||||||
};
|
type = "disk";
|
||||||
zfs = {
|
device = "/dev/nvme0n1";
|
||||||
size = "100%";
|
content = {
|
||||||
content = {
|
type = "gpt";
|
||||||
type = "zfs";
|
partitions = {
|
||||||
pool = "tank";
|
ESP = {
|
||||||
};
|
size = "512MiB";
|
||||||
};
|
type = "EF00";
|
||||||
|
priority = 1;
|
||||||
|
content = {
|
||||||
|
type = "filesystem";
|
||||||
|
format = "vfat";
|
||||||
|
mountpoint = "/boot";
|
||||||
};
|
};
|
||||||
};
|
};
|
||||||
|
root = {
|
||||||
|
size = "100%";
|
||||||
|
priority = 2;
|
||||||
|
content.format = "ext4";
|
||||||
|
};
|
||||||
};
|
};
|
||||||
};
|
};
|
||||||
zpool = { ... };
|
};
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue