Closed tuxjz closed 2 years ago
Can you see if there's a reliable automated way to detect the partitions on your setup? I'll be happy to integrate it into migrate2rocky if there is.
I'll be happy to revisit this if there is a way to determine the EFI partitions in any sort of automated way other than just knowing what they are. I'm closing this issue for now, please feel free to re-open it if you have further information.
Migration script gives an error:
I have few servers booting out of SAN (using Fibre Channel with multipath) so root device is backed by multipathd mapper device and script isn't going well with that. I have tracked down, that it is starting to fail on line 561
efi_disk
(lsblk doesn't give any output = empty string) and then on next line 562 -efi_partition
fails for non existent partition (as mentioned above from the script log). IIRC when using multipath, partitions are mapped on different device-mapper "devices".https://github.com/rocky-linux/rocky-tools/blob/92b35b59d9095c29a7cbc583e4d8c63663f5f79a/migrate2rocky/migrate2rocky.sh#L561 https://github.com/rocky-linux/rocky-tools/blob/92b35b59d9095c29a7cbc583e4d8c63663f5f79a/migrate2rocky/migrate2rocky.sh#L562
whole disk device is mpatha = /dev/mapper/mpatha = /dev/dm-0 efi partition is mpatha1 = /dev/mapper/mpatha1 = /dev/dm-2
My monkey patch/workaround was to place multipaths to function as static vars:
Then it completed migration successfully.