My original question:
=====================
We are receiving a few errors on a certain drive. The errors are shown below. I know which drive is
the culprit but which slice on the drive is the specific problem. The drive layout is also shown
below. I think the info I'm looking for is contained in the 'WARNING' line in the error output but
I forgot how to read it. Any help would be appreciated.
System info:
------------
Sparc Center 2000E
Solaris 2.5.1 patched
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Rick von Richter | Phone: 619-552-6222
Systems/Network Admin | Fax: 619-552-6221
Maintenance Warehouse | Email: rickv@mwh.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Science is true. Don't be misled by facts.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error output
============
Feb 25 06:08:54 ares unix: Requested Block: 12821824 Error Block: 12821829
Feb 25 06:08:54 ares unix: Vendor: SEAGATE Serial Number: LA036649
Feb 25 06:08:54 ares unix: Sense Key: Media Error
Feb 25 06:08:54 ares unix: ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xea
Feb 25 06:08:54 ares unix: WARNING: /io-unit@f,e1200000/sbi@0,0/dma@0,81000/esp@0,80000/sd@1,0
(sd16):
Feb 25 06:08:54 ares unix: Error for Command: read(10) Error Level: Retryabl
Feb 25 06:08:54 ares unix: e
Feb 25 06:08:55 ares unix: Requested Block: 12821824 Error Block: 12821829
Feb 25 06:08:55 ares unix: Vendor: SEAGATE Serial Number: LA036649
Feb 25 06:08:55 ares unix: Sense Key: Media Error
Feb 25 06:08:55 ares unix: ASC: 0x11 (unrecovered read error), ASCQ: 0x0, FRU: 0xea
Drive layout
============
ascii name = <WESTERN SCIENTIFIC SEAGATE ST19171N cyl 5266 alt 2 hd 20 sec 168>
pcyl = 5268
ncyl = 5266
acyl = 2
nhead = 20
nsect = 168
Part Tag Flag Cylinders Size Blocks
0 swap wu 0 - 0 1.64MB (1/0/0) 3360
1 swap wu 1 - 1159 1.86GB (1159/0/0) 3894240
2 backup wm 0 - 5264 8.44GB (5265/0/0) 17690400
3 unassigned wm 1160 - 5265 6.58GB (4106/0/0) 13796160
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
Answers:
========
>From Sun, the short of it is... there is no way to tell which partition is causing the headache by
looking at the above error message. The best way is to umount the filesystems and fsck them one by
one.
Thanks to all who submitted.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:47 CDT