# Troubleshooting 1-Touch for Linux

The following section provides information on some of the troubleshooting scenarios related to 1-Touch Recovery:

Problem or Error | Solution
`Unable to retrieve the job details <corresponding job ID:XX>` | This error message appears during the 1-Touch Recovery if the file system restore job on the CommServe is killed or failed. Use the /init command to restart the file system restore job.
`Error 17: Cannot mount selected Partition.` | The system fails to boot because the boot disk is changed before recovery. Perform the following steps to boot the client: If the boot disk has changed, make sure it is selected as a bootable disk in the BIOS settings. Edit the grub menu during boot. Change the root (hd#) entry to use the proper root disk. Continue to boot. Once the system is up, user can run the grub-install to make the fix permanent.
1-Touch recovery completes successfully but machine throws grub errors during boot up. | This error occurs possibly due to incorrect configuration of disk boot sequence. To resolve this issue, if both IDE and SATA/ SCSI disks are present on the machine being recovered, make sure that the BIOS boot sequence is set appropriately on the source and the client machines. In general, as IDE disks are enumerated before the locally attached SATA/ SCSI disks, if the boot device is a SATA/ SCSI disk then the BIOS boot sequence should be configured to enumerate SATA/ SCSI disks first.
`1-Touch recovery failed because of mismatch between the configurations of backed up and restored systems.` | This error occurs when the vendor information for a drive is not available. Typically the vendor information is not available for a flash drive or pen drive. To resolve this issue, make sure that no flash drives or pen drives are connected to the client computer before starting the 1-Touch recovery.
The sourceclient_recovery client is registered successfully, but the next page displays the error message `Post-install operations failed. Error: qlogin failed. Unable to verify credentials` | This error occurs when the client name used for the registration is wrong. The Display Name of the SourceClient needs to be utilized, and it is case sensitive. Alternatively, this error can show up when the client does not have any 1-Touch backups.
`Error Code: [24:42] Description: Cannot start restore program on host [10.10.10.10*sourceclient_recovery*8111*8402] - a network error occurred or the product's services are not running. Source: MediaAgent, Process: fsIndexedRestore` | See KB article 84797.

×

Loading...