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

List:       hpux-admin
Subject:    [HPADM] Adding disk: device driver missing
From:       "Shaw, Marco" <Marco.Shaw () aliant ! ca>
Date:       2008-09-24 14:00:39
Message-ID: B708C920604DF74A9B259056B737AD8903984BB2 () nbexmb04 ! aliant ! icn
[Download RAW message or body]

Recently had some disks added via our SAN.

 

Ioscan shows the new disk, but it appears device drivers haven't been
created.

 

Oddly enough, it seems that in our lab, a disk device driver was created
in one of the two boxes without problems.  I even tried rebooting the
one where the disk driver is still missing, but that didn't fix
anything.

 

"ioscan -fnC disk" reports:

Good:

disk     20  0/6/1/0/4/0.27.0.0.0.2.7  sdisk      CLAIMED     DEVICE
EMC     SYMMETRIX

                            /dev/dsk/c9t2d7   /dev/rdsk/c9t2d7

Bad:

disk     22  0/6/1/0/4/0.27.0.0.1.0.6  sdisk      CLAIMED     DEVICE
EMC     SYMMETRIX

 

Both production machines show the "bad" output above.  They haven't been
rebooted though.

 

I shouldn't need to make any kernel changes?  Maybe I can create the
disk device drivers manually?

 

Is there a "magic formula" to determining the cXtXdX value?  The target
in particular and disk in particular.

 

Marco

 

 


[Attachment #3 (text/html)]

<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal>Recently had some disks added via our SAN.<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Ioscan shows the new disk, but it appears device drivers
haven&#8217;t been created.<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Oddly enough, it seems that in our lab, a disk device driver
was created in one of the two boxes without problems.&nbsp; I even tried rebooting
the one where the disk driver is still missing, but that didn&#8217;t fix
anything.<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>&#8220;ioscan &#8211;fnC disk&#8221; reports:<o:p></o:p></p>

<p class=MsoNormal>Good:<o:p></o:p></p>

<p class=MsoNormal>disk&nbsp;&nbsp;&nbsp;&nbsp; 20&nbsp;
0/6/1/0/4/0.27.0.0.0.2.7&nbsp; sdisk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
CLAIMED&nbsp;&nbsp;&nbsp;&nbsp; DEVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
EMC&nbsp;&nbsp;&nbsp;&nbsp; SYMMETRIX<o:p></o:p></p>

<p class=MsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;& \
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 <span lang=FR-CA>/dev/dsk/c9t2d7&nbsp;&nbsp; /dev/rdsk/c9t2d7<o:p></o:p></span></p>

<p class=MsoNormal>Bad:<o:p></o:p></p>

<p class=MsoNormal>disk&nbsp;&nbsp;&nbsp;&nbsp; 22&nbsp;
0/6/1/0/4/0.27.0.0.1.0.6&nbsp; sdisk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
CLAIMED&nbsp;&nbsp;&nbsp;&nbsp; DEVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
EMC&nbsp;&nbsp;&nbsp;&nbsp; SYMMETRIX<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Both production machines show the &#8220;bad&#8221; output
above.&nbsp; They haven&#8217;t been rebooted though.<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>I shouldn&#8217;t need to make any kernel changes?&nbsp; Maybe
I can create the disk device drivers manually?<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Is there a &#8220;magic formula&#8221; to determining the
cXtXdX value?&nbsp; The target in particular and disk in particular.<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Marco<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>


--
             ---> 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] 

Configure | About | News | Add a list | Sponsored by KoreLogic