Gutsy Upgrade problem
Rick Knight
rick_knight at rlknight.com
Sat Mar 22 02:46:52 UTC 2008
NoOp wrote:
> On 03/19/2008 09:15 PM, Rick Knight wrote:
>
>
<snipped>
>
> Then do sudo update-grub.
>
> Please also just use a simple fstab, then build up once that works.
>
>
>>> You might try just a simple fstab first (save your old under a different
>>> name & ensure the UUID's are correct) to clear out the possibility of
>>> problems with the other device definitions:
>>>
>>> # /etc/fstab: static file system information.
>>> #
>>> # <file system> <mount point> <type> <options> <dump> <pass>
>>> proc /proc proc defaults 0 0
>>> # /dev/sdb5 (change sd* and UUID if necessary)
>>> UUID=cb18ce85-3710-4259-9abb-ce8a0ca67e13 / ext3
>>> defaults,errors=remount-ro 0 1
>>> # /dev/sdb6 (change sd* and UUID if necessary)
>>> UUID=8c1fbc9c-8304-4f24-b5bb-af1626035357 none swap sw
>>> 0 0
>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
>>> /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
>>> /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
>>>
>>> And boot. If you get the basics correct (main partition & swap) then you
>>> can add in your other drives/partions one by one.
>>>
>>> If the above screws up your feisty drive mounts, don't panic, just boot
>>> into recovery mode and change the fstab back to the old.
>>>
>>>
>>>
>>>
>> Why did Ubuntu/Kubuntu/Debian go to /dev/sd* drive designation? What
>> kernel modules are involved? Since /dev/sd is essentially SCSI Disk I
>> assume it's part of SCSI subsystem, but what makes it see IDE/EIDE/ATA
>> Hard drives? Maybe I'm missing some part of that.
>>
>
> 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.
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.
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.
rick at rick:/home/rick-bad$ sudo /sbin/vol_id -u /dev/sd*
/dev/sd*: error opening volume
Thanks again,
Rick
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: blkid.lst
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20080321/3c87664e/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fdisk.lst
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20080321/3c87664e/attachment-0001.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: menu.lst
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20080321/3c87664e/attachment-0002.ksh>
More information about the ubuntu-users
mailing list