Hi Adrian, Thanks for the detailed report (nice system btw!). I'd recommend running Vagrant with the debug flag, like `vagrant ssh --debug`. That will show a detailed log of all the commands Vagrant is running. It could be that something like a PowerShell script or some other host introspection is accessing the magnetic disks.
Please let us know if you find anything interesting! Cheers, Jeff On Thu, May 7, 2020 at 12:07 AM Adrian Wallaschek <adr...@wallaschek.de> wrote: > It is not a matter of a VM. The magnetic disks are just in the host. They > are not used by any VM nor VMware nor Vagrant. Right now, my MP3 collection > is on them. The whole Vagrant and VM stuff ist on SSD. > > But wenn I run "vagrant ssh" (e.g.) in the Powershell, then it first spins > up the HDDs. They are not in the PATH, they do not contain Software, > nothing. > > I beliebe from some weird reason vagrant when starting enumerate the disks > in the system and checks for - maybe - config files or so on each one of > them. > I would think that somebody would know or recognize this behaviour and > give me a hint on how to inhibit that. (config directive, whatever). > > So to make it clear: even if no VM is running .... this happens when > running vagrant: it wakes up my HDDs (Y: and Z:, while VMware and Vagrant > are on V: and system is on C: each on separate physical volumes). > > > To explain it in more detail: > > C: is a mirror set of two NVMe SSDs (2x 1TB) > V: is a striped volume of two other NVMe SSDs (2x2TB) > some other SATA SSDs (4 pcs, unrelated) have own drive letters > Y: is a magnetic disk (8TB) > Z: is a magnetic disk (ditto) > > If on V: I run vagrant whatever, the command spins up Y: and Z:, not only > that ... it also waits for the spin up to complete, which is boring me. > > > Does that kind of explain the problem better? > > > Am Dienstag, 5. Mai 2020 11:06:37 UTC+2 schrieb Alvaro Miranda Aguilera: >> >> What about you mount in the guest some remote filesystem ?? >> >> in that way will be accessed only when needed. >> >> without much information about how your pc looks like, boot disk, >> filesystem layout, will be a lot of guessing. >> >> So i would take the simple route and use a filesystem to the VM. >> >> Alvaro. >> >> -- > 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/95992818-0bd1-41b4-843c-4fdc0b1f0132%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/95992818-0bd1-41b4-843c-4fdc0b1f0132%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAAf6Gac8v0W%2BWnCrQ-2QVCGGrfcfCddu%2B7rjLgT4bLLxSu9UxA%40mail.gmail.com.
