Anyone use Veracrypt? CHKDSK issues at boot?
Discussion
I decided to give it a go on my full system. Currently done that sans my Win10 install which is unencrypted.
I'm having issues with CHKDSK triggering at boot. Everything apparently checks out, but it can be time consuming. 20 min boot times? No thanks.
Currently run Win7 C on primary drive. Full sys partition encrypted. Boot loader at front.
Win 10 on another drive, so Win boot loader was present to manage that. Win select boot loader behind the VC one.
"D" drive is a fully encrypted volume that is mounted on load into Win7 using the system encryption password (system fav)
It's mounted in Win10 if I provide the password upon logon (user fav)
"S" drive is just an old random scratch disk.
So in Win7 I see C D S. The Win10 drive and the encrypted 'chunk' that D mounts from are just un-defined drive letters to avoid confusion.
In Win10 I see C D S. The Win7 drive and encrypted 'chunk' that D mounts from are un-defined also.
The main question is, until I had this issue (I think) I just left all the drive letters present, so Win10 could 'see' Win7 as Z, and Win7 'saw' Win10 as Y, and the D drive encrypted chunk was mounted as E in both OS.
Up until that point it appeared to operate without issue.
The CHKDSK concern seems to be a problem when I've been in one 7 and then run 10, or vice versa, almost like they're not happy that entire drives are being unmounted by the OS and maybe having data changed... CHKDSK is then noticing this and just doing safety checks?!
It seems if 7 loads, then the 10 drive, the D drive 'holder' and the S drive are checked.
If 10 loads, then the 7 drive, the D drive 'holder' and the S drive are checked.
From what I can see they all check out ok... but I'm a bit worried about data loss.
Possibly a question for dedicated VC forums, but I thought I'd ask here first.
Just to confirm, all data is backed up.
I'm tempted to just decrypt it all and run all the drives exposed in both OS again and then slowly swap back to see what triggers the issue.
I'm having issues with CHKDSK triggering at boot. Everything apparently checks out, but it can be time consuming. 20 min boot times? No thanks.
Currently run Win7 C on primary drive. Full sys partition encrypted. Boot loader at front.
Win 10 on another drive, so Win boot loader was present to manage that. Win select boot loader behind the VC one.
"D" drive is a fully encrypted volume that is mounted on load into Win7 using the system encryption password (system fav)
It's mounted in Win10 if I provide the password upon logon (user fav)
"S" drive is just an old random scratch disk.
So in Win7 I see C D S. The Win10 drive and the encrypted 'chunk' that D mounts from are just un-defined drive letters to avoid confusion.
In Win10 I see C D S. The Win7 drive and encrypted 'chunk' that D mounts from are un-defined also.
The main question is, until I had this issue (I think) I just left all the drive letters present, so Win10 could 'see' Win7 as Z, and Win7 'saw' Win10 as Y, and the D drive encrypted chunk was mounted as E in both OS.
Up until that point it appeared to operate without issue.
The CHKDSK concern seems to be a problem when I've been in one 7 and then run 10, or vice versa, almost like they're not happy that entire drives are being unmounted by the OS and maybe having data changed... CHKDSK is then noticing this and just doing safety checks?!
It seems if 7 loads, then the 10 drive, the D drive 'holder' and the S drive are checked.
If 10 loads, then the 7 drive, the D drive 'holder' and the S drive are checked.
From what I can see they all check out ok... but I'm a bit worried about data loss.
Possibly a question for dedicated VC forums, but I thought I'd ask here first.
Just to confirm, all data is backed up.
I'm tempted to just decrypt it all and run all the drives exposed in both OS again and then slowly swap back to see what triggers the issue.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff