I've used Firstboot-growfs a few times and it usually goes without a snag. I touch /firstboot, reboot the box and when it comes back up it resizes the partition and resizes the filesystem.
I've just spun up a FreeBSD 12 box, [vagrant@freebsd ~]$ freebsd-version 12.0-RELEASE-p5 I was able to resize the VMDK (by converting it to a VDI.. etc) 3. Name: ada0p3 Mediasize: 32212254720 (30G) <snip> type: freebsd-ufs index: 3 end: 65011837 start: 2097278 Consumers: 1. Name: ada0 Mediasize: 157286400000 (146G) Sectorsize: 512 Mode: r2w2e5 but I can't seem to get past this point. Nothing shows up in /var/log/messages or in dmesg to indicate that there was a failure. Strangely enough on reboot, the triggerfile /firstboot is gone as if to indicate something was done. Thanks. -- 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/69c40317-dbfe-4915-8eb6-546665435a90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
