欢迎光临我的博客

日志

关于我

lsxblog

文章分类

LOFTER精选

八招诀窍，教你实力撩妹 >

网易考拉推荐

GACHA精选

Logical Drive Not On Preferred Path

2010-05-07 16:08:34| 分类：存储 | 标签： |举报 |字号大中小订阅

下载LOFTER 我的照片书 |

ibm ds4300多路径消失

Details

Storage Subsystem:
Preferred owner: Controller in slot B
Current owner: Controller in slot A
Affected array: 1
Logical Drive: 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30

Logical Drive Not On Preferred Path

What Caused the Problem?

There is a problem accessing the controller listed in the Recovery Guru Details Area. Any logical drives that have this controller assigned as their preferred path will be moved to the non-preferred path (alternate controller). This procedure will help you pinpoint the problem along the data path. Because the logical drives will be moved to the alternate controller, they should still be accessible. Therefore, no action is required on the individual logical drives.

Possible causes include:

The controller failed a manually initiated diagnostic test and was placed Offline.
The controller was manually placed Offline using the Advanced>>Recovery>>Place Controller>>Offline menu option.
There are disconnected or faulty cables.
A Hub or Fabric switch is not functioning properly.
A host adapter has failed.
The storage subsystem contains a defective RAID controller.

The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution
Do not replace the controller until you are instructed to do so. This procedure will instruct you to check the components along the connection, check the host adapters, and eventually instruct you to replace the controller, if necessary.

Caution
Electrostatic discharge can damage sensitive components. Use a grounding wrist strap or other anti-static precautions before removing or handling components.

Important Notes

When Auto Logical Drive Transfer (ADT) is enabled, it can take several minutes for the host-based, multi-path failover driver to recognize a restored or modified preferred path (use the Storage Subsystem Profile to determine whether you have ADT enabled on a mapped host; see Step 9 below). A Logical Drive Not On Preferred Path error will be reported during this time. If you have recently modified the preferred path using the Array>>Change>>Ownership/Preferred Path or Logical Drive>>Change>>Ownership/Preferred Path menu options or performed a recovery procedure that has restored a preferred path, wait at least 10 minutes and run the Recovery Guru again using the Recheck button. If this error is reported again, perform the recovery procedures listed below.
Not all models of storage subsystems contain batteries. If your storage subsystem does not contain batteries, you can ignore any references to them in the following steps. To determine if your storage subsystem contains batteries, use the Storage Subsystem>>View Profile option and select the Enclosures tab. Storage Subsystems without batteries will not have those components listed.
If the controllers for this storage subsystem are located in an enclosure containing both controllers and drives, you may have to insert the battery from the old controller canister into the new replacement controller canister. Consult the following steps and your hardware documentation for details.

Recovery Steps

1

If...

Then...

The controller was manually placed Offline

Place the controller back Online by highlighting the controller in the Physical View of the Subsystem Management Window and selecting Advanced>>Recovery>>Place Controller>>Online.

Go to Step 9.

The controller was NOT manually placed Offline

Go to Step 2.

2

Check the following components on both ends of the connection for loose connections or visible damage:

External cables
Hubs and switches

If...	Then...
The connection components are OK	Go to Step 3.
There is a problem with the connection	Fix the connection problem. Then, go to Step 8.

3

Use the information in the following table to determine the action to take.

If...

Then...

The host connected to this storage subsystem is NOT connected to any other storage subsystems

Verify that its host adapter is operational.

If the host adapter is operational, the controller in the storage subsystem is probably defective. Go to Step 4.
If the host adapter is defective, correct the problem, then go to Step 8.

The host connected to this storage subsystem is connected to other storage subsystems

Check the Enterprise Management Window for storage subsystems showing a Needs Attention status.

If one or more storage subsystems connected to this host/host adapter does not have a Needs Attention status, then the controller in the storage subsystem is probably defective. Go to Step 4.
If every storage subsystem connected to this host/host adapter has a Needs Attention status, then the associated host adapter is probably defective. Fix the host adapter problem, then go to Step 8.

4

Remove the defective controller. The defective controller (A or B) is listed in the Recovery Guru Details area.

Note: Before you insert a new controller canister into an Out-of-Band Managed Storage Subsystem (refer to the Network Management Type column in the Enterprise Management Window), you must update the DHCP/BOOTP server so that it will associate the new controller's hardware Ethernet address with the host name and IP address previously assigned to the removed controller.

To update the DHCP/BOOTP server, find the entry associated with the removed controller and replace its Ethernet address with the new controller's Ethernet address. The controller's Ethernet address is located on an Ethernet ID label on the controller canister in the form xx.xx.xx.xx.xx.xx. If you need more details, consult the Storage System Planning Guide.

5

If...

Then...

The controllers for this storage subsystem are located in an enclosure containing both controllers and drives

Check to see if the new controller canister contains a battery.

If your model of storage subsystem does not contain batteries, go to Step 6.
If your model of storage subsystem is supposed to contain batteries and...
- there is not a battery installed in the new controller canister, then install the battery from the old canister and go to Step 6.
- there is a battery installed in the new controller canister, then go to Step 6.

The controllers for this storage subsystem are located in an enclosure containing only controllers

Go to Step 6.

6

Make sure at least 1 minute has elapsed. Then, insert the new controller canister firmly into place.

Note the controller slot (A or B) of the affected controller listed in the Recovery Guru Details area. Highlight this controller slot in the Physical View of the Subsystem Management Window.

If...	Then...
The controller indicates that it is Active/Optimal	Go to Step 7.
The controller indicates that is Offline	Select Advanced>>Recovery>>Place Controller>>Online and then go to Step 7.

7

If...

Then...

The controllers for this storage subsystem are located in an enclosure containing both controllers and drives

Determine whether you need to reset the battery age.

If your model of storage subsystem does not contain batteries, go to Step 9.
If your model of storage subsystem is supposed to contain batteries and...
- you installed the battery from the old controller canister, then you don't need to reset the battery age. Go to Step 9.
- there was already a battery in the new replacement controller canister, then you must reset the battery age using the following procedure:

Select the Components button on the enclosure containing the controllers in the Physical View of the Subsystem Management Window. Highlight the Batteries option and select the Reset button associated with the new controller canister (A or B). Then, go to Step 9.

The controllers for this storage subsystem are located in an enclosure containing only controllers

Go to Step 9.

8

Note the controller slot (A or B) of the affected controller listed in the Recovery Guru Details area. Highlight this controller slot in the Physical View of the Subsystem Management Window.

If...	Then...
The controller indicates that it is Active/Optimal	Go to Step 9.
The controller indicates that is Offline	Select Advanced>>Recovery>>Place Controller>>Online and then go to step 9.

9

If you have logical drives mapped to hosts that have Automatic Logical Drive Transfer (ADT) disabled, it may be necessary to redistribute the logical drives to their preferred controller. Use the following steps to determine the ADT status of the hosts connected to your storage subsystem:

a

Open the Storage Subsystem Profile by selecting the Storage Subsystem>>View Profile menu option from the Subsystem Management Window. Then, select the profile's Mappings tab.

b

Scroll to the NVSRAM Host Type Internal Definitions section.

c

If...

Then...

There are hosts mapped to logical drives on this storage subsystem that have an ADT status of disabled

OR

There are hosts mapped to logical drives on this storage subsystem that are not running a host-based, multi-path failover driver

It may be necessary to redistribute the logical drives to their preferred controller. If the Subsystem Management Window's Advanced>>Recovery>>Redistribute Logical Drives menu option is available, select the option.

Note: If you have a mix of hosts with ADT enabled and ADT disabled, all logical drives will be immediately assigned back to their preferred path. However, until the host-based, multi-path failover driver detects the valid preferred path (may take several minutes), the logical drives mapped to the ADT-enabled hosts may get temporarily returned back to the non-preferred path.

If the menu option is not available (grayed out), the logical drives are already associated with their preferred controllers and no action is needed.

Go to Step 10.

There are NO hosts mapped to logical drives on this storage subsystem with an ADT status of disabled

AND

All hosts mapped to logical drives on this storage subsystem are running a host-based, multi-path failover driver

No action is required.

If logical drives need to be redistributed to their preferred controller, the host-based, multi-path failover driver will automatically initiate the transfer.

Note that detection of a restored preferred path by the multi-path failover driver can take several minutes.

Go to Step 10.

10

Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed.

If...

Then...

Another type of failure is reported in the Summary area

Follow the recovery procedures given for that failure.

No failures are reported are reported in the Summary area

You are finished with the recovery procedure.

Note: If you replaced the controller and the file systems/logical drives do not respond, reboot your host.

评论这张

转发至微博

阅读(2553)| 评论(0)

推荐转载

历史上的今天

在LOFTER的更多文章

this.p={  m:2,
              b:2,
              loftPermalink:'',
              id:'fks_080069080084081064083085081095080094082069092080086064',
              blogTitle:'Logical Drive Not On Preferred Path ',
              blogAbstract:'<H2\>ibm ds4300多路径消失</H2\>\r\n<H2\>Details</H2\>Storage Subsystem: <BR\>Preferred owner: Controller in slot B<BR\>Current owner: Controller in slot A<BR\>Affected array: 1<BR\>Logical Drive: 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30<BR\>\r\n<P\></P\>\r\n<H1\>Logical Drive Not On Preferred Path </H1\>\r\n<H2\>What Caused the Problem? </H2\>\r\n<P\>There is a problem accessing the controller listed in the Recovery</P\>',
              blogTag:'',
              blogUrl:'blog/static/483686032010474834903',
              isPublished:1,
              istop:false,
              type:0,
              modifyTime:0,
              publishTime:1273219714903,
              permalink:'blog/static/483686032010474834903',
              commentCount:0,
              mainCommentCount:0,
              recommendCount:0,
              bsrk:-100,
              publisherId:0,
              recomBlogHome:false,
              currentRecomBlog:false,
              attachmentsFileIds:[],
              vote:{},
              groupInfo:{},
              friendstatus:'none',
              followstatus:'unFollow',
              pubSucc:'',
              visitorProvince:'',
              visitorCity:'',
              visitorNewUser:false,
              postAddInfo:{},
              mset:'000',
              mcon:'',
              srk:-100,
              remindgoodnightblog:false,
              isBlackVisitor:false,
              isShowYodaoAd:false,
              hostIntro:'',
              hmcon:'1',
              selfRecomBlogCount:'0',
              lofter_single:'<iframe width="140" height="560" style="overflow:hidden;" src="http://www.lofter.com/mailEntry.do?blogad=1&blog" frameBorder="0"></iframe>'
            }

{list a as x}
    {if !!x}
    <div class="iblock nbw-fce nbw-f40">
      <a class="fc03 noul" target="_blank" hidefocus="true" href="http://blog.163.com/${x.visitorName}/">
      {if x.visitorName==visitor.userName}
      <img alt="${x.visitorNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.visitorName)}&r=${visitor.imageUpdateTime}"/>
      {else}
      <img alt="${x.visitorNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.visitorName)}"/>
      {/if}
      </a>
      <div class="cwd vname thide">
        {if x.moveFrom=='wap'}
          <a class="noul pnt" target="_blank" href="http://blog.163.com/services/wapblog.html?frompersonalbloghome"><span title="来自网易手机博客" class="iblock wapIcon"> </span></a>
        {elseif x.moveFrom=='iphone'}
          <a class="noul pnt" target="_blank"><span title="来自iPhone客户端" class="iblock iphoneIcon"> </span></a>
        {elseif x.moveFrom=='android'}
          <a class="noul pnt" target="_blank"><span title="来自Android客户端" class="iblock androidIcon"> </span></a>
        {elseif x.moveFrom=='mobile'}
          <a class="noul pnt" target="_blank" href="http://blog.163.com/services/emsblog.html?frompersonalbloghome"><span title="来自网易短信写博" class="iblock wapIcon"> </span></a>
        {/if}
        <a class="fc03 m2a"  target="_blank" hidefocus="true" href="http://blog.163.com/${x.visitorName}/">
          ${fn(x.visitorNickname,8)|escape}
        </a>
      </div>
    </div>
    {/if}
    {/list}

<#--最新日志，群博日志--> <#--推荐日志-->

<p class="fc06">推荐过这篇日志的人：</p>
    <div>
      {list a as x}
      {if !!x}
      <div class="iblock nbw-fce nbw-f40">
        <a class="fc03 noul" target="_blank" hidefocus="true" href="http://blog.163.com/${x.recommenderName}/">
        <img alt="${x.recommenderNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.recommenderName)}"/>
        </a>
        <div class="cwd thide">
          <a class="fc03 m2a" target="_blank" hidefocus="true" href="http://blog.163.com/${x.recommenderName}/">
            ${fn(x.recommenderNickname,6)|escape}
          </a>
        </div>
      </div>
      {/if}
      {/list}
    </div>
    {if !!b&&b.length>0}
    <p  class="fc06">他们还推荐了：</p>
    <ul>
    {list b as y}
      {if !!y}
        <li class="rrb"><span class="iblock">·</span><a class="fc03 m2a" target="_blank" href="http://blog.163.com/${y.recommendBlogPermalink}/?from=blog/static/483686032010474834903">${y.recommendBlogTitle|escape}</a></li>
      {/if}
    {/list}
    </ul>
    {/if}

<#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇，下一篇--> <#-- 热度 -->

{list a as x}
    {if !!x}
    <div class="hotItem iblock nbw-fce nbw-f40">
      <a class="fc03 noul" target="_blank" hidefocus="true" href="http://blog.163.com/${x.publisherUsername}/">
      {if x.publisherUsername==visitor.userName}
      <img alt="${x.publisherNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.publisherUsername)}&r=${visitor.imageUpdateTime}"/>
      {else}
      <img alt="${x.publisherNickname|escape}" onerror="this.src=location.f40" class="cwd bdwa bdc0" src="${fn1(x.publisherUsername)}"/>
      {/if}
      </a>
      <div class="cwd vname thide">
        <a class="fc03 m2a"  target="_blank" hidefocus="true" href="http://blog.163.com/${x.publisherUsername}/">
          ${fn(x.publisherNickname,8)|escape}
        </a>
      </div>
      <a class="f-myLikeIcons hottype {if x.type==1} js-liketype{elseif x.type==2} js-reblogtype{elseif x.type==3} js-sharetype{else}{/if}" target="_blank" hidefocus="true" href="http://blog.163.com/${x.publisherUsername}/"> </a>
    </div>
    {/if}
    {/list}

<#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->

页脚

我的照片书 - 博客风格 - 手机博客 - 下载LOFTER APP - 订阅此博客

欢迎光临我的博客

导航

日志

Logical Drive Not On Preferred Path

ibm ds4300多路径消失

Details

Logical Drive Not On Preferred Path

What Caused the Problem?

Important Notes

Recovery Steps

历史上的今天

最近读者

热度

在LOFTER的更多文章

评论

页脚