previous problem sort of resolved
Jim
lawrence.jim at gmail.com
Thu Dec 23 15:06:41 UTC 2004
On Thu, 23 Dec 2004 01:16:36 -0600, Jonathan Berry <berryja at gmail.com> wrote:
> On Wed, 22 Dec 2004 22:58:41 -0500, Jim <lawrence.jim at gmail.com> wrote:
> > results of cmds you asked for
> > ********************************************************************************
> [snip]
> > [root at My_World ~]# fdisk -l
> > Disk /dev/hda: 80.0 GB, 80026361856 bytes
> > 255 heads, 63 sectors/track, 9729 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> >
> > Device Boot Start End Blocks Id System
> > /dev/hda1 * 1 3824 30716248+ 7 HPFS/NTFS
> > /dev/hda2 3825 9729 47431912+ f W95 Ext'd (LBA)
> > /dev/hda5 3825 4085 2096451 7 HPFS/NTFS
> > /dev/hda6 4086 5105 8193118+ 7 HPFS/NTFS
> > /dev/hda7 5106 5118 102280+ 83 Linux
> > /dev/hda8 5118 5249 1048288+ 82 Linux swap
> > /dev/hda9 5249 9729 35991112+ 83 Linux
> [snip]
> > [root at My_World ~]# mount
> > /dev/hda9 on / type ext3 (rw)
> [snip]
> >
> > [root at My_World ~]# cat /etc/fstab
> > # This file is edited by fstab-sync - see 'man fstab-sync' for details
> > LABEL=/ / ext3 defaults 1 1
> > LABEL=/boot /boot ext3 defaults 1 2
> [snip]
> > /dev/hda8 swap swap defaults 0 0
> >
> [snip]
> > *************************************************************************************
>
> Wow, I think I was right. Something was causing your /boot/ partition
> to not be mounted. And it wasn't mounted when you did the update, so
> the new kernel was placed in the /boot/ folder.
>
> On Wed, 22 Dec 2004 23:14:38 -0500, Jim <lawrence.jim at gmail.com> wrote:
> > ok i removed my second hard drive and low and behold!!! i have a
> > grub folder!!!
> [snip]
> > [root at My_World ~]# mount
> > /dev/hda9 on / type ext3 (rw)
> > none on /proc type proc (rw)
> > none on /sys type sysfs (rw)
> > none on /dev/pts type devpts (rw,gid=5,mode=620)
> > usbfs on /proc/bus/usb type usbfs (rw)
> > /dev/hda7 on /boot type ext3 (rw)
> > none on /dev/shm type tmpfs (rw)
> > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
>
> Looks like maybe your second hard disk has a label that is "/boot" or
> something else causing it to not want to mount /boot. You can edit
> /etc/fstab and change the line:
> LABEL=/boot /boot ext3 defaults 1 2
> to
> /dev/hda7 /boot ext3 defaults 1 2
> and you should be able to put your second hard drive back. Now, you
> can reinstall the newer kenel with /boot mounted properly. Or you
> could perhaps do this (as root):
>
> umount /boot
> mkdir /tmp/boot/
> cp -a /boot/* /tmp/boot/
> rm -f /boot/*
> mount /boot
> cp -a /tmp/boot/* /boot/
> rm -fr /tmp/boot/
>
> Then edit you grub.conf, now that you have found it : ). Just copy
> the old kernel section and change all the numbers to match the new
> kernel. Be careful when doing the "rm" commands above. Be sure
> things copied and /boot is not mounted for the first one.
> This was certainly a strange one! Hope you get it all straightened out.
>
> Jonathan
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>
you lost me on this one....
i removed ther newest kernel hoping that up2date would see that it is
the old one and notify me that there is a new one (so far not so)
grub.conf only shows my XP & Core 3 kernel (kernel-2.6.9-1.667)
the only kernel installed is the kernel-2.6.9-1.667
I still have the problem of updates choosing Core 2
I don't want to install the second HD what is another option?
thanks
--
James Lawrence
NY
More information about the fedora-list
mailing list