@SatishI Hello again.
You data is most likely just find. Rockstor manages the mounts of all managed pool (btrfs volumes) and their consequent shares (btrfs subvolumes). So if the rockstor.service fails there are not mounts. Which means the mount points will be just that: empty directories awaiting the pool and subsequent shares to be mounted.
3.8.16 to 3.9.2-33 (currently) is a fairly massive jump but I don’t think there were any db changes. But in the mean time there have been a huge number of upstream changes. When you initiated the stable channel subscriptions did you reboot soon there after? It can take quite a while of all of the upstream packages to go in if that is what happened.
To try and further diagnose this, given there were no real db changes, however there was a large migration mechanism change at around 3.8.15:
Upgrading to 3.8.16 from 3.8-14 or before? Read this
this shouldn’t have affected your db update, yet the dependent service of the rockstor.service
, rockstor-pre.service looks to have failed
at the database migration point:
This is odd as we haven’t seen a failure there for quite some time.
As this issue occurred during an update could you given the output of the following command, as your system may be in a partially updated state, although the new rockstor package seems to have gone in ok given your ‘yum info rockstor’ output.
yum update
That should tell us if all is well on the system packages side as it may just be related to that.
As to:
It should be safely tucked away in your data pool / drives which are I suspect, given the failed rockstor service, still unmounted.
You can see what is currently mounted via:
cat /proc/mounts
and to see an overview of all btrfs devices, and their associated pool affiliations via:
btrfs fi show
And assuming you didn’t choose to use your system disk for any data then a fresh install using a different system disk on this machine (make sure to not leave the original attached) is an option here. But note that it is best to first detach all data disks (and the prior system disk), install, subscribe, do all updates patiently (can take 10s of minutes if it’s a slow machine), then reboot to make sure all is ok, then shutdown, re-attach all data pool disks, boot up and import your freshly re-attached prior pool. If done on the same machine (motherboard) then you should get the same appliance id and so the same activation code should work). The Reinstalling Rockstor may be of use here.
But the above ‘brute force’ approach of re-installing will loose all settings. But we do now have the currently undocumented (my fault) command line config backup capability:
which should produce a file of your current settings. But I’m unsure if it will work in your setting, ie broken rockstor-pre.service.
But is an option for re-gaining access to your pool/data and setting up new exports etc for it’s network access. However it may not be all that much hassle to repair this install as we know roughly where it is currently failing.
Lets see the output of that ‘yum update’ command is first and take it from there.