Sponsored Content
Full Discussion: iostat -En errors
Operating Systems Solaris iostat -En errors Post 302464536 by zaza on Wednesday 20th of October 2010 11:13:25 AM
Old 10-20-2010
iostat -En errors

I all,

I would like to know what are the causes of :

-soft error
-harderror
-transport error

and how to avoid and repare them.

I got the iostat out put below:
Code:
atng-mm01% iostat -En | grep -i hard
c0t0d0           Soft Errors: 1 Hard Errors: 0 Transport Errors: 0 
c0t0d1           Soft Errors: 1 Hard Errors: 0 Transport Errors: 0 
c2t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
c2t1d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
c1t0d0           Soft Errors: 126860 Hard Errors: 0 Transport Errors: 190295 
c0t0d2           Soft Errors: 1 Hard Errors: 0 Transport Errors: 0 
c0t0d3           Soft Errors: 1 Hard Errors: 0 Transport Errors: 0 
rmt/0            Soft Errors: 0 Hard Errors: 0 Transport Errors: 0

the c1t0d0 is a DVD

thanks,

Last edited by Scott; 10-20-2010 at 01:14 PM.. Reason: Please use code tags for input, output and log files as well as code
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Adapter Errors and Link Errors

$ errpt | more IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR 3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies

2. AIX

Adapter Errors and Link Errors

$ errpt | more IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR 3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR B8113DD1 ... (2 Replies)
Discussion started by: mcastill66
2 Replies

3. Filesystems, Disks and Memory

Help with iostat ...

All, I am attempting to help tune a Sun for better performance (mainly for SAS 9.1), and have found indicators pointing to poor I/O utilization. I have run iostat -cx, and found one device in particular where the %w is in the 90's during processing. I have a feeling that this is where the SAS... (3 Replies)
Discussion started by: dj_is
3 Replies

4. UNIX for Dummies Questions & Answers

Major OS errors/Bash errors help!!!!

Hi all, dummy here.... I have major errors on entering the shell. On login I get: -bash: dircolors: command not found -bash: tr: command not found -bash: fgrep: command not found -bash: grep: command not found -bash: grep: command not found -bash: id: command not found -bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies

5. Solaris

iostat -nE with Hard Errors

iostat -nE returns the followings I want to know what is happening to my StorEDGE A1000? Can someone help me? It is a critical device. (1 Reply)
Discussion started by: nickychung
1 Replies

6. AIX

how to identified this iostat value

Hi All AIX expert i'm using AIX 5.2 When i execute this command which is : ---------------------------------------------------------------------- >> iostat -a System configuration: lcpu=4 disk=30 tty: tin tout avg-cpu: % user % sys % idle % iowait ... (2 Replies)
Discussion started by: adzuanamir
2 Replies

7. Red Hat

iostat on Redhat 5

A find for the "iostat" command on a redhat 5 update 4 comes back with no results. Any separate rpm needs to be installed to get the binary for this ? Thanks in advance. (1 Reply)
Discussion started by: uxadmin007
1 Replies

8. UNIX for Dummies Questions & Answers

transport errors in iostat

Hi Unix experts, I have a question regarding a disk failure seen in "iostat -Enm" output: # iostat -Enm c1t0d0 Soft Errors: 0 Hard Errors: 7 Transport Errors: 9 Vendor: FUJITSU Product: MAU3073NCSUN72G Revision: 0802 Serial No: 0514F005M0 Size: 73.40GB <73400057856 bytes> Media... (5 Replies)
Discussion started by: dyavuzy1
5 Replies

9. AIX

Help with iostat

Hello, I support Oracle 11g on AIX 7.1. Using the command $iostat -D hdisk2 hdisk4 hdisk5 5 I get the following output: hdisk5 xfer: %tm_act bps tps bread bwrtn 44.0 1.4M 178.2 1.4M 14.7K read: ... (3 Replies)
Discussion started by: oracledba1024
3 Replies

10. Solaris

Sense key unit attention & iostat hardware and transport errors on SAN disks

Hello, I'm trying to get to the bottom of SAN disk errors we've been seeing. Server is Sun Fire X4270 M2 running Solaris 10 8/11 u10 X86 since April 2012. SAN HBAs are SG-PCIE2FC-QF8-Z-Sun-branded Qlogic. SAN storage system is Hitachi VSP. We have 32 LUNs in use and another 8 LUNs not brought... (4 Replies)
Discussion started by: TKD
4 Replies
IOSTAT2PCP(1)						       Performance Co-Pilot						     IOSTAT2PCP(1)

NAME
iostat2pcp - Import iostat data and create a PCP archive SYNOPSIS
iostat2pcp [-v] [-S start] [-t interval] [-Z timezone] infile outfile DESCRIPTION
iostat2pcp reads a text file created with iostat(1) (infile) and translates this into a Performance Co-Pilot (PCP) archive with the basename outfile. If infile is "-" then iostat2pcp reads for standard input, allowing easy preprocessing of the iostat(1) output with sed(1) or similar. The resultant PCP archive may be used with all the PCP client tools to graph subsets of the data using pmchart(1), perform data reduction and reporting, filter with the PCP inference engine pmie(1), etc. A series of physical files will be created with the prefix outfile. These are outfile.0 (the performance data), outfile.meta (the metadata that describes the performance data) and outfile.index (a temporal index to improve efficiency of replay operations for the archive). If any of these files exists already, then iostat2pcp will not overwrite them and will exit with an error message. The first output sample from iostat(1) contains a statistical summary since boot time and is ignored by iostat2pcp, so the first real data set is the second one in the iostat(1) output. The best results are obtained when iostat(1) was run with its own -t flag, so each output sample is prefixed with a timestamp. Even better is -t with $S_TIME_FORMAT=ISO set in environment when iostat(1) is run, in which case the timestamp includes the timezone. Note that if $S_TIME_FORMAT=ISO is not used with the -t option then iostat(1) may produce a timestamp controlled by LC_TIME from the locale that is in a format iostat2pcp cannot parse. The formats for the timestamp that iostat2pcp accepts are illustrated by these examples: 2013-07-06T21:34:39+1000 (for the $S_TIME_FORMAT=ISO). 2013-07-06 21:34:39 (for some of the European formats, e.g. de_AT, de_BE, de_LU and en_DK.utf8). 06/07/13 21:34:39 (for all of the $LC_TIME settings for English locales outside North America, e.g. en_AU, en_GB, en_IE, en_NZ, en_SG and en_ZA, and all the Spanish locales, e.g. es_ES, es_MX and es_AR). In particular, note that some common North American $LC_TIME settings will not work with iostat2pcp (namely, en_US, POSIX and C) because they use the MM/DD format which may be incorrectly converted with the assumed DD/MM format. This is another reason to recommend setting $S_TIME_FORMAT=ISO. If there are no timestamps in the input stream, iostat2pcp will try and deduce the sample interval if basic Disk data (-d option for iostat(1)) is found. If this fails, then the -t option may be used to specify the sample interval in seconds. This option is ignored if timestamps are found in the input stream. The -S option may be used to specify as start time for the first real sample in infile, where start must have the format HH:MM:SS. This option is ignored if timestamps are found in the input stream. The -Z option may be used to specify a timezone. It must have the format +HHMM (for hours and minutes East of UTC) or -HHMM (for hours and minutes West of UTC). Note in particular that neither the zoneinfo (aka Olson) format, e.g. Europe/Paris, nor the Posix TZ format, e.g. EST+5 is allowed for the -Z option. This option is ignored if ISO timestamps are found in the input stream. If the timezone is not specified and cannot be deduced, it defaults to "UTC". Some additional diagnostic output is generated with the -v option. iostat2pcp is a Perl script that uses the PCP::LogImport Perl wrapper around the PCP libpcp_import library, and as such could be used as an example to develop new tools to import other types of performance data and create PCP archives. CAVEAT
iostat2pcp requires infile to have been created by the version of iostat(1) from <http://freshmeat.net/projects/sysstat>. iostat2pcp handles the -c (CPU), -d (Disk), -x (eXtended Disk) and -p (Partition) report formats (including their -k, -m, -z and ALL variants), but does not accommodate the -n (Network Filesystem) report format from iostat(1); this is a demand-driven limitation rather than a technical limitation. SEE ALSO
Date::Format(3pm), Date::Parse(3pm), iostat(1), LOGIMPORT(3), PCP::LogImport(3pm), pmchart(1), pmie(1), pmlogger(1) and sed(1). 3.8.10 Performance Co-Pilot IOSTAT2PCP(1)
All times are GMT -4. The time now is 10:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy