My pool has gone read-only. I think I know why - it is likely self-inflicted and related to Pool is read-only - #8 by wdc Troubleshooting steps from that post haven’t worked so I’m on to a new plan.
I have good backups and my Rockon configurations, etc. are documented. My thought is to delete the pool (“Pool1”), recreate it, recreate the shares, recreate the Samba shares, and restore the data. Specifically:
Stop the Rockon service.
Delete Pool1.
Create a new Pool1 using the same disks.
Recreate the shares (assumption: they would have been deleted automagically in step 2).
Recreate the Samba shares.
Re-enable the Rockon service and test/correct/reinstall as needed.
My questions for the smart people here:
Is that a sensible plan? e.g, should I manually delete Samba and disk shares prior to deleting Pool1?
Have I missed something? Am I doing it right?
The Rockons share is on Pool1 (not ROOT); I”m unsure if restoring that is a good plan or I should just reinstall my Rockons. In any case, that may be the easy part.
I’m running Rockstor 4.6.1-0.
Pools (Note that WD8TbExt is my backup pool; a USB-attached drive.)
I would do a re-installation. For that the configuration backup functionality can be your friend (mostly ). If you are planning on re-creating the pool1 and its shares the exact same way/naming, etc. (you are correct, the shares will be deleted along with the pool and all their data), you could take the configuration backup before removing samba shares and shut down your Rockons.
Once you’ve rebuilt the Pool and the shares (and - you don’t have to, but just in case - assign the Rockon pool share in the Rockon service), use the restore configuration backup that you took prior to blowing away the pool. That way, it should automatically restore your samba shares and Rockons and you don’t have to manually create them.
I don’t remember whether having active samba share definitions prevents you from deleting the pool, but I think it does, because when you try to delete a share that has a Samba export Rockstor stops you from doing that.
ah yes, because you the file system is mounted as read-only, you can’t make any changes (including a pool deletion). And since that’s your fundamental problem, we don’t need to discuss on how you can mount it in degraded or just read/write mode ..
I think the wipefs is probably the option you have to go with at this point. Not sure, but you might have to unmount the pool as well before the wipefs (but you’ll find out).
wipefs worked. I then rebuilt the pool and shares keeping the same names. The config restore brought back the rockons but not their configs; it also didn’t recreate the Samba shares. I think this was because it initially errored on a rockon that I hadn’t deleted so perhaps the process stopped at that point.
Not a big deal. Samba shares were simple to recreate. Files are restoring now (that will run into the night, I think) and I’ll recreate rockon configs once the restores are done.
Thank you again for the help and the sanity checks.
). If you are planning on re-creating the pool1 and its shares the exact same way/naming, etc. (you are correct, the shares will be deleted along with the pool and all their data), you could take the configuration backup before removing samba shares and shut down your Rockons.
