Sense Key: Media Error

Hi all,

We have below WARNING in /var/adm/messages file from our Solaris server.

WARNING: /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0 (sd0):
Error for Command: write(10) Error Level: Fatal
Requested Block: 16745265 Error Block: 16745269
Vendor: SEAGATE Serial Number: 0030V0KX4A
Sense Key: Media Error
ASC: 0x14 (recorded entity not found), ASCQ: 0x1, FRU: 0x3
WARNING: /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0 (sd0):
Error for Command: write(10) Error Level: Retryable
Requested Block: 15943457 Error Block: 15943457
Vendor: SEAGATE Serial Number: 0030V0KX4A
Sense Key: Media Error
ASC: 0x14 (recorded entity not found), ASCQ: 0x1, FRU: 0x3

We didn't explain and solve the problem. Could you please help us.
Thanks for your supports.

Disk has gone bad. Needs replacement

Thanks incredible for your support.

It is most important for us
How we fix this disk without replacement?

If we decide this faulty disk....
Our design is complicated. We have two disk in the server and six disk in the RAID unit.
How we find faulty disk between these eight disk.
Could you please help us.
Thank.

provide the df -k output first.
if you using the SVM, then provide metastat -p output
if using VxVM, provide the vxdisk list vxdg list outputs

We'll see first. better don't take risk if its serious.
Also provide the iostat -En output

Hi incredible,

df -k output is below..

Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 75668 33278 34830 49% /
/dev/dsk/c0t0d0s6 371137 193105 140922 58% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/dsk/c0t0d0s3 6384917 1422756 4323671 25% /var
/dev/dsk/c0t0d0s5 987302 625411 263161 71% /opt
swap 1207904 368 1207536 1% /tmp
/dev/dsk/c0t1d0s0 3697157 451082 2876365 14% /var/opt/SUNWconn
/dev/dsk/c0t1d0s1 2773262 107749 2388193 5% /var/opt/yasar/logs
/dev/dsk/c0t1d0s7 1849454 54714 1609800 4% /var/opt/yasar/backup
/dev/dsk/c1t1d0s0 11943267 402305 10346642 4% /var/opt/yasar/zailed/home
/dev/dsk/c1t1d0s1 3980411 1218733 2363638 35% /var/opt/yasar/config
/dev/dsk/c1t1d0s3 3980411 9 3582362 1% /var/opt/yasar/eventLogs
/dev/dsk/c1t1d0s7 996382 2254 894498 1% /var/opt/yasar/misc

metastat -p, vxdisk and vxdg commands are not applicaple our system. Output is command not found.

for iostat command, "-En" parameters are unknown. iostat -xtc output is below.

                             extended disk statistics       tty         cpu

disk r/s w/s Kr/s Kw/s wait actv svc_t %w %b tin tout us sy wt id
fd0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 0 472 26 8 39 27
sd0 0.2 6.3 1.9 48.4 7.0 4.2 1710.8 37 55
sd1 0.2 8.2 5.1 65.6 0.0 0.2 17.9 0 13
sd6 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0
sd24 0.1 0.4 0.5 3.6 0.0 0.0 2.4 0 0
sd25 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0

Thanks for your support.

You'd better backup ur OS and data first
iostat -En should work.
uname -a --> output?
And you're using only 3 disks? there's no mirror for redundancy. its very bad dude.
Are you still recieving the errors or has it stopped? I can assure that its not a good sign. You may either loose your data or your system may panic and not become bootable

Worst case , you will have to restore the OS to a new disk from a tape backup if its the one being affected

Yes, We have backed up our data, but not OS.
We are sure, OS dont responce iostat -En command. Output is below.

server1:{127}% iostat -En
Usage: iostat [-tdDxcI] [-l n] [disk ...] [interval [count]]

uname -a output is below

server1:{128}% uname -a
SunOS server1 5.5.1 Generic_103640-27 sun4u sparc SUNW,Ultra-2

We are still receiving same errors. And /var/adm/messages file is growing. This file's size is 30 MB. Is this status dangerous? Should I delete this file?
In addition, OS is very slow. It reply very late and open tools very slow. Is it normal?
We have tape backup.
Thanks.

omg.. brother.. its getting serious, dun delete messages file, you may clear its contents for now "cat /dev/null > /var/adm/messages.
Stop accessing the system for any further I/O activities.
Get a replacement disk - same part-number
Restore data which is residing on the failed disk from tape (Serial Number: 0030V0KX4A )
installboot bootblk on slice 0 to make it bootable
shutdown the system.
insert new disk replacing the faulty one
power on the system for boot up