Multipathd not starting up properly

Multipathd not starting up properly

[Adam Huffman]

I'm seeing the following messages when I start multipathd:

Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s /block/sda
Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s /block/sdb

Here is the output of multipath -v 3:


load path identifiers cache
#
# all paths in cache :
#
  0:0:0:0 sda 8:0  [ready] Raidtec /JEFF            /0281
  0:0:1:0 sdb 8:16  [ready] Raidtec /JEFF            /0281
cciss!c0d0 blacklisted
dm-0 blacklisted
dm-1 blacklisted
dm-2 blacklisted
fd0 blacklisted
hda blacklisted
md0 blacklisted
ram0 blacklisted
ram10 blacklisted
ram11 blacklisted
ram12 blacklisted
ram13 blacklisted
ram14 blacklisted
ram15 blacklisted
ram1 blacklisted
ram2 blacklisted
ram3 blacklisted
ram4 blacklisted
ram5 blacklisted
ram6 blacklisted
ram7 blacklisted
ram8 blacklisted
ram9 blacklisted
===== path info sda (mask 0x1f) =====
bus = 1
dev_t = 8:0
size = 2929684480
vendor = Raidtec
product = JEFF
rev = 0281
h:b:t:l = 0:0:0:0
tgt_node_name = 0x20000010e9004510
serial = 11900002000010

path checker = readsector0 (internal default)
state = 2
getprio = (null) (internal default)
prio = 1
getuid = /sbin/scsi_id -g -u -s /block/%n (internal default)
error calling out /sbin/scsi_id -g -u -s /block/sda
uid =  (callout)
===== path info sdb (mask 0x1f) =====
bus = 1
dev_t = 8:16
size = 2929684480
vendor = Raidtec
product = JEFF
rev = 0281
h:b:t:l = 0:0:1:0
tgt_node_name = 0x20000010e9004510
serial = 11900002000010

path checker = readsector0 (internal default)
state = 2
getprio = (null) (internal default)
prio = 1
getuid = /sbin/scsi_id -g -u -s /block/%n (internal default)
error calling out /sbin/scsi_id -g -u -s /block/sdb
uid =  (callout)
#
# all paths :
#
  0:0:0:0 sda 8:0 1 [ready] Raidtec /JEFF            /0281
  0:0:1:0 sdb 8:16 1 [ready] Raidtec /JEFF            /0281

I don't seem to be getting anything useful without this call out working.

Any suggestions appreciated.

Adam

Re: Multipathd not starting up properly

[Hannes Reinecke]

Adam Huffman wrote:
> I'm seeing the following messages when I start multipathd:
> 
> Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> /block/sda
> Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> /block/sdb
> 
> Here is the output of multipath -v 3:
> 
> 
[ .. ]
> path checker = readsector0 (internal default)
> state = 2
> getprio = (null) (internal default)
> prio = 1
> getuid = /sbin/scsi_id -g -u -s /block/%n (internal default)
> error calling out /sbin/scsi_id -g -u -s /block/sda

This is your problem. Somehow 'scsi_id' cannot talk to the drive.
Try 'sg_inq /dev/sda' to find out where the problem is.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de

Re: Multipathd not starting up properly

[seth vidal]

On Wed, 2006-08-30 at 09:42 +0200, Hannes Reinecke wrote:
> Adam Huffman wrote:
> > I'm seeing the following messages when I start multipathd:
> > 
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> > /block/sda
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> > /block/sdb
> > 
> > Here is the output of multipath -v 3:
> > 
> > 
> [ .. ]
> > path checker = readsector0 (internal default)
> > state = 2
> > getprio = (null) (internal default)
> > prio = 1
> > getuid = /sbin/scsi_id -g -u -s /block/%n (internal default)
> > error calling out /sbin/scsi_id -g -u -s /block/sda
> 
> This is your problem. Somehow 'scsi_id' cannot talk to the drive.
> Try 'sg_inq /dev/sda' to find out where the problem is.
> 

And this:
 error calling out /sbin/mpath_prio_alua 65:16

Any suggestions on what to look for for that?

-sv

RE: Multipathd not starting up properly

[Brian Geisel]

Hey Seth,

Forewarning: While I've done multipathing for quite some time I am new
to dm, so I'm going on multipathing / SCSI knowledge more than dm
knowledge.  It is possible I may be leading you down the wrong path (no
pun intended).

That being said, I have to assume that /sbin/mpath_prio_alua is issuing
a report target ports groups (SCSI cmd) to determine ALUA priority.  You
may want to issue the "sg_rtpg" command to each of your paths and see if
that is failing anywhere.  That seems to be the rough equivalent of
sending sg_inq when a path seems to be down.

Usually path tests are done with inquiry and/or TUR.  ALUA preference
must be determined from report target port groups.  That will at least
tell you if it's something obvious like old firmware that doesn't
support ALUA (how HP does their new A/A) or a check condition.  -- not
suggesting that's the problem, just giving an example --

FWIW,
Brian

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of seth vidal
Sent: Wednesday, August 30, 2006 8:25 AM
To: device-mapper development
Subject: Re: [dm-devel] Multipathd not starting up properly

On Wed, 2006-08-30 at 09:42 +0200, Hannes Reinecke wrote:
> Adam Huffman wrote:
> > I'm seeing the following messages when I start multipathd:
> > 
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s

> > /block/sda
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s

> > /block/sdb
> > 
> > Here is the output of multipath -v 3:
> > 
> > 
> [ .. ]
> > path checker = readsector0 (internal default)
> > state = 2
> > getprio = (null) (internal default)
> > prio = 1
> > getuid = /sbin/scsi_id -g -u -s /block/%n (internal default)
> > error calling out /sbin/scsi_id -g -u -s /block/sda
> 
> This is your problem. Somehow 'scsi_id' cannot talk to the drive.
> Try 'sg_inq /dev/sda' to find out where the problem is.
> 

And this:
 error calling out /sbin/mpath_prio_alua 65:16

Any suggestions on what to look for for that?

-sv


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Multipathd not starting up properly

[Adam Huffman]

On 30/08/06, Hannes Reinecke <hare@suse.de> wrote:
> Adam Huffman wrote:
> > I'm seeing the following messages when I start multipathd:
> >
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s
> > /block/sda
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s
> > /block/sdb
> >
> > Here is the output of multipath -v 3:
> >
> >
> [ .. ]
> > path checker = readsector0 (internal default)
> > state = 2
> > getprio = (null) (internal default)
> > prio = 1
> > getuid = /sbin/scsi_id -g -u -s /block/%n (internal default)
> > error calling out /sbin/scsi_id -g -u -s /block/sda
>
> This is your problem. Somehow 'scsi_id' cannot talk to the drive.
> Try 'sg_inq /dev/sda' to find out where the problem is.
>

Here's the output of that command:

sg_inq /dev/sda
standard INQUIRY:
  PQual=0  Device_type=0  RMB=0  [ANSI_version=2]  version=0x02
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=1  Resp_data_format=2
  SCCS=0  ACC=0  ALUA=0  3PC=0  Protect=0
  BQue=0  EncServ=1  MultiP=1  MChngr=0  [ACKREQQ=0]  Addr16=0
  [RelAdr=0]  WBus16=0  Sync=0  Linked=0  [TranDis=0]  CmdQue=1
    length=49 (0x31)   Peripheral device type: disk
 Vendor identification: Raidtec
 Product identification: JEFF
 Product revision level: 0281
 Product serial number: 119000020000JEFF

Adam

Re: Multipathd not starting up properly

[David Wysochanski]

Adam Huffman wrote:
> I'm seeing the following messages when I start multipathd:
> 
> Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> /block/sda
> Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> /block/sdb
> 

Does /sbin/scsi_id exist on your system?

Did you try running this manually from the command line?

RE: Multipathd not starting up properly

[Charles Polk]

Is this for me???

Charles R. Polk -           Sr. Systems Engineer
ViON Corporation
Cell: (301) 518-9266 -       Pager: (888) 257.5538
Fax: (202) 342-1404
E-Mail: charles.polk@vion.com
 
http://www.vion.com

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On
Behalf Of David Wysochanski
Sent: Wednesday, August 30, 2006 2:48 PM
To: device-mapper development
Subject: Re: [dm-devel] Multipathd not starting up properly

Adam Huffman wrote:
> I'm seeing the following messages when I start multipathd:
> 
> Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> /block/sda
> Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s 
> /block/sdb
> 

Does /sbin/scsi_id exist on your system?

Did you try running this manually from the command line?

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Multipathd not starting up properly

[Adam Huffman]

On 30/08/06, David Wysochanski <davidw@netapp.com> wrote:
> Adam Huffman wrote:
> > I'm seeing the following messages when I start multipathd:
> >
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s
> > /block/sda
> > Aug 29 19:00:21 multipathd: error calling out /sbin/scsi_id -g -u -s
> > /block/sdb
> >
>
> Does /sbin/scsi_id exist on your system?
>

It does.

> Did you try running this manually from the command line?
>

Here's the output of /sbin/scsi_id -v -g -u -s /block/sda

(I found I had to alter scsi_id.config, to put in the Vendor and Model)

set_options: option 'g'
set_options: option 'u'
set_options: option 's' arg '/block/sda'
scsi_id: target_path /sys/block/sda
scsi_id: class_dev 0x0x8a484b8; class_dev_parent 0x(nil)
create_tmp_dev: (/sys/block/sda)
sysfs_get_attr: /sys/block/sda/dev
get_major_minor: dev value 8:0
create_tmp_dev: tmpdev '/dev/tmp-scsi-maj8-min0-7108'
sysfs_get_attr:
/sys/devices/pci0000:00/0000:00:04.0/0000:06:00.0/0000:07:01.0/host0/target0:0:0/0:0:0:0/vendor
sysfs_get_attr:
/sys/devices/pci0000:00/0000:00:04.0/0000:06:00.0/0000:07:01.0/host0/target0:0:0/0:0:0:0/model
get_file_options: vendor='Raidtec
'; model='JEFF
'
get_file_options: config file line 28: vendor '(null)'; model
'(null)'; options '-b'
get_file_options: no match
get_file_options: config file line 33: vendor 'Raidtec'; model 'JEFF';
options '-g'
get_file_options: matched vendor/model
per_dev_options: option 'g'
scsi_id: per dev options: good 1; page code 0x0; callout ''
scsi_id: buffer unaligned 0x0x8a48808; aligned 0x0x8a48a00
scsi_get_serial: opening /dev/tmp-scsi-maj8-min0-7108
scsi_inquiry: 0:0:0:0 evpd 1, page 0x0
scsi_get_serial: 0:0:0:0: Checking page0

I still get the same error message when starting multipathd, even with
the change to scsi_id.config

Adam