April 15, 201511 yr Hi guys, I have a user share which I created when testing Plex and now I'm no longer running plex I have decided to delete the share Issue is, in windows explorer I right click and delete contents but the folder does not delete. The popup says deleting zero bytes and the folder remains I've looked at the share in the unraid web gui but as the share indicates it's not empty I can't select delete Any one have some ideas? Ps. I'm running v6b12 Thanks Adam
April 15, 201511 yr Telnet into the server, browse to /mnt/user run mc and delete the share from there
April 16, 201511 yr Community Expert If the share is empty, unRAID will actually give you a delete button on the settings page for that share.
April 16, 201511 yr Author Thanks.. I'll try the telnet suggestion. That's the thing, inside the share is a folder which i can't delete. From windows I right click delete but it doesn't actually delete. Although it says folder is zero bytes in size So from the gui, it thinks it not empty an doesn't give me option to delete.
April 16, 201511 yr Thanks.. I'll try the telnet suggestion. That's the thing, inside the share is a folder which i can't delete. From windows I right click delete but it doesn't actually delete. Although it says folder is zero bytes in size So from the gui, it thinks it not empty an doesn't give me option to delete. Yeah, that is often the case, when you run mc you'll be able to delete it, don't worry.
April 16, 201511 yr Author Thanks Sureguy and CHBMP..telnet worked a treat Cheers Next question tho, now that the share deleted, Another "appdata" share was automatically created. I already have one I vreated earlier for docker. Both are are not empty, both have security as public and both export. Except I can't see the new one from windows explorer. Any ideas why/how the second one comes about? Cheers
April 16, 201511 yr Community Expert Thanks Sureguy and CHBMP..telnet worked a treat Cheers Next question tho, now that the share deleted, Another "appdata" share was automatically created. I already have one I vreated earlier for docker. Both are are not empty, both have security as public and both export. Except I can't see the new one from windows explorer. Any ideas why/how the second one comes about? Cheers unRAID automatically creates a share if it finds a top-level folder. One issue is that in Linux case is significant while Windows ignores it and this can lead to unexpected results sometimes. You probably need to check each disk to see if you have appdata top level folders with different capitalization, and if found they need to be made to exactly match the share name you have set up..
April 16, 201511 yr Community Expert Thanks Sureguy and CHBMP..telnet worked a treat Cheers Next question tho, now that the share deleted, Another "appdata" share was automatically created. I already have one I vreated earlier for docker. Both are are not empty, both have security as public and both export. Except I can't see the new one from windows explorer. Any ideas why/how the second one comes about? Cheers unRAID automatically creates a share if it finds a top-level folder. One issue is that in Linux case is significant while Windows ignores it and this can lead to unexpected results sometimes. You probably need to check each disk to see if you have appdata top level folders with different capitalization, and if found they need to be made to exactly match the share name you have set up.. And if you intended appdata to be cache-only as I suspect, make sure you don't have it on any other drive. All user shares including cache: v /mnt/user All user share except for cache: v /mnt/user0
April 16, 201511 yr I had the same issue and couldnt delete plex. Tried a ton of times, but it just wouldnt work. use the advice above to run MC (midnight commander) and you can delete it from there without problems, and then easily kill the share.
April 17, 201511 yr Author Thanks Sureguy and CHBMP..telnet worked a treat Cheers Next question tho, now that the share deleted, Another "appdata" share was automatically created. I already have one I vreated earlier for docker. Both are are not empty, both have security as public and both export. Except I can't see the new one from windows explorer. Any ideas why/how the second one comes about? Cheers unRAID automatically creates a share if it finds a top-level folder. One issue is that in Linux case is significant while Windows ignores it and this can lead to unexpected results sometimes. You probably need to check each disk to see if you have appdata top level folders with different capitalization, and if found they need to be made to exactly match the share name you have set up.. Thanks....Turned out it was the capital A. Once I changed this, all was good Cheers
May 3, 201511 yr I'm also having a problem removing shares. I've looked for the case issue. Not a problem. When i clear either the appdata or plex share names (see screenshot), no delete share button and no apply are available... http://my.jetscreenshot.com/12412/20150503-htpf-198kb
May 3, 201511 yr Community Expert I'm also having a problem removing shares. I've looked for the case issue. Not a problem. When i clear either the appdata or plex share names (see screenshot), no delete share button and no apply are available... http://my.jetscreenshot.com/12412/20150503-htpf-198kb It's not necessary to clear the share name field. All that's required is for the share to be empty. The screenshot says it's not.
May 3, 201511 yr Yeah, i wondered about that. There's no files in it. If you look at the directory in telnet, the directory is empty. the only hidden files in the directory (ls -a) are the ./ and ../ Same for the plex directory... what else could be keeping it from deleting?
May 3, 201511 yr Community Expert So you are doing ? ls -a /mnt/user/appdata What do you get from ? v /mnt
May 3, 201511 yr Ok, think I figured this out. I had tried to delete the directory before I deleted the share. You can't delete the share if the directory has been deleted. Proper steps 1. delete all files in the share (but don't delete the share directory (i.e. \mnt\cache\appdata) 2. From webgui>shares>[sharename], verify that the share empty? is Yes. 3. There should be a delete button just below the share empty heading. http://my.jetscreenshot.com/12412/20150503-6ckn-42kb 4. Click done and the share is removed. Or so I thought. Clicking the Delete checkbox and then click done, DOES NOT delete the share... What am I missing?
May 3, 201511 yr Our posts crossed... Here's the ls and v command output... http://my.jetscreenshot.com/12412/20150503-zqsd-60kb
May 3, 201511 yr Looking at the v /mnt output, why are there two user directories? user0 and user? user0 is the contents of the array excluding any files which are currently residing on the cache drive user is the contents of the array including all files which are currently on the cache drive
May 3, 201511 yr Community Expert user is the user shares including any files that may still be on cache. user0 is the user share excluding any files that may still be on cache. The mover script basically does rsync from cache to user0. The reason I asked for that was to make sure the user share system was working correctly. Instead of clicking Done, you have to click Delete. There is a reported defect that causes you to have to click the checkbox twice enable the Delete button.
May 3, 201511 yr Ha! And I can confirm that 'double click to delete' function. It did what was expected when that happened! Thanks!
September 22, 20205 yr I had the same problem. Easiest solution for me was to delete the share using the app Krusader by djaydev.
January 18, 20215 yr I had this issue recently. The root cause was that I had piHole installed and I modified my router to use piHole for DNS. The errors showed that the TCP connection for Docker was trying to use a local IP address (192.168.1.52) which was a clue I had things configured wrong and thus Docker containers could not be downloaded from the repo. I put my router back to default settings and everything was fixed right away.
Archived
This topic is now archived and is closed to further replies.