Dynamic Root Disk A.3.10.* Release Notes (January 2012)

4. Known Problems and Workarounds
4.1 DRD OE Update Issues
Issue Description – DRD runcmd update-ux fails with local source depots
When executing "
drd runcmd update-ux" on the inactive DRD system image using a directory depot (or
mounted media) that resides on the active system image, the command fails with this error:
ERROR: The expected depot does not exist at "<depot_name>"
Issue Resolution
In order to use a directory depot on the active system image, you will need to install March 2010 or later
versions of DRD, SWM, and SW-DIST products from an OE depot. This must be done before the clone is
created, so the new DRD, SWM, and SW-DIST are on the active system and on the clone.
The following assumes the OE depot is at
/var/depots/1003-DCOE. This must be executed as root:
swinstall -x autoselect_dependencies=false -s /var/depots/1003-DCOE \
DRD SWM SW-DIST PHCO_36525
Issue Description – DRD Updates from multiple-DVD media
DRD updates directly from media require the September 2010 OE (or later) versions of DRD, SWM and SW-DIST
products.
Issue
Resolution
In order to use a media depot to do a DRD update, you will need to first install September 2010 or later
versions of DRD, SWM, and SW-DIST products from the media. This must be done before the clone is created,
so the new DRD, SWM, and SW-DIST are on the active system and on the clone.
To install these products execute a command like to following. This assumes that the first DVD of the September
2010 or later release is mounted to /SD_CDROM.
swinstall -x autoselect_dependencies=false -s /SD_CDROM \
DRD SWM SW-DIST PHCO_36525
Now you can create the clone, then perform an oe update from media on the clone.
4.2 Rehosting Issues
Issue Description – drd status reports error on rehosted boot disk
After rehosting a clone disk using "
drd rehost" and booting that disk, running DRD commands may result in
the following error. The new rehosted machine may not recognize the disks that were on the previous system
and which are now specified in the
/var/opt/drd/registry/registry.xml file.
ERROR: Cannot display clone information: either the registry
data is corrupted or there is no clone on the system.
- Could not display the clone information.
- The disk "/dev/disk/disk12" cannot be associated with
a disk with an EFI partition.
- The command "/usr/sbin/diskinfo/dev/rdisk/disk12_p1"