Can't boot Lucid after upgrade from Karmic

[Goh Lip]

On 05/28/2010 01:35 AM, Tony Pursell wrote:
> On 28 May 2010 at 1:28, Goh Lip wrote:
>
>>
>> On 05/28/2010 12:56 AM, Tony Pursell wrote:
>>> On 28 May 2010 at 0:43, Goh Lip wrote:
>>>>
>>>> On 05/27/2010 11:49 PM, Tony Pursell wrote:
>>>>
>>>>>
>>>>> I tried the grub commands, but they failed. Are the GRUB2
>>>>> commands?  I have the old Grub which doesn't show a 'search'
>>>>> command in its list of available commands.
>>>>
>>>> Oh, you're right. It's grub-legacy then and the 'find' function is not
>>>> so refined, just finding the 'stage1' for booting. I now assume the
>>>> following and change if necessary..
>>>>
>>>> o you have the (lucid) 2.6.32-21-generic installed.
>>>> o you have a separate /boot partition and you know what it is (hd0,x)
>>>>      -note and reminder that (hd0,x) is sda(x+1)
>>>>      -reminder I am talking about /boot, not '/'
>>>
>>> /boot is not a separate partition.  It is just a directory in root.
>>>
>>>>
>>>>
>>>> At grub (legacy) prompt, please type
>>>> root   (hd0,x)
>>>> kernel /vmlinuz-2.6.32-21-generic root=/dev/sda(x+1) ro single
>>>> initrd /initrd.img-2.6.32-21-generic
>>>> boot
>>>>
>>>> As an example, if your /boot is sda8, type the following....
>>>> root   (hd0,7)
>>>> kernel /vmlinuz-2.6.32-21-generic root=/dev/sda8 ro single
>>>> initrd /initrd.img-2.6.32-21-generic
>>>> boot
>>>>
>>>
>>> Do I do these after booting to a CLI using the Karmic Kernel?
>>>
>>>
>>>>
>>>> (I have to continue this as we need to do this if successful..)
>>>> If sucessfully booted up, you will go to the recovery mode at *lucid*
>>>> choose root shell with networking
>>>> then type....
>>>> apt-get install --reinstall ubuntu-desktop   {if kubuntu, use kubuntu}
>>>> apt-get -f install
>>>> dpkg --configure -a
>>>> apt-get update
>>>> apt-get upgrade
>>>> reboot
>>>>
>>
>>
>>>>
>>
>>>> Do you think it's okay to install the linux
>>>> kernel/image2.6.32-22-generic at this point? And install the grub-pc later?
>>>>
>>>
>>> This is on of the 3 Lucid kernels I have installed.
>>>
>>
>> Good info here, Tony.
>>
>> *If* it is successful and at the recovery mode of any of the lucid
>> kernels, say 2.6.32-21 or 2.6.32-22, the commands do not give unusual or
>> error feedback.
>>
>> Then reboot again but without the 'single' , as an example...
>>
>> root   (hd0,7)
>> kernel /vmlinuz-2.6.32-21-generic root=/dev/sda8 ro
>> initrd /initrd.img-2.6.32-21-generic
>> boot
>>
>>
>> note: the kernel line, remove the 'single' (you can try
>> vmlinuz-2.6.32-22) - should work then.
>>
>> Then you should be able to boot to the lucid properly using (manual)
>> grub-legacy commands. Since lucid uses grub2 instead, you should install
>> grub2 by "sudo apt-get install grub-pc" , (there have been some changes
>> and if this command doesn't work, use "sudo apt-get install grub2")
>>
>> Proceed to full installation of grub2 by following the instructions
>> carefully, there is a need to issue a command, (memory a bit rusty..I
>> think it's convert to something...besides chainload from legacy). Please
>> make sure you do the "convert something" command.
>>
>> Then we're home.
>>
>
> Thanks for all your help, Goh Lip, but none of it worked.  There would
> seem to be something much more fundamental at work here.  I think I
> will have to re-install and maybe use Grub2.
>
> Tony
>
>
>
Wait,wait, not so fast.  you mentioned, and I missed that, /boot is a 
directory in '/'.
(thought you had all in separate partitions per your much much earlier 
message)

use then the following

root   (hd0,x)
kernel /boot/vmlinuz-2.6.32-21-generic root=/dev/sda(x+1) ro single
initrd /boot/initrd.img-2.6.32-21-generic
boot


where (hd0,x) is the '/' partition instead, okay?

reminder (hd0,x) is sda(x+1)

Tony, please let us know what that '/' partition is in
sday and (hd0,x) so we don't make assumptions.
Also hope you did not have '/' in ext4, right?

Regards - Goh Lip


-- 
Life is a sexually transmitted disease with a 100% mortality rate