[Bug 949992] Re: Upgrade from Lucid to Precise results in broken grub configuration
Rick McBride
rick.mcbride at canonical.com
Fri Mar 9 19:54:04 UTC 2012
That's meant to be update-manager -d of course.
On 03/09/2012 01:31 PM, Rick McBride wrote:
> Actually, during the dist-manager -d install, I did get a dialog that
> was all "unknown character" blocks in the message and on the buttons. I
> don't know what it was asking. It didn't appear to block (I never
> answered it, not being able to read it), but it was perhaps that
> message. I HAVE seen it in the past, but not during this testing session.
>
> I had meant to reproduce and document that weird dialog, but got
> distracted by this problem. I'll go back and get more info on that
> either over the weekend or Monday, when I have capacity on my VM host to
> make another pre-update clone and run the process again.
>
> The only dialog that I recall, apart from the typical "remove these
> packages?" type things, was to do with restarting services.
>
>
>
> On 03/09/2012 11:48 AM, Colin Watson wrote:
>> You should run 'sudo dpkg-reconfigure grub-pc' and instruct it to
>> install the boot loader somewhere, probably /dev/vda.
>>
>> The debconf database shows that the following question was presented to
>> you at some point:
>>
>> You chose not to install GRUB to any devices. If you continue, the
>> boot loader may not be properly configured, and when this computer next
>> starts up it will use whatever was previously in the boot sector. If
>> there is an earlier version of GRUB 2 in the boot sector, it may be
>> unable to load modules or handle the current configuration file.
>>
>> If you are already using a different boot loader and want to carry on
>> doing so, or if this is a special environment where you do not need a
>> boot loader, then you should continue anyway. Otherwise, you should
>> install GRUB somewhere.
>>
>> Continue without installing GRUB?
>>
>> Do you remember seeing this question? It was intended to strongly
>> discourage setups like this ...
>>
>
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/949992
Title:
Upgrade from Lucid to Precise results in broken grub configuration
Status in “update-manager” package in Ubuntu:
New
Bug description:
Performed update-manager -d upgrade from lucid VM to precise. On
completion, rebooted, and rather than Precise, I'm confronted with a
grub>
prompt.
Attempted recovery by setting root and loading config, but get
"unknown command hwmatch" when it tries to load the grub.cfg.
Manually loading vmlinuz and initrd after setting root only gets me as
far as a busybox prompt.
Obviously I can't get to the point where I can run ubuntu-bug in that
VM, so my ability to get logs is currently limited.
I'm still attempting recovery of the VM, as it's blocking further Ubuntu One upgrade testing that I'm engaged in. I'll add further information if/as I find it.
---
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 12.04
GsettingsChanges:
com.ubuntu.update-manager first-run false
com.ubuntu.update-manager launch-time 1331071487
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
Package: update-manager 1:0.156.7
PackageArchitecture: all
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Tags: precise dist-upgrade
Uname: Linux 3.2.0-18-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-03-07 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/949992/+subscriptions
More information about the foundations-bugs
mailing list