11-12-2008
Install Solaris 10 with an internal StorageTek SAS HBA Raid card
Hi all
i would like to ask some suggests about my next job!
I have to install a new Sun Netra T5220, with an additional internal StorageTek SAS HBA Raid.
The problem come in if every disk is now controlled by the HBA, how can I install the OS?
No disk is being detected by the OS.
SAS card detected with no issue.
Is network install the only way out?
Thanks in advance.
Regards
8 More Discussions You Might Find Interesting
1. Solaris
I need to install a raid HBA internal card on a T5240. The reason is I have
more drives and the current mother board controller does not support more
than 4 drives.
My question is I have raidctl set up on current drives. If I install new HBA
card do I have to delete current raidctl and... (3 Replies)
Discussion started by: photon
3 Replies
2. UNIX for Advanced & Expert Users
I have a V490 that has couple internal disks attached to the same dual-port HBA card that I'm planning attach to the SAN for additional storage.
Would I sacrifice performance if I use the same HBA?
Is it better to throw in a new HBA instead? (1 Reply)
Discussion started by: kiem
1 Replies
3. Solaris
i was given a task which needs to perform a raid 1 on the boot disk, and 4 other disks on raid 10.
Is there any other alternative in installing solaris 10 other than through network installation?will be using solaris update 6.
while reading through the user guide i got pretty confuse.
... (1 Reply)
Discussion started by: monstar1407
1 Replies
4. Solaris
Dear Friends,
I need to configure T5240 with Internal SAS RAID HBA(SG-XPCIESAS-R-INT-Z).. T5240 uses 8 hard disks... From the documents of RAID card I have found that I need to create a jump start server to include three packages SUNWaac, StorMan, SUNWgccruntime if Im using solaris10 5/08...
... (5 Replies)
Discussion started by: nicktrix
5 Replies
5. Solaris
Hi all
I had update a server from Solaris 8 to Solaris 10
is it the HBA driver still need to reinstall?
since i can get the driver info as below:
root@sgerpdev # fcinfo hba-port
HBA Port WWN: 21000003ba9b58a3
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
... (1 Reply)
Discussion started by: SmartAntz
1 Replies
6. Solaris
Hi,
i have a two port hba card in solaris 10 system one of which is disabled. How to enable and configure the other port.
---------- Post updated at 08:17 AM ---------- Previous update was at 03:40 AM ----------
please help :( (7 Replies)
Discussion started by: rishiraaz
7 Replies
7. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
8. Solaris
Dear all,
I have a new Oracle Blade X4-2B server, running Solaris 10.
The server comes with a HBA card that will not be used now. It has not fibers connected to it. As a consequence, its leds never stop flashing.
My question is: how to disable this HBA card, without removing it physically... (2 Replies)
Discussion started by: Gus1971
2 Replies
LEARN ABOUT DEBIAN
smp_rep_phy_err_log
SMP_REP_PHY_ERR_LOG(8) SMP_UTILS SMP_REP_PHY_ERR_LOG(8)
NAME
smp_rep_phy_err_log - invoke REPORT PHY ERROR LOG SMP function
SYNOPSIS
smp_rep_phy_err_log [--help] [--hex] [--interface=PARAMS] [--phy=ID] [--raw] [--sa=SAS_ADDR] [--verbose] [--version] [--zero]
SMP_DEVICE[,N]
DESCRIPTION
Sends a SAS Management Protocol (SMP) REPORT PHY ERROR LOG function request to a SMP target. The SMP target is identified by the SMP_DEVICE
and the SAS_ADDR. Depending on the interface, the SAS_ADDR may be deduced from the SMP_DEVICE. The mpt interface uses SMP_DEVICE to iden-
tify a HBA (an SMP initiator) and needs the additional ,N to differentiate between HBAs if there are multiple present.
OPTIONS
Mandatory arguments to long options are mandatory for short options as well.
-h, --help
output the usage message then exit.
-H, --hex
output the response (less the CRC field) in hexadecimal.
-I, --interface=PARAMS
interface specific parameters. In this case "interface" refers to the path through the operating system to the SMP initiator. See
the smp_utils man page for more information.
-p, --phy=ID
phy identifier. ID is a value between 0 and 254. Default is 0.
-r, --raw
send the response (less the CRC field) to stdout in binary. All error messages are sent to stderr.
-s, --sa=SAS_ADDR
specifies the SAS address of the SMP target device. Typically this is an expander. This option may not be needed if the SMP_DEVICE
has the target's SAS address within it. The SAS_ADDR is in decimal but most SAS addresses are shown in hexadecimal. To give a number
in hexadecimal either prefix it with '0x' or put a trailing 'h' on it.
-v, --verbose
increase the verbosity of the output. Can be used multiple times
-V, --version
print the version string and then exit.
-z, --zero
zero the Allocated Response Length field in the request. This option also zeros the Request Length field in the request. This is
required for strict SAS-1.1 compliance. However this option should not be given in SAS-2 and later; if it is given an abridged
response may result.
NOTES
Similar information is maintained for SAS SSP target phys (e.g. on a SAS disk). It can be obtained from the Protocol Specific Port log page
with the sg_logs utility.
Similar information may be obtained for SAS initiator phys (e.g. on a SAS HBA). As an example in Linux 2.6.28 error information can be
found in this directory /sys/class/sas_phy/phy-4:0 (for the phy 0 in SCSI/SAS host 4).
Similar information may be obtained for SATA device phys (e.g. on a SATA disk). If there is a SAT layer between OS and the SATA device then
the sg_sat_phy_event utility can fetch the information.
CONFORMING TO
The SMP REPORT PHY ERROR LOG function was introduced in SAS-1 . The "Expander change count" field was added in SAS-2 .
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright (C) 2006-2011 Douglas Gilbert
This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
SEE ALSO
smp_utils, smp_phy_control(smp_utils), sg_logs(sg3_utils), sg_sat_phy_event(sg3_utils)
smp_utils-0.96 May 2011 SMP_REP_PHY_ERR_LOG(8)