Hi Eugene, Yes, I rebuilt the initrd.
After the original post, I dug a but more into the problem and found the lvms were mapped to /dev/dm-*, a complete no-no. I remember installing that server with the "install text multipath" option. Anyhow, since it is my test server, I decided to rebuild and map the lvms to /dev/mapper/* as per RH docs. Thanks, Win > ------------------------------ > > Message: 7 > Date: Thu, 24 Sep 2009 17:39:24 -0500 > From: Eugene Vilensky <[email protected]> > Subject: Re: [rhelv5-list] Kernel 2.6.18-164.el5 and Dynamic > Multipathing issue > To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii; format=flowed; > delsp=yes > > Hi, > > Has initrd been rebuilt with your HBA/san device drivers? > > Sent from mobile > > On Sep 24, 2009, at 1:13 PM, Win Htin <[email protected]> wrote: > >> HI folks, >> >> I recently updated my kernel on RHEL 5.2 from 2.6.18-128.2.1.el5 to >> 2.6.18-164.el5. When I tried booting up with the new kernel the boot >> up fails with the following error messages: >> >> -------------------------- < Start > >> ------------------------------------------------- >> Red Hat nash version 5.1.19.6 starting >> device-mapper: table: 253:0: multipath: unknown hardware handler type >> device-mapper: table: 253:0: multipath: unknown hardware handler type >> No devices found >> Reading all physical volumes. This may take a while... >> Found volume group "VolGroup00" using metadata type lvm2 >> 2 logical volume(s) in volume group "VolGroup00" now active >> Welcome to Red Hat Enterprise Linux Server >> ... >> ... >> ... >> Checking filesystems >> /dev/VolGroup00/LogLov00: clean >> fsck.ext3: no such file or directory while trying to open /dev/ >> mapper/mpath0p1 >> /dev/mapper/mpath0p1: >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 >> filesystem (and not swap or ufs or something else), then the >> superblock >> is corrupt, and you might try running e2fsck with an alternate >> superblock: >> e2fscl -b 8193 <device> >> [FAILED] >> **** An error occured during the file system check. >> **** Dropping you to a shell; the system will reboot >> **** when you leave the shell. >> Give root password for maintenance >> (or type Control-D to continue): >> >> ------------------------- < End > >> ------------------------------------------------------ >> >> Re-booting with the previous kernel has no issues. >> Is there something special I need to do for the DMP? >> >> TIA, >> Win _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
