I copied a hard disk with kubuntu 13.10 to a new (bigger) one with dd, taking extra care to verify the copy with hashing it using md5sum. The copy was fine.
It bootet correctly, everything behaved normally.
After the upgrade to 14.04, the system didn't boot any more because of the error discussed in this thread.
It could be made to run normally with the methods suggested somewhere in this thread, e.g. booting from a Live system (debian based that one), mounting relevant partitions, chrooting, rewriting the boot sector as described above, unmounting, rebooting.
So maybe this bug has to do with switching hard disk.
Is the installer creating some kind of hash or ID of the disk in order to determine it's course of action in some branches of it's code execution? This might be the reason for the breaking of the update in my case.
I had same data on a new disk.
If some hash/ID of the HD (as an individual HD) informs the installer that I switched the disk and that for that reason it shall not write the complete set of parts of the updated grub, then this is the reason why it failed in my case.
I copied a hard disk with kubuntu 13.10 to a new (bigger) one with dd, taking extra care to verify the copy with hashing it using md5sum. The copy was fine.
It bootet correctly, everything behaved normally.
After the upgrade to 14.04, the system didn't boot any more because of the error discussed in this thread.
It could be made to run normally with the methods suggested somewhere in this thread, e.g. booting from a Live system (debian based that one), mounting relevant partitions, chrooting, rewriting the boot sector as described above, unmounting, rebooting.
So maybe this bug has to do with switching hard disk.
Is the installer creating some kind of hash or ID of the disk in order to determine it's course of action in some branches of it's code execution? This might be the reason for the breaking of the update in my case.
I had same data on a new disk.
If some hash/ID of the HD (as an individual HD) informs the installer that I switched the disk and that for that reason it shall not write the complete set of parts of the updated grub, then this is the reason why it failed in my case.