hts: Thanks for the suggestion, but the problem was fixed when the bad SAN Switch was replaced. The conclusion was the SAN Switch was not passing the PowerPath commands through in a timely manner for what ever reason. Therefore the /dev/emcpower* names did not get created early enough during boot for LVM to see the devices and activate the Volume Groups. Thanks: Jack Allen -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Shashank Sent: Wednesday, June 18, 2008 10:46 PM To: General Red Hat Linux discussion list Subject: Re: EMC Power Path for RH EL 5.2 > not being there at boot and the Volume Group not > being activated. After the system finished booting and you logged in and > looked they were there and you could activate the Volume Groups that > were on the SAN. We have very similar problems, however ours is an HP XP 12k SAN. I think with your newer kernel, EMC modules may not be loaded by default. Therefore, the need to vgchange -ay after rebooting. Does your /etc/modprobe.conf have all the required information about EMC powerpath (I am assuming there might be something similar to what we have for qlogic) plus the required kernel files (.ko) What you could try doing is creating a new initrd image. Make sure you backup your old initrd mv /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.img.back mkinitrd /boot/initrd-`uname -r`.img `uname -r` Then reboot the system with the new image in place. IF nothing, you can remove the newly created image and restore the old one. hth, -S >We had EMC support look into this and Red Hat and they > could not come up with a reason as to why. Then the customer told me > they have had to reboot this system and some others now and then because > all SAN connectivity would get stuck. They said they would have to reset > one of the SAN Switches before things would work again. We got them to > replace the SAN Switch and guess what, the EMC devices would show up as > they are suppose to at boot time. > > We have many customers on RH AS 4.X, but several want to know > when we are going to support RH EL 5.X, so that was the reason we got > the new systems and are going to compile our application on them and > support it. I know the binaries from RH AS 4.X will run on the RH EL > 5.X, but we would rather run things on the same OS version they are > compiled on. We did have to make some minor tweaks to the code, some > system #defines conflicted, some things are defined in different *.h > files. The Application is compiled on AIX, HP/UX and Linux with only a > minor number of #ifdef type things for each OS. > > Thanks: > Jack Allen > > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Troy > Sent: Wednesday, June 18, 2008 6:06 PM > To: General Red Hat Linux discussion list > Subject: Re: EMC Power Path for RH EL 5.2 > > We're still running rhel4 because of a problem we had with PowerPath > running on rhel5. You might want to looking into mount options > problems for EMC devices. > > I know we had a problem when we set the fsck mount option to 2. During > the boot process PowerPath wasn't enabled yet, so those EMC devices > would fail to mount, because they couldn't be checked. We were left > with either setting that option to 0, and forgoing the check > altogether, or staying with rhel4. We elected to stay at rhel4. > > > > > On Jun 18, 2008, at 2:38 PM, Allen, Jack wrote: > >> Hello: >> I have run into a little bit of a problem dealing with EMC >> Power >> Path. I know, your first thought is, so why are you asking this list >> about it and not EMC? I have asked EMC indirectly (see below) and did >> not really like their answer. >> >> I have some new systems that I installed RH EL 5.1 on with the >> assumption that EMC Power Path would be supported on it. And I think >> it >> was, is. I have Power Path install on some other systems running RH AS >> 4.6. Because the SAN is from EMC is the reason our SAN group wanted me >> to use Power Path. >> >> While waiting for our SAN group to allocate disk space and >> cable >> up the systems I have been keeping the system up to date via yum. >> Along >> the way the kernel version has changed and the over all system is >> now RH >> EL 5.2. So when the SAN group told me the SAN was all connected and I >> needed to install EMC Power Path is when it was identified there is a >> problem. It will not install. >> >> When rpm is run with the latest file from EMC I get an error >> stating the software is for RHEL5. That's correct, just RHEL5, no dot >> anything. I had our SAN group contact EMC and the response back from >> EMC >> was RH EL 5.2 will not be supported until the 4 QT of this year. >> >> So my first question is has anyone else run into this problem? >> >> If so what did you do? >> >> I know I can probably use the Multi Path software that comes >> with Linux, but I would like to keep all my systems configured as mush >> the same a possible. This just makes dealing with the SAN group a lot >> easier. >> >> Thanks: >> Jack Allen >> >> -- >> redhat-list mailing list >> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >> https://www.redhat.com/mailman/listinfo/redhat-list > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
