![]() ![]() As others have said, image backups are compressed, so you won't necessarily need a target whose capacity matches your source, or even the capacity you're consuming on the source. PS: Thank you for pointing out the tools I have run Memtest86 before and the last surface check of the drive showed no errors, but I might need to check this again!Ĭlick to expand.1. Today's example for the other PC (about 1 year old): creating a full image of the SSD (about 64 GB I think) took less than 20 minutes, but creating a 10 GB incremental image (no consolidation) of the HD took 2 hours and 20 minutes! The terribly slow speed issue happens on two completely different systems though. I hope it survives until Apple releases new iMacs). This was probably bad luck (or a dying drive indeed this PC over 10 years old. Luckily a "chkdsk /scan /F" run in a Command Prompt as Administrator restored the filesystem. The partition table was still OK according to TestDisk, but both TestDisk and Windows itself could not access the partition. And after that Windows complained that the partition was not formatted and refused to open it. I think Reflect even checks a disk before starting the backup. I agree that it's weird (and probably a coincidence), since the last file I saved to that partition was fine on Friday evening (a MP3 that I played multiple times). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |