Note: You must be registered in order to post a reply. To register, click here. Registration is FREE!
T O P I C R E V I E W
pfeldman
Posted - March 21 2015 : 18:13:05 I attempted to clone a disk. After 6 hours, Reflect reported that it was 1 percent done, so I aborted the process. I presume that one of the two drives it bad. When something like this happens, it would be great if Reflect report that a drive is bad and identified the bad drive.
Dr. Phillip M. Feldman
2 L A T E S T R E P L I E S (Newest First)
GoneToPlaid
Posted - June 14 2015 : 20:19:16 There are many stand-alone programs which can check the S.M.A.R.T status of hard drives. Some of these programs are GNU with freely available source code. Reflect should, in addition to verifying the drive's file system, automatically check both the source and backup drive S.M.A.R.T status and warn the user if either drive's status indicates a failing drive. For the source drive, a bad S.M.A.R.T status should automatically trigger Reflect to skip bad sectors while backing up, or to optionally try to read the bad sectors up to X number of times while backing up before giving up on the bad sectors and moving on with the backup. Acronis tries to repeatedly read bad sectors while backing up, and frequently repeated access attempts to read bad sectors eventually are successful. Reflect should automatically attempt the same while backing up, yet warn the user that the backup may take much longer than normal if the source drive reports S.M.A.R.T problems.
For the destination drive, S.M.A.R.T issues should automatically abort the backup since the destination drive is not reliable.
quote:Originally posted by StephenG
Hi Dr.Feldman
Thanks for your feedback I have passed it onto the development team for evaluation.
Please read through this knowledge base article on possible performance issues. Although its the V6 knowledge base it still applies to V5.