[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hpux-admin
Subject:    [HPADM] SUMMARY: SCSI: Parity error -- lbolt: 34700671, dev: 1f026000
From:       Eric Watson <ewatson () law ! harvard ! edu>
Date:       2000-05-30 20:15:59
[Download RAW message or body]

This could easily be an o/s issue that could be fixed with patches.  We had
the same problem and it was fixed by installation of the latest round of
SCSI and LVM patches.

At the least consider (for an S800 running 10.20):

PHCO_11817
PHCO_18563
PHKL_13729
PHKL_16751
PHKL_21370
PHKL_13044
PHKL_13729
PHKL_21085

Note that most of these are kernel rebuilds and require reboots.  You can
copy all the patches into your own depot using:

# swcopy -x enforce_dependencies=true -s /source/ \* @ /target/

where /source/ is the patch (with path) and /target/ is a directory you
create.  You'll have to swcopy each patch manually but this way you only
have to build the kernel and reboot once.

Of course, it's probably a good idea to check with Response Center before
patching.

Eric

******************************
Eric Watson
Sr. Systems Administrator
Harvard Law School
617-496-6518
******************************

-----Original Message-----
From: hpux-admin-owner@dutchworks.nl
[mailto:hpux-admin-owner@dutchworks.nl]On Behalf Of
R.Hildebrandt@tu-bs.de
Sent: Tuesday, May 30, 2000 9:44 AM
To: hpux-admin@dutchworks.nl
Subject: [HPADM] SUMMARY: SCSI: Parity error -- lbolt: 34700671, dev:
1f026000


Am 30.05.2000 um 12:22:21 +0200 schrieb Ralf Hildebrandt folgendes:
>
> This is a 735/99 with 10.20
> What disk is producing this error?
>
> vmunix: SCSI: Parity error -- lbolt: 34700671, dev: 1f026000
>

To cut a long story shot: It's /dev/dsk/c2t6d0 == / :(


Am 30.05.2000 um 11:41:53 +0100 schrieb Vince Taylor folgendes:
>
> I believe you need to do the following...
>
> 	ls -l /dev/dsk | grep 26000
>
> and this will pick out the relevent disk.
>
> The "1b" converts to decimal 31 (known as the major number), which is the
> block disk device, and the remaining part "026000" is known as the minor
> number.
>
> Vince.

Am 30.05.2000 um 13:53:13 +0200 schrieb Ilan Green folgendes:
> 1f - 31 the FW/SCSI c2t6...

Am 30.05.2000 um 07:57:21 -0400 schrieb Marillier, Allan folgendes:
> This looks like a failed SCSI disk. I have had many failures
> on 4.3 Gb Jamaica disks - that is the typical symptom.
> If you check through your syslog you may find messages
> indicating which disk it is. If you have predictive diagnostics
> running, you should find it in there also.
> The other option is to start by trying to access each file system
> and see which don't respond. This can be time consuming
> sometimes - I have in the past just issued a
> find /
> and watched to see which file system was reached when it hangs,
> and eventually times out. Once you know which file system is affected,
> you can use lvdisplay -v, or strings /etc/lvmtab|more to see which
> disks are included in the file system, then start doing pvdisplay
> and diskinfo on those to find which one it is. diskinfo will probably
> still report something, unless the disk has died completely, while
> pvdisplay will probably give errors.

Am 30.05.2000 um 08:06:26 -0400 schrieb Robert Alexander folgendes:
> by looking at the dev field, you can tell that it is the device with major
number
> 31 (hex 1f) the other fields of the device number show you the minor
number and
> target.  You should be able to do a ls -l on /dev/dsk and /dev/rdsk and
tell which
> device it is.

Am 30.05.2000 um 14:23:10 +0100 schrieb Andy Cranston folgendes:
> Hello Ralf,
>
> The clue is in the "dev: 1f026000".
>
> The "1f" from "1f026000" in decimal is 31.  31 is the major device number
> for block device disks in /dev/dsk (do a ls -l /dev/dsk and column 5 is
> always 31).
>
> In /dev/dsk the files are cXtYdZ with X, Y and Z integers.  the "02" from
> "1f026000" is the controller c2, the "6" from "1f026000" is the target ID
t6
> and one of the zeroes is d0.  Well it's near enough.
>
> Anyway my guess is when you track this device down it will be a CD-ROM.
>
> Because CD-ROMs on HP-UX appear as disks it is sometime possible for
> utilities like LVMcollect to ask the CD-ROM for boot LIF information and
> stuff like that.  The CD-ROM driver barfs at these requests and can dump
odd
> messages in syslog.  Here is one I get every week when LVMcollect runs on
an
> R class:
>
> May 27 05:02:01 hpr1 vmunix: SCSI: Attempt to access partially open device
> -- dev: bc012000
>
> It's a long shot - but then they always are :-)
>
> Regards,
>
> Andy Cranston,
> Euphony Communications (but I was at RSL COM for a while :-)

--
Ralf Hildebrandt <R.Hildebrandt@tu-bs.de> www.stahl.bau.tu-bs.de/~hildeb
So unleash your nmap-from-hell and beware, you may tickle an obscure
bug in an ancient box hand-built by Seymour Cray himself, the only one
of its kind ever made, whose sole user pays the salaries of everyone
you ever met in the entire time you worked at the company, with money
he makes with an investment strategy hand-coded in assembler for this
special machine, by an analytic wizard who has since died.


--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact
majordomo@dutchworks.nl
       Name: hpux-admin@dutchworks.nl     Owner:
owner-hpux-admin@dutchworks.nl

 Archives:  ftp.dutchworks.nl/pub/digests/hpux-admin       (FTP, browse
only)
            http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse &
search)




--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
       Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
 
 Archives:  ftp.dutchworks.nl/pub/digests/hpux-admin       (FTP, browse only)
            http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)

[prev in list] [next in list] [prev in thread] [next in thread]