Secure Path Installation Errors on RH 2.1

[SHANE CORBAN]

Hi
I'm attempting to install Secure Path 3.0c, on a redhat linux server running 2.4.9-e.38 kernel and after rebooting after installation, my file system becomes a read-only file system after it attempts to load the swsp modules..
It complains about not being able to open /proc/partitions even thought the proc filesystem has been mounted..the exact error is 'mount: could not open /proc/partitions, so UUID and LABEL conversion cannot be done'

Can someone please shed some light on this, or has anyone encountered this..

Thanks
Shane

[Michael Smith_17]

I am making the assumption that you are upgrading from securepath 3.0b, in which case, I know the problem. After the upgrade, the /etc/init.d/boot.d/S*swsp is not removed....,and another one is added...

Let me explain:

SecurePath 3.0b has the following

/etc/init.d/boot.d/S01boot.qla2x00
/etc/init.d/boot.d/S01boot.swsp
/etc/init.d/boot.d/S03boot.localfs (not from Secure Path)

When I upgraded to 3.0c...

I ended up with

/etc/init.d/boot.d/S01boot.qla2x00
/etc/init.d/boot.d/S01boot.swsp
/etc/init.d/boot.d/S03boot.localfs
/etc/init.d/boot.d/S03boot.qla2x00
/etc/init.d/boot.d/S03boot.swsp

the boot.swsp makes your file system read only in preparation for boot.localfs, however, because a second copy of boot.swsp was running AFTER boot.localfs, the second boot.swsp was making my root fs read only again...

The Simple solution is just remove the S03boot.swsp and S03boot.qla2x00, ie so that you only have one of each, with each of them occuring BEFORE boot.localfs

(This lovely screwup caused me a 4 hour downtime while I troubleshooted this)

Hope its the solution to your problem

Mike

[SHANE CORBAN]

Unfortunately not i think Mike, thanks for your help nonetheless. I was installing SP 4.0c on a clean redhat installation(no previous copies of SP were ever loaded on this host)..

It baffles me, I have one lun shared on an MSA bewteen two hosts(as part of a linux cluster setup), and am thinking this might have something got to do with it..

It works on one host and not on the other even though the two hosts are identical kernel, filesystem and hba driver wise..

Anyone else got any ideas
Thanks Again Mike
Shane