The same problem happened with a server after I upgrade the kernel
to 2.6.9-42.0.2.
Another server, with similar configuration, boots normally on new
kernel.
Both uses software RAID and LVM2, (/boot on md0 and Logical Volume
on md1). Only differences between the servers is HD, on first have
two Seagate (ST380013AS Rev: 3.18) 80 GB, another have two
Western Digital (WDC WD2000JD-55H Rev: 08.0) 120 GB.
As it is a production server, I didn't make any test to investigate
the problem, just boot on previous kernel.
Heitor A. M. Cardozo
----- Original Message -----
From: "Gerald Waugh" <gwaugh@xxxxxxxxxxxxxxxxxxxxxxx>
To: "'CentOS mailing list'" <centos@xxxxxxxxxx>
Sent: Saturday, September 02, 2006 2:08 PM
Subject: RE: [CentOS] Kernel-2.6.9-42.0.2EL fails to boot after
upgradetoCentOS 4.4
> > >
> > Since I'm still happily running CentOS 4.3, I should probably keep my
> > thoughts
> > to myself, but that immediate kernel panic sure is a reminder of
> > attempting to boot
> > an i686 kernel with an i586 processor. I'd try to duplicate the
> > reported symptom
> > but my AMD K6-2 box has become an "organ transplant" donor
> > strictly because of kernel requirements.
> >
>
> It's a Tyan GS14 Celeron D 2.53GHz
> My console output reads (in-part)
>
> ata1: SATA max UDMA/133 cmd 0x30D0 ctl 0x30C6 bmdma 0x3090 irq 10
> ata2: SATA max UDMA/133 cmd 0x30C8 ctl 0x30C2 bmdma 0x3098 irq 10
> ata1: dev 0 ATA-7, max UDMA/133, 234441648 sectors: LBA48
> ata1: qc timeout (cmd 0xef)
> ata1: failed to set xfermode (err_mask=0x4)
> scsi0 : ata_piix
> ata2: SATA port has no device.
> scsi1 : ata_piix
> Loading dm-mod.ko module
> device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@xxxxxxxxxx
> Loading jbd.ko module
> Loading ext3.ko module
> Loading dm-mirror.ko module
> Loading dm-zero.ko module
> Loading dm-snapshot.ko module
> Making device-mapper control node
> Scanning logical volumes
> RKernel panic - not syncing: Attempted to kill init!
> eading all physi cal volumes. This may take a while...
> No volume groups found
> Activating logical volumes
> Volume group "VolGroup00" not found
> ERROR: /bin/lvm exited abnormally! (pid 318)
>
>
> Gerald
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
