This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

linux back ups failing error code 19 Attach device failed for device path of '/dev/dm-0'

so i am new to this software and i am sure i may have overlooked something. but for now i need to get backups working. so here is the error message and stack trace info :

Exception chain:

 

  • Attach device failed for device path of '/dev/dm-0' with error code 19
  • Call to service method 192.140.500.799:8006/.../driver GET failed: Attach device failed for device path of '/dev/dm-0' with error code 19
  • The transfer of one or more volume images from a protected machine to the Core has failed
  • One or more errors occurred.

STACK TRACE:

Server side:Replay.Core.Contracts.Transfer.CoreTransferFailedException: The transfer of one or more volume images from a protected machine to the Core has failed ---> System.AggregateException: One or more errors occurred. ---> WCFClientBase.ClientServerErrorException: Call to service method 192.140.500.799:8006/.../driver GET failed: Attach device failed for device path of '/dev/dm-0' with error code 19 ---> System.AggregateException: Attach device failed for device path of '/dev/dm-0' with error code 19 ---> System.InvalidOperationException: Attach device failed for device path of '/dev/dm-0' with error code 19 at Replay.Common.Implementation.Drivers.BlockSnap.AttachDeviceInternal (System.String devicePath) [0x00000] in :0 at Replay.Common.Implementation.Drivers.BlockSnap.AttachDevice (System.String devicePath, System.String mountDevicePath, Boolean createChangelogStorage, Boolean createDataStorage, Boolean vssSupported) [0x00000] in :0 at Replay.Common.Implementation.Drivers.DriverApiImplementation.AttachVolume (Replay.Common.Implementation.Win32Api.LinuxPartition partition) [0x00000] in :0 at Replay.Common.Implementation.Drivers.DriverApiImplementation.AttachVolume (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0 at Replay.Common.Implementation.Drivers.DriverApiImplementation.EnableVolumeLogging (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName, UInt32 epoch, Boolean generateNewGuid) [0x00000] in :0 at Replay.Agent.Implementation.Drivers.DriverApi.EnableVolumeLogging (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName, UInt32 epoch, Boolean generateNewGuid) [0x00000] in :0 at Replay.Agent.Implementation.Drivers.DriverVolumeLinux.Enable (UInt32 newEpochNumber, Boolean generateNewGuid) [0x00000] in :0 at Replay.Agent.Implementation.Drivers.DriverVolumeLinux.Enable () [0x00000] in :0 at Replay.Agent.Implementation.Transfer.TransferSessionBase.RemoveUnReliableVolumes (IDriversService driversService, IStorageMetadata storageMetadata, IEnumerable1 volumes, IDictionary2 errorVolumes) [0x00000] in :0

--- End of inner exception stack trace --- at Replay.Agent.Implementation.Transfer.TransferSessionBase.GetVolumeInfo (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0 at Replay.Agent.Implementation.Transfer.TransferSessionBase.GetDriverMetadata (Replay.Common.Contracts.Metadata.Storage.VolumeName volumeName) [0x00000] in :0 at Replay.Agent.Management.Transfer.TransferManagementBase.GetDriverMetadata (System.String snapshotSetId, System.String volumeName) [0x00000] in :0 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in :0

--- End of inner exception stack trace --- at WCFClientBase.HttpResponseMessageExtensions.Check(HttpResponseMessage message, Uri uri, String method, ILogger logger) at WCFClientBase.ClientBase.GetResponse(Uri uri, String method, String knownEtag) at WCFClientBase.ClientBase.ExecuteServiceCall[T](Uri uri, String method, String knownETag) at Replay.Agent.Client.TransferManagementAgentClient.GetDriverMetadata(String snapshotSetId, String volumeName) at Replay.Core.Implementation.Agents.AgentClient.GetDriverMetadata(Guid snapshotSetId, VolumeName volumeName) at Replay.Core.Implementation.Agents.TransferAgentClient.GetDriverMetadata(Guid snapshotSetId, VolumeName volumeName) at Replay.Core.Implementation.Transfer.VolumeTransferJobBase.DetermineDataToSendTask() at System.Threading.Tasks.Task.Execute()

--- End of inner exception stack trace --- --- End of inner exception stack trace --- at Replay.Core.Implementation.Transfer.TransferJob.DetermineDataToSend() at Replay.Core.Implementation.Transfer.TransferJob.TransferTaskSteps() at Replay.Core.Implementation.Transfer.TransferJob.TransferTaskInternal() at Replay.Core.Implementation.Transfer.TransferJob.TransferAgentTask() at Replay.Core.Implementation.Transfer.TransferJob.TransferTask() at System.Threading.Tasks.Task.Execute()

 

LOGS :

   at Replay.Agent.Implementation.Transfer.TransferSessionBase.RemoveUnReliableVolumes(IDriversService driversService, IStorageMetadata storageMetadata, IEnumerable`1 volumes, IDictionary`2 errorVolumes) +0x0 6000337
System.InvalidOperationException depth 0: GetAttachedDevices failed to return a proper list of devices, error code 19 (0x80131509)
Service Host Error: Service error while handling request [GET https://192.168.2.199:8006/apprecovery/api/agent/transfer/snapshots/8470e577-0291-4240-a3dd-667610307442/volumes/~|~~|~%253f~|~Volume%257bd2dd969a-e10d-739d-02a6-071629d19cb4%257d~|~/driver]: Attach device failed for device path of '/dev/dm-0' with error code 19
System.AggregateException depth 0: Attach device failed for device path of '/dev/dm-0' with error code 19 (0x80131500) ---> (Inner Exception #0 depth 0) System.InvalidOperationException depth 1: Attach device failed for device path of '/dev/dm-0' with error code 19 (0x80131509)
   at Replay.Agent.Implementation.Transfer.TransferSessionBase.RemoveUnReliableVolumes(IDriversService driversService, IStorageMetadata storageMetadata, IEnumerable`1 volumes, IDictionary`2 errorVolumes) +0x0 6000337
System.InvalidOperationException depth 0: GetAttachedDevices failed to return a proper list of devices, error code 19 (0x80131509)

 

So far the root partition cannot be backed up. i have only been able to back up the swap file ... no idea ... as far as i can tell the agent is the latest one available. the system is ubuntu 16 64bit. any suggestions

Parents
  • There may be various causes:
    1. One of the services are stopped (rapidrecovery-agent, rapidrecovery-vdisk, rapidrecovery-mapper)
    2. Agent version mismatch with core version.
    3. Services modules are not loading.
    4. Kernel headers installed are not correct.
    ----
    It is likely that configuration needs to be run:
    - rapidrecovery-config -m all
    Should you see errors about the kernel headers, re-run agent configuration
    - rapidrecovery-config
    -- select option "6 on"
    -- select option "4 all"
    - check the service "service rapidrecovery-vdisk status"
    - start the service "service rapidrecovery-vdisk start"
    ----
    The above suggestions just cover a commonly seen situation.
    If in doubt after these steps, we suggest that you reboot the linux server, and check again.

    Should you find other issues, or need assistance troubleshooting, we suggest that you please open a service request from our support portal.

    I hope this helps.

Reply
  • There may be various causes:
    1. One of the services are stopped (rapidrecovery-agent, rapidrecovery-vdisk, rapidrecovery-mapper)
    2. Agent version mismatch with core version.
    3. Services modules are not loading.
    4. Kernel headers installed are not correct.
    ----
    It is likely that configuration needs to be run:
    - rapidrecovery-config -m all
    Should you see errors about the kernel headers, re-run agent configuration
    - rapidrecovery-config
    -- select option "6 on"
    -- select option "4 all"
    - check the service "service rapidrecovery-vdisk status"
    - start the service "service rapidrecovery-vdisk start"
    ----
    The above suggestions just cover a commonly seen situation.
    If in doubt after these steps, we suggest that you reboot the linux server, and check again.

    Should you find other issues, or need assistance troubleshooting, we suggest that you please open a service request from our support portal.

    I hope this helps.

Children
No Data