From: Patrick Mansfield <patmans@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Unable to get INQUIRY vpd 1 page 0x0
Date: Tue, 14 Mar 2006 09:09:16 -0800 [thread overview]
Message-ID: <20060314170916.GA6505@us.ibm.com> (raw)
In-Reply-To: <20060314050311.38998.qmail@web33309.mail.mud.yahoo.com>
On Mon, Mar 13, 2006 at 09:03:11PM -0800, li nux wrote:
> --- Patrick Mansfield <patmans@us.ibm.com> wrote:
>
> > On Mon, Mar 13, 2006 at 03:00:46AM -0800, li nux
> > wrote:
> > > On doing a '/etc/init.d/boot.udev start' or
> > 'multipath
> > > -v2 -d' i get following error for all the devices:
> > >
> > > creating device nodes 0:0:0:0: sg_io failed status
> > 0x0
> > > 0x1 0x0 0x0
> > > 0:0:0:0: Unable to get INQUIRY vpd 1 page 0x0.
> > > 0:0:0:1: sg_io failed status 0x0 0x1 0x0 0x0
> > >
> > > Can somebody have an idea, what i need to correct.
> >
> > You can run scsi_id manually like:
> >
> > scsi_id -g -s /block/sda
> > scsi_id -g -s /block/sdb
> >
> > Or for whatever devices are at 0:0:0:0 and 0:0:0:1
> >
>
> This also gives the same error
> 0:0:0:1: sg_io failed status 0x0 0x1 0x0 0x0
> 0:0:0:1: Unable to get INQUIRY vpd 1 page 0x0.
> error calling out /sbin/scsi_id -g -u -s /block/sda
Where did the "error calling out" come from if you are running scsi_id
from the command line?
> Why it is enquiring page 0x0, vpd enquires from page
> 0x80 or 0x83, right ?
No. See the SCSI SPC spec, vital product data parameters, or look at
scsi_id source code. Page 0 gives a list of the supported vpd pages.
You can override scsi_id to skip page 0, and use vpd page 0x80 or 0x83.
> > Also try normal read/write to the devices.
> >
>
> This works
>
> > And you should have posted the full dmesg output
> > (that includes all
> > SCSI and perhaps PCI messages).
It might help if you supply more information ... also your configuration
and distro.
> > The devices are getting a host status of 1, that is
> > a DID_NO_CONNECT and
> > generally means the initiator could not talk to the
> > target (the linux
> > driver or hardware can't communicate with the disk),
> > it is also used by
> > linux scsi core when it kills IO (like when a device
> > is hot-unplugged
> > while IO is in progress).
>
> You are right, The devices were hot-unplugged and then
> new devices were hot-plugged. But udev should take
> care of these events and should refresh its
> device-name mappings accordingly ?
Yes.
> After a rebooted, new disks under /proc/partitions
> looks like cciss/c0d0p1 etc.
> how should i run scsi_id on these ?
I thought that was what you did above ... I don't know about cciss, and
have never used it.
If this is a problem with the cciss devices, you have to figure it out or
find someone that knows more about them.
I guess they don't support VPD page 0x0, but are failing in a very weird
way.
-- Patrick Mansfield
prev parent reply other threads:[~2006-03-14 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 11:00 Unable to get INQUIRY vpd 1 page 0x0 li nux
2006-03-13 17:23 ` Patrick Mansfield
2006-03-14 5:03 ` li nux
2006-03-14 17:09 ` Patrick Mansfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060314170916.GA6505@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox