@alex6dj Hello there, and welcome the the Rockstor community forum.
The boot message indicates a fail of the system file system (Label: ROOT). And given this happens only on reboot I’m wondering if this is just a space issue. Our installer defaults to boot to snapshot, even if there is not enough root to support it. That way we ensure this capability exists. However if the is in fact insufficient room for these snapshots to be taken it may very well fail in this way.
Does your system drive conform to the current:
Minimum system requirements: Quick start — Rockstor documentation
When we moved to our “Built on openSUSE” base we increased it. But as of v4.5.4, our first Poetry based build where we basically build many of our dependencies upon install, our install and resulting install, takes a lot more space:
V4.5+ Testing Channel Changelog - #4 by phillxnet
The existing recommendation for minimum system disk should be enough however.
Let us know if this possible cause may be relevant in your case. I.e. what is the size of the system disk you are experiencing this failure on. Also could the dive have hardware failures later on in its surface that are only provoked, similarly, by our now much larger install. Our pre Poetry installers were around 600 MB, but we are now at around 900 MB!! The modern nature of our newer build is definitely worth the space but I was a little disappointed with such a jump.
There are memory and drive testing tips in our:
Pre-Install Best Practice (PBP): Pre-Install Best Practice (PBP) — Rockstor documentation
Another caveat that may be relevant here, if you have used a different system disk for the v4.5.6-0 install but left the existing v4.1.0-0 disk attached, that’s not going to work. We basically fail in such a scenario according to:
But that look different to what you have described. And from the report, and memory, it fails the install. However I have seen a reboot (after successful install) be affected by a prior existing system disk, such that the reboot then failed due to conflicts.
Another caveat is that on install (first run on rockstor-pre) our Postgres database is established, at in turn creates yet more space requirement.
Installed and setup before first reboot:
localhost:~ # btrfs fi usage /mnt2/ROOT | grep 'Device allocated:'
Device allocated: 2.52GiB
And after the first reboot the allocated remains unchanged but the “Used:” element is around 10 MB or so larger.
So all in still fairly manageable, but once the ROOT snapshots start mounting, especially after changes (OS updates) up this can increase significantly.
All pending updates to our 4.5.6-0 based downloadable installer (rockstor-4.5.7-0 not included), once installed, push the Allocated and Used to:
Device allocated: 3.52GiB
There is a kernel update in there so that’s fairly large. Note we have an additional Chunk (1GB) allocation having taken place now.
Could it also be that there was some data transferred to the system pool (via a share created on the ROOT pool) prior to the first reboot after install. Our installer does a kexec (kernel switch) from that of the installer to that of the installed image during the first boot. But on reboot the installed image kernel is first to kick things off.
Hope that helps, and let us know some more info and if the system drive is failing later on its usable area or the like. We may also take up more memory now I think, but again not much more.