https://community.hpe.com/t5/disk-enclosures/compaq-storageworks/m-p/2763671#M5478 when i attach a storageworks raid array 7000 to either a K class or a N class .<BR />Running hp ux v 11.00 64 bit .<BR />if i do an ioscan -fnC disk i can see all of the disks <BR />however when i go into sam i can only see disks at lun 0 .<BR /> Mon, 15 Jul 2002 10:36:40 GMT Mr Alan WARD 2002-07-15T10:36:40Z https://community.hpe.com/t5/disk-enclosures/compaq-storageworks/m-p/2763671#M5478 when i attach a storageworks raid array 7000 to either a K class or a N class .<BR />Running hp ux v 11.00 64 bit .<BR />if i do an ioscan -fnC disk i can see all of the disks <BR />however when i go into sam i can only see disks at lun 0 .<BR /> Mon, 15 Jul 2002 10:36:40 GMT https://community.hpe.com/t5/disk-enclosures/compaq-storageworks/m-p/2763671#M5478 Mr Alan WARD 2002-07-15T10:36:40Z https://community.hpe.com/t5/disk-enclosures/compaq-storageworks/m-p/2763672#M5479 Alan,<BR /><BR />With the VA7x00 HP array, there is a software called Command View SDM. This is used to manage the array. Further, it provides an "ArmServer" for array interrogation which SAM counts on for array, path, and LUN identification. Since you have a Storage Works device, chances are that SAM doesn't know how to interpret the information (I'm not 100% positive). You might look at the file pd_devinfo.tx and see if there is a similar array in that file. If so, you may be able to manually edit the file so SAM recognizes it. However, please note that if you patch or upgrade, this file can be overwritten. If you add the Volume Groups, Logical Volumes, and file systems manually, SAM may then see all the LUNS okay and it is seeing the OS and mountpoints versus trying to interrogate the array.<BR /><BR />HTH,<BR /><BR />Dave Mon, 15 Jul 2002 14:14:36 GMT https://community.hpe.com/t5/disk-enclosures/compaq-storageworks/m-p/2763672#M5479 David Bell_1 2002-07-15T14:14:36Z