[ping - need added help/suggestions] Re: Gutsy Upgrade problem

[Rick Knight]

NoOp wrote:
> On 03/31/2008 04:57 PM, Rick Knight wrote:
>
>   
>>>> NoOp,  I've done a screenshot of gparted for both hda and hdb and they 
>>>> are attached here.
>>>>
>>>>
>>>> The output of "find /boot/grub/stage1" in grub is "hd1,4"
>>>>
>>>> Looking at gparted I can see that somewhere during one upgrade or 
>>>> another I've lost the mount point for /dev/hdb1, it's supposed to be my 
>>>> /boot partition. Somehow I have a boot directory on /dev/hda5. Maybe I 
>>>> need to do some cleanup and get my boot partition working.
>>>>     
>>>>         
>>> Perhaps you can try:
>>>
>>> sudo grub
>>> grub> root (hd1,4)
>>> grub> setup (hd0)
>>> grub> quit
>>> Reboot (to hard drive).
>>>
>>> That will setup grub on hd0 (your fat32) but point grub to use hd1,4
>>> (hda5) as the primary boot location. *However* before you do that it
>>> might be wise to let some others on the list provide their input in case
>>> I am wrong (been there, done that).
>>>
>>> Anyone else care to comment/help?
>>>
>>>
>>>
>>>   
>>>       
>> Thanks NoOp.
>>
>> Anyone else have any suggestions?
>>
>> Nils Kassube?
>>
>> Anyone?
>>
>>     
>
> +1
>
> Can anyone else please assist/comment?
>
>
>   
NoOp,

When I ran gparted and posted the results here, I saw that GRUB and my 
boot partition were not where they should have been (or where I thought 
they were). I decided last night to correct this and see if it would 
solve my Gutsy problem. I moved GRUB and everything in my /boot folder 
on /dev/hda5 to /dev/hda2, deleted the /boot folder on /dev/hda5 and 
then ran update-grub and then grub ...

sudo grub
grub> setup (hd0)
find /grub/stage1

(hd0,1)
grub> boot (hd0,1)

quit

I also modified /etc/fstab to reflect the change to the boot partition 
and to make sure only my /boot and / and swap partitions were listed. I 
used sudo blkid /dev/hda2 to get the ID for the new /boot partition and 
made sure all the UUIDs in fstab and menu.lst matched. I also changed 
menu.lst to recognize (hd0,1) as the boot device.

I rebooted, first into my Feisty kernel. It worked fine. I rebooted into 
the Gutsy kernel. Same errors as before. The drives are not being 
created under the 2.6.22-14-generic kernel. Under Feisty the drives are 
created as /dev/hdxn with UUIDs as symbolic links to /dev/hdxn.

I read this on the Ubuntu-devel-discuss mailling list...

"Starting from Gutsy, the old IDE chipset drivers are no longer included 
in the kernel package. The libata based drivers, being cleaner and 
easier to maintain, have taken the places of the old drivers.

However, external CD writers don't work with the new libata based IDE drivers. Please see bug report #109211 <https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/109211> for details. Considering that external CD/DVD writers are widely used hardware, I suggest keep the old IDE drivers until this bug is fixed, so that users can still use their external CD/DVD writers in Ubuntu after very little manual configuration. They should not conflict with anything if not loaded"

I realize the author is talking about external CD-ROM drives, but could 
this be what I'm running into? Would I be able to fix my issue by 
building a new kernel with support for the older IDE drivers? I have an 
older Soyo motherboard with a Via chipset. Maybe my chipset is not 
compatible with the newer SATA drivers.

(typing this from memory so I may not be totally accurate with the 
commands I  ran last night)

Thanks,
Rick