1834149 Members
2255 Online
110064 Solutions
New Discussion

Hard Disk Problem

 
SOLVED
Go to solution
Waqar Razi
Regular Advisor

Hard Disk Problem

I am having the following error message in the syslog:

Aug 11 14:48:17 WARRIOR vmunix: SCSI: First party detected bus hang -- lbolt: 49380
8152, bus: 1
Aug 11 14:48:17 WARRIOR vmunix: lbp->state: 5020
Aug 11 14:48:17 WARRIOR vmunix: lbp->offset: 2f8
Aug 11 14:48:17 WARRIOR vmunix: lbp->uPhysScript: 1000000
Aug 11 14:48:17 WARRIOR vmunix: From most recent interrupt:
Aug 11 14:48:17 WARRIOR vmunix: ISTAT: 0a, SIST0: 90, SIST1: 00, DSTAT:
00, DSPS: 01628000
Aug 11 14:48:17 WARRIOR vmunix: NCR chip register access history (most recent la
st): 251582355 accesses
Aug 11 14:48:17 WARRIOR vmunix: 0, ISTAT<-20
Aug 11 14:48:17 WARRIOR last message repeated 3 times
Aug 11 14:48:17 WARRIOR vmunix: 8001186, ISTAT<-20
Aug 11 14:48:17 WARRIOR vmunix: 0, ISTAT<-20
Aug 11 14:48:17 WARRIOR vmunix: 1998634, ISTAT<-20
Aug 11 14:48:17 WARRIOR vmunix: 0, ISTAT<-20
Aug 11 14:48:17 WARRIOR last message repeated 2 times
Aug 11 14:48:17 WARRIOR vmunix: 15758980, ISTAT<-20
Aug 11 14:48:17 WARRIOR vmunix: 0, ISTAT<-20
Aug 11 14:48:17 WARRIOR last message repeated 3 times
Aug 11 14:48:17 WARRIOR vmunix: 0, ISTAT: 28
Aug 11 14:48:17 WARRIOR vmunix: lsp: 0
Aug 11 14:48:17 WARRIOR vmunix: lbp->owner: 1746e680
Aug 11 14:48:17 WARRIOR vmunix: bp->b_dev: 1f013000
Aug 11 14:48:17 WARRIOR vmunix: scb->io_id: 147be2e
Aug 11 14:48:17 WARRIOR vmunix: scb->cdb: 2a 00 00 00 08 04 00 00 08 00
Aug 11 14:48:17 WARRIOR vmunix: lbolt_at_timeout: 493789952, lbolt_at_st
art: 493789952
Aug 11 14:48:17 WARRIOR vmunix: lsp->state: 10d
Aug 11 14:48:17 WARRIOR vmunix: scratch_lsp: 1746e680
Aug 11 14:48:17 WARRIOR vmunix: Pre-DSP script dump [1635c030]:
Aug 11 14:48:17 WARRIOR vmunix: 78346e00 0000000a 78350800 00000000
Aug 11 14:48:17 WARRIOR vmunix: 0e000004 010003c0 80000000 00000000
Aug 11 14:48:17 WARRIOR vmunix: Script dump [1635c050]:
Aug 11 14:48:17 WARRIOR vmunix: 9f0b0000 00000006 98080000 00000005
Aug 11 14:48:17 WARRIOR vmunix: 721a0000 00000000 c0000004 0100035c
Aug 11 14:48:17 WARRIOR vmunix: NCR chip register dump:
Aug 11 14:48:17 WARRIOR vmunix: 00: SCNTL3: 1b SCNTL2: 80 SCNTL1:
10 SCNTL0: d8
Aug 11 14:48:17 WARRIOR vmunix: 04: GPREG: 07 SDID: 03 SXFER:
08 SCID: 47
Aug 11 14:48:17 WARRIOR vmunix: 08: SBCL: 26 SSID: 86 SOCL:
06 SFBR: 00
Aug 11 14:48:17 WARRIOR vmunix: 0c: SSTAT2: 08 SSTAT1: 0e SSTAT0:
00 DSTAT: 80
Aug 11 14:48:17 WARRIOR vmunix: 10: DSA: ffffffc9
Aug 11 14:48:17 WARRIOR vmunix: 14: RESV14: ff RESV15: ff RESV16:
ff ISTAT: 28
Aug 11 14:48:17 WARRIOR vmunix: 18: CTEST3: 20 CTEST2: 45 CTEST1:
f0 CTEST0: 04
Aug 11 14:48:17 WARRIOR vmunix: 1c: TEMP: 010000d0
Aug 11 14:48:17 WARRIOR vmunix: 20: CTEST6: c0 CTEST5: 03 CTEST4:
88 DFIFO: 00
Aug 11 14:48:17 WARRIOR vmunix: 24: DCMDDBC: 9f0b0000
Aug 11 14:48:17 WARRIOR vmunix: 28: DNAD: 01000058
Aug 11 14:48:17 WARRIOR vmunix: 2c: DSP: 01000058
Aug 11 14:48:17 WARRIOR vmunix: 30: DSPS: 00000006
Aug 11 14:48:17 WARRIOR vmunix: 34: SCRATCHA: ff00086e
Aug 11 14:48:17 WARRIOR vmunix: 38: DCNTL: 21 DWT: 00 DIEN:
7f DMODE: 80
Aug 11 14:48:17 WARRIOR vmunix: 3c: ADDER: 0100005e
Aug 11 14:48:17 WARRIOR vmunix: 40: SIST1: 00 SIST0: 40 SIEN1:
87 SIEN0: 8f
Aug 11 14:48:17 WARRIOR vmunix: 44: GPCNTL: 0f MACNTL: 00 SWIDE:
ff SLPAR: 3c
Aug 11 14:48:17 WARRIOR vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1:
00 STIME0: 0c
Aug 11 14:48:17 WARRIOR vmunix: 4c: STEST3: 80 STEST2: 20 STEST1:
00 STEST0: 06
Aug 11 14:48:17 WARRIOR vmunix: 50: RESV50: ff RESV51: ff SIDL1:
00 SIDL0: 00
Aug 11 14:48:17 WARRIOR vmunix: 54: RESV54: ff RESV55: ff SODL1:
ff SODL0: 0d
Aug 11 14:48:17 WARRIOR vmunix: 58: RESV58: ff RESV59: ff SBDL1:
00 SBDL0: 00
Aug 11 14:48:17 WARRIOR vmunix: 5c: SCRATCHB: 00000000
Aug 11 14:48:17 WARRIOR vmunix: Zalon register dump:
Aug 11 14:48:17 WARRIOR vmunix: IO_STATUS: b9000060
Aug 11 14:48:17 WARRIOR vmunix: IO_II_DATA: b9000060
Aug 11 14:48:17 WARRIOR vmunix: IO_DC_DATA: 80808080
Aug 11 14:48:17 WARRIOR vmunix:
Aug 11 14:48:17 WARRIOR vmunix: SCSI: Resetting SCSI -- lbolt: 493808252, bus: 1
Aug 11 14:48:17 WARRIOR vmunix:
Aug 11 14:48:17 WARRIOR vmunix: SCSI: Reset detected -- lbolt: 493808252, bus: 1
Aug 11 14:48:17 WARRIOR vmunix: LVM: VG 1 : PV 2 (device 0x1f013000) is POWERFAILED
Aug 11 14:48:23 WARRIOR vmunix: LVM: Recovered Path (device 0x1f013000) to PV 2 in
VG 1.
Aug 11 14:48:23 WARRIOR vmunix: LVM: Restored PV 2 to VG 1.

I need to find out the hard disk which has problems and the volume group in which it is located.
7 REPLIES 7
Tim Nelson
Honored Contributor
Solution

Re: Hard Disk Problem

>Aug 11 14:48:17 WARRIOR vmunix: LVM: VG 1 : PV 2 (device 0x1f013000) is POWERFAILED


/dev/dsk/c1t3d0



candlejack
Advisor

Re: Hard Disk Problem

Please run the following as root and see if any disks are marked as "NOT CLAIMED"

ioscan -fnC disk
"The future starts today, not tomorrow." -Pope John Paul II
Waqar Razi
Regular Advisor

Re: Hard Disk Problem

Can u give me details what was the problem because that disk seems to be CLAIMED in ioscan -funC disk.
Tim Nelson
Honored Contributor

Re: Hard Disk Problem

The drive reset. Powered off then back on..

It is either failing, or has a bad connections.

Monitor. If it never fails again then it was just gas. If it fails again then replace it.

OldSchool
Honored Contributor

Re: Hard Disk Problem

actually, Tim told you. If you note, the fault recovered, so all you can go on is the log

"Aug 11 14:48:17 WARRIOR vmunix: LVM: VG 1 : PV 2 (device 0x1f013000) is POWERFAILED
Aug 11 14:48:23 WARRIOR vmunix: LVM: Recovered Path (device 0x1f013000) to PV 2 in
VG 1.
Aug 11 14:48:23 WARRIOR vmunix: LVM: Restored PV 2 to VG 1."
piyush mathiya
Trusted Contributor

Re: Hard Disk Problem

Hi,
I think Tim is right, but if you have some doubt, then you can use "dd" command to clarify it. . .

dd if=/dev/rdsk/c1t3d0 of=/dev/null bs=64k
Asif Sharif
Honored Contributor

Re: Hard Disk Problem

Salam Waqar,

I think you are experiencing hardware errors on a disk.

Test the disk with dd command.

# dd if=/dev/dsk/cxtxdx of=/dev/null bs=64 count=1000

If successful, the results of this command will look similar to:

100+0 records in
100+0 records out

further you can check with diskinfo command.

#diskinfo /dev/rdsk/cxtxdx
check for errors.


Regards,
Asif Sharif

Regards,
Asif Sharif
Regards,
Asif Sharif