'ResB RTTnLogMessages100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216218219220222223224225226227231234235244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323325326327328329330331332333336337339340341342343344345346347348349350352353354355356357358359360361362363364365366367369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402404405406407408409410411412413414415416417418419420422424426427428429430431432433435436438440441443445446447448449450451452453454455456457458459460461462463464466467468469470471472473474475476477478479480481483485486487488489490491492493494495496497498500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533535537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573575577578579580581582583584585586587588589590591592593594595596597598599600601602603606607608609610611612613614615616617618619620621622623624625626628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788790791793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083{0}{1}{0}{1}{2}Not ManagedVxVM ManagedTest Message{0}{1}{2}{3}Invalid inputInsert a disk.Format failed.Network adapter{0}{1}{2}{3}{4}Internal error.Invalid disk ID.DVD/CD-ROM driveInvalid plex ID.Adding mirror...Formatting {0}...{0}() failed: {1}Floppy disk driveFormat completed.Invalid region ID.Creating volume...Enter SRT location{0}{1}{2}{3}{4}{5}OEM Drivers by {0}Invalid volume ID.Creating volume {0}Unknown device classCannot quick format.putenv() failed: {0}{0}({1}) failed: {2}VxVM hostid is empty.{0}{1}{2}{3}{4}{5}{6}Unpacking miniroot...Repacking miniroot...Invalid disk group ID.Virtual network driverFloppy disk controllerNative Windows DriversUnknown attribute {0}.Invalid {0} value {1}.Volume is not mirrored.External Procedure: {0}Invalid mount point ID.Could not split mirror.IDE ATA/ATAPI controllerInternal database error.SCSI and RAID controllerInvalid pointer to disk.Please enter a response.Quick formatting volume.Could not delete volume.Could not create volume.Could not extend volume.Operation not supported.No length was specified.No disks were specified.error closing "{0}": {1}{0}{1}{2}{3}{4}{5}{6}{7}Encapsulating disk {0}...Zfs volume {0} not found.Failed to configure VxVM.Could not read disk file.No target disk specified.Could not initialize COM.Internal parameter error.Could not enumerate disks.No override was specified.Hardware abstraction layerNo slice number specified.No product name specified.Unknown resource type {0}.Zfs volume {0} not mapped.Option "-{0}" is ambiguous.Failed to create partition.Disk {0} is already in use.error writing to "{0}": {1}Could not encapsulate disk.Unrecogized /dev path: {0}.Storage pool {0} not found.No disk name was specified.{0}{1}{2}{3}{4}{5}{6}{7}{8}Failure creating volume {0}.Please answer "yes" or "no".Failed to start NFS service.Could not enumerate volumes.No slice name was specified.The inf file {0} is missing.File system cannot be added.Fail to modify SRT Registry.No volume name was specified.Error reading from "{0}": {1}unable to scrub configurationDid not find any disk groups.Disk set {0} cannot be added.Zfs filesystem {0} not found.Began formatting destination.Invalid working configuration."Unknown role type requested."ZFS Storagepool {0} not mapped{0}{1}{2}{3}{4}{5}{6}{7}{8}{9}Unable to create directory {0}Cannot determine disk io size.The media cannot be formatted.No volume group was specified.No disk specified for mapping.Could not get etc/filesystems.Could not assign drive letter.Unsupported Linux release: {0}Could not query LDM interface.Device type must be specified.ZFS volume {0} already exists.Could not create LDM instance.unable to verify configurationNo partition name was specifiedCannot retrieve size from "{0}"Could not label Linux disk {0}.No length or percent specified.Failed to import volume groups.Partition length cannot be zeroConverting disk {0} to basic...No disk set name was specified.Please specify a volume layout.Could not set active partition.No partition type was specifiedFailed to pack slices together.Could not get LDM class object.Could not find the boot device.Cannot determine volume io size.Failed to create disk group {0}.error reading symlink "{0}": {1}Unknown option "-{0}" specified.No partition name was specified.Multidisk selection not allowed.Invalid HPUX partition specifiedCould not unassign drive letter.Invalid volume layout, id = {0}.Could not find Solaris disk {0}.Could not create Linux disk {0}.Cannot open "{0}" for input: {1}Could not delete basic partition.Volume group {0} cannot be added.Failed to create LVM disk groups.No disk group name was specified.Could not enumerate file systems.Cannot find a disk with id = {0}.A volume named {0} already existsNo filesystem name was specified.Could not enumerate disk regions.Could not enumerate access paths.Converting disk {0} to dynamic...cannot open "{0}" for output: {1}No metadevice name was specified.Raid5 volumes cannot have copies.Failed to create all disk groups.Cannot rename "{0}" to "{1}": {2}No file system type was specified.Could not enumerate drive letters.unable to parse client informationNo partition identifier specified.Failure packing subdisks together.Error reading input from pipe: {0}Could not connect to SFW interfaceNo multidevice name was specified.File contents missing for file {0}Cannot create directory "{0}": {1}ZFS Filesystem {0} already mapped.Could not discover disks--rc({0}).Unable to create multi device {0}.Disk {0} is not in disk group {1}.Failed to create SVM disk set {0}.Cannot retrieve Linux device name.Failed to create VxVM disk groups.Error while creating partition mapNo storage pool name was specified.Could not enumerate volume members.Failed to create ZFS storage pools.Failed to create AIX volume groups.Formatting is {0} percent complete.Slice number {0} is already in use.Could not add access path, path={0}Could not discover plexes--rc({0}).No multidevice level was specified.No volume group name was specified.No physical volumes were specified.Logical volume {0} cannot be added.Unrecognized volume type or layout.The volume length was not specifed.Cannot create Linux mount point {0}.The system volume cannot be removed.Poorly formed mount point, path={0}.Volume layout {0} is not recognized.File system type {0} not recognized.A disk set named {0} already exists.Unable to locate disk for slice {0}.Failed to get NetBackup Server Name.Could not create logical volume {0}.Could not get the IP address for {0}Could not create Linux partition {0}Failed to create LVM disk group {0}.Could not get partition information.Cannot lock the disk for formatting.I/O error occurred while formatting.The file system type {0} is invalid.unable to process package file list.Cannot copy file "{0}" to "{1}": {2}No disk specified when adding slice.Unable to restore Linux boot loader.Could not find a Solaris boot slice.Cannot find volume group. - vgId {0}Failed to create extended partition.Could not open disk file, device={0}Cannot find a Linux disk for id {0}.Could not recreate volumes--rc({0}).Could not discover volumes--rc({0}).The volume layout was not specified.Must specify attribute {0} with {1}.Could not format drive {0}--rc({1}).Waiting for Network installation ...Cannot set quota for storage pool {0}Partition {0} should be mapped first.No partition identifier was specifiedCould not add a mirror to the volume.No logical volume name was specified.No hot spare pool name was specified.No soft partition name was specified.Volume {0} already has a file system.Waiting to connect to disk manager...Disk {0} is not part of disk set {1}.No Config class in parse client info.Could not get VCS directory, rc = {0}Could not save dmsetup command outputunable to process Package uniqueness.Could not run command ({0})--rc({1}).Could not discover subdisks--rc({0}).Boot Image file "{0}" does not exist.Parent Zfs filesystem {0} not mapped.Cannot find logical volume. - lvId {0}Failed to create SVM volume, id = {0}.The disk denied access for formatting.Cannot specify attribute {0} with {1}.Unknown volume layout specified - {0}.Failed to initialize SVM disk set {0}.The disk set named {0} does not exist.Could not create boot volume--rc({0}).No length specified when adding slice.Could not open inf file {0}, rc = {1}.Volume {0} already has a drive letter.A metadevice named {0} already exists.A disk group named {0} already exists.unable to extract file {0} from bundleCould not query partition information.Could not write partition information.Could not delete access path, path={0}Slice, {0}, already has a file system.Encapsulation task was not successful.Could not find disk for partition {0}.{0} should be mapped onto the {1} diskFailed to create disk group, name={0}.No physical extent size was specified.No physical volume name was specified.Bad label given to the format command.Could not deport disk group, name={0}.EA Format value can be either v1 or v2.Choose ''Cancel'' to halt the restore. Failed to create logical volume id {0}.Could not save multipath command outputCould not find Solaris native disk {0}.Could not import disk (group), disk={0}unable to move/delete config for clientThe partition {0} could not be removed.Only dynamic disks can be encapsulated.No database replica name was specified.Could not convert disk to a basic disk.Path to the install media is not valid.The basic disk group cannot be deleted.Could not recreate disk groups--rc({0}).Disk {0} is already in another disk set.Could not discover disk groups--rc({0}).Operation failed due to network problem.Synchronization is {0} percent complete.The metadevice named {0} does not exist.The network interface was not specified.A volume group named {0} already exists.A storage pool named {0} already exists.Device {0} was specified more than once.)Disk does not have an extended partition.)Boot Image {0} verification unsuccessful.)WARNING - in.rarpd is not running on {0}.)Could not discover file systems--rc({0}).)Could not discover mount points--rc({0}).)Raid5 layout must have 3 or more columns.)Could not save cryptsetup command output.)Could not discover license keys--rc({0}).)Could not create boot partition--rc({0}).)Original partition {0} is already mapped.)System volume not found in configuration.)Could not convert disk to a dynamic disk.)The volume for subdisk {0} was not found.)Unable to restore all Linux file systems.)The specified device, {0}, was not found.)Unable to get Boot Image {0} Information.)Unable to restore all Linux mount points.)The configuration is missing information.)No components found for multi device {0}.)Could not recreate file systems--rc({0}).)Could not format boot drive {0}--rc({1}).)Cannot create Linux LVM volume group {0}.)Disk {0} already has an active partition.*Cannot specify both slice name and number.*Skipping non-system critical disk set {0}.*Disk set not found that contains disk {0}.*configuration does not contain system data*Unable to get NetBackup Master information*Could not create Linux file system id {0}.*A logical volume named {0} already exists.*The specified package, {0}, was not found.*Failed to create SVM volumes or disk sets.*The specified resource, {0}, is not valid.*Could not remove a mirror from the volume.*Operation map disk resource not supported.*unable to read Xml data into CBmrDb object*A soft partition named {0} already exists.*Partition {0} should be mapped before {1}.*A volume mounted on {0} cannot be striped.*A hot spare pool named {0} already exists.+At least one hardware ID must be specified.+Could not query database for package table.+Could not create Linux physical volume {0}.+Failed to create volumes on Solaris slices.+Malformed header - Missing ExitCode string.+Partition {0} should be mapped on disk {1}.+Plex {0} is not associated with volume {1}.+Cannot find a plex for SVM volume id = {0}.+Name PnPInstanceID Description Type Enabled+Cannot find a Linux file system for id {0}.+Cannot set reservation for storage pool {0}+Requested disk {0} is read-only restricted.,{0} received an unknown exception. Halting..,Could not create Linux LVM volume group {0}.,Old style inf files ({0}) are not supported.,WARNING - inetd tftpd is not running on {0}.,Could not write the mklv command. - lvId {0},Could not write the chlv command. - lvId {0},Mount point {0} is not in the configuration.,The slice, {0}, is not in the configuration.,Could not write the mkfs command. - fsId {0},Failed to write commands to format disk {0}.,The specified slice, {0}, is already in use.,Cannot find a subdisk for SVM plex id = {0}.,Could not discover ZFS information--rc({0}).,Could not discover SVM information--rc({0}).,Unrestricting DMP disk {0} is not supported.,Unable to restore all Linux logical volumes.,Discovered OEM ({0}) drivers from client {1},Could not query database for override table.,Could not print VTOC in {0} at {1}--rc({2}).,Attribute ''{0}'' can only be provided once.,Could not get system root, error code = {0}.,Could not write the chvg command. - vgId {0},ZFS Storagepool for volume {0} is not mapped,Failed to write the chvg command. - vgId {0},Could not get logical volume pbuf attribute.-The file system type is required to find {0}.-Operation remove disk resource not supported.-No device(s) for storage pool were specified.-Cannot find a slice for SVM subdisk id = {0}.-Failed to set the host list for disk set {0}.-Failed to mount volumes for SVM disk set {0}.-Failed to set the disk list for disk set {0}.-Failed to write the chmod command. - mpId {0}-Unable to build up available disk space list.-Cannot find native disk name for disk id {0}.-Driver file {0} is not on the running system.-Could not get Windows root, error code = {0}.-Incorrect format of disk attribute, value={0}-ZFS root pool cannot have seperate log device-Failed to write the chown command. - mpId {0}-Failed to write the mount command. - mpId {0}-ZFS Storagepool not mapped for filesystem {0}-Cannot create container for logical partition-Could not add Solaris disk for partition {0}.-Disk {0} is in use by another volume manager.-Could not find free region on disk, disk={0}.-Could not match volume with a current volume.-Could not find disk {0} in the configuration.-Could not find {0} which is referenced in {1}-Cannot find the soft partition with id = {0}..No multidevice component device was specified..Unrestricting iSCSI disk {0} is not supported..Operation is not available with this resource..Getting network adapters info failed, rc = {0}.Slice {0} is in use by another volume manager..The disk is read-only and cannot be formatted..Null pointer passed to function in {0} at {1}..Could not save st.conf in {0} at {1}--rc({2})..Boot Image {0} has been successfully verified..Could not save sg.conf in {0} at {1}--rc({2})..Could not save sd.conf in {0} at {1}--rc({2})..Failed to create volumes for SVM disk set {0}..Mapping is not supported for disabled devices..License key, {0}, is not in the configuration..Could not discover mount information--rc({0})./Unable to load command output for command = {0}/A volume group cannot have more than 128 disks./Could not find multidevice {0} in configuration/Cannot determine the netmask for interface {0}./The boot volume was not found in configuration./Mapping is not defined for extended partitions./Extra devices for striping found on column {0}./Could not discover volume information--rc({0})./An invalid operating system type was specified./WARNING - rpc.bootparamd is not running on {0}./There are no viable layouts that can be mapped./A slice of length {0} will not fit on the disk./Could not update {0}. Name resolution may fail./Cannot find native disk name for disk id = {0}./Failed to adjust length for soft partition {0}./Cannot find the slices for hot spare, id = {0}./Could not create native partitions on disk {0}./Do not know how to handle multi-path disk: {0}./The database length specified, {0}, is too big.0ZFS Filesystem {0} is not mapped, please map it.0Failed to write the importvg command. - vgId {0}0NFS service is not active -- trying to start it.0Cannot find the disk containing the subdisk {0}.0There are no disks assigned to volume group {0}.0The valid operations for resource {0} are: {1}0A volume group cannot have more than 1024 disks.0Use the -name option to specify the license key.0The plex for database replica {0} was not found.0The underlying disk for slice {0} was not found.0Cannot find the volume record for plex id = {0}.0Need {0} disk(s) but only {1} disk(s) specified.0Cannot create Linux file systems on LVM volumes.0Map operation not implemented for this resource.0Cannot find a Linux native partition for id {0}.0Unable to restore all Linux multi device arrays.0Could not add mirror(s) to boot volume--rc({0}).0The {0} attribute is only valid with {1} layout.0Cannot find the plex record for volume id = {0}.0Unable to get Network information for Client {0}1Failed to adjust length for database replica {0}.1Cannot determine Linux distribution of this host.1Driver file {0} is not on the installation media.1The specified resource is not a database replica.1No space left in storage pool {0} for volume {1}.1Could not match requested disks to current disks.1Choose ''No'' to use existing external procedure.1{0} should be mapped as a first partition of {1}.1Unable to get Network information for Client {0}.1Could not find mount point for filesystem id {0}.1A subdisk of length {0} does not fit on disk {1}.1No plex found that is associated with volume {0}.1A swap device was not found in the configuration.1Could not find the Solaris disk on partition {0}.2Cannot find the disk set record for plex id = {0}.2Could not create dynamic volume {0} in {1} at {2}.2No physical volume is selected. Please select one.2unable to extract file {0} from bundle, trying {1}2Failed write commands to mount volumes. - vgId {0}2Could not read /etc/vfstab in {0} at {1}--rc({2}).2Failed to append vfstab with mount point {0} data.2IP address {0} was not found in the configuration.2Boot image {0} does not belong to boot server {1}.2There are no more partitions available on disk {0}2A device type must be specifed for this operation.2Operation is not available for this resource type.2Network interface {0} is not in the configuration.2The volume for database replica {0} was not found.2Could not get SSA adapters in {0} at {1}--rc({2}).2Unable to perform operation on read-only disk {0}.2Linux native partition {0} has no associated disk.2Could not add mirror(s) to system volume--rc({0}).3Could not get Persistent DSF to Legacy DSF mapping.3Error: No interfaces were discovered on the client.3The specified plex, {0}, is not a submirror of {1}.3Unable to perform operation on restricted disk {0}.3The requested volume, {0}, is not a soft partition.3Failed to create file systems for SVM disk set {0}.3Could not find the volume {0} in the configuration.3Cannot find the slice record for sub disk id = {0}.3The subdisk for database replica {0} was not found.3Could not discover disk group information--rc({0}).3Could not create basic partition {0} in {1} at {2}.3Failed write commands to create volumes. - vgId {0}3Could not add mirrors to system volume(s)--rc({0}).3None of the disks specified can hold the partition.4Failed write commands to create volumes. - vgId {0}.4Columns and stripe width must be specified together.4The {0} attributes is only valid with {1} resources.4Command operation not implemented for this resource.4The disks provided cannot hold the specified volume.4Multidevice {0} refers to non-existent partition {1}4Failed to create soft partition using plex id = {0}.4Failed to write commands to create volume. - Id {0}.4Failed to run pntadm command for DHCP configuration.4Failed to install boot programs on disk. - vgId {0}.4Cannot find the disk set record for volume id = {0}.4Could not get service pack level, return code = {0}.4Operation failed due to VxSS authentication failure.4Disk name is not set for diskId = {0} in {1} at {2}.4Could not promote the boot disk to dynamic--rc({0}).4Mount point {0} already exists in the configuration.4Volumes cannot span further than 2TB on an MBR disk.4Linux filesystem id {0} has no associated partition.4Unable to get Config {0} infotmation for Client {1}.4Unable to get the System information for Client {0}.4Could not create device for Linux filesystem id {0}.4Could not discover file system information--rc({0}).4Could not find the file system in the configuration.4A plex named {0} was not found in the configuration.4The requested disk, {0}, does not have an SMI label.4Cannot modify Solaris/Solaris2 active partition {0}.5Not enough space left on {0} for Boot Image creation.5No space left in storage pool {0} for filesystem {1}.5Failed to write commands mount volumes from disk {0}.5Both volume group and disk group cannot be specified.5The DHCP configuration for network {0} was not found.5Cannot find the sub disk record(s) for plex id = {0}.5Could not find the disk set {0} in the configuration.5Could not save powermt output in {0} at {1}--rc({2}).5Failed to write commands to clean VxVM disk id = {0}.5Invalid operation on disk {0}. Last disk in disk set.5The operation, {0} is not supported for resource, {1}5Failed write commands to initialize disk. - vgId {0}.5Could not get SSA connections in {0} at {1}--rc({2}).5Unrecognized RAID level assigned to multi device {0}.5Could not create system critical components--rc({0}).5Choose ''Continue'' to ignore the error and continue.5Could not find disk locations in {0} at {1}--rc({2}).5Volume information is missing from the configuration.5No regions found for volume when removing the mirror.5Could not get Volume Manager version from API, hr={0}6Cannot create Linux file systems on native partitions.6There are no extended partitions available on disk {0}6EFI System Partition size cannot be greater than 32 GB6The specification contains devices of different sizes.6Could not discover physical disk information--rc({0}).6The license key, {0}, is already in the configuration.6Could not get SSA translations in {0} at {1}--rc({2}).6A Big volume group cannot contain more than 128 disks.6Solstice Disk Suite full implementation not supported.6No regions found for disk; The disk ID may be invalid.6Failed to create hot spare pools for SVM disk set {0}.6Could not write the mkvg command for volume group {0}.6Could not write the lvmo command for volume group {0}.6Allocate Boot Image {0} received on wrong boot server.6Cannot find Package installer {0} in the install path.6Could not write physical volume map in RTE. - vgId {0}6Failed to write commands to create file system id {0}.6Unable to modify resync pass on non-mirror volume {0}.6Could not promote the system disk to dynamic--rc({0}).7You must remove this partition''s physical volume first7You cannot activate a partition during a map operation.7Attribute {0} cannot be changed during a map operation.7Removing all volumes and/or partitions from disk {0}...7The specified number of copies must be between 1 and 4.7The working configuration does not have a system entry.7Please provide only slices for ZFS Rootpool {0} mapping7Only primary or logical partitions may be used for LVM.7Not enough disk space available to satisfy the request.7Failed to create SVM database replica for disk set {0}.7The specified disks do not have enough available space.7The path of an existing mount point cannot be modified.7The working configuration does not have a config entry.7Cannot determine disk mapping due to missing arguments.7Could not get file system usage in {0} at {1}--rc({2}).7Could not get HP-UX boot volume in {0} at {1}--rc({2}).7Do you want to try to run the external procedure again?7Could not get fsadm information in {0} at {1}--rc({2}).7Unable to load command output. Command OutputType = {0}7Could not get fstyp information in {0} at {1}--rc({2}).7Could not find the disk group {0} in the configuration.7Network interface {0} does not have the IP address {1}.7Could not find disk partition {0} in the configuration.8Cannot create Linux file systems on multi-device arrays.8Physical volume {0} does not belong to volume group {1}.8The specified package configuration, {0}, was not found.8Physical volume {0} is not a member of volume group {1}.8At least one slice must be specified for this operation.8Cannot find the hot spare pool record for plex id = {0}.8This disk cannot be removed because it contains volumes.8The number of stripe devices on plex {0} does not match.8The gateway {0} could not be found in the configuration.8Failed to write commands to clean Solaris disk id = {0}.8Critical mountpoints are missing from the configuration.8Failed write commands to create file systems. - vgId {0}8Primary configuration object missing from configuration.9The {0} attribute is only valid with {1} and {2} layouts.9Could not find the volume group {0} in the configuration.9Could not find native partition {0} in the configuration.9The specified package is not in the configuration, id={0}9Could not get ZFS pool information in {0} at {1}--rc({2})9Cannot delete disk {0}; at least one partition is in use.9Cannot find space to fit requested partition on disk {0}.9An error occurred while discovering mass storage drivers.9Cannot support more than 15 partitions per disk on Linux.9SRT location already exists. Do you want to overwrite it?9The format for a device attribute has too many arguments.9Could not assign drive letter {0} to volume {1}--rc({2}).9Could not match drive letter with a current drive letter.9Cannot set quota {0} bytes less than used space {1} bytes9Swap slice size cannot be smaller than one disk cylinder.9Transfer External Procedure {0} from NetBackup server? 9Could not collect Veritas Licensing information--rc({0}).9Failed to write commands create file systems on disk {0}.:Failed to write commands to create file system. - fsId {0}:Cannot find any physical volumes for LVM volume group {0}.:Partition id for {0} must be set to 0x8e for use with LVM.:Choose ''Try Again'' to execute External Procedure again. :Could not find crash dump location in {0} at {1}--rc({2}).:Could not find swap space location in {0} at {1}--rc({2}).:Please specify a package name for the requested operation.:Unable to verify/create new slice in target configuration.:A Standard volume group cannot contain more than 32 disks.;The system volume can only be primary, simple, or mirrored.;Failed to add mount point ({0}) id = {1} to the mount list.;Failed to write commands to import volume group. - vgId {0};Failed to modify /tftpboot/menu.lst.{0} for 64-bit support.;Cannot change the number of copies for boot logical volume.;Failed to write commands to create volume group. - vgId {0};The upper bound is not a multiple of the number of columns.;Could not write the varyoffon command for volume group {0}.;Failed to write commands to create swap file system id {0}.;Could not find the logical volume {0} in the configuration.<Could not discover Veritas File System information--rc({0}).<Destination disk {0} is already in use by some volume group.<Disk set {0} was not found in the destination configuration.<Could not get mount point attributes in {0} at {1}--rc({2}).<The specified stripe width is invalid for this configuration<Conflicting information in disk name {0} and disk usage {1}.<The object relationship is invalid for database replica {0}.<The type of a disk cannot be changed during a map operation.<OutputType empty in command output header. Skipping file {0}<The database replica {0} was not found in the configuration.<Cannot change the number of stripes for boot logical volume.<A minimum of 3 devices is required to build a RAID 5 volume.<Could find Windows volume name for volume device, volume={0}<Could not find the physical volume {0} in the configuration.<Cannot find the mount point record for file system id = {0}.=Cannot set reservation {0} bytes greater than quota {1} bytes=Cannot find exactly one disk access record for disk id = {0}.=Failed write commands to initialize volume group. - vgId {0}.=Modification of attribute {0} not supported for resource {1}.=The soft partition, {0}, is already in use by metadevice {1}.=Failed to write commands to create volumes in disk group {0}.=Could not find the volume group for Linux logical volume {0}.=Unable to modify mirror read option on non-mirror volume {0}.=Invalid attempt to initialize the unnamed disk set, id = {0}.=The specified list source attribute value, {0}, is not valid.=Could not get volume group attributes in {0} at {1}--rc({2}).=Could not find the specified zone "{0}" in the configuration.=Failed to write commands to create logical volume. - lvId {0}=Cannot create volume greater than 2TB size on MBR Basic disk.=The specified slice, {0}, was not found in the configuration.=Disk {0} cannot be specified to receive the ''stand'' volume.=Cannot set quota {0} bytes less than reserved space {1} bytes=An error occurred while running the external procedure {0}. =The configuration does not contain exactly one config object.=Could not get physical disk locations in {0} at {1}--rc({2}).=Could not get logical volume mappings in {0} at {1}--rc({2}).>Permission may only be one of read-only, read-write, ro, or rw>Could not get SVM database information in {0} at {1}--rc({2}).>The layout of volume {0} cannot hold the boot partition files.>Please specify a package resource for the requested operation.>This disk group cannot be removed because it contains volumes.>Disk cannot be converted to basic because it contains volumes.>The boot volume cannot reside on a spanned or extended volume.>Could not get location for system dump in {0} at {1}--rc({2}).>A hot spare pool named {0} was not found in the configuration.>The specified volume, {0}, was not found in the configuration.>Could not get active mount information in {0} at {1}--rc({2}).>Unable to modify mirror write option on non-mirror volume {0}.>Could not get SVM disk set information in {0} at {1}--rc({2}).>Failed to setup and run dhtadm command for DHCP configuration.>Unable to get NetBackup master information for Config Id = {0}>Could not get VXFS version information in {0} at {1}--rc({2}).>Could not get VXVM version information in {0} at {1}--rc({2}).>The file system type is not compatible with the given options.>Could not find disk read-only property in {0} at {1}--rc({2}).>Slice {0} doesn''t have enough space for the specified length.>An error occurred while discovering network interface drivers.>The configuration does not contain exactly one network object.>A host entry already exists with the given host-name and role.?The maximum number of partitions is already in use on disk {0}.?Could not get disk encapsulation information from disk manager.?The logical volume size must be 1 logical partition or greater.?The metadevice name specified, {0}, must have format d[0-8192].?There is not enough disk space available to create this volume.?Target disk {0} is having partition(s) belonging to other disk.?Must specify a partition name, disk name, and partition length.?Updating network paramaters ... (This may take several minutes)?Could not find disk with reference ID {0} in the configuration.?There are no disks available to create log plex for volume {0}.?Could not discover Veritas Volume Manager information--rc({0}).?Could not get logical volume attributes in {0} at {1}--rc({2}).?Cannot specify a percentage when inquiring for available disks.@The location of disk {0} is missing from the configuration data.@Disk tagging is unsupported in VxVM versions before version 5.x.@Could not get JFS file system attributes in {0} at {1}--rc({2}).@Could not get physical volume attributes in {0} at {1}--rc({2}).@The system volume cannot reside on a spanned or extended volume.@There are no physical volumes available to map volume group {0}.@The vendor partition cannot be removed during an inline mapping.@The vendor partition cannot be changed during an inline mapping.@This volume cannot be removed because it contains a file system.@The slice name provided must be in ''/dev/dsk/c#t#d#s#'' format.@The layout of volume {0} cannot hold the system partition files.@Disk partition {0} is already being used by another multidevice.@Disk {0} cannot be specified to receive the ''standvol'' volume.@The specified disk, {0}, already exists as part of disk set {1}.@The supported operation for resource, "driver", is "initialize".AFailed to write commands to create volume group rootvg. - vgId{0}ACould not get JFS2 file system attributes in {0} at {1}--rc({2}).ACould not get lengths of physical volumes in {0} at {1}--rc({2}).ATo delete partitions you must start with the rightmost partition.AThe target disk {0} must first be cleared of existing partitions.AParser returned with non-zero return code = {0}, OutputType = {1}AA database replica named {0} already exists in the configuration.ACannot set reservation {0} bytes greater than available {1} bytesAUnable to set route for host {0} - gateway {1}, return code = {2}ACould not run command ({0}) in {1} at {2}--rc({3}),exitCode({4}).ADo not know how to make file system type {0}, file system id {1}.BYou cannot change the partition identifier during a map operation.BThe filesystem name is missing from configuration data. - fsId {0}BPhysical volume {0} is already being used by another volume group.BCommand exportfs failed to share the Network Shared Resource Tree.BThe system volume must have a file system but volume {0} does not.BThe valid attributes for resource {0} and operation {1} are: {2}BThe value of {0} for. Valid values are 256, 512, 1024, 2048, 4096.BCould not get all volume group information in {0} at {1}--rc({2}).BDisk set for volume {0} was not found in the source configuration.BCould not get persistent mount information in {0} at {1}--rc({2}).BCannot specify both length and percentage when adding a partition.CNo submirror names were specified while creating mirror volume {0}.CSlice with cylinder aligned offset {0} and length {1} does not fit.CBMR does not support legacy (non plug and play) network cards ({0})CCould not get SVM volume layout information in {0} at {1}--rc({2}).CCould not collect Veritas Volume Manager disk information--rc({0}).CThe plex for soft partition {0} was not found in the configuration.CCould not get locations of physical volumes in {0} at {1}--rc({2}).CSoft partition {0} is part of volume {1}. Please remove volume {2}.CAt least one database replica must exist before adding metadevices.DDisk {0} not found in a disk set. Please add disk to disk set first.DThe File system to map will no longer fit with the length specified.DDisk {0} is already in use for volume {1}. Unable to use it for log.DThe specified number for resync pass number must be between 0 and 9.DUnable to modify interlace value on non-striped/non-raid volume {0}.DUnable to extract either {0} or {1} file from bundle. Cannot import.DCould not get HP-UX volume group information in {0} at {1}--rc({2}).DThe NetBackup client version is incompatible with the master server.DCould not get attributes of physical volumes in {0} at {1}--rc({2}).DThe volume group name is missing from configuration data. - vgId {0}DThe Linux LVM physical volume {0} is not associated with any device.DA local database replica must be created before any named disk sets.DUpgrading rootvg to a Scalable or a Big volume group is not allowed.DCould not get general file system attributes in {0} at {1}--rc({2}).EConfiguration already has a device with Plug-and-Play instance id={0}EThe new filesystem, {0}, needs {1} but has only {2} blocks available.EDisk {0} already has the maximum allowed number of primary partitionsEThe metadevice named {0} already has a filesystem associated with it.ECannot delete SRT "{0}" because restore tasks are associated with it.EThe configuration does not contain exactly one RestoreOptions object.ECould not collect Veritas Volume Manager layout information--rc({0}).EMultidevice level may only be one of linear, stripe, mirror, or raid5EA network interface with MAC address {0} is not in the configuration.EThe volume for soft partition {0} was not found in the configuration.EThe slice underlying sub disk {0} was not found in the configuration.EDisk {0} has a bad type or invalid geometry and will not be restored.EYou must specify at least two copies to create a mirror storage pool.EVxVM version information missing in the configuration, in {0} at {1}.FThe hot spare pool name specified, {0}, must have format hsp[000-999].FCould not copy registry key from {0}\{1} to {2}\{3}, return code = {4}FDisk group tagging is unsupported in VxVM versions before version 5.x.FThe subdisks specified in this operation are not in the same disk set.FThe subdisk for soft partition {0} was not found in the configuration.FThe specified soft partition, {0}, was not found in the configuration.FThe logical volume name is missing from configuration data. - lvId {0}FYou must specify at least two devices to create a raidz1 storage pool.FYou must specify at least two devices to create a mirror storage pool.GDisk {0} must already contain ''stand'' to receive the ''root'' volume.GNew partition offset and/or length conflict with existing partition {0}GMultiple HPUX partitions on a Physical Volume is not a supported configGCannot utilize disk {0} because the backup tag slice is in use for SVM.GThis file system cannot be removed because a mount point references it.GThe slices specified are not present on disks within the same disk set.GThe mount point location is missing from configuration data. - mpId {0}GCould not discover Veritas Volume Manager version information--rc({0}).GYou must specify at least four devices to create a raidz3 storage pool.GCould not get disk mappings for logical volumes in {0} at {1}--rc({2}).HCould not find any non-global zone device with the specified name "{0}".HCannot set number of stripes greater than original volume configuration.HUnable to add database replica to slice that already contains sub disks.HThis program should only be run on the Bare Metal Restore Master Server.HYou must specify at least three devices to create a raidz2 storage pool.HThis logical volume cannot be removed because it contains a file system.HCould not find client operating system information in the configuration.HCould not find an active Solaris/Solaris2 native partition for disk {0}.HThis volume group cannot be removed because it contains logical volumes.ICould not find the Solaris disk for native disk {0} in the configuration.IThe number of devices on submirror {0} doesn''t match the other plex(es).IStorage Pool {0} used size {1} bytes cannot fit into the provided devicesIErrors were encountered while discovering NIC packages, return code = {0}IDowngrading a Big Volume Group to a Standard Volume Group is not allowed.IChoose ''Yes'' to transfer the external procedure from NetBackup server. I''{0}'' resolves to ''{1}'', which cannot be used to setup a Boot Server.IThe new filesystem size is not big enough to contain the filesystem data.IStripe width, in kilobytes, must be a power of 2 in the range 4 to 32768.IThe boot volume can only reside on a mirror with a maximum of two copies.JDisk set for hot spare pool {0} was not found in the source configuration.JThe number of devices does not align with the specified number of stripes.JCannot set Reservation size {0} bytes greater than volume length {1} bytesJCannot determine this boot server''s hostname. Set the hostname and retry.JThe specified interlace value must be between 16 blocks and 100 megabytes.KThe column number, {0}, is out of range of the specified number of stripes.KThe system volume can only reside on a mirror with a maximum of two copies.KCould not get major/minor numbers for volume groups in {0} at {1}--rc({2}).KCannot determine the IP address of {0}. Resolve any DNS problems and retry.KA soft partition named {0} must first exist before creating a volume on it.KThe length of the system volume cannot be changed during an inline mapping.LErrors were encountered while discovering Hotfix packages, return code = {0}LA common slice length must be specified if slice devices are being utilized.LCould not match a disk with a current disk. Port({0}), Target({1}), LUN({2})LCould not get major/minor numbers for logical volume in {0} at {1}--rc({2}).LSlice associated with soft partition {0} was not found in the configuration.LCould not collect Veritas Volume Manager configuration information--rc({0}).LA non-global zone name must be specified in order to complete the operation.MRequired rootdg information is missing from the configuration, in {0} at {1}.MColumn numbers for each device must be specified when stripes greater than 1.NCannot change the length of the boot logical volume from 1 physical partition.NThe filesystem for mount point location {0} is missing from the configuration.NSoft partition {0} has a filesystem on it. Please remove filesystem {1} first.NThe specified package does not match the client operating system type/version.NThe logical name for a disk is missing from the configuration data. - pvId {0}OThe package, {0}, is already configured for this client. Please use ''modify''.OTo change the disk type, either the disk must be empty or use the force option.PThe value of {0} for maxpp is invalid. Valid values are 32, 64, 128, 1024, 2048.PSlice {0} is encapsulated for volume manager use. It cannot be removed directly.PCould not get data from the following registry key: {0}{1}{2}, return code = {3}PThe number of devices specified to create a mirror with {0} copies isn''t valid.PMust provide a name, length, and at least one partition name for new multidevicePSoft partition {0} has a mount point on it. Please remove mount point {1} first.PDisk {0} has resources configured on it. Unable to complete requested operation.PPhysical volume for partition {0} not available. Invalid Original Configuration.QThe specified private region size, {0}, exceeds the maximum number of blocks {1}.QLogical Volume ''stand'' must first exist before mapping of ''root'' can proceed.RCould not erase disk {0}--rc({1}). Manually erase non-essential volumes and retry.RChanged inetd.conf but could not refresh inetd process. bootpd will fail to start.RCould not assign {0} to volume group {1}, it is already a member of another group.RThe gateway interface cannot be modified. Instead remove it and add it to another.TThe number of disks in the source disk set is not equal to the number in the target.TYou cannot specify a submirror, {0}, while creating a RAID 5 or concatenated volume.UFailed to prepare logical volumes to be root, boot, swap or dump volumes. - vgId {0}.USlice with cylinder aligned offset {0} and length {1} is bigger than disk length {2}.UDowngrading a Scalable Volume Group to a Big or Standard Volume Group is not allowed.UThe IP address interface cannot be modified. Instead remove it and add it to another.UAn error occurred while processing driver for {0}, Please verify driver installation.VCould not set value {0} for the following registry key: {1}\{2}\{3}, return code = {4}VThe number of submirrors specifed, {0}, doesn''t match the number of specified copies.VCan not allocate SRT ''{0}'', network share ''{1}'' already exists. Delete it manuallyV{0} is invalid device , Please use listdisks=true attribute for list of valid devices.VThe number of devices does not align with the specified number of stripes and mirrors.WPartition sizes cannot be modified. Please remove and re-add partition at desired size.WThe slice, {0}, contains a file system. Specify the force option to remove this volume.XVolume {0} is a database replica. Please remove it using the ''metadb'' resource remove.XCannot activate/deactivate partitions while an active Solaris/Solaris2 partition exists.XThe volume, {0}, contains a file system. Specify the force option to remove this volume.XA JFS log must exist in volume group ''{0}'' before a JFS logical volume can be created.YUnable to authorize the user, the user doesn''t have the rights to perform the operation.ZCannot remove active partition {0} from multidevice {1}; partition must be spare or failedZCannot utilize disk {0} because it has slices in use that are not on the backup tag slice.ZA JFS2 log must exist in volume group ''{0}'' before a JFS2 logical volume can be created.ZCluster command haclus returned error = {0}. Assuming Veritas Clustering is not installed.[More than one interface has the IP address {0}. Specify the interface to resolve ambiguity.[Unable to authorize the host, the system doesn''t have the rights to perform the operation.[There are virtual adapters on the system. Manual intervention may be needed during restore.\Driver file {0} is missing on the system. It may be needed during dissimilar system restore.\Cannot use whole disk {0} as LVM physical volume; disk partition table must be erased first.]The partition {0} hosts a physical volume. Specify the force option to remove this partition.]The file system, {0}, has a mount point. Specify the force option to remove this file system.]Disk {0} must already contain ''standvol'' to receive the ''rootvol'' or ''swapvol'' volume..^The partition {0} belongs to a multidevice. Specify the force option to remove this partition.^Volume ''standvol'' must first exist before mapping of ''rootvol'' or ''swapvol'' can proceed.^Device Type not supported for zfs rootpool, zfs rootpool supportes only mirror and concat type_The volume, {0}, contains a mount point system. Specify the force option to remove this volume.aZFS supports only single device rootpool for CONCAT layout. Please select only one device to map.aCould not find any logical volume, multidevice array, or partition named {0} in the configurationbThe specified disk is invalid for logical partition. Select MBR disk to create logical partitions.cInvalid user defined property specified, you can only change the exisiting user defined properites.dThe type attribute is no longer supported. Please use convert attribute to change the disk type.dThe disk group {0} still contains disks. Use the -force option to remove everything from disk group.eCannot create subdisk {0} on a slice that already contains a subdisk which is not a database replica.fError restarting dhcpd. Please be sure the DHCPD server package is correctly installed and configured.fThe disk group {0} still contains volumes. Use the -force option to remove everything from disk group.gA non-global zone filesystem could not be found in the configuration using the specified device: "{0}".gSolaris 10 U8 ZFS clients doesnt support RAIDZ3 layout, RAIDZ3 support is available from Solaris 10 U9.hError loading "{0}" file. Please be sure the DHCPD server package is correctly installed and configured.itftpd service is not active. Please verify TFTPD server is installed and [X]INETD is properly configured.jThe disk {0} cannot be converted to MBR/GPT. Please make sure the disk doesn''t contain any volumes in it.jName Description User Description Windows Version Driver Date Driver Version Driver TypeoCould not make failed multidevice partition {0} active or spare; it must be removed from the multidevice first.pA device name associated with a non-global zone element needs to be provided in order to complete the operation.sNo NICs were found with the following MAC address: {0} This may cause the restore to fail. Do you wish to continue?tThe specified volume {0} is neither a RAID5 or mirrored volume. It cannot have a hot spare pool associated with it.uCannot map {0} to non empty disk {1} of {2} type. Please unmap all partitions on the selected disk and retry mapping.wThe disk containing the root filesystem was found to be both managed and non-managed which is an invalid configuration.xSome files installed by hotfix {0} is missing on the system. Those files may be needed during dissimilar system restore.zCould not remove volume because it contains a filesystem. Either remove the filesystem first or specify the -force option.{An active Solaris/Solaris2 partition already exists on disk {0}. Please remove dependent resources and partition {1} first.{Multidevice parity may only be one of left-symmetric, right-symmetric, left-asymmetric, right-asymmetric, ls, rs, la, or ra|Neither Windows Logical Disk Manager nor Veritas Storage Foundation for Windows appears to be active. Using VDS interface...|Neither Windows Logical Disk Manager nor Veritas Storage Foundation for Windows appears to be active. Using LDM interface...|Could not remove volume because it contains a mount point. Either remove the mount point first or specify the -force option.|Could not remove disk set because it contains a metadevice. Either remove the metadevice first or specify the -force option.}Warning: The directory {0} is remotely mounted which will severely limit it''s ability to function as a Shared Resource Tree.܀Could not remove filesystem because it contains a mount point. Either remove the mount point first or specify the -force option.܂Could not remove soft partition because it contains a filesystem. Either remove the filesystem first or specify the -force option.܄Could not remove disk set because it contains a hot spare pool. Either remove the hot spare pool first or specify the -force option.܄Could not remove soft partition because it contains a mount point. Either remove the mount point first or specify the -force option.܈Logical Volume ''root'' must be the first volume on a disk. No empty disks were found that meet the criteria for ''root'' configuration.܈Volume ''standvol'' must be the first volume on a disk. No empty disks were found that meet the criteria for ''standvol'' configuration.܈The partition {0} is an extended partition containing one or more logical partitions. Specify the force option to remove this partition.܊Logical Volume ''stand'' must be the first volume on a disk. No empty disks were found that meet the criteria for ''stand'' configuration.܏Examples for listing a Windows LDM Volume are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource volume -operation listܔExamples for listing a Windows LDM disk are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation listܕThere is more than one package with the name {0}. Please provide a description string or the name of the client for the package to resolve ambiguity.ܖCannot determine this boot server''s name. There may be problems with the NetBackup configuration. Fix any NetBackup configuration problems and retry.ܖExamples for listing a Windows LDM Partition are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource partition -operation listܖThis matches drivers within the configuration to built-in or added drivers in the database. Driver packages are added to the configuration as needed.ܗCannot activate a Solaris/Solaris2 partition via partition modification. You must remove and re-add the partition specifying the active=true attribute.ܙExamples for listing a Windows LDM access path are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource accesspath -operation listܛExamples for listing a Windows LDM drive letter are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource driveletter -operation listܛExamples for listing a Windows LDM file system are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation listܝExamples for listing a Windows LDM logical drive are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation listܞThe .inf file for the device {0} is missing from the system. Please install the latest version of the {1} drivers, which, in most cases, resolves the problem.ܥThe disk {0} cannot be demoted to Basic. Please make sure the disk is dynamic and doesn''t contain any volumes in it except the System Volume in case of system disk.ܨThe dhcpd service is not active. Please verify DHCPD server is installed and properly configured. This is required in order to do BMR network boot based client restore.ܩWARNING: The reservation value for some of filesystems of ZFS Storagepool {0} doesnt fit for mapping, hence removed their reservation. Use ChangeProperties to set again.ܩExamples for displaying a Windows LDM Volume are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource volume -operation display -name myRaid5VolumeܪExamples for displaying a Windows LDM drive letter are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource driveletter -operation display -name C:ܫExamples for deleting a Windows LDM file system are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource filesystem -operation delete -name Volume23ܫA boot server with the name ''{0}'' does not exist. Unable to update boot server information. Check whether the boot server has been registered with the BMR Master Server.ܬThe driver for {0} is not compatible with Windows PE. You may need to create a driver package that is Windows PE compatible to restore this system using Bare Metal Restore.ܮA boot server with the name ''{0}'' already exists, and it''s Operating System does not match this boot server''s Operating System. Delete the existing boot server and retry.ܯExamples for displaying a Windows LDM disk are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation display -name myLogicalDriveܲExamples for displaying a Windows LDM access path are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource accesspath -operation display -name F:mountPointܴThe .inf file {0} does not have the neccessary information about the driver files. Please install the latest version of the {1} drivers, which, in most cases, resolves the problem.ܵCannot update boot server information in the BMR database. Either the database is not functioning, or the bmrd on the BMR master server is not running. Fix these problems and retry.ܵExamples for displaying a Windows LDM Partition are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource partition -operation display -name myPrimaryPartitionܶExamples for displaying a Windows LDM file system are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation display -name myLogicalDriveܶThe driver ''{0}'', of Version ''{1}'' is not compatible with WindowsPE. You may need to create a driver package using an earlier version of the driver that was WindowsPE compatible.ܸExamples for displaying a Windows LDM logical drive are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation display -name myLogicalDriveA directory value for a non-global file system should be specified in order for the operation to complete. A directory value usually is the mount point of a file system in the non-global zone.Examples for deleting a Windows LDM drive letter are: Examples 1) Delete a drive letter bmrconfig -client myClient -configuration myConfig -resource driveletter -operation delete -name F:Examples for deleting a Windows LDM access path are: Examples 1) Delete an access path bmrconfig -client myClient -configuration myConfig -resource accesspath -operation delete -name F:mountPointThe disk {0} cannot be promoted to Dynamic. Please make sure the disk is basic, doesn''t contain any volumes in it except the System Volume in case of system disk and the disk size is not greater than 2 TB in case of MBR.Cannot add boot server ''{0}'' to the BMR database. Either the BMR database has not been setup, or the database service is not functioning, or the bmrd on the BMR master server is not running. Fix these problems and retry.Cannot query the BMR database for existing boot servers. Either the BMR database has not been setup, or the database service is not functioning, or the bmrd on the BMR master server is not running. Fix these problems and retry.The partition, {0}, contains dependent resources which may include Solaris disk(s) as part of a disk group. You must use the force option to remove this partition understanding that doing so will remove all resources utilizing this partition.Unable to connect to the BMR Master Server, therefore the support for BMR has currently been disabled. Troubleshooting Steps: 1. Verify if the BMR Master Server has been registered with NetBackup Master Server, 2. Verify if the BMR Master Server is running. No space left on device. Please ensure that the specified target location for the Shared Resource Tree has adequate free space, and retry the command. Please refer to the System Administrator''s Guide for Bare Metal Restore for the space requirements for creating Shared Resource Trees./The valid attributes and examples for deleting a Linux partition are: Attributes 1) name (required) -- <name> device file path for the partition Example 1) Delete a partition bmrconfig -client myClient -configuration myConfig -resource partition -operation delete -name /dev/sda15The valid attributes and examples for deleting a Linux volume group are: Attributes 1) name (required) -- <name> name of the volume group Example 1) Delete the volume group bmrconfig -client myClient -configuration myConfig -resource volumegroup -manager lvm -operation delete -name vg00fThe valid attributes and examples for deleting a Linux multidevice are: Attributes 1) name (required) -- /dev/md<n> Multidevice pathname, where 0 <= n <= max multidevice number Examples 1) Delete a multidevice from the configuration bmrconfig -client myClient -configuration myConfig -resource multidevice -manager native -name /dev/md0lThe valid attributes and examples for mapping a Windows LDM drive letter are: Attributes 1) volume (required) -- <volume name> Name of volume, partition or logical drive to assign drive letter Examples 1) Map a drive letter bmrconfig -client myClient -configuration myConfig -resource driveletter -operation map -name F: -attributes "volume=Volume23"tThe valid attributes and examples for adding a Windows LDM access path are: Attributes 1) volume (required) -- <volume name> Name of volume, partition or logical drive to assign access path Examples 1) Add an access path bmrconfig -client myClient -configuration myConfig -resource accesspath -operation add -name F:mounPoint -attributes "volume=Partition20"vThe valid attributes and examples for mapping a Windows LDM access path are: Attributes 1) volume (required) -- <volume name> Name of volume, partition or logical drive to assign access path Examples 1) Map an access path bmrconfig -client myClient -configuration myConfig -resource accesspath -operation map -name F:mountPoint -attributes "volume=Partition20"xExamples for removing a Windows LDM Volume are: Use the -force option when the volume has a file system and/or drive letter or access path Examples 1) bmrconfig -client myClient -configuration myConfig -resource volume -operation delete -name myRaid5Volume 2) bmrconfig -client myClient -configuration myConfig -resource volume -operation delete -name myRaid5Volume -forceyThe valid attributes and examples for changing a Windows LDM Partition are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the partition Examples 1) Change the length of a primary partition bmrconfig -client myClient -configuration myConfig -resource partition -operation change -name myPrimaryPartition -attributes "length=7G"|The valid attributes and examples for changing a Windows LDM logical drive are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the logical drive Examples 1) Change the length of a logical drive bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation change -name myLogicalDrive -attributes "length=7G"݆The valid attributes and examples for modifying a system resource are: Attributes 1) cpu -- the number of CPUs for the system 2) memory -- Total number of Physical memory size in bytes Examples 1) bmrconfig -client myClient -configuration myConfig -resource system -operation changes -name system -attributes "cpu=3" "memory=6000000"ݓExamples for deleting a Windows LDM Partition are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource partition -operation delete -name myPrimaryPartition 2) bmrconfig -client myClient -configuration myConfig -resource partition -operation delete -name myPrimaryPartition -force Use the -force option when the partition has a file system and/or drive letter or access pathݙExamples for deleting a Windows LDM logical drive are: Examples 1) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation delete -name myLogicalDrive 2) bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation delete -name myLogicalDrive -force Use the -force option when the logical drive has a file system and/or drive letter or access pathThe valid attributes and examples for deleting a Linux logical volume are: Attributes 1) name (required) -- /dev/<volume group name>/<volume name/> the full pathname of the logical volume 2) force -- true | false forces the removal of the volume along with any filesystem or mount point that uses it Example 1) Deleting a logical volume bmrconfig -client myClient -configuration myConfig -resource logicalvolume -operation delete -name /dev/vg00/lv01The valid attributes and examples for modifying a Windows LDM Volume are: Attributes 1) length -- the new length of the volume parts of stripes, mirrors and RAID5 volumes are extended equally; spanned volumes are extended wherever possible 2) layout -- mirror|simple only valid on system volume; adds/removes a mirror to/from the system volume Examples 1) bmrconfig -client myClient -configuration myConfig -resource volume -operation change -name myRaid5Volume -attributes "length=6G"The valid attributes and examples for adding a Windows LDM drive letter are: Attributes 1) volume (required) -- <volume name> Name of volume, partition or logical drive to assign drive letter Examples 1) Add a drive letter bmrconfig -client myClient -configuration myConfig -resource driveletter -operation add -name F: -attributes "volume=Volume23" Notes 1) When a drive letter is assigned, some attributes are copied from the original volume with this drive letter to the volume that is getting the drive letter.*The valid attributes and examples for changing a Windows LDM file system are: Attributes 1) type (required) -- ntfs|fat32|fat16 The type for formatting the volume. 2) label -- <label string> The label for the volume. Default is no label. 3) compress - true|false Wheter of not the file system should be compressed. Default=false. Examples 1) Change a file system bmrconfig -client myClient -configuration myConfig -resource filesystem -operation change -name Volume23 -attributes "type=fat32" "compressed=false"zThe valid attributes and examples for adding a Windows LDM file system are: Attributes 1) type (required) -- ntfs|fat32|fat16 The type for formatting the volume. 2) volume (required) -- <name of volume> The volume that will have the file system 3) label -- <label string> The label for the volume. Default is no label. 4) compress - true|false Wheter of not the file system should be compressed. Default=false. Examples 1) Add a file system bmrconfig -client myClient -configuration myConfig -resource filesystem -operation add -name Volume23 -attributes "type=ntfs" "volume=Volume23"ޕThe valid attributes and examples for mapping a Windows LDM file system are: Attributes 1) type (required) -- ntfs|fat32|fat16 The type for formatting the volume. 2) volume (required) -- <name of volume> The volume that will have the file system 3) label -- <label string> The label for the volume. Default is no label. 4) compress - true|false Wheter of not the file system should be compressed. Default=false. Examples 1) Map a file system bmrconfig -client myClient -configuration myConfig -resource filesystem -operation map -name myOriginalVolume -attributes "type=ntfs" "compressed=true" "volume=Volume23"ޗThe valid attributes and examples for mapping a Windows LDM Partition are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the partition 2) disk (required) -- <disk name> the disk(s) that may be used by the partition ; if more than one specified, it is non-deterministic which will be used 3) listDisks -- true|false when true, instead of mapping the partition, this operation lists the disks that could hold the partition. Examples 1) Map to a primary partition bmrconfig -client myClient -configuration myConfig -resource partition -operation map -name myOriginal -attributes "length=4G" "disk=DeviceHarddisk0"޵The valid attributes and examples for mapping a Windows LDM logical drive are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the logical drive 2) disk (required) -- <disk name> the disk(s) that may be used by the logical drive; if more than one specified, it is non-deterministic which will be used 3) listDisks -- true|false when true, instead of mapping the logical drive, this operation lists the disks that could hold the logical drive. Examples 1) Map to a logical drive bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation map -name myOriginal -attributes "length=4G" "disk=DeviceHarddisk0"The valid attributes and examples for adding a Windows LDM disk are: Attributes 1) disk (required) -- <disk name> the disk(s) that may be used by the volumes, partitions and logical drives that use this disk 2) listDisks -- true|false when true, instead of mapping the disk, this operation lists the disks that could could be used for mapping the disk. Examples 1) Mapping a disk to a single disk bmrconfig -client myClient -configuration myConfig -resource disk -operation map -name DeviceHarddisk0 -attributes "disk=DeviceHarddisk2" 2) Mapping a disk to multiple disks bmrconfig -client myClient -configuration myConfig -resource disk -operation map -name DeviceHarddisk0 -attributes "disk=DeviceHarddisk2" "disk=DeviceHarddisk1"cThe valid attributes and examples for mapping a Linux partition are: Attributes 1) name (required) -- <name> device file path for the partition 2) disk (required) -- <disk> disk to which the partition will be mapped 3) length -- <length>[GgMmKkBb] length of mapped partition 4) maplevel -- full | filesystem | volume determines extent of mapping; full indicates that the filesystem and mount point should be recreated, filesystem indicates that the filesystem should be recreated but not the mount point, and volume indicates that no filesystem or mount point will be recreated Example 1) Map to a primary partition bmrconfig -client myClient -configuration myConfig -resource partition -operation map -name /dev/hdb3 -attributes "disk=/dev/sdc" "length=800M" "maplevel=full"߃The valid attributes and examples for adding a Windows LDM Partition are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the partition 2) disk (required) -- <disk name> the disk(s) that may be used by the volume; if more than one specified, it is non-deterministic which will be used Examples 1) Add a primary partition bmrconfig -client myClient -configuration myConfig -resource partition -operation add -name myPrimaryPartition -attributes "length=4G" "disk=DeviceHarddisk0" Note 1) If this is the fifth primary partition added to a disk, the last primary partition added to this disk and this partition will be converted into logical drives. 2) If this is the fourth primary partition added to a disk and the disk already has at least one logical drive, this partition will be converted into a logical drive.ߛThe valid attributes and examples for adding a Windows LDM logical drive are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the logical drive 2) disk (required) -- <disk name> the disk(s) that may be used by the logical drive; if more than one specified, it is non-deterministic which will be used Examples 1) Add a logical drive bmrconfig -client myClient -configuration myConfig -resource logicaldrive -operation add -name myLogicalDrive -attributes "length=4G" "disk=DeviceHarddisk0" Notes 1) If this is the first logical drive added to a disk and the disk already has four primary partitions, the the last primary partition added to that disk will be converted into a logical drive. 2) If this is the first logical drive added to a disk and the disk already has three primary partitions, the extended partition will fill the remainder of the disk.The valid attributes and examples for changing a Windows LDM disk are: Attributes 1) type -- The type attribute is no longer supported. Please use convert attribute to change the disk type. 2) convert -- mbr_dynamic | gpt_dynamic | mbr_basic | gpt_basic Convert the disk to MBR dynamic or GPT dynamic or MBR basic or GPT basic disk. Examples 1) Promote a disk to mbr dynamic bmrconfig -client myClient -configuration myConfig -resource disk -operation change -name myLogicalDrive -attributes "convert=mbr_dynamic" 2) Revert a disk to gpt basic bmrconfig -client myClient -configuration myConfig -resource disk -operation change -name myLogicalDrive -attributes "convert=gpt_basic" Notes 1) The disk must be empty except for the system volume/partition or possibly a vendor partition. 2) When promoting a disk, a basic system partition is converted to a simple volume. 3) When reverting a disk, a dynamic system volume is converted to a primary partition.JThe valid attributes and examples for mapping a Linux volume group are: Attributes 1) name (required) -- <name> name of the volume group 2) physicalvolume -- <physical volume name> name of the physical volume that is being mapped; multiple physical volumes will be specified separately 3) maplevel -- full | physicalvolume map level full attempts to recreate the volume group, all associated logical volumes, file systems, and mount points; map level physicalvolume only creates a new volume group and maps newly created physical volumes to it 4) listdisks -- true | false lists available disks; no other action is performed Examples 1) Attempt to map a Linux volume group and all its associated volumes and file systems bmrconfig -client myClient -configuration myConfig -resource volumegroup -manager lvm -operation map -name vg00 -attributes "physicalvolume=/dev/sda" "physicalvolume=/dev/sdb" "physicalvolume=/dev/sdc1" "maplevel=full" 2) Show the disks available for mapping a Linux volume group with the given physical volumes bmrconfig -client myClient -configuration myConfig -resource volumegroup -manager lvm -operation map -name vg00 -attributes "physicalvolume=/dev/sda3" "physicalvolume=/dev/sdb4" "maplevel=physicalvolume" "listdisks=true"Help for bmrconfig with the license resource 1) Listing Licenses bmrconfig -resource license -client <clientName> -configuration <configurationName> -operation list 2) Adding a License bmrconfig -resource license -client <clientName> -configuration <configurationName> -operation add -name <theLicenseKey> -attributes "product = vxvm | vxfs | sfw" ["description=<productDescription>"] ["version=<productVersion>"] 3) Changing a License bmrconfig -resource license -client <clientName> -configuration <configurationName> -operation change -name <theLicenseKey> -attributes ["product = vxvm | vxfs | sfw"] ["description=<productDescription>"] ["version=<productVersion>"] ["key=<newKey>"] 4) Display License Details bmrconfig -resource license -client <clientName> -configuration <configurationName> -operation display -name <theLicenseKey> 5) Removing a License bmrconfig -resource license -client <clientName> -configuration <configurationName> -operation delete -name <theLicenseKey>The valid attributes and examples for adding a Linux partition are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the partition 2) type (required) -- primary | logical the partition type; if logical, an extended partition will be created if necessary to contain the new partition Partitions are numbered as they are created; the first primary partition will be 1, the second will be 2, etc. The first logical volume will be 5, the second 6, etc. 3) id (required) -- linux | swap | lvm | raid partition identifier; specifies how the partition is to be used 4) disk (required) -- <disk> name of disk to house the partition 5) boot -- true | false identifies whether partition is bootable (default is false) Examples 1) Create a primary partition to host a file system bmrconfig -client myClient -configuration myConfig -resource partition -operation add -attributes "disk=/dev/sda" "length=256M" "type=primary" "id=linux" 2) Create a logical partition for use as a physical volume bmrconfig -client myClient -configuration myConfig -resource partition -operation add -attributes "disk=/dev/hdb" "length=4G" "type=logical" "id=lvm" 3) Create a bootable partition bmrconfig -client myCLient -configuration myConfig -resource partition -operation add -attributes "disk=/dev/hda" "length=64M" "type=primary;" "id=linux" "boot=true"The valid attributes and examples for mapping a Linux multidevice are: Attributes 1) name (required) -- /dev/md<n> multidevice pathname, where 0 <= n <= max multidevice number 2) length (required) -- <length>[GgMmKkBb] length of the multidevice 3) layout (required) -- linear | stripe | mirror | raid5 multidevice layout; a multidevice can map to a lower RAID level (e.g., raid5 -> stripe), but not to a higher one 4) disk (required) -- <disk path name> name of the disk(s) that the device is being mapped to; multiple disks are specified separately 5) maplevel -- full | filesystem | volume determines the extent of mapping; full indicates that the filesystem and mount point should be recreated, filesystem indicates that the filesystem should be recreated but not the mount point, and volume indicates that no file system or mount point will be recreated 6) listdisks -- true | false shows the available disks for a given layout; no other action is performed Examples 1) Map a multidevice and its associated file system and mount point to a new set of disks bmrconfig -client myClient -configuration myConfig -resource multidevice -manager native -operation map -name /dev/md1 -attributes "length=50M" "layout=raid5" "disk=/dev/sda" "disk=/dev/sdb" "disk=/dev/hda" "maplevel=full" 2) Show all disks available to host a mirrored multidevice of length 1 GB bmrconfig -client myClient -configuration myConfig -resource multidevice -manager native -operation map -name /dev/md1 -attributes "length=2G" "layout=mirror" "listdisks=true":The valid attributes and examples for mapping a Linux logical volume are: Attributes 1) name (required) -- /dev/<volume group name>/<volume name> the full pathname of the logical volume 2) length (required) -- <length>[GgMmKkBb] the length of the logical volume 3) layout (required) -- striped | concatenated the logical volume layout 4) columns -- <n> number of columns (stripes) for a striped layout, where 1 <= n <= number of physical volumes in volume group; default value is 1 5) stripelength -- <stripelength>[GgMmKkBb] width of a column (stripe); required if number of columns is specified. Stripelength must be 2^n where 2 <= n <= 9 6) maplevel -- full | filesystem | volume determines the extent of mapping; full indicates that the filesystem and mount point should be recreated, filesystem indicates that the filesystem should be recreated but not the mount point, and volume indicates that no file system or mount point will be recreated 7) listdisks -- true | false list all available physical volumes appropriate for the specified layout; no other action is performed. Example 1) Map a 2GB logical volume with 3 columns and a stripelength of 256, recreating any filesystems and mount points bmrconfig -client myClient -configuration myConfig -resource logicalvolume -operation map -name /dev/vg00/lv01 -attributes "length=2G" "layout=striped" "columns=3" "stripelength=256" "maplevel=full" 2) Display all disks available to map a 1GB logical volume striped across 2 physical volumes bmrconfig -client myClient -configuration myConfig -resource logicalvolume -operation map -name /dev/vg00/lv01 -attributes "length=1G" "layout=striped" "columns=2" "stripelength=128" "listdisks=true"bThe valid attributes and examples for adding a Windows LDM Volume are: Attributes 1) length (required) -- <length>[GgMmKkBb] the length of the volume 2) layout (required) -- simple|spanned|striped|mirror|raid5 the layout of the volume 3) disk (required) -- <disk name>[,<length to use>[GgMmKkBb] ] the disk(s) that may be used by the volume; if fewer required, non-deterministic which one(s) will be used The disk usage can be constrained so that no more than the amount specified is used by the volume; the total of disk usages must be greater than or equal to volume length 4) columns -- 2+ for stripes; 3+ for RAID5 the number of columns in a striped or RAID5 volume Required for striped and RAID5 volumes; invalid for other layouts 5) copies -- 2 the number of data copies in a mirrored volume required for mirrors; invalid for other layouts Examples 1) Create a simple volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name mySimpleVolume -attributes "length=4G" "layout=simple" "disk=DeviceHarddisk4" 2) Create a spanned volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name mySpannedVolume -attributes "length=5G" "layout=spanned" "disk=DeviceHarddisk4,2G" "disk=DeviceHarddisk5,3G" 3) Create a striped volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name myStripedVolume -attributes "length=4G" "layout=striped" "disk=DeviceHarddisk4" "disk=DeviceHarddisk5" "columns=2" 4) Create a mirrored volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name myMirroredVolume -attributes "length=4G" "layout=mirror" "disk=DeviceHarddisk4" "disk=DeviceHarddisk5" "copies=2" 5) Create a RAID5 volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name myRaid5Volume -attributes "length=4G" "layout=raid5" "disk=DeviceHarddisk4" "disk=DeviceHarddisk5" "disk=DeviceHarddisk6" "columns=3" The valid attributes and examples for mapping a Windows LDM Volume are: Attribute 1) length -- <length>[GgMmKkBb] the new length of the volume; defaults to original length 2) layout -- simple|spanned|striped|mirror|raid5 the new layout of the volume; defaults to original layout 3) disk (required) -- <disk name>[,<length to use>[GgMmKkBb] ] the disk(s) that may be used by the volume; if fewer required, non-deterministic which one(s) will be used The disk usage can be constrained so that no more than the amount specified is used by the volume; the total of disk usages must be greater than or equal to volume length 4) columns -- 2+ for stripes; 3+ for RAID5 the number of columns in a striped or RAID5 volume; defaults to original number of columns Required for striped and RAID5 volumes; invalid for other layouts 5) copies -- 2 the number of data copies in a mirrored volume; defaults to original number of copies required for mirrors; invalid for other layouts 6) listDisks -- true|false when true, instead of mapping the volume, this operation lists the disks that could hold the volume. Examples 1) Map to a simple volume bmrconfig -client myClient -configuration myConfig -resource volume -operation map -name mySimpleVolume -attributes "length=4G" "layout=simple" "disk=DeviceHarddisk4" 2) Map to a spanned volume bmrconfig -client myClient -configuration myConfig -resource volume -operation map -name mySpannedVolume -attributes "length=5G" "layout=spanned" "disk=DeviceHarddisk4,2G" "disk=DeviceHarddisk5,3G" 3) Map to a striped volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name myStripedVolume -attributes "length=4G" "layout=striped" "disk=DeviceHarddisk4" "disk=DeviceHarddisk5" "columns=2" 4) Map to a mirrored volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name myMirroredVolume -attributes "length=4G" "layout=mirror" "disk=DeviceHarddisk4" "disk=DeviceHarddisk5" "copies=2" 5) Map to a RAID5 volume bmrconfig -client myClient -configuration myConfig -resource volume -operation add -name myRaid5Volume -attributes "length=4G" "layout=raid5" "disk=DeviceHarddisk4" "disk=DeviceHarddisk5" , 0 5 : ? D I N S X ]0 b g l q v { 4 8 <   %@*/49>CHMRWD\afkpuzHLP )TX\`dhlptx -| 1 5  = $(,048<@ ADHLPTX\`dh Elptx| I  M Q U  $(,048<@D aHLPTX\`dhlptx| i m    $(,0 48<@DHLPTX \`dhlptx|       $(,0 48<@DHLPTX \`dhlptx|       $ !(,048<@DHL %PTX\`dhlp )tx| - 1  5 9  $(, q048<@DHLPT uX\`dhlpt yx| }    $(,04 8<@DHLPTX\ `dhlptx|      $(,048<@ DHLPTX\`dh lptx|   &        $ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x |       $ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x |       $ ( , 0 4 8 < @ D H L P T X \ ` d h l p t x |         $ ( , 0 4 8 < @ D H  L P T X \ ` d h l    p t x | ! % )  -      $ ( ,`+`t` e`h`$`Z`)`+"` D``B`w`/`` N``N5`````19``C`D````j``#&`4X`62`S`7R```N`@` `B`````7"`4`,`b%`o\`kl`W`R`Xk``;`6``3`0Q` `` ``ˁ```K`3>`.````&`$z``^``A2``j`/`Q`n``@`0``L`-`l`S]`5`w`O`Ji`*` `c`*`Y`5`GH`U``7`(`i`{`-``O`1`1`1`e```8B`md` `'`6```s``rW`J`[`}`z(`y"`pX`zj`~``Eo`Q5`T=`m`?`-C`0#`-`-`UU`V5`cL`n``c`-`^`}`f`H`e` _`Cg`2$`3m`)e`0`<`3`v`y```"``2``<`p`Zl`````h``r` ` `Vm` &`P`o`gP`I%`P`k``K `C3`"`b`,`c`:`H`M`8`S`9`x` `` k`2` `J`PY``+``~````5`,`2`@3```3`x``E`S`a9`B`Kw` L`M`+`>`1`R`\4`>=`X``;R` `M`g`j`_a`5`\``n`O`u`?`$`F`(]`"`Ql`&~``c``&`>`/`&(`D``)`M`%``w[`a` ``)` ```M`\``4`v`O` `r`.```;`@`}``'U` %`,0`[`9````S`` `u``!``|```q`?```n```C`/`F `)``N`I`=`G}`uW``?7`_&`L`U`(`w`3`i`l)`(`?`%`&`U`%`L`Ae`D7`6`#`M'`t`$`#`,`9````%|`:````P`1 `"` `!>`G`=u`E;`@f`?`V`V`i>`i`h``r`r`*`]`.)`!`g`r`$```+O`M``8`&`+`Dk`S%`C` ``J3````Q`p```W```"```W`YO``` `at```L`jt` ``G`C`O`"0`i|`t`J```|```#O`lh`#`9h``]`LO``F`%`z`|8`$$``r`q`m%`sW`V``Y`-q```e```A```2`@`n``5r````C`M``F`'`{``b``@`o```d`Q`Z`a`{````K`````|z`B`[```E``"``[`D`^````T`*`:]`b`w```x``-`v``y`/=`I`> `H`H`A`>`f`s`/k`x`RH`0`(`\``>o`I`Y`X2`d`qW``V`*n`m`HQ`(`<{``\n`T``M`Y`V``*``,`R```%`^>`S` ` `````4``t`.`Î`;`s``G`̓`T``3``` `ְ`Ƿ``<``t```P`$``````b``OF`"``:,`\``R``5C` `` `I[```3`w`u``` `E`U`*`f`$"`/`s`B` `^x`` ?`]`$O`z`-`97`"Y`KA`K`H`x`X`<`)`~K``;``d<`x_`0``W`tW`g`:` ```Z``f`}```8``f```]V`` -`R`U`g`0` `"``k.`z``` `n!``*`&S`C`:`` ``)`)` _` ` D`_`B`?i`v``%Q``q`!f`!`T` ``O``@``6``#x`4`4``+`1h```R`) `n```a` ``;!`P`]`m`;```]`` ``G`d`@`` ``W``X`q````!```j` `1``=`e,`.W`Tu`x```b`_`%`*A` c``+|`B1`{```'`1`Z`|``2S`1h`9`%&`U`!``}@`@`Ļ``8`.W```V`0`ϋ`8s``I`{`q`dx``` ```+`7`y``{`=`v``]`j`(``,]`.`P"`k`[P`Z3`q`{``o``v```h`|``I`3`s`O}`J``f`_`p```Bd` v` `WN`c` ?```s`vW`P```4)`Nk`5`A`'*`ƃ`yc``~` #``n`0``J`F?`u` n