From owner-freebsd-scsi Thu May 4 20: 6:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id D58B737B730 for ; Thu, 4 May 2000 20:06:32 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA50562; Thu, 4 May 2000 21:06:28 -0600 (MDT) (envelope-from ken) Date: Thu, 4 May 2000 21:06:28 -0600 From: "Kenneth D. Merry" To: David Wolfskill Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ch: warning: could not map element source addr... valid element type Message-ID: <20000504210628.A50524@panzer.kdm.org> References: <200005030404.e4344ql31790@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200005030404.e4344ql31790@pau-amma.whistle.com>; from dhw@whistle.com on Tue, May 02, 2000 at 09:04:52PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 02, 2000 at 21:04:52 -0700, David Wolfskill wrote: > But just as I was getting ready to leave the machine room, I glanced up > at the console (which I had inadvertently left on), and I saw a large > quantity fo messages like that in the Subject: -- e.g. > > /kernel: ch: warning: could not map element source address 256d to a > valid element type > > (The address in question rotated among 256d, 512d, 768d, 1280d, 1536d, > 1792d, and 1280d. The changer in question has 7 slots. More below.) From what I can tell, this is exactly what it claims to be. There is an element in the changer that has a source address that doesn't map to any slot, picker, driver or portal we know about. > One of the things it does early on (for example) is issue "chio params" > and "chio status" commands (and parse the results of same) in order to > get a clue as to what the changer thinks its current configuration & status > is. > > With that in mind, here are the results of the commands in question: > > eng-backup# chio params > /dev/ch0: 7 slots, 1 drive, 1 picker > /dev/ch0: current picker: 0 > eng-backup# chio status > picker 0: > slot 0: > slot 1: > slot 2: > slot 3: > slot 4: > slot 5: > slot 6: > drive 0: > eng-backup# > > > The warning messages in question appear to be generated in coincidence > with issuing the latter command ("chio params"). [Basis for this > observation is watching a "tail -f /var/log/message" while issuing the > above sequence of commands.] [ ... ] > ch0 at ahc1 bus 0 target 1 lun 0 > ch0: Removable Changer SCSI-2 device > ch0: Serial Number ADIC910279414 > ch0: 3.300MB/s transfers > ch0: 7 slots, 1 drive, 1 picker, 0 portals Can you send the output of: chio -IS That should give us the internal identifiers claimed for each element, as well as the source address, if any, for each element. (We shouldn't see a source element for the element in question, though, for the same reason you're getting the warning.) It may be that the changer is just saying that the source element in question is valid, when it really isn't. Hopefully the above command will shed some more light on things. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message