dmesg

[Ravinder Singh Gill]

when I did dmesg I got the following as part of my output. Can anybody advise what this is & what action should be taken?


SCSI: Read error -- dev: b 31 0x003000, errno: 126, resid: 2048,
blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
LVM: vg[1]: pvnum=3 (dev_t=0x1f003000) is POWERFAILED

SCSI: Write error -- dev: b 31 0x003000, errno: 126, resid: 43008,
blkno: 1238, sectno: 2476, offset: 1267712, bcount: 43008.
percival:/#

[Patrick Wallek]

Check your disks and see if you have a disk that has died.

The worriesome message is:
LVM: vg[1]: pvnum=3 (dev_t=0x1f003000) is POWERFAILED

That indicates the c0t3d0 has potentially failed.

[Torsten. · Accepted solution]

Hi Ravinder,

that seems to be a bad disk.
Try

ioscan -fnkCdisk

and look for "NO_HW" to find it.

[Jeff Schussele]

Hi Ravinder,

It means that at some point - dmesg is not time stamped, check the syslog.log for date/time - the system saw a problem with /dev/dsk/c0t3d0
This might have been a transient problem, but at the time the system could not access it.

HTH,
Jeff

[Alex Lavrov.]

Yout have a bad disk in your system.

Look at this line:

dev: b 31 0x003000

If you do "lsdev | grep 31", you'll see that 31 is number of disk driver, so the failed device is disk.

To find the disk that failed, you must look at "0x003000". I guess the disk is /dev/dsk/c3t0d0.

Do, "ioscan -fnCdisk" and look at the lines that have "NO_HW" in them. If you see it, than defentely the disk is gone. To verify it, do:

dd if=/dev/rdsk/c3t0d0 of=/dev/null bs=8192

You probably will see error messages or dd will hang. Call HP support and replace the disk.

Alex.

[Alex Lavrov.]

Sorry, the disk is dev/rdsk/c0t3d0 ofcourse.

My mistake.

[Cem Tugrul]

Ravinder,

What about the lights on this disk?
amber/green?

it seems something wrong on your power supply
of the disk.

ioscan -fnCdisk?
(As Torsten mentioned) check state of disk
CLAIMED or NO_HW

Good Luck,

[John E.Ophious]

G'day mate,

Just as all my other partners have posted, it looks like you could potentially have a bad disk. However, I would like to add that before tossing it in the trash, you may want to examine the disk for any loose connections/bent pins/missing terminators, etc. I've had this happen in the past where a simple reseat would solve the problem. If this does work, get a good backup asap and be sure to monitor this disk closely afterwards for any performance degradation.

[Ravinder Singh Gill]

i did an ioscan -fnC disk and all the disks showed as claimed.

[Siju Jose_1]

Hi Ravinder

I would suggest you run a cstm .Look for errors in the output and REPLACE the drive at the earliest.

a.cstm
b.map --select the device Num
c.sel dev "dev no"
d.info
e.infolog

Siju