Firstboot-growfs does not growfs after touching /firstboot

[Andrew Villano]

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.

[Dennis Chang]

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).

[Andrew Villano]

That's correct, I expanded the VMDK to VDI using vboxmanage and I would like firstboot-growfs to reconfigure the disk inside the OS.

I confirmed that the size of the partitions is still 30GB using fdisk.

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/uPBPVKz4CZY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
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.

[Dennis Chang]

I don't know firstboot-growfs (or BSD very well), but my guess is that it applies to BSD slices and not partitions.

My advice to you is to investigate how to expand a partition in BSD. BSD uses similar tools as Linux (which I'm more familiar with),

for instance fdisk (for MBR partitions), or sgdisk (for EFI partitions). There should be a way to expand the partition (in a safe way).

[Andrew Villano]

The way to grow a partition is to use growfs, however you cannot enlarge the root partition while it is in use. Usually this means going down to single user mode via a usb rescue image or the sort while having the root filesystem unmounting, resizing the partition with gparted/fdisk and then enlarging the filesystem with growfs. As these boxes are headless and do not have a console, it is not possible to do this. This is why the firstboot- packages exist, to do this on boot before the filesystem is mounted. However, it doesn't appear they are working as intended.

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/uPBPVKz4CZY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/ba40f5b2-8dd4-4d51-86a7-260d4a9dd2e7%40googlegroups.com.

[Dennis Chang]

Vagrant may be headless, but you can get a console screen through Virtualbox.

Why not use Virtualbox to boot from an ISO and then you can make changes to the partitions?

[Andrew Villano]

I connect to the machine in question over ssh. It is not local and does not run an X server AFAIK.

On Wed, May 29, 2019 at 5:26 PM Dennis Chang <dennis...@gmail.com> wrote:

Vagrant may be headless, but you can get a console screen through Virtualbox.

Why not use Virtualbox to boot from an ISO and then you can make changes to the partitions?

--

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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/uPBPVKz4CZY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/cdc00f02-983a-4484-9d17-e5c449790ff9%40googlegroups.com.

[Dennis Chang]

There is a way in Linux which allows you to rescan the scsi disk and modify the partition table while having booted from the disk/partition.

There might be a way to do the same in FreeBSD.

https://www.freebsd.org/doc/handbook/disks-growing.html

But I should state the obvious, this is not a vagrant problem.

Good luck