No psuedo device names on boot - RHEL4

O.k. I've got a good one for you. I've check all previous forum posts and the KB and found nothing. Here is a growing problem I am seeing in my Linux enviroment:

On RHEL boxes (mostly 4.0) I am starting to see the following issues:

1. The PowerPath modules are not loaded at boot.
2. And/or the psuedo device names do not get assigned on boot (after they have been assigned and saved).

I have found this old code from older version of PP that was in the /etc/rc.d/rc.sysint file:

echo -n $" storage" <--Insert just after this line
###BEGINPP
# Configure and initialize PowerPath.
if [ -f /etc/init.d/PowerPath ]; then
/etc/init.d/PowerPath start
fi
###ENDPP

And that seems to allow PP to load at startup now. But now I don't get psuedo device names whenever PP loads up (see details below)

Has anyone else seen this problem? Here is an example of what I am talking about:

OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 5)
Kernel: 2.6.9-55.0.6.ELsmp #1 SMP Thu Aug 23 11:11:20 EDT 2007 i686 i686 i386 GNU/Linux
PPVersion: EMCpower.LINUX-4.5.3-003
NaviVersion: naviagentcli-6.24.1.5.0-1
HBABIOS: Latest QLA EMC support (1.08 I think)
HBAFirmware: Firmware version 4.00.23 [IP] ,
HBADRIVER: Driver version 8.01.04-d8

Has Oracle 10G RAC using ASM with RAW devices.

oracleasm-support-2.0.3-1
oracleasmlib-2.0.2-1
oracleasm-2.6.9-55.0.6.ELsmp-2.0.3-1
/sbin/insmod /lib/modules/2.6.9-42.0.10.ELsmp/kernel/drivers/char/hangcheck-timer.ko hangcheck_tick=30 hangcheck_margin=180 get's loaded out of /etc/rc.d/rc.local

Rawdevices does not start and the Pseudo names do not get assigned devices are not assigned.

Example:

CLARiiON ID=APM000XXXXXXX [XXXXXXX1]
Logical device ID=60060160A95C1C0012EE0D57C3F9DB11 [LUN-X]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
1 qla2xxx sdc SP A1 active alive 0 0
1 qla2xxx sdf SP B0 active alive 0 0
2 qla2xxx sdi SP A0 active alive 0 0
2 qla2xxx sdl SP B1 active alive 0 0


CLARiiON ID=APM000XXXXXXX [XXXXXXX1]
Logical device ID=60060160A95C1C0013EE0D57C3F9DB11 [LUN-Y]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
1 qla2xxx sdd SP A1 active alive 0 0
1 qla2xxx sdg SP B0 active alive 0 0
2 qla2xxx sdj SP A0 active alive 0 0
2 qla2xxx sdm SP B1 active alive 0 0

CLARiiON ID=APM000XXXXXXX [XXXXXXX1]
Logical device ID=60060160A95C1C007E6978F4ADEDDB11 [LUN-Z]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
1 qla2xxx sdb SP A1 active alive 0 0
1 qla2xxx sde SP B0 active alive 0 0
2 qla2xxx sdh SP A0 active alive 0 0
2 qla2xxx sdk SP B1 active alive 0 0

Is ANYONE running into this? I'm going to have to open a case with EMC but if anyone else is seeing this that is leverage to fix the problem

Thanks,
Shmac