6
1
Context: I decided to encrypt a 2TB Internal Sata II hard drive I use for personal files (photo collections, tax prep PDFs, hosting a synced Dropbox folder, some non-HD video files, driver install backups, etc). The drive is nearly full of content at this point; and I store new files to another larger disk, as well as backup the 2TB to the larger drive.
I'm using the current VeraCrypt version (VeraCrypt 1.0f-2). And I used the standard Volume Creation Wizard for full drive/partition encryption, with no wipe (fast), and basic AES settings... just to keep thieves hands off my data (I'm not worried about the CIA/NSA).
System is Win7 64bit OS (run off a nice SSD), Quad Core 2.6ghz AMD Athlon II, 8GB 1333 DDR3 RAM, the hard drive being encrypted is a fairly old Western Digital formatted to NTFS (it ran fine prior to this process being started).
Questions 1 + 2: Why is this going to take nearly 4 whole days to complete (96h; I estimated 6mbps)? Is this normal?
I can't find anything online that estimates initial hard drive encryption speeds for any quantities of data on any types of hard drives. Everything says "it just depends on hardware." Which is no help, for even general comparison.
I've read that encryption takes place in the processor, and that it generally runs faster when there are more cores because VeraCrypt uses them in parallel. But my processor is basically at idle! With Firefox open (10 tabs), a file browser, and the encryption taking place I'm averaging around 7% utilization across the cores (it only spikes for a second if I open another tab or start another activity elsewhere).
And the RAM utilization is only at about 25% (normal for just the OS and Firefox).
Questions 3 + 4: Is it normal for a processor to appear at idle while completing the initial encryption of a large hard drive/partition? And, is there an option somewhere that can tell VeraCrypt to use whatever resources it wants to speed up the process?
Note: The majority of the 'speed' questions I've encountered online are regarding the initial mounting with VeraCrypt--which is slower than with TrueCrypt because of added security measure--or on the fly encryption/decryption speeds. The questions I've asked are not about those things, but instead specifically being asked to learn from those with experience what kind of speed they experienced during the initial encryption of whole data drives/partitions, not their mounting or on the fly encryption/decryption; as well as what kind of resource utilization is normal (Processor/RAM %).
Encryption is a slow process, but I wouldn't expect it to take 4 days for 2TB. Unless VeraCrypt is written poorly. – RoraΖ – 2015-04-15T11:38:46.880
1Some of your problem is your drive is nearly full. So the encryption process is going to take longer for that reason. Its also possible the drive isn't healthy, and is encountering errors, or at least Windows is waiting for I/O events to be completed. I would ask this question on the Veracrypt project, why not ask the author, your use case is very specific and not easily replicated. – Ramhound – 2015-04-15T12:09:14.807
2@Ramhound I was hoping to hear from experience, like: "I encrypted a newer, 20% full, SATA III HDD with VeraCrypt (~1TB of data). It took 9hrs, and the encryption thrashed my processor." or "I've encrypted both mostly empty and full drives with VeraCrypt. The full ones took longer, regardless of size"... these types of answers share useful information, from experience. Of course, I noted all of that in the original question. – User832 – 2015-04-15T18:31:18.960
1@Ramhound I do however appreciate your confirmation that some of the issue is likely due to the drive being so full... I suspected that, obviously, but hearing it from somebody else is something. – User832 – 2015-04-15T18:31:42.823
@Rambound This is false. I have a brand new hard drive, a HDD connected in SATA, of 4TB and that I filled with about 2GB of data (so less than 1%) before using Veracrypt. Veracrypt says it's going to take 5 days to encrypt in place, with default settings as OP did. There's something wrong here. And I checked, my CPU has hardware acceleration support for AES (10 Gbit/s according to benchmark). I have a quite fast computer, it's made to compute a lot for research purposes. – gaborous – 2020-02-16T16:38:04.683
Correction: benchmark speed is 10GB/s for AES – gaborous – 2020-02-16T17:30:31.327