Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1600545.1
Update Date:2017-11-02
Keywords:

Solution Type  Problem Resolution Sure

Solution  1600545.1 :   Cannot Mirror Volume After It Cracked - nbd: Could not locate nbd connected disk for dasd id  


Related Items
  • Sun Storage 5310 NAS Gateway System
  •  
  • Sun Storage 5210 NAS Appliance
  •  
  • Sun Storage 5310 NAS Appliance
  •  
  • Sun Storage 5320 NAS Appliance
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: SE5xxx NAS
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-7947792851>

Applies to:

Sun Storage 5310 NAS Appliance - Version All Versions and later
Sun Storage 5210 NAS Appliance - Version All Versions and later
Sun Storage 5310 NAS Gateway System - Version All Versions and later
Sun Storage 5320 NAS Appliance - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Unable to re-mirror volume after it cracked

We have primary NAS <source> with volume <volume name> and this was mirrored to NAS <target>.

After the mirror broke or "cracked" .  The mirror was deleted and then a re-mirror was attempted via GUI but this failed with the following status:

'Unable to attach parts'.

and

Error seen in the syslogs:

    nbd: Could not locate nbd connected disk for dasd id xxxx

 
Via the GUI:

    Unable to attach parts


Also if you deleted the mirror set on the <source>  and deleted the mirror volume on <target> and then tried to re-mirror the same error occured.

Note that the following message in the system events log  'nbd: Could not locate nbd connected disk for dasd id xxxx.

Other symptoms : On the <source> the volume is composed of two partitions of xxxMB and xxxMB. Before deleting  the mirror volume on the <target> NAS it was identical to the <source> NAS i.e. two partitions.

Now you can see only one xxxxMB partition <target>.  The other partition that was part of the volume shows as being 'free to allocate'.



Cause

The target had "stale " data about the mirror volume in question.

Solution

The mirror was successfully re-made after a reboot of the target NAS

 

*** Currency check - 03-JUN-2015 ***

*** Currency check - 02-NOV-2017 ***

References

<BUG:17719849> - CANNOT MIRROR VOLUME - COULD NOT LOCATE NBD CONNECTED DISK FOR DASD ID

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback