Hi again. Just an update:
- the debug log showed nothing I could identify as relevant - as I suspected some code to traverse the drive-letters in search of something, whatever, I unmounted the HDD from Y: and Z: and mounted them onto some directory mount point on the C: drive. Thus I assured that no reasonable data-access would hit the disks. I am pretty sure that Vagrant does not traverse directories. The log would show and it would be "mind-blowingly" slow. Effect? None? Still the drives spin up when vagrant comes to play. I take a few consequences from this: - I stopped suspecting the root-cache in the vagrant-area - I begin to suspect Windows. For some reason, likely the powershell or some system call spins up the drives. I will not try to debug Windows. It is by far easier to configure the drives to not go to power-save mode early. This is slightly frustrating but pursueing the matter further? With Microsoft? I do not hate myself enough to do that. So thanks for the advice, but I have to take the easy way out. Best regards, Adrian -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2def9db9-faa9-45ac-a32c-8d4d1fc5960a%40googlegroups.com.
