Gutsy Upgrade problem

[Rick Knight]

NoOp wrote:
> On 03/21/2008 07:46 PM, Rick Knight wrote:
>   
>> NoOp wrote:
>>     
>
> Boot back into feisty. Insert the alternate Gutsy cd and re-upgrade:
>
> https://help.ubuntu.com/community/GutsyUpgrades
>   http://www.ubuntu.com/getubuntu/upgrading
>
>   
I'm downloading it now.
>>> https://help.ubuntu.com/community/UsingUUID
>>>
>>> If all else fails, then I'd recommend that you boot back into the
>>> feisty kernel and do another upgrade using the alternate CD. You
>>> can try an online upgrade, but I find it easier to upgrade from the
>>> alternate CD (just put it in and it should prompt you) and then do
>>> the online updates afterwards.
>>>
>>> https://help.ubuntu.com/community/GutsyUpgrades 
>>> http://www.howtogeek.com/howto/linux/upgrade-ubuntu-from-feisty-to-gutsy/
>>>
>>>
>>>
>>>
>>>       
>> NoOp,
>>
>> I've done as you suggested and ran sudo update-grub. I've verified
>> the UUIDs using vol_id and blkid. I've also verified the swap UUID.
>> They are all correct. I did notice a message that I had missed
>> before. During the boot process for 2.6.22-14-generic, towards the
>> end I see this...
>>
>> ide_media (some number) main: Unable to read from
>> /proc/ide/ide0/hda/media.
>>     
>
> So use the simple limited fstab as I've been suggesting.
>
> I don't know how much clearer I can make this: you *cannot* use hd* with
> Gutsy. You *must* use sd* and UUID.
>
>
>   
>> Since this mentions hda it refers to my Windows drive that also has a
>>  previous Linux installation on it. Probably a symptom of whatever
>> else is wrong here.
>>     
>
> Then please do as requested and comment out all but the required boot
> and swap in the fstab and try a minimal fstab. Grub is trying to mount
> something that is not there. Clean your grub and fstab's to minimal and
> then add the additional partions/devices.
>
>   
I've done this. Nothing in my current fstab except my boot drive, swap 
and proc. No /dev/hd*, just UUIDs.

>> I am still unable to boot the 2.6.22-14-generic kernel.
>>
>>
>>
>> I'm attaching the output of sudo fdisk -l, blkid, vol_id -u /dev/sd
>> (and /dev/hd*) and menu.lst.
>>
>> This is the output of /sudo /sbin/vol_id -u /dev/sd*. As you can see,
>> I have no /dev/sd* devices.
>>     
>
> * meaning you replace the asterisk with your actual device:
>
> sd*
> sda1
> sda2
> etc.
>
> So:
> sudo /sbin/vol_id -u /dev/sda1
> sudo /sbin/vol_id -u /dev/sda5
> etc.
>
> There is no sd* - it was used as an example and meant for you to replace
> the asterisk with your actual device.
>
> And the fact that you have hd* and no sd* devices is the problem.
>
>   
I have no /dev/sdXN in my system. No /dev/sda1, no /dev/sdb5, no 
/dev/sdb6. When I change grub and fstab to use /dev/sdb5, I can boot. 
Grub won't even read the boot loader and I get grub errors. Whatever is 
responsible for creating the /dev/sd paths on my system isn't working 
and I don't know what it is. What creates these paths?

Anyway, I still can't boot into 2.6.22-14-generic. I'm downloading the 
alternate CD now.

Thanks again,
Rick