Sorry for the dumb question. While learning to manage Zpool, I tried to include my /home/vladas to the general pool as zroot/home/vladas, according to the existing example made by initial installation to HDD:
No error warning issued, zpool history shows /home/vladas added to the pool zroot, yet home directory is empty, and also Openbox menu is not working now.
# zfs set canmount=on zroot/home did not help, # zfs unmount zroot/home responds by cannot unmount zroot/home: not currently mounted message.
I am learning ZFS handbook and manual further, although do not find an explanation yet.
Realizing that the system is locked to read-only, I rebooted as a single user to restore access according FreeBSD FAQ 10.5:
# mount -urv /
No effect. Apparently, because my filesystem is ZFS, not UFS. Its analog unlocked the system:
# zfs set readonly=off zroot
I then backed up my /home/vladas and verified chpass — no credentials has been changed since the day of NomadBSD installation last year.
I have no idea what to do next. ZFS terms in the handbook and manual are not clear to me, a non-techie desktop user. Wich one of create-destroy, attach-detach, import-export, mount-unmount, send-receive, online-offline means including and excluding my dataset to and from a pool?
root@:/# zfs unmount zroot/home/vladas
cannot unmount zroot/home/vladas: not currently mounted
root@:/# zfs unmount zroot/home
cannot unmount zroot/home: not currently mounted
Although zfs list claims zroot/home/vladas is still there in a pool.
# zfs destroy -nv zroot/home/vladas
would destroy zroot/home/vladas
Should I remove -n (no)? I am not sure it would not really destroy all my settings and assets. I am afraid, I will wait for tomorrow.
reverted NomadBSD to the previous state, but /home was not included to the pool during installation, just an empty /usr/home. Thus the desktop remains locked, still Failed to execute login command.
zroot/home canmount on local zroot/home mountpoint /home local zroot/home/vladas canmount on local zroot/home/vladas mountpoint /home/vladas inherited from zroot/home zroot/usr canmount off local zroot/usr mountpoint /usr local zroot/usr/home canmount on default zroot/usr/home mountpoint /usr/home inherited from zroot/usr
…
(Re: your post 2, it seems reasonable to summarise that the user data is not lost; that we should focus on possible explanations for failure to execute a login command.)
I don’t know enough about NomadBSD to tell whether the rollback might have had a negative impact.
My system here was locked from vladas and became read-only for admin.
Then I attempted to fix my pool — the history goes on:
2022-02-27.19:09:57 zfs set canmount=on zroot/home/vladas
2022-02-27.20:04:20 zfs set canmount=on zroot/home
2022-02-27.21:20:05 zfs set compression=off zroot/home
As far as I can remember, /home and /home/vladas were real assets from the begining, and /usr/home was always empty, with no links. Anyway, the system was locked before the mounting attempt — immediately after zfs create -v zroot/home/vladas.