08-30-2011
It'd help to know what your system was.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I need explanations about physical disks and physical volumes. What is the difference between these 2 things?
In fact, i am trying to understand what the AIX lspv2command does.
Thank you in advance. (2 Replies)
Discussion started by: VeroL
2 Replies
2. Red Hat
Hi All,
How do I verify the sata/sas controller status on my redhat 2.6?
Thanks.
Itik (1 Reply)
Discussion started by: itik
1 Replies
3. UNIX for Advanced & Expert Users
Hi All:
I am using an adaptor between a 1TB SATA hard drive and solaris 8 box with 68 pin scsi. I use the format utility to partition the HD which works fine but when I use newfs, I get some errors. I will place them below.
I have blocked and the error message is in red.
Anybody got any... (1 Reply)
Discussion started by: mndavies
1 Replies
4. Filesystems, Disks and Memory
Hello,
I wanted to share an experience I had today which was quite a learning experience and perhaps useful for others who may run into the issue at some point in the future.
Basically, the scenario involves a OS which was installed on a machine which hardware-wise, had a SATA Drive. The... (0 Replies)
Discussion started by: septima.pars
0 Replies
5. SCO
Is SATA hard disk is suooprted by SCO OpenServer 5.05? If No, how to couter this problem. If yes, please provide the installation steps. (2 Replies)
Discussion started by: rakeshkumar9919
2 Replies
6. Hardware
Hello everybody,
I need to connect a laptop 2.5 SATA hard drive to a Desktop board (which uses 3.5' SATA hard drives). I've tried the connectors and they fit excellent in the 2.5 SATA connectors.
The problem is that the laptop hard drive uses 5v and the PC's power source sends 12v. So, my... (4 Replies)
Discussion started by: Zykl0n-B
4 Replies
7. Hardware
Hi everyone
(see attachments)
I bought an HP Elitebook 8460p on eBay and it came with a password-locked Hitachi hard drive which I was told is the original hard drive. I don't know the password for the drive and running the diagnostics tools I see the hard drive is healthy. I tried booting... (9 Replies)
Discussion started by: milhan
9 Replies
8. AIX
OSLevel: 5300-10-02-0943
System Model: IBM,8203-E4A
Power 6
==
Hi!
I replaced a failed pdisk in the raid enclosure as follows,
- rmdev -l 'pdisk18' '-d'
- Replaced it.
- cfgmgr (detected)
- I can see the new drive, with the correct serial #
lscfg -v -l pdisk18
pdisk18... (2 Replies)
Discussion started by: estrar
2 Replies
9. AIX
Hello,
I would like to check how many SAS disks and its size per disk for the whole power system. As per my understanding, if we assign the SAS controller to LPAR, then we can see the disk in lpar smitty command.
How can we check from the Power machine(physical ones) as well? I think the... (5 Replies)
Discussion started by: Phat
5 Replies
LEARN ABOUT DEBIAN
smp_rep_phy_event
SMP_REP_PHY_EVENT(8) SMP_UTILS SMP_REP_PHY_EVENT(8)
NAME
smp_rep_phy_event - invoke REPORT PHY EVENT SMP function
SYNOPSIS
smp_rep_phy_event [--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 EVENT 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 identify 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.
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 EVENT function was introduced in SAS-2 .
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright (C) 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_rep_phy_event_list(smp_utils) sg_logs, sg_sat_phy_event(sg3_utils)
smp_utils-0.96 May 2011 SMP_REP_PHY_EVENT(8)