which disk organisation for a stable system?

nakamura85

I had a lot of problems with Ghostbsd and the updates, and some times, I lost my configuration and some data.
Now the data are in a separarte disk.
The OS is in a SSD (SSD1), and for a new installaton (because of a problematic update), I have installed the last version in a second SSD (SSD2). After the reboot, i try to import the pool in SSD1, I can not use the system (for example: # ls: not found...). 2 pools with an OS, is not a good idea, it seems.
I wonder if it is possible to organise the SSD1 with the OS, which is crashed at each re-installation,
and SSD2 with a pool "/home/myuser",
I think it is necessary to create a link in SSD1 /home/myuser to the pool in SSD2?
In SSD1 /home/myuser is a link to the directory in SSD2; the pool in SSD2 is named "myuser", with a mount point in /home. Is it correct? Or /home/myuser?
Thanks for your ideas.

vimanuelt

You are on the right track. I keep the OS and DATA separate, too. Using a pool for '/home/myuser' is what I do. Eric is working on a new installer. You will need to submit a feature request on GhostBSD's github site to get your idea included. ghostbsd/issuesissues/new?assignees=&labels=feature&template=feature_request.yaml

nakamura85

Thanks for your answer.
During a re-installation I unplug the SSD2, for the security of my data.
After installation, I import the pool "myuser", I erase the directory /home/myuser and create a logical link to "myuser" in
SSD2. And I attribute the mountpoint /home/myuser for the pool "myuser".
Correct?
Or the logical link is unuseful with zfs?
Is there a conflict; /home/myuser is created during Ghosbsd installation, and I mount "myuser" in /home?
So, 2 "myuser" in /home.