SCSI: Write Error.

[Fernando Plaza]

Hi, I wont know if this message is a real HW Problem or, like I see in this forum, is only a response time problem ?

Thank You

ct 28 08:35:39 noasap vmunix: SCSI: Write error dev: b 31 0x8000, errno: 126, resid: 8192,
ct 28 08:35:39 noasap vmunix: #blkno: 2747312, sectno: 5494624, offset: -1481719808, bcount: 8192.
ct 28 08:35:39 noasap vmunix: LVM: vg[0]: pvnum=1 (dev_t=0x1f008000) is POWERFAILED
ct 28 08:35:39 noasap vmunix:
ct 28 08:35:39 noasap vmunix: SCSI: Write error dev: b 31 0x8000, errno: 126, resid: 8192,
ct 28 08:35:39 noasap vmunix: #blkno: 2752264, sectno: 5504528, offset: -1476648960, bcount: 8192.
ct 28 08:35:39 noasap vmunix:
ct 28 08:35:39 noasap vmunix: SCSI: Write error dev: b 31 0x8000, errno: 126, resid: 8192,
ct 28 08:35:39 noasap vmunix: #blkno: 2759760, sectno: 5519520, offset: -1468973056, bcount: 8192.
ct 28 08:35:39 noasap vmunix:
ct 28 08:35:39 noasap vmunix: SCSI: Write error dev: b 31 0x8000, errno: 126, resid: 8192,
ct 28 08:35:39 noasap vmunix: #blkno: 2959336, sectno: 5918672, offset: -1264607232, bcount: 8192.
ct 28 08:35:39 noasap vmunix:
ct 28 08:35:39 noasap vmunix: SCSI: Write error dev: b 31 0x8000, errno: 126, resid: 8192,
ct 28 08:35:39 noasap vmunix: #blkno: 3087256, sectno: 6174512, offset: -1133617152, bcount: 8192.

[Stefan Farrelly]

It certainly is something to be worried about. Looks like one of your disks is on its way to the big bit bucket in the sky.

Contact HP and log a hardware call.

[sung-hoon chang]

Hello

One of the Your disk in VG00 is H/W failed.
Maybe the disk device file is c0t8d0(?). And the disk use HSC interface because the block device number in kernel IO table is 0x1f(31).
You can confirm by lsdev command.
"lsdev | grep 31"

I think, the disk maybe have a disk performance problem.

ASAP, replace the disk and fix.

Regards.

[sung-hoon chang]

Hello

One of the Your disk in VG00 is H/W failed.
Maybe the disk device file is c0t8d0(?). And the disk use HSC interface because the block device number in kernel IO table is 0x1f(31).
You can confirm by lsdev command.
"lsdev | grep 31"

I think, the disk maybe have a disk performance problem.

ASAP, replace the disk and fix.

Regards.

[Fernando Plaza]

Stefan Farrelly and sung-hoon chang...
I belive that the best action can be replace the disk.

Thank you.

[Rob Smith]

Fernando,

Hi, try the following patches;
PHKL_16751
PHCO_16591
PHKL_21595
PHKL_16957
PHKL_20611
PHKL_21661
Also, make sure the SCSI firmware on your drives is up to date.

Hope this helps

Regards,
Robert

[Victor Mendham]

Just wondering, if you know by now if this was a real SCSI error?
I need to use IT/O to monitor the syslog for errors. So if this is a real SCSI
error I would like to use the sytax from the log for my testing?

Please let me know if this problem was real.