- Joined
- Jan 1, 2016
- Messages
- 9,700
Just a warning more than anything for the others out there...
I had just upgraded to TrueNAS 12.0 Core after the release (great stuff).
I wanted to start upgrading my jails... and then I saw that I had an old jail not running since a few months that I should be able to get rid of, having replaced it... so I selected it in the GUI and used the delete function to delete it... fine, I thought...
Then I realized it had not only deleted that jail (called plex), but also deleted the other (still running) jail that I had replaced it with (called plexmediaserver-plexpass).
I guess that the explanation for it is somewhere in the first jail's name being a substring of the second, but that's a really poor result for a GUI operation that clearly should only operate on the selected jail.
WATCH OUT for those of you with similar/derivative jail names.
I am in the process of rebuilding my jail with the script that I had fortunately made during the making of the last one. Nothing lost as I store all my DB and config outside the jail.
I had just upgraded to TrueNAS 12.0 Core after the release (great stuff).
I wanted to start upgrading my jails... and then I saw that I had an old jail not running since a few months that I should be able to get rid of, having replaced it... so I selected it in the GUI and used the delete function to delete it... fine, I thought...
Then I realized it had not only deleted that jail (called plex), but also deleted the other (still running) jail that I had replaced it with (called plexmediaserver-plexpass).
I guess that the explanation for it is somewhere in the first jail's name being a substring of the second, but that's a really poor result for a GUI operation that clearly should only operate on the selected jail.
WATCH OUT for those of you with similar/derivative jail names.
I am in the process of rebuilding my jail with the script that I had fortunately made during the making of the last one. Nothing lost as I store all my DB and config outside the jail.