Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

migrating from internal raid controller to external HBA

895121Jul 26 2015 — edited Jul 29 2015

Hello,

To test a third party (SGI) jbod device connected it to an existing internal sun 375-3536  SAS controller, using an internal to external SAS cable.   Had to install the Solaris storage manager software in order for Solaris to see the drives in the jbod connected to the SAS raid controller.   Recently purchased a sun/oracle  75-3537-02 R50 Adaptec ASR-5085 External SAS HBA.   The idea is to migrate the disks out of Solaris storage manager and have Solaris access them directly using an external HBA, and cut out the middleware raid software and present the disks natively to solaris for zfs pools.   However, after removing the logical devices from six of the sixteen disks in the jbod, Solaris still does not see the six disks not configured with Storage manager.  Ten of the disks still have logical devices configured on them in Storage manager and can be seen as before.


A few notes.  Both controllers are currently installed in the system, and OBP see's them when using probe-scsi-all.   Also,  after installing the external HBA, disconnected the jbod from the internal raid controller, and connected it to the external HBA.   Solaris and Storage Manager picked the disks up after a couple of reboots and probe-scsi-all commands.  One of the probe-scsi commands output the configuration had changed, and asked if I wanted to accept the new configuration.   Once I did the disks in the jbod now attached to the external HBA were seen in Solaris, and its how the system is currently running.    Should I be able to use the adaptec external HBA to directly access the disks without using the Storage Manager app?  If so, is having the storage manager application installed causing a problem?   Does the external HBA (seen in Storage Manager) need to be unconfigured or removed from Storage manager?     Below is the output of the last probe-scsi-all command run before executing a boot -r.  Any help in getting the disks to be seen in solaris without using the storage manager raid software is appreciated.


Thanks,

{0} ok probe-scsi-all

/pci@0/pci@0/pci@8/pci@0/pci@a/SUNW,emlxs@0,1

Cannot Init Link.

/pci@0/pci@0/pci@8/pci@0/pci@a/SUNW,emlxs@0

Cannot Init Link.

/pci@0/pci@0/pci@8/pci@0/pci@8/scsi@0

Waiting for AAC Controller to start: . . Started

AAC Kernel Version: 15825

/pci@0/pci@0/pci@8/pci@0/pci@2/scsi@0

Waiting for AAC Controller to start: . . Started

AAC Kernel Version: 15825

Target 0 Volume 0

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 1 Volume 1

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 2 Volume 2

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 3 Volume 3

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 4 Volume 4

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 5 Volume 5

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 6 Volume 6

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 7 Volume 7

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900682241 Blocks, 1997 GB

Target 8 Volume 8

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 GB

Target 9 Volume 9

  Unit 0   Disk     Adaptec RAID ASR5805    V1.0    3900680193 Blocks, 1997 G

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 26 2015
Added on Jul 26 2015
6 comments
988 views