Podcast about my frustrating GhostBSD upgrade experience. (video)

GNU2BSD

If anyone is interested I was a guest on the Linux OTC video podcast with some of my fellow hosts from the mintCast, a Linux podcast, where I had a chance to express my long positive experience with GhostBSD and then sudden frustration with the GhostBSD upgrade experience. Maybe my own fault for having a small hard drive, little RAM, and a lack of understanding about ZFS. But nonetheless it starts in detail at 13:18 and went on for most of the show. Sharing while I am still deciding if I have it in me to upgrade my hardware and then start over with a re-install to make GhostBSD usable again.

Linux OTC

vimanuelt

While ZFS is an excellent filesystem, it was designed with multi-disk systems in mind, where features such as redundancy and data integrity provide the greatest benefit. GhostBSD chose to support a single filesystem (ZFS) to reduce the problem space. Supporting multiple filesystems requires significant development, testing, and maintenance effort, and GhostBSD does not currently have the developer resources to do that effectively. For much of its history, development has depended largely on the efforts of a single maintainer.

Although many users run GhostBSD successfully on laptops with a single disk, the system is particularly well suited to desktops and workstations with multiple drives, where ZFS can take full advantage of mirroring, redundancy, snapshots, and other advanced features.

Before investing in a larger disk and additional RAM, I suggest trying FreeBSD. It offers a different experience from GhostBSD and provides useful perspective on the strengths and trade-offs of each system. Having that contrast can help you better appreciate what GhostBSD and FreeBSD each bring to the table.

Once you have upgraded your hardware, I would recommend giving GhostBSD another try. The additional storage and memory should provide a more comfortable environment and allow you to take fuller advantage of what GhostBSD has to offer.

GNU2BSD

vimanuelt I actually am using a desktop with GhostBSD and it worked just fine with the previous version despite limited RAM and a single system SSD. The thing is I could easily add a spare external hard drive to it right now if I need extra space for snapshots and backups. I even asked about doing this in a recent thread here on the forum, but I didn't get an answer as to how to do it. My problem may very well be solvable even now for all I know, but the GhostBSD documentation barely explains anything about ZFS, which it really should for a system that is geared towards people trying FreeBSD on the desktop for the first time if it's so integral at this point. Could I have added a 300 GB external hard drive and used that for my snapshots before my upgrade instead of unknowingly and fatally filling up nearly all of my main system drive? Could I still do that now after the fact? I wish I could find the answer in the documentation or someone could explain it to me.

vimanuelt

A Short ZFS Guide for GhostBSD and FreeBSD Users

What Is ZFS?

ZFS is both a filesystem and a volume manager. Unlike UFS, where partitions, filesystems, and storage management are separate tasks, ZFS combines them into a single system.

A ZFS installation consists of one or more storage pools called zpools. Filesystems are created inside these pools.

Basic Terms

Pool (zpool)
A pool is a collection of storage devices managed by ZFS. It is roughly equivalent to a storage container.

Dataset
A dataset is a filesystem within a pool. Datasets can have their own properties, quotas, compression settings, and snapshots.

Snapshot
A snapshot is a read-only copy of a dataset at a specific point in time. Snapshots consume little space initially and are useful for recovery.

Boot Environment (BE)
A boot environment is a bootable snapshot of the operating system. Before major upgrades, GhostBSD can create a new boot environment, allowing you to roll back if something goes wrong.

Common Layouts

Single-Disk System

Most GhostBSD installations use a single pool named zroot.

Both the operating system and user data reside in the same pool.

Two-Disk System

A more flexible arrangement separates the operating system from user data:

zroot  (OS)
└── ROOT

zdata    (User Data)
├── home/<username>
├── documents
└── backups

This arrangement simplifies operating-system reinstallation and backup management.

Useful Commands

Display pools:

zpool list

Display pool status:

zpool status

List datasets:

zfs list

List snapshots:

zfs list -t snapshot

Display space usage:

zfs list -o name,used,available

Creating Snapshots

Create a snapshot:

sudo zfs snapshot zdata/home@before-upgrade

List snapshots:

zfs list -t snapshot

Delete a snapshot:

sudo zfs destroy zdata/home@before-upgrade

Compression

ZFS compression is generally recommended:

sudo zfs set compression=lz4 zdata

Compression is fast and often reduces storage usage without noticeable performance loss.

Monitoring Drive Health

Check pool health:

zpool status

A healthy pool reports:

state: ONLINE

If errors appear, investigate them promptly and ensure backups are current.

Scrubs

A scrub verifies data integrity and repairs corruption when redundant copies are available.

Start a scrub:

sudo zpool scrub zroot

Check progress:

zpool status

For most desktop systems, a monthly scrub is sufficient.

Backups

Snapshots are not backups. If a disk fails, snapshots on that disk fail with it.

Maintain at least one separate backup, preferably on another disk or system. ZFS send and receive can efficiently replicate snapshots between pools.

Best Practices

Enable compression.
Take snapshots before upgrades.
Scrub pools regularly.
Monitor zpool status.
Keep backups on separate storage.
Consider separate pools for the operating system and user data when possible.
Avoid running a nearly full pool. Keep at least 10–20% free space available.

vimanuelt

A Short bectl Guide for FreeBSD and GhostBSD Users

What Is a Boot Environment?

A boot environment (BE) is a bootable copy of your operating system stored on ZFS. It allows you to test upgrades, install software, or modify system configuration without risking your current working system.

If something goes wrong, you can boot an earlier environment and continue working.

Viewing Boot Environments

List all boot environments:

bectl list

Example:

BE              Active Mountpoint Space Created
default         NR     /          2.1G  2026-06-01
pre-upgrade     -      -          500M  2026-05-31

Active Flags

N — Active now.
R — Active on reboot.
T — Active for the next boot only.
Combinations such as NR and NRT are possible.

Creating a Boot Environment

Before making major changes:

sudo bectl create pre-upgrade

This creates a new boot environment cloned from the currently running system.

Testing Changes Safely

The safest workflow is to activate a boot environment for one boot only:

sudo bectl activate -t pre-upgrade
sudo reboot

The system will boot into pre-upgrade once. If the upgrade fails, a subsequent reboot returns to the normal default boot environment.

Making a Boot Environment Permanent

If testing succeeds:

sudo bectl activate pre-upgrade

Future boots will use this environment until another boot environment is activated.

Working with Snapshots

Create a snapshot of a boot environment:

sudo bectl create pre-upgrade@clean

List snapshots:

bectl list -s

A snapshot is not a boot environment and cannot be activated directly.

To create a new boot environment from a snapshot:

sudo bectl create -e pre-upgrade@clean recovery

The new boot environment can then be activated and booted.

Mounting a Boot Environment

Mount a boot environment for inspection:

sudo bectl mount pre-upgrade /mnt

When finished:

sudo bectl unmount pre-upgrade

Renaming a Boot Environment

sudo bectl rename pre-upgrade freebsd-15.0

Descriptive names make older environments easier to identify.

Removing a Boot Environment

Delete an unused boot environment:

sudo bectl destroy old-be

Delete a snapshot:

sudo bectl destroy pre-upgrade@clean

Only remove environments you no longer need.

Recommended Upgrade Procedure

Create a boot environment:

sudo bectl create pre-upgrade

Activate it for one boot:

sudo bectl activate -t pre-upgrade
sudo reboot

Perform the upgrade.

If the system operates correctly, make the boot environment permanent:

sudo bectl activate pre-upgrade

Keep the previous environment until you are satisfied that the upgraded system is stable.

Best Practices

Create a boot environment before every operating-system upgrade.
Use activate -t when testing significant changes.
Keep at least one known-good boot environment.
Remove obsolete environments periodically.
Remember that boot environments protect the operating system, not your personal files.

Remember

Boot environments are one of the most valuable features of ZFS. They provide a simple method of testing upgrades and recovering from mistakes with little more than a reboot.