I suppose what I am hoping for is that we move beyond the notion that GhostBSD is simply FreeBSD with training wheels, as I mentioned in another thread. :-) When installing, we could select either a basic (single drive) option or an advanced install (multi-drive RAIDZ) option. This could replace the current custom option.
Although desktop users are often assumed to prefer simple, single-disk setups, there is a growing segment, particularly among power users, developers, and professionals, that would benefit from a more robust and modular configuration. Separating the operating system from user data offers several practical advantages. It simplifies system recovery and reinstallation by allowing the operating system to be replaced without affecting personal files. It also enables cleaner upgrade paths, reducing the risk of misconfiguration or accidental data loss. This separation improves compatibility with advanced ZFS features such as snapshots, compression, and replication, and it supports the use of multiple storage devices with redundancy through RAIDZ.
ZFS RAIDZ adds a valuable layer of resilience by distributing data across multiple disks with parity. RAIDZ1 requires a minimum of three hard disk drives and can tolerate the failure of one without data loss. RAIDZ2 requires at least four drives and can survive the failure of any two. This is particularly important for safeguarding user data, including personal documents, multimedia libraries, and development environments. In this proposed setup, a minimum of one drive is required for the operating system, and three or more additional drives are needed to enable RAIDZ for user data.
To support this, I propose enhancing the GhostBSD installer with an optional setup workflow that includes several key features. First, users should be able to select separate disks for the operating system and for user data. The installer should provide a guided interface for creating a ZFS storage pool using RAIDZ1 or RAIDZ2, based on the number of disks available. It should also allow the user’s home directory to reside on the ZFS data pool, mounted during installation. To support long-term maintainability, the installer should be capable of detecting and importing an existing ZFS data pool during future installations. This would simplify disaster recovery and make system transitions more seamless. Additionally, the installer should include a concise explanation of RAIDZ and its requirements to help users make informed decisions.
This enhancement would significantly improve system reliability and provide stronger data protection for desktop users. It would promote best practices in storage management while preserving the simplicity of the default installation path. By presenting it as an advanced option, GhostBSD could serve both new users and experienced users who require more control over system architecture.
