On Tue, 2009-05-12 at 09:47 -0600, Shad L. Lords wrote:
> Chris Boyd wrote:
> > So I have an issue with CentOS 5.3 i386, LVM, and SATA.
> >
> > Boot device is a 200GB ATA disk on hda2.
> >
> > I've added a couple of disks with the on-the-mobo SATA controller ports
> > and grown the EXT3 fs with system-config-lvm.
> >
> > Then, as an experiment, I added a PCI SATA controller and an additional
> > disk. Ran system-config-lvm, added the new space to the existing
> > VolGroup00, and all was good.
> >
> > Feeling confident, I shut the box down and plugged another disk in to
> > the PCI SATA controller. On reboot, I was greeted with a kernel panic
> > since the OS could not find "really-long-label." Removing the new SATA
> > disk did not fix the issue.
>
> My guess would be that the driver for the new PCI card isn't part of the
> initrd. If you don't have any data on the drive yet you could always
> reduce the vg so that it is no longer included. You could also recreate
> your initrd to include the driver for the pci card.
Alternately, since the BIOS re-assigned the drive letters, the mkinitrd
still contains ignore-lock-failure for only the originally installed
disk. I've successfully handled this (in test and live) by extracting
the mkinitrd (cpio format, IIRC), changing the init to ignore lock
failures on the new disk and making a new initrd. Then it worked.
However, this was for a fall-back for if the first drive got trashed,
the back-up disk had an LV with a slightly modified name and would be
seen as the new sda.
For the OP's situation, might need to search a little further to get to
the same results. But I think it's surely something in the initrd, even
if the driver is the same.
>
> -Shad
> <snip sig stuff>
--
Bill
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
