@Colin Watson: Thanks for taking the time to look into this. I was left very disheartened earlier in the year when I upgraded, hit this problem and then was just dismissed.
The reason I am commenting now is I ran an apt-get dist-upgrade yesterday. I booted the machine this evening and have hit the same error. I know I installed a new kernel, I'm guessing there was a grub upgrade.
I don't need the machine now so I can leave it before attempting to fix. What can I do to get more information to either determine whether this bug affects me or help with a solution? Adam Niedling previously suggested the output of "sudo parted -l" and "sudo debconf-show grub-pc" would be useful. Is that still the case?
@Colin Watson: Thanks for taking the time to look into this. I was left very disheartened earlier in the year when I upgraded, hit this problem and then was just dismissed.
The reason I am commenting now is I ran an apt-get dist-upgrade yesterday. I booted the machine this evening and have hit the same error. I know I installed a new kernel, I'm guessing there was a grub upgrade.
I don't need the machine now so I can leave it before attempting to fix. What can I do to get more information to either determine whether this bug affects me or help with a solution? Adam Niedling previously suggested the output of "sudo parted -l" and "sudo debconf-show grub-pc" would be useful. Is that still the case?
Regards,
Cian