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: Mon, 13 Mar 2006 09:23:00 -0800 [thread overview]
Message-ID: <20060313172300.GA13879@us.ibm.com> (raw)
In-Reply-To: <20060313110046.91886.qmail@web33302.mail.mud.yahoo.com>
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
Also try normal read/write to the devices.
And you should have posted the full dmesg output (that includes all
SCSI and perhaps PCI messages).
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).
If you get this error all the time, you won't be able to send any commands
to the device. Since the device actually showed up (and linux scsi core
device discovery sent at least an INQUIRY to it OK), something else is now
causing it to fail, you need to figure that out.
Depending on results, discussion should probably be moved to
linux-scsi@vger.kernel.org
-- Patrick Mansfield
next prev parent reply other threads:[~2006-03-13 17:23 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 [this message]
2006-03-14 5:03 ` li nux
2006-03-14 17:09 ` Patrick Mansfield
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=20060313172300.GA13879@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.