Accessing a StorageTek 2530 Disk array from SUN, SPARC Enterprise T2000

UNIX Solaris
1

Hello,
Wondering if anyone can help me with mounting a file share from my Sun T2000 server running Solaris 10 to my connected 2530 disk array?
I believe I've connected the disk array correctly and I have created a volume on the array using the filesystem (Sun_SAM-FS, RAID-5).
The T2000 server appears to see the disk array but not able to write a disk label or mount a filesystem on it as the following commands show:-
root@sesame # format
Searching for disks...done

c4t0d0: configured with capacity of 1395.79GB

AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@0,0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@780/pci@0/pci@9/scsi@0/sd@1,0
2. c4t0d0 <SUN-LCSM100_S-0735-1.36TB>
/pci@7c0/pci@0/pci@9/LSILogic,sas@0/sd@0,0
Specify disk (enter its number): 2
selecting c4t0d0
[disk unformatted]
Disk not labeled. Label it now? y
Warning: error writing EFI.
Write label failed

partition> print
Current partition table (original):
Total disk sectors available: 2927157214 + 16384 (reserved sectors)

Part Tag Flag First Sector Size Last Sector
0 root wm 34 128.00MB 262177
1 swap wu 262178 128.00MB 524321
2 unassigned wu 0 0 0
3 unassigned wm 0 0 0
4 unassigned wm 0 0 0
5 unassigned wm 0 0 0
6 usr wm 524322 1.36TB 2927157213
8 reserved wm 2927157214 8.00MB 2927173597

partition>
root@sesame # mount /dev/dsk/c4t0d0s6 /array01
mount: I/O error
mount: Cannot mount /dev/dsk/c4t0d0s6
root@sesame #

To be honest I've never attached an array to a Unix server before so any pointers would be appreciated.
Thanks, DD :slight_smile:

2

why a SAM-FS? how do you configure the array (which software)?

3

Yeah I'm just using the Sun StorageTek Comman Array Manager Software

I was just trying some of the pre-defined file system types, here is the list to choose from.

TABLE 12   Predefined Storage Profiles for the Sun StorageTek  Arrays

Name                    RAID Level      Segment Size    Read-Ahead Mode         Drive Type      Number of Drives 
Default 	        RAID-5               512 KB               Enabled               ANY               Variable 
High_Capacity_Computing RAID-5               512 KB               Enabled               SATA               Variable 
High_Performance_Computing RAID-5            512 KB               Enabled               SAS               Variable 
Mail_Spooling           RAID-1               512 KB               Enabled               SAS               Variable 
Microsoft_Exchange      RAID-5               32 KB               Enabled               SAS               4 
Microsoft_NTFS          RAID-5               64 KB               Enabled               ANY               4 
Microsoft_NTFS_HA       RAID-1               64 KB               Enabled               2500: SAS        Variable 
NFS_Mirroring           RAID-1               512 KB               Enabled               SAS               Variable 
NFS_Striping            RAID-5               512 KB               Enabled               SAS               Variable 
Oracle__10_ASM_VxFS_HA  RAID-5               256 KB               Enabled               SAS               5 
Oracle__8_VxFS          RAID-5               128 KB               Enabled               SAS               4 
Oracle__9_VxFS_HA       RAID-5               128 KB               Enabled               SAS               Variable 
Oracle_DSS              RAID-5               512 KB               Enabled               SAS               Variable 
Oracle_OLTP             RAID-5               512 KB               Enabled               SAS               Variable 
Oracle_OLTP_HA          RAID-1               512 KB               Enabled               SAS               Variable 
Random_1                RAID-1               512 KB               Enabled               SAS               Variable 
Sequential              RAID-5               512 KB               Enabled               SAS               Variable 
Sun_SAM-FS              RAID-5               128 KB               Enabled               ANY               4 
Sun_ZFS                 RAID-5               128 KB               Enabled               ANY               4 
Sybase_DSS              RAID-5               512 KB               Enabled               SAS               Variable 
Sybase_OLTP             RAID-5               512 KB               Enabled               SAS               Variable 
Sybase_OLTP HA          RAID-1               512 KB               Enabled               SAS               Variable 
VxFS                    RAID-5               128 KB               Enabled               ANY               4

I did format the array with Sun ZFS filesystem to start with but had no luck then.

So thought I'd try Sun_SAM-FS to see if that was any more compatible but no luck so far.

Was wanting a small block size as I want to put a lot of small files onto the disk array when I start using it.

The only documentation I've fun on how to configure the array has been :-
http://dlc.sun.com/pdf/820-2431-10/820-2431-10.pdf

And that says nothing about selecting the type of filesystem which would be most compatible with a SPARC Solaris 10 machine and how to go about actually mounting the file system to prepare it for use.

Cheers, Malcolm.

4

just stay with the default... unless you want to build a zpool from your luns or use samfs on your luns.

5

Will try formattting with the default option once I get past a new password problem:-
"The operation to unmap or delete volume ses_array_vol_01 failed. The operation cannot be completed because you did not provide a valid password. Open the Storage System's folder in the left hand navigational tree, click on the Administration folder, then click on Manage passwords and provide a valid Storage System password."

I have no idea what the valid storage system password would be, I never set one.

Nevermind it's nearly the weekend.

DD :slight_smile:

Update -
After a few minutes, I went to the Administration (Manage Passwords...) again, and I filled ONLY the fields (New Password, and Verify New Password), leaving the OLD password field (which is REQUIRED), blank. And I got a Success !!! blue i , great.

Reformatting array with default filesystem now... will try mounting the array again on Monday morning.

6

Re-created the disk array volume with the Default file system option and then tried again to mount the file system without success.

Anyone any suggestions where I'm going wrong?

Thanks, DD.

Actions shown below :-

root@sesame # reboot -- -r


root@sesame # /usr/sbin/devfsadm
root@sesame #
root@sesame # format
Searching for disks...done

c4t0d0: configured with capacity of 1395.79GB


AVAILABLE DISK SELECTIONS:
       0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@780/pci@0/pci@9/scsi@0/sd@0,0
       1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@780/pci@0/pci@9/scsi@0/sd@1,0
       2. c4t0d0 <SUN-LCSM100_S-0735-1.36TB>
          /pci@7c0/pci@0/pci@9/LSILogic,sas@0/sd@0,0
Specify disk (enter its number): 2
selecting c4t0d0
[disk unformatted]
Disk not labeled.  Label it now? y
Warning: error writing EFI.
Write label failed


FORMAT MENU:
        disk       - select a disk
        type       - select (define) a disk type
        partition  - select (define) a partition table
        current    - describe the current disk
        format     - format and analyze the disk
        repair     - repair a defective sector
        label      - write label to the disk
        analyze    - surface analysis
        defect     - defect list management
        backup     - search for backup labels
        verify     - read and display labels
        inquiry    - show vendor, product and revision
        volname    - set 8-character volume name
        !<cmd>     - execute <cmd>, then return
        quit
format> partition


PARTITION MENU:
        0      - change `0' partition
        1      - change `1' partition
        2      - change `2' partition
        3      - change `3' partition
        4      - change `4' partition
        5      - change `5' partition
        6      - change `6' partition
        select - select a predefined table
        modify - modify a predefined partition table
        name   - name the current table
        print  - display the current table
        label  - write partition map and label to the disk
        !<cmd> - execute <cmd>, then return
        quit
partition> print
Current partition table (original):
Total disk sectors available: 2927157214 + 16384 (reserved sectors)

Part      Tag    Flag     First Sector          Size          Last Sector
  0       root    wm                34       128.00MB           262177
  1       swap    wu            262178       128.00MB           524321
  2 unassigned    wu                 0            0                0
  3 unassigned    wm                 0            0                0
  4 unassigned    wm                 0            0                0
  5 unassigned    wm                 0            0                0
  6        usr    wm            524322         1.36TB           2927157213
  8   reserved    wm        2927157214         8.00MB           2927173597

partition> quit
format> quit

root@sesame # cd /
root@sesame # mount /dev/dsk/c4t0d0s6 /array01
mount: I/O error
mount: Cannot mount /dev/dsk/c4t0d0s6
7

are you on the latest firmware for the array? i remember there were issues... also try a SMI label instead of the EFI label. just call "format -e" and choose SMI. also you've to build a FS before you can mount the new volume! read "man newfs" or "man zpool" if you are going to use ZFS.

8

If you are going to use a zpool, it is better to create individual disk sized LUNs. Even without being able to enable the individual disk caches ZFS works/performs *much* better when it sees a bunch of disks rather than one big one.

Also if you want to use UFS you will have to keep an EFI label. The LUN size is too big for an SMI label. The big problem right now is that there is no filesystem on disk.

9

yes, you are right. the max size for UFS with SMI label is just under 1 TB. i think it was something like 970 GB...

10

I'm confused, I thought the array was formatting itself and that's why it took 4 hours to initialize?
I tired the other suggestions but didn't get to far.
Cheers DD.

  root@sesame #
  root@sesame # newfs /dev/rdsk/c4t0d0s6
  /dev/rdsk/c4t0d0s6: I/O error
  root@sesame # newfs /dev/dsk/c4t0d0s6
  /dev/rdsk/c4t0d0s6: I/O error
  root@sesame # format -e
  Searching for disks...done
   
  c4t0d0: configured with capacity of 1395.79GB
   
   
  AVAILABLE DISK SELECTIONS:
         0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
            /pci@780/pci@0/pci@9/scsi@0/sd@0,0
         1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
            /pci@780/pci@0/pci@9/scsi@0/sd@1,0
         2. c4t0d0 <SUN-LCSM100_S-0735-1.36TB>
            /pci@7c0/pci@0/pci@9/LSILogic,sas@0/sd@0,0
  Specify disk (enter its number): 2
  selecting c4t0d0
  [disk unformatted]
  Disk not labeled.  Label it now? y
  Warning: error writing EFI.
  Write label failed
11

just for testing try to create a zpool out of the lun...

# zpool create mypool c4t0d0

if the command runs without errors, look for /mypool has been created and is writeable...

12

I'll second that recommendation.

But if that doesn't work, run this (sh/bash) command and post the results:

for port in `fcinfo hba-port | grep "Port WWN" | awk '{ print $4 }'`; do fcinfo remote-port -ls -p $port; done

That should show something like this:

-bash-3.2# for port in `fcinfo hba-port | grep "Port WWN" | awk '{ print $4 }'`; do fcinfo remote-port -ls -p $port; done
Remote Port WWN: 200600a0b8166aee
    Active FC4 Types: 
    SCSI Target: yes
    Port Symbolic Name: 
    Node WWN: 200600a0b8166aec
    Link Error Statistics:
        Link Failure Count: 0
        Loss of Sync Count: 0
        Loss of Signal Count: 1
        Primitive Seq Protocol Error Count: 0
        Invalid Tx Word Count: 0
        Invalid CRC Count: 0
    LUN: 0
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007349FD1521d0s2
    LUN: 1
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A049FD1836d0s2
    LUN: 2
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009649FC6F02d0s2
    LUN: 3
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006D49FC6C85d0s2
    LUN: 4
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009C49FC70B2d0s2
    LUN: 5
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006F49FC6D71d0s2
    LUN: 6
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009E49FC75DCd0s2
    LUN: 7
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007649FD158Dd0s2
    LUN: 8
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A249FD18AEd0s2
    LUN: 31
      Vendor: IBM     
      Product: Universal Xport 
      OS Device Name: /dev/rdsk/c5t2d31s2
Remote Port WWN: 200700a0b8166aee
    Active FC4 Types: 
    SCSI Target: yes
    Port Symbolic Name: 
    Node WWN: 200600a0b8166aec
    Link Error Statistics:
        Link Failure Count: 0
        Loss of Sync Count: 0
        Loss of Signal Count: 1
        Primitive Seq Protocol Error Count: 0
        Invalid Tx Word Count: 0
        Invalid CRC Count: 0
    LUN: 0
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007349FD1521d0s2
    LUN: 1
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A049FD1836d0s2
    LUN: 2
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009649FC6F02d0s2
    LUN: 3
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006D49FC6C85d0s2
    LUN: 4
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009C49FC70B2d0s2
    LUN: 5
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006F49FC6D71d0s2
    LUN: 6
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009E49FC75DCd0s2
    LUN: 7
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007649FD158Dd0s2
    LUN: 8
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A249FD18AEd0s2
    LUN: 31
      Vendor: IBM     
      Product: Universal Xport 
      OS Device Name: /dev/rdsk/c5t3d31s2
Remote Port WWN: 200600a0b8166aed
    Active FC4 Types: 
    SCSI Target: yes
    Port Symbolic Name: 
    Node WWN: 200600a0b8166aec
    Link Error Statistics:
        Link Failure Count: 0
        Loss of Sync Count: 0
        Loss of Signal Count: 1
        Primitive Seq Protocol Error Count: 0
        Invalid Tx Word Count: 0
        Invalid CRC Count: 0
    LUN: 0
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007349FD1521d0s2
    LUN: 1
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A049FD1836d0s2
    LUN: 2
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009649FC6F02d0s2
    LUN: 3
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006D49FC6C85d0s2
    LUN: 4
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009C49FC70B2d0s2
    LUN: 5
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006F49FC6D71d0s2
    LUN: 6
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009E49FC75DCd0s2
    LUN: 7
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007649FD158Dd0s2
    LUN: 8
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A249FD18AEd0s2
    LUN: 31
      Vendor: IBM     
      Product: Universal Xport 
      OS Device Name: /dev/rdsk/c1t0d31s2
Remote Port WWN: 200700a0b8166aed
    Active FC4 Types: 
    SCSI Target: yes
    Port Symbolic Name: 
    Node WWN: 200600a0b8166aec
    Link Error Statistics:
        Link Failure Count: 0
        Loss of Sync Count: 0
        Loss of Signal Count: 1
        Primitive Seq Protocol Error Count: 0
        Invalid Tx Word Count: 0
        Invalid CRC Count: 0
    LUN: 0
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007349FD1521d0s2
    LUN: 1
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A049FD1836d0s2
    LUN: 2
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009649FC6F02d0s2
    LUN: 3
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006D49FC6C85d0s2
    LUN: 4
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009C49FC70B2d0s2
    LUN: 5
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000006F49FC6D71d0s2
    LUN: 6
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D0000009E49FC75DCd0s2
    LUN: 7
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166AEC0000007649FD158Dd0s2
    LUN: 8
      Vendor: IBM     
      Product: 1742-900        
      OS Device Name: /dev/rdsk/c0t600A0B8000166B0D000000A249FD18AEd0s2
    LUN: 31
      Vendor: IBM     
      Product: Universal Xport 
      OS Device Name: /dev/rdsk/c1t1d31s2
13

achenle, That would strike me as an odd thing to do ( running FC commands to find details of a SAS array ).

DD - Have a look at the 'dmesg' output and also run another 'devfadm -C', I have on occasion seen seemingly spontaneous HBA controller device number remaps happing with similar hardware.

14

Here is the output people suggested I should look at.

Looked at it and still scratching my head a bit.

Any thoughts?

DD :o

root@sesame # zpool create mypool c4t0d0
cannot label 'c4t0d0': failed to write EFI label
use fdisk(1M) to partition the disk, and provide a specific slice
root@sesame #

root@sesame # for port in `fcinfo hba-port | grep "Port WWN" | awk '{ print $4 }'`; do fcinfo remote-port -ls -p $port; done
Remote Port WWN: 500110a0008b731a
        Active FC4 Types:
        SCSI Target: yes
        Node WWN: 500110a0008b7319
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 5100
                Loss of Signal Count: 26
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
        LUN: 0
          Vendor: HP
          Product: Ultrium 4-SCSI
          OS Device Name: /dev/rmt/0n
        LUN: 1
          Vendor: HP
          Product: MSL G3 Series
          OS Device Name: /devices/pci@780/pci@0/pci@8/SUNW,emlxs@0/fp@0,0/sgen@w500110a0008b731a,1
root@sesame #

-- dmesg gave a lot of output but think this is the section we are interested in?
root@sesame # dmesg
Jun 22 12:39:11 sesame scsi: [ID 193665 kern.info] sd4 at mpt1: target 0 lun 0
Jun 22 12:39:11 sesame genunix: [ID 936769 kern.info] sd4 is /pci@7c0/pci@0/pci@9/LSILogic,sas@0/sd@0,0
15

if the above HBA is connected to the array, there are a lot of errors... so you might want to check the cables from the server to the array... and as reborg suggested, i don't know if the "fc" commands work for SAS devices...

16

Do you have a copy of the "lsiutil" utility? You can download it from LSI's web site.