New Kernel Hangs-up Booting

[Joseph Abrahams]

Okay, here's my grub.conf file.  Each entry looks the same (no hde
anywhere), but only "Red Hat Linux-up (2.4.20-8)" is bootable.  I don't
see where hde is coming from during the boot process.

#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/hda3
#          initrd /initrd-version.img
#boot=/dev/hda1
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-31.9)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-31.9 ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.20-31.9.img
title Red Hat Linux (2.4.20-31.9smp)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-31.9smp ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.20-31.9smp.img
title Red Hat Linux (2.4.20-8smp)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.20-8smp.img
title Red Hat Linux-up (2.4.20-8)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.20-8.img

Thanks again,
Joseph


>>> Mark Knecht <markknecht at gmail.com> 02/27/05 12:40 PM >>>
On Sun, 27 Feb 2005 12:25:30 -0600, Joseph Abrahams <abrahjm at auburn.edu>
wrote:
> I recently installed redhat 9.0.  After letting the automatic updater
> install kernel 2.4.20-31.9 on top of the existing 2.4.20-8, I've
> experienced problems booting.  Grub now has four entries (two for
> 2.4.20-8 and two for 2.4.20-31.9).  The old kernel still boots fine,
but
> if I boot from 2.4.20-31.9 it gets to "hde: attached ide-disk drive"
and
> won't go any farther.
> 
> My coputer is a pentium4 originally with windows XP on a SATA drive. 
I
> installed redhat on an new ultra ata/100 drive.  I noticed during
> installation that the installed couldn't see my SATA drive, but
> everything worked fine until inatalling the new kernel.
> 
> Thanks for help,
> Joseph

Joseph,
   This is most likely a case where the drive is changing names
depending on what's being booted. I've had this problem on a couple of
machines.

   First, RH9 is most probably not going to know a thing about SATA
drives. This is good since you'r enot apparently using it for this
installation, but even once you get RH9 up and running you will likely
not be able to mount the SATA drive even for data transfer.

   The key to figuring this out is to VERY carefull watch the boot
process. Very early in the process the part of the boot loader that
understands your system hardware will put up some messages about the
drives it is seeing. I expect that your EIDE drive is probably
/dev/hda with this kernel. Watch the process, soo if you can spot
that, and if you do then adjust your /etc/fstab file to point at
/dev/hda (or whatever you see) instead of /dev/hde.

   This problem can also be caused by a boot time option built into
the kernel that tells the system to boot offboard EIDE chipsets before
the system's chipset.

Normal:
EIDE channel 1 - chipset - /dev/hda & /dev/hdb
EIDE channel 2 - chipset - /dev/hdc & /dev/hdd
PCI EIDE Adapter - /dev/hde and higher

Offboard first
PCI Adapter - /dev/hda
EIDE channel 1 - /dev/hde & /dev/hdf
EIDE channel 2 - /dev/hdg & /dev/hdh

I've had systems where this turns around on my when I get a new
kernel, even using all EIDE.

   Hope this helps. Good luck and write back if you need more info.

Cheers,
Mark

_______________________________________________
Redhat-install-list mailing list
Redhat-install-list at redhat.com
https://www.redhat.com/mailman/listinfo/redhat-install-list
To Unsubscribe Go To ABOVE URL or send a message to:
redhat-install-list-request at redhat.com
Subject: unsubscribe