On Sat, 2006-09-02 at 12:08 -0500, Gerald Waugh wrote: > > > > ><snip> > 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 at redhat.com > 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! I've seen this before... while developing my fallback procedure. If my brain was younger... > 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) I don't use sata (yet) or raid or jbod but this sure sounds like the initrd problem I encountered. Boot into rescue mode and do a pvscan -- verbose. In *my* case, I had to make my fallback volume a different volume group. Trying to boot, it seems there is a hard-coded VolGroup00/LogVol00 in the init file in the initrd. It is on an ignorelockingfailure. I edited that file remade my initrd, did grub-install and all worked. Does you /etc/fstab show the full /VolGorup or /dev/mapper by any chance? Maybe it's not VolGroup00? Anyway, I don't know why yours would be different, but I hoped this might be a clue. > > > Gerald > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos