topic Re: dmesg lbolt error in Operating System - HP-UX

dmesg lbolt error

Md.Shahabuddin — Mon, 29 Dec 2008 05:54:31 GMT

Hi,
I am getting this following error in dmesg.

SCSI: Resetting SCSI -- lbolt: 163871137, bus: 0
SCSI: c720_reset_wait_done: LBP_RESET_PENDING -- lbolt: 163871537, dev: cb000002
lbp->state: c028
lbp->offset: 0
lbp->uPhysScript: 900000
From most recent interrupt:
ISTAT: 00, SIST0: 00, SIST1: 00, DSTAT: 00, DSPS: 00000000
lsp: 0000000043a069a0
bp->b_dev: cb000002
scb->io_id: 0
scb->cdb:
lbolt_at_timeout: 163870937, lbolt_at_start: 163869437
lsp->state: 86
lbp->owner: 0000000043a069a0

----------------------------------------------

As per my knowledge i know that this error comes only when the disk has got corrupted, but ioscan is showing all of my disk is claimed.
Here is the output.

disk 0 8/8.1.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c1t1d0 /dev/rdsk/c1t1d0
disk 1 8/8.2.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 8/8.3.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c1t3d0 /dev/rdsk/c1t3d0
disk 3 10/8.1.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c3t1d0 /dev/rdsk/c3t1d0
disk 4 10/8.2.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 5 10/8.3.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c3t3d0 /dev/rdsk/c3t3d0
disk 6 10/8.4.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c3t4d0 /dev/rdsk/c3t4d0
disk 7 10/12/5.2.0 sdisk CLAIMED DEVICE PIONEER DVD-ROM DVD-303
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0

-----------------------------------------------

Note: No errors in syslog.log file.

-----------------------------------------------
Event log error:

Disk at hardware path 10/8.1.0 : Media failure
-----------------------------------------------

Kindly suggest me what i should conclude of the above mention errors.

Re: dmesg lbolt error

Prashanth Waugh — Mon, 29 Dec 2008 06:01:48 GMT

Hi ,
Check wheteher its a problem related to disk or scsi card

ioscan -fn | grep 10/8.1.0

Regards
Prashnat

Re: dmesg lbolt error

Md.Shahabuddin — Mon, 29 Dec 2008 06:31:58 GMT

Hi prashant,

That command is not showing any output. It is hung.

Re: dmesg lbolt error

john korterman — Mon, 29 Dec 2008 10:49:17 GMT

Hi,

you may perhaps conclude that the dmesg output is not related to the event log error:

The dmesg is about the device
cb000002
which is probably not a disk, but please check it on your system:
Discard the last two characters, the "02", and consider the rest like this, "cb 00 0 0"
cb is a hex representation for the major number referring to the id of the driver for the device.
The numeric driver id can - in decimal notation - be fed to the lsdev commond: the decimal value of cb is 203 - try
# lsdev 203
which on your system should produce a few words of explanation, perhaps that this is the driver for a tape device.
This device in question should use the device file "c00 t0 d0", i.e. "c0t0d0".
The message LBP_RESET_PENDING probably just means that the OS had had to wait too long for an answer, which may not be all that serious.

However, the event log error is not quite understandable, as the query hangs and the ioscan does not.
But I think you should examine /dev/dsk/c3t1d0
Try to read from the disk, e,g,:
# dd if=/dev/dsk/c3t1d0 bs=8k count=1
it should produce output like this
1+0 records in
1+0 records out

If you use LVM, try also
# vgdisplay -v | grep stale
which should produce no output.

regards,
John K.

Re: dmesg lbolt error

Md.Shahabuddin — Mon, 29 Dec 2008 11:08:42 GMT

Hi john,

thanks for your time u have given on my post. Here are some of the outputs.

# lsdev 203
Character Block Driver Class
203 -1 sctl ctl

-------------------------------------------
# dd if=/dev/dsk/c3t1d0 bs=8k count=1
/dev/dsk/c3t1d0: I/O error
dd: cannot open /dev/dsk/c3t1d0

--------------------------------------------

vgdisplay is not showing any stale error. I am not able to write anything on that disk.
--------------------------------------------

# diskinfo /dev/rdsk/c3t1d0
SCSI describe of /dev/rdsk/c3t1d0:
vendor: SEAGATE
product id: ST39173WC
type: direct access
size: 0 Kbytes
bytes per sector: 0

--------------------------------------------

Note: This disk does not belongs to any VG.
This disk does not have any entry in lvmtab file.
---------------------------------------------

What else should we do?

Re: dmesg lbolt error

john korterman — Mon, 29 Dec 2008 12:19:12 GMT

Hi again,

one thing that makes sense is that "vgdisplay -v | grep stale" does not produce any ouput, as /dev/dsk/c3t1d0 is not in lvmtab and hence not administered by LVM

However, the rest makes very little sense to me:

1) the lsdev output indicates that the driver is not installed in your kernel - which it should. Does the file /dev/dsk/c0t0d0 exist? what does "diskinfo /dev/rdsk/c0t0d0" show?

2) the file /dev/dsk/c3t1d0 seems to exist, and the OS believes it to be Seagate disk of size 0. The size somehow explains why you cannot write to it, but does otherwise not make any sense.

The mess of the device files can also be caused a faulty restore. Do you have any evidence of this?
Can you pinpoint when your system started behaving like this?

regards,
John K.

Re: dmesg lbolt error

Md.Shahabuddin — Tue, 30 Dec 2008 04:11:09 GMT

Hi John,

As there is no disk like c0t0d0, so it would not show any output.
c3t1d0 does exist and it is claimed. This error has occured only after reformatting the server. After restoration this problem has started.

Regards
Shahab