24.10
I’ve been playing around with ‘immich’. Now I wanted to start fresh and for that simply delete the child dataset ‘immich’ and then create it again.
Had this issue before and I tried almost everything. then Install the File browser app from the store I managed to delete the folder without issue.
I think this is a glitch. Give it a try.
This is interesting. Can you clarify the timeline and the steps you took a bit more?
I’m gathering that at some point you created a dataset for immich and then installed the app pointing at your immich dataset host path.
Then you decided to start fresh so you deleted the existing dataset.
You did this using the Datasets screen in the UI?
Had you already deleted the installed immich app before removing the dataset? If so did you use the “Remove ixVolumes” when you deleted the app?
I don’t see anything wrong with the error message. It tried to create a dataset and then told you it couldn’t do that because something already exists at that path. It didn’t specify whether the object at that path was a dataset or a directory.
Via the webgui I created the child dataset ‘immich’ inside the dataset ‘apps’
via the shell I created the folders required for immich inside the immich dataset: library, uploads,thumbs,profile,video,backups,postgres
via the webgui I added and configured immich, pointing to the folders inside the immich dataset
played around with immich until I decided its time to start fresh and deploy it ‘for real’
stopped the app via the webgui
via the webgui I delete the child dataset ‘immich’
then via the webgui tried to create it again, got the error that it already exists
rebooted TrueNAS
via the webgui tried to create it again, still got the error that it already exists
via the shell found that the folder ‘immich’ with all subfolders still existed
deleted the folder ‘immich’ using rm -r , now I could create the child dataset
I did not remove the immich app - I only stopped it.
I should have made a screenshot of the error window in the webgui as that read ‘dataset allready exists’.
You are right that the actual error message inside the collapsed window (which I posted) is correct as it says that the path exists which is how I found out.
The error message inside the window should also say “path exists” not “dataset exists”.
This lines up with what I was suspecting, which is that if you tried to delete the dataset without first removing the app and it’s mounted host path(s), that may have prevented a full deletion of the data.
If so there should be a way to implement some better error handling or at least a warning of the possibility.
As @Johnny_Fartpants suggested, you should submit a bug report for this and we can investigate further.
Agreed. Please include that in the bug report as well.