Hi Andrew, Correct me if I'm wrong, but you expanded the VMDK to VDI from 30 GB to 146 GB using VBoxManage? And then you wanted to use firstboot-growfs to reboot and reconfigure the disk (inside the OS) so that FreeBSD can see the expanded disk?
I haven't used FreeBSD in a while but, if I'm not mistaken, if FreeBSD installer creates MBR partitions on your disk, then FreeBSD also creates UFS slices within a partition. In this case, GrowFS would need to expand both the partition (whether primary or logical) and the slices within it. If FreeBSD installer creates EFI partitions, similarly, GrowFS would need to expand the EFI partition and the slices within it. Given that you don't see anything in /var/log/messages, I would confirm the size of the partitions (through fdisk/sgdisk, or similar tools). -- 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/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/a064607c-fa5f-40b0-a6d6-dee9b440206b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
