Gutsy Upgrade problem

[NoOp]

On 03/30/2008 02:32 PM, Rick Knight wrote:
> NoOp wrote:
>> On 03/30/2008 10:31 AM, Rick Knight wrote:
>>
>>   
>>> It looks to me like the Gutsy upgrade worked but something else is 
>>> broken. I found a bug report that matches my symptoms on launchpad 
>>> (https://bugs.launchpad.net/ubuntu/+bug/190588) and added my comments to 
>>> it, but there hasn't been any response to the original report in well 
>>> over a month. What else can I do to find a solution to this problem?
>>>     
>>
>> I'm wondering if perhaps you are having a similar problem to what my
>> friend in Sweden had - particularly since you had/have linux on sda as well.
>>
>> >From your previous:
>>   
>>> /dev/hda1: UUID="448C-C79B" TYPE="vfat" 
>>> /dev/hda2: LABEL="/boot" UUID="d6f73dcb-5ca0-4c1d-85e1-48e7146026b3" SEC_TYPE="ext2" TYPE="ext3" 
>>> /dev/hda5: LABEL="/" UUID="a13285d9-22aa-45f0-86c1-7612dd07c8a7" SEC_TYPE="ext2" TYPE="ext3" 
>>> /dev/hda6: TYPE="swap" UUID="8c1fbc9c-8304-4f24-b5bb-af1626035357" 
>>> /dev/hdb1: UUID="e3756958-033e-41a9-b193-b04e66efb452" SEC_TYPE="ext2" TYPE="ext3" 
>>> /dev/hdb5: UUID="cb18ce85-3710-4259-9abb-ce8a0ca67e13" SEC_TYPE="ext2" TYPE="ext3" 
>>> /dev/hdb6: TYPE="swap" UUID="7c1edba8-4077-4dae-9454-9336e87d614c" 
>>>     
>>
>>   
>>> Disk /dev/hda: 40.0 GB, 40020664320 bytes
>>> 255 heads, 63 sectors/track, 4865 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0x33a133a0
>>>
>>>    Device Boot      Start         End      Blocks   Id  System
>>> /dev/hda1   *           1        1215     9759456    c  W95 FAT32 (LBA)
>>> /dev/hda2            1216        1229      112455   83  Linux
>>> /dev/hda3            1230        4865    29206170    5  Extended
>>> /dev/hda5            1230        4802    28700059+  83  Linux
>>> /dev/hda6            4803        4865      506016   82  Linux swap / Solaris
>>>
>>> Disk /dev/hdb: 251.0 GB, 251000193024 bytes
>>> 255 heads, 63 sectors/track, 30515 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0x0002675a
>>>
>>>    Device Boot      Start         End      Blocks   Id  System
>>> /dev/hdb1               1          19      152586   83  Linux
>>> /dev/hdb2              20       30515   244959120    5  Extended
>>> /dev/hdb5              20       30266   242958996   83  Linux
>>> /dev/hdb6           30267       30515     2000061   82  Linux swap / Solaris
>>>     
>>
>>   
>>> title		Ubuntu 7.10, kernel 2.6.22-14-generic
>>> root		(hd1,4)
>>> kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=cb18ce85-3710-4259-9abb-ce8a0ca67e13 ro quiet splash
>>> initrd		/boot/initrd.img-2.6.22-14-generic
>>> quiet
>>>     
>>
>> Grub is saying that root is on hd1,4 (sdb5 or hdb5) - I wonder if
>> perhaps the upgrade caused grub to point to a previous root location hda2.
>>
>> Can you boot into feisty and then open gparted and see where your mount
>> points are, and boot flags on both drives?
>>
>> Also can you please:
>>
>> sudo grub
>> grub> find /boot/grub/stage1
>> grub> quit
>> Note the location that find /boot/grub/stage1 returns then quit.
>>
>>
>>
>>
>>   
> 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?