3Par LUNs not seen after reboot?

[Speedwy]

I have a 3Par T800 and I have ran into problems with the 3Par LUN's "disappearing" when a server is rebooted. The server is a SUSE 10 Linux running in a Polyserve Cluster (Polyserve is an HP proprietary NAS clustering solution). After rebooting I have to manually issue a rescan of the scsi bus using the HP "hp_rescan -a" utility. If a do an "fdisk -l" after rebooting and before running the rescan I do not see any 3Par LUNs. This is a huge problem because the polyserve cluster won't form if it can't see all the LUNs it's supposed to see. I'm using the host persona "generic legacy". Has anyone seen this sort of behavior before?

[Richard Siemers]

We also use T800s, not very much linux though other than Netapp and 3 or 4 redhat boxes, Majority of our hosts are AIX, ESX and Windows. We've never had an issue where the host doesn't immediately see the LUNs after reboot. For linux we use generic legacy too.

Check out this link: Link to Qlogic article

[Speedwy]

Thanks Richard! What I don't understand is these same SUSE servers have both EVA and 3Par attached storage and the EVA storage is seen fine after a reboot, it's only the 3Par storage that isn't. Strange. Anyway I've got one of the nodes disabled from the cluster so that I can play around with it to see if I can figure out what the problem is. I'll post my results.

[Speedwy]

Quick update. I haven't been able to figure out yet why the SUSE servers aren't seeing the 3Par LUN upon reboot but I was able to band-aid it by putting in a startup script that did a rescan of the LUNs before the cluster forms. Interestingly when I tried to run this script at run-level 2 it didn't work, I had to execute the script at run level 3 for the rescan to pick up the 3Par LUN.