I have installed FreePBX 17 via the ISO method, and it worked without any issues, but it’s not giving the logical volumes enough space. I don’t understand how it’s deciding how much space to give the LV’s… It only gave my root volume 4GB!!! That filled up after I restored my backup. It only gave my /tmp volume 3GB, but I was able to mount over it to restore my backup. All of my drive space is in the /var/spool volume. I have two 480GB SSD’s setup on a raid1. Can someone please tell me how to give my root volume more space? If I need to install Debian first and then use the script method, I will. I just don’t want to go through all of that if it’s just gonna set up the LV’s the same way.
Howdy! Welcome back to the forums.
Can you post the output of vgdisplay and lvdisplay ? Maybe in our pastebin.freepbx.org ?
Standard Debian install will let you lay out the drives as you like. The FreePBX 17 ISO makes assumptions which are geared towards new installations at the factory/warehouse.
Here ya go!
I don’t know how these Debian based systems work, but it sounds like you’re putting your backups in the wrong place. The majority of space should be allocated to a /var partition, and backups should be in that partition. e.g. we store ours in /var/spool/asterisk/backups before copying to external storage. Backup unpacking should happen in /tmp.
Since this is a new system, would it be better to install Debian first and then install FreePBX via the script? If it will allow me to specify the LV sizes that is. I’ve already moved my licenses to this system, but I can remove them.
That’s exactly what happened. I uploaded my backup via the backup and restore module and it attempted to restore my backup. It failed because /tmp was only 3GB. I solved that issue by mounting over that volume and the backup restored as it should have. Now I am running into the issue where / doesn’t have enough space. Like I said, I have a 480GB raid1 setup and over 300GB has been allocated to /var/spool. So, something weird is going on with the partitioning when FreePBX is installed via the ISO. I am thinking about just wiping this system out and installing Debian first then running the script. I am not sure it’s worth the hassel if the script will let me specify my volume sizes.
Ok I’ll shut my RHEL mouth now lol
Well yes. Sangoma make a big announcement about how when FreePBX v17 was launched that with the move to Debian, Sangoma would no longer be releasing ISO versions of FreePBX installs. However, that didn’t stop penguin because within six months of making this announcement he introduced SNGDEB at AsteriCon 2025. So now we’ve gone from “We’re not making ISOs” to “Here’s our ISO you should use this and ignore what we said before”.
The SNGDEB ISO is nothing more than a Sangoma branded and modified version of the Debian 12 install. It does nothing more than install Debian 12 and on completion of the install and reboot runs the same install script we would all run on any other Debian 12 install.
However, since the ISO That Should Not Exist does exist, I’d say you’re still better off with using a standard Debian ISO. SNGDEB seems more problematic than its worth and really doesn’t offer you anything of real substance.
This might get patched soon in the “backup” module by allowing you to specify an alternate restore temp directory when using the fwconsole command line interface e.g. you could point it to somewhere in /var/spool/. (The trade-off in that case would be that you are both untarring and restoring in the same partition – so some size-sanity checks might be helpful to integrate there as well.)
Curious how big was your backup ?
I think it was like 2.9 GB. It was a full backup with CDR. I think once it was uploaded there wasn’t enough room to unpack and restore it.