At Thu, 17 Dec 2009 09:51:06 -0600 CentOS mailing list <centos@xxxxxxxxxx> wrote: > > Jussi Hirvi wrote: > >> Jussi Hirvi wrote: > >>> On both my "old" (booting ok) and "new" (not booting) disc the > >>> modprobe.conf contained > >>>> alias scsi_hostadapter ata_piix > >>> So it seems to me modprobe.conf was up-to-date. > > On 17.12.2009 15:22, Les Mikesell wrote: > >> If the disks take the same driver it should boot or at least get to a point > >> where you get an error message with the reason. Are you sure it isn't a cable > >> or drive select problem? > > > > I don't think there can be a cable select problem with SATA drives. :-) > > > > Anyway, another drive booted ok when attached to the same SATA cable. > > > > I did not get an error message, in fact the bootup hang on a blank > > screen (I have not seen that before) some time before the CentOS splash > > screen (I don't remember more exactly anymore, and cannot check). > > The first boot stages should happen with the the machine bios loading > grub, then the kernel and initrd. It sounds like you aren't even getting > that far. The usual driver/controller mismatch results in the kernel > still being loaded by bios, doing it's device detection, then failing > because it can't mount the root partition. Is the disk you are trying to > boot part of a raid? And maybe the wrong half? Or simply not marked as a bootable disk? > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@xxxxxxxxxxxx -- http://www.deepsoft.com/ModelRailroadSystem/ _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos