Skip to main content

Scheduled task blocked by presence of bit locker partition-which is neither the source or target drive

Thread needs solution

There are a number of good threads on problems with bit locker. Mine is a bit different.

I backup my system drive to one external hard drive. A second external hard drive houses a bit locker encrypted partition but this is neither backed up nor used as a location where backups reside. When this partition is locked my scheduled backups fail with the same error I get when I start Acronis-"cannot read sectors". If I unlock the drive -I do not need to decrypt it -- the task runs fine.

What Acronis starts up it makes a surveillance of all drives and if anything is encrypted it gives the "cannot read sectors" error. I believe it must be doing the same thing at the time that the scheduled task runs. Is there a switch or other configuration change which would simply tell Acronis to ignore that drive. I prefer not to have to remember to unlock it each night and then re-lock it in the morning. Again the encrypted drive is not used as either a source or target in any backup job.

Any tips appreciated. Thank you in advance.

Kevin

0 Users found this helpful

Hello Kevin,

Let me shed some light on the issue.

Indeed, Acronis scans every hard drive in the system before every backup job and there's no way to skip any of the drives installed in your system.

However, there's a way to overcome this 'read errors' messages. While creating a backup task, please go to Backup Options, then to Error handling and set 'Ignore bad sectors' and 'Do not show messages and dialogs while processing (silent mode)' to Enabled.

This should fix the issue.

Please let me know if the above workaround didn't help you.

Thank you.

Thank you very much. This sounds like a very reasonable approach. If I take these steps to I lose all the protections against writing to bad sectors or other problems which could result in my backup being unreadable? Is there any verify process or other safeguard. I would like to avoid creating bad backups and not knowing it until it comes time to restore :-) just a thought?

Hello Kevin,

In that case I may suggest you to enable Silent Mode only, so you will be able to check logs after the backup and find out if there were any issues.

Please reply to this thread if you have any additional questions.

Thank you.