Verify Disk

[Qcheck]

We got the following error:

Disk at hardware path 0/1/1/1.0.0 : Media failure

I did verify and for me everything looks okay. But how can I verify there is no hard disk error. I just want to verify with you gurus, to make sure I am not missing anything....

Thanks

[Ganesan R · Accepted solution]

Hi,

Use dd command to verify the media errors

Command syntax would be

#dd if=/dev/rdsk/cxtxdx of=/dev/null bs=1024k

[Qcheck]

Thank you Ganesan, But I issued that command over an hr ago, and still the prompt didn't come back yet. Do u think it is a problem or still working? What should I do?

[Andres_13]

The time it will take varies depending on your disk's size and the io rate the server might be issuing.

Also you can check syslog.log for errors and you can do a pvdisplay -v /dev/dsk/cxtydz and check for "stale" status

Regards.

[Qcheck]

The dd command is still running and I am trying to kill and couldn't do it.

[Adam W.]

I would say it safe afte that amount of time to say you need to get the disk replaced. if the dd doesn't return, it is a safe assumption. try:

ioscan -fnC disk
pvdisplay -v

[Andres_13]

Is it working?

if dd appears to be hunged i would ask you something else:

disk capacity?

vgdisply -v
pvdisplay -v cxtydz | grep stale
ioscan fn

Regards!

[LJenkins]

HI Pratibha

First in this case I will check the device using the command

/usr/sbin/ioscan -fn | more

with the log result I will find the correct path 0/1/1/1.0.0 and i would check if the device is CLAIMED or not.

and if you need to check the hard disk use

/usr/sbin/ioscan -funC disk


if you need anything else please provide the result of the command

I hope this help you

Regards

Luis Jenkins

[Bill Hassell]

Do you see disk errors in syslog? Look in /var/adm/syslog/syslog.log. The dd command should run at about 2GB/min, so 100GB would need less than an hour. If you kill the dd command, it will tell you the number of records completed so far. With bs=1024k, the records are 1MB each. If the records completed is very low, then dd is stuck trying to talk to the disk. This is a good indication of a disk failure too.

[Trng]

hI pRathiba,

check in syslog and check for any eventlog reported by EMS .

check diskinfo listing properly or not

and then use dd if=/dev/rdsk/cxtxdx of=/dev/null bs=1024k to verify


regards
skr

[Qcheck]

syslog.log:Oct 31 20:07:24 omrhx04 EMS [2626]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_1_1_1.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 172097540 -r /storage/events/disks/default/0_1_1_1.0.0 -n 172097538 -a
syslog.log:Nov 1 20:07:25 omrhx04 EMS [2626]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_1_1_1.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 172097540 -r /storage/events/disks/default/0_1_1_1.0.0 -n 172097539 -a
syslog.log:Nov 2 19:07:27 omrhx04 EMS [2626]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/0_1_1_1.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 172097540 -r /storage/events/disks/default/0_1_1_1.0.0 -n 172097540 -a

Thank you for all your responses.
I see the above error from the syslog. On Friday, I did unmirror the rootvg so that rootvg doesn't sync with the bad disk. We are planning on replacing the disk tonight. Any ideas?

[James R. Ferguson]

Hi:

> We are planning on replacing the disk tonight. Any ideas?

Yes, read and follow the guidelines here:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

A search of this forum for threads about disk replacement would have turned up this suggestion multiple times, too.

Regards!

...JRF...

[Qcheck]

Disk has been replaced and thank you all for your help...