You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really appreciate your work making this container. I was previously using RClone, which is great but I find this much more reliable so far.
I am having one issue however and that is that when the container is shutdown or restarted something is not unmounting properly.
I am running on Unraid, and when I stop the Seadrive container the mount appears to go with it. Meaning it's no longer visible in the file explorer via the Unraid UI.
However running ls -lh /mnt/remotes/ reveals that the mount directory is still there but in an odd state where the user, group, and perms are all just question marks.
This causes an error when starting the container next time that the directory already exists.
if I run fusermount3 -u /mnt/remotes/seadrive followed by rmdir /mnt/remotes/seadrive first, then I can start the container again just fine.
The text was updated successfully, but these errors were encountered:
Thanks for creating an issue. I know this issue exists, but didn't care to fix it yet. I'll try to resolve it within the coming days, now that I know this is a problem for other people as well :)
I really appreciate your work making this container. I was previously using RClone, which is great but I find this much more reliable so far.
I am having one issue however and that is that when the container is shutdown or restarted something is not unmounting properly.
I am running on Unraid, and when I stop the Seadrive container the mount appears to go with it. Meaning it's no longer visible in the file explorer via the Unraid UI.
However running
ls -lh /mnt/remotes/
reveals that the mount directory is still there but in an odd state where the user, group, and perms are all just question marks.This causes an error when starting the container next time that the directory already exists.
if I run
fusermount3 -u /mnt/remotes/seadrive
followed byrmdir /mnt/remotes/seadrive
first, then I can start the container again just fine.The text was updated successfully, but these errors were encountered: