Timeline for GRUB config file is set to an old /root partition after every kernel update
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 10, 2021 at 19:08 | comment | added | telcoM | When cloning a partition, the default assumption is that the new one will be 100% identical to the original... including any filesystem UUIDs. When cloning an entire disk, any UUIDs in the partition table will likewise be copied, unless you specifically take steps to re-uniquify them. This question has a list of filesystem-specific commands for changing the UUIDs. I'd suggest not deleting the question, as it might be helpful to someone else. | |
| Jan 10, 2021 at 14:09 | vote | accept | Blume | ||
| Jan 10, 2021 at 14:09 | comment | added | Blume | I did some tests with the /etc/grub.d/os-prober script, and I noticed that it was always detecting the two partitions, but they had the same UUID (clonezilla restore must have done so), and were both referenced by their common UUID on both entries on GRUB. I generated a new UUID for the old partition, and now I have two grub entries that work correctly for both. Since the problem was more about me not noticing the UUIDs and less about grub, should I just delete the question or edit it to be more clear about that ? | |
| Jan 10, 2021 at 14:01 | vote | accept | Blume | ||
| Jan 10, 2021 at 14:09 | |||||
| Jan 10, 2021 at 1:00 | history | answered | telcoM | CC BY-SA 4.0 |