Login or Register to Ask a Question and Join Our Community


Solaris

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

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Accessing a StorageTek 2530 Disk array from SUN, SPARC Enterprise T2000
# 8  
Old 06-22-2009
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  
Old 06-22-2009
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  
Old 06-22-2009
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.
Code:
  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  
Old 06-22-2009
just for testing try to create a zpool out of the lun...
Code:
# zpool create mypool c4t0d0

if the command runs without errors, look for /mypool has been created and is writeable...
# 12  
Old 06-22-2009
Quote:
Originally Posted by DukeNuke2
just for testing try to create a zpool out of the lun...
Code:
# zpool create mypool c4t0d0

if the command runs without errors, look for /mypool has been created and is writeable...
I'll second that recommendation.

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

Code:
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:

Code:
-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  
Old 06-22-2009
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  
Old 06-23-2009
Here is the output people suggested I should look at.

Looked at it and still scratching my head a bit.

Any thoughts?

DD Smilie
Code:
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
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Start /SYS on SUN SPARC does not start machine [SUN SPARC ENTERPRISE T-5240]

-> start /SYS Are you sure you want to start /SYS (y/n)? y Starting /SYS ]-> show HOST /HOST Targets: bootmode diag domain Properties: autorestart = reset autorunonerror = false bootfailrecovery = poweroff ... (29 Replies)
Discussion started by: z_haseeb
29 Replies

2. Filesystems, Disks and Memory

SAN questions about Sun StorageTek array

Hi, I have a question about Sun StorageTek Common Array Manager (CAM): What is the concept of 'host'? Is it the hostname of the server that has access to the managed array? If so, can I use its IP instead of its hostname? I've found a 'host' under CAM called XYZ (See below). In our... (7 Replies)
Discussion started by: aixlover
7 Replies

3. Filesystems, Disks and Memory

Backup Sun StorageTek Common Array Manager's configuration

In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10. Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies

4. Solaris

Sun StorageTek Common Array Manager 6.0 works very slowly

Hi! I have Sun StorageTek 2540 FC array and CAM works very slowly - I can wait for software response even more than 2 minutes... I run this software on Windows machine with Firefox Web Browser but speed is terrible... How can I make it works at least a little bit faster?.. (2 Replies)
Discussion started by: Sapfeer
2 Replies

5. Solaris

Sun Sparc T2000 + StorageTek 2540 - Help, I'm lost

I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it. I have one StorageTek 2540 array that I would like to connect to the T2000. For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies
Login or Register to Ask a Question