topic Re: disk error in Operating System - HP-UX

disk error

Daniel Gizaw — Wed, 14 May 2003 19:01:40 GMT

Is the below error message from dmesg serious? how can I fix it?

Thank you

Daniel

SCSI: Write error -- dev: b 31 0x043000, errno: 126, resid: 262144,
blkno: 67072, sectno: 134144, offset: 68681728, bcount: 262144.

SCSI: Write error -- dev: b 31 0x043000, errno: 126, resid: 26624,
blkno: 774, sectno: 1548, offset: 792576, bcount: 26624.
LVM: Failed to automatically resync PV 1f043000 error: 5

SCSI: Read error -- dev: b 31 0x043000, errno: 126, resid: 2048,

SCSI: Read error -- dev: b 31 0x053000, errno: 126, resid: 2048,
blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
LVM: Recovered Path (device 0x1f043000) to PV 1 in VG 2.
LVM: Recovered Path (device 0x1f053000) to PV 1 in VG 2.
LVM: Restored PV 1 to VG 2.
LVM: Recovered Path (device 0x1f043000) to PV 1 in VG 2.
LVM: Restored PV 1 to VG 2.
LVM: Failed to automatically resync PV 1f043000 error: 5

Re: disk error

PIYUSH D. PATEL — Wed, 14 May 2003 19:06:51 GMT

Daniel,

Unmount the filesystem and run fsck on the filesystem and check for any errors.

Seems to be some problem with the disk media. Good option is to replace the disk but for the timebeing you can format the disk and reuse it.
Take proper backup and then restore the data after formatting.

Good luck,
Piyush

Re: disk error

A. Clay Stephenson — Wed, 14 May 2003 19:11:52 GMT

Yes, it's almost certainly serious. At the very least /dev/dsk/c4t3d0 has problems (disk is probably failing)and /dev/dsk/c5t3d0 may have problems as well. Did a drive enclosure suffer a momentary power failure? Were cables unplugged? The system seems to have recovered but VG2 has some stale PE's. Try a vgsync /dev/vg02. If VG2 is mirrored then this is no big deal but if not then I hope you have recent/reliable backups.

Re: disk error

Daniel Gizaw — Wed, 14 May 2003 19:15:34 GMT

Piyush,
Thank you very much for your fast response.
How can I identify the disk?

ioscan does not show me any error.

Daniel

Re: disk error

James R. Ferguson — Wed, 14 May 2003 19:30:14 GMT

Hi Daniel:

The disk(s) in question are c4t3d0 and c5t3d0.

They are identified in hexadecimal notation (0x) with the device kind (a SCSI disk) noted as the first two hex-digits ('1f' or decimal 31) or as 'dev: b 31' for a block device, kind-31.

The general device format is:

MMBBTLFF

Where: MM = Major number
BB = Bus number
T = Target
L = LUN
FF = Flags

Hence, the major number = 0x1f = 31 in decimal (a disk);
...and the Bus is the card instance number = 04
...and the Target = 3 or the device???s SCSI ID
...and the LUN = 0 or the logical unit number
...and therefore the device is /dev/dsk/c4t3d0

Regards!

...JRF...

Re: disk error

PIYUSH D. PATEL — Wed, 14 May 2003 19:35:35 GMT

Daniel,

You may have two or more disks in your volume group vg02.

The device names for the disks are /dev/dsk/c3t4d0 and /dev/dsk/c3t5d0.
#vgdisplay -v /dev/vg02

ioscan would not give you any errors since the system can still access the disks but the system is having problems reading/writing to these disks. You may have temporary problems but you can get the system checked up by a HP engineer if you are getting these errors repeatedly.

Thanks,
Piyush

Re: disk error

PIYUSH D. PATEL — Wed, 14 May 2003 19:35:49 GMT

Re: disk error

PIYUSH D. PATEL — Wed, 14 May 2003 19:36:29 GMT

Re: disk error

Daniel Gizaw — Wed, 14 May 2003 20:01:26 GMT

Thank you all for the good education I got. I will do fsck first and call HP to replace the disk.

Thank you agian

Daniel

Re: disk error

Dario_1 — Wed, 14 May 2003 20:11:49 GMT

Daniel:

You got good answers, but check this post. It has very good answers regarding your situation.

Good Luck!!

DR

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf84063f96280d711abdc0090277a778c,00.html

Re: disk error

rachelgomez_123 — Tue, 03 Jan 2023 06:16:31 GMT

Quick fix
Check the boot order in the BIOS settings, and change the settings if necessary.
Reset BIOS to default.
Use a repair tool to repair the Master Boot Record (MBR) or Boot Sector.
Check all cables and jumpers.
Test your computer's RAM to check if the read disk error is related to faulty RAM stick or slot.

Regards,

Rachel Gomez