Not sure if this will make much sense as i don't fully understand how this happens but hope someone is smarter then me and can give me some pointers:

 

Issue:

I have share called Download on a cache drive.

A while ago (2 months ago) it suddenly split the directory i linked to over 3 data drives (or maybe it was there all along?) and 1 or 2 of the drives had actually two Download directories on it; one with capital D and one with a regular d.

I couldn't access the Download share from a remote windows PC anymore.

 

My poor fix:

I am not fully sure how i fixed it anymore but i logged in on the Unraid PC and used the Midnight Commander to copy most of the content to a single drive (pretty sure i was missing stuff still which i couldn't find anywhere) and to a single directory called download.

It was quite messy but in the end i got it in one drive.

Somehow i managed to remove or disable the Download share and relink it to the correct directory again.

This didn't go without problems as for a couple of minutes i couldn't restart Unraid anymore. Again i don't remember how i fixed it which isn't quite helpfull i know.

 

And it's back!

So a few days ago the same problem returned!

I can't access the share remotely and yesterday i also noticed SABnzbd which is supposed to run on the cache drive stopped working too. Sickbear still works but now i'm starting to wonder if it is actually running on the cache drive and maybe the cache drive is just failing?

The drive overview doesn't show any issues but when i tested the cache drive it stuck at 90% for 30mins before i canceled it while it did 0-90 within a fraction of that time.

 

Help!

Any ideas what might have caused this, how to fix it and how to prevent it in the future?

I installed Unraid in June 2012 so i'm still using that version. (which i can't look up atm)

If you need any other info, let me know and i will try to get it.

 

Thanks in advance for any help!

 

 

You are probably giving the drive a normal name.

 

Example: If you create a share on the cache drive called SUPERCACHE

 

Then the mover will start moving it to the data drives and create a share for it.. Since standard all drives are included it will split your data over all drives using your generic rules for that.

 

If you want to avoid a cache directory beiing moved you need to make the share "cache only" (that is an option under share settings), or create the directory with a leading dot (like .SUPERCACHE), a leading dot is the equivalent of a hidden directory in unix and will prevent the mover from taking action on it. The "share only" setting is the method you should use, the dot method works also.

 

Thanks for the quick reply!

Let me see if i understand you correctly:

 

The drive name needs to have a normal name, does this need to be all CAPS?

Or do you mean the folder/directory name ór the share name? (or all of the above?)

 

I will see if i got the cache only option set or not. I'm pretty sure i've set it to a single drive so it wouldn't spread but i might have ballsed up keeping it on the cache drive, didn't realise it could move everything to a new drive automatically if it doesnt fit on the original drive anymore.

Also, it has split the download directory over multiple drives anyway, not sure how it managed to do that yet.

 

You think setting the mentioned settings correctly can fix everything or am i likely to make a brand new DOWNLOAD folder (all caps right?) and make a new share to it?

 

Thanks once again!

Maybe I understood your question wrong..

 

Your issues is that you had a 'Download' directory and now all of a sudden you also have a 'download' directory on your unraid system and the share you access from windows is now empty ?

I might have multiple issues actually but they are all related.

 

Like you said i had a Download directory and a share with the same name pointing to that directory.

Now i have a 'Download' and a 'download' directory and can't access them from windows, not just empty... it just can't access it as if it's pointing to a non-existing directory.

 

Also the Download folder was original on my cache drive. Now it seems to be relocated and spread over my 3 data drives.

Two drives contain both a 'Download' and a 'download' folder and the third only has a 'download' folder.

The splitting of the directory in two and the relocating might have been unrelated but i doubt it, hadn't notice this before until the share didn't work anymore (which has happened twice since june)

the second issue is what I described. a directory on the cachedrive will become a share unless it is hidden.

I will start with keeping the download directory on the cache drive by setting that checkbox then, i'm guessing that is preferable to the hidden option.

Just need to get everything back to the place it is supposed to be then and then hope it won't happen again.

 

En bedankt voor de hulp!

With "cache only" checked it will not !

I will start with keeping the download directory on the cache drive by setting that checkbox then, i'm guessing that is preferable to the hidden option.

Just need to get everything back to the place it is supposed to be then and then hope it won't happen again.

 

En bedankt voor de hulp!

 

You can turn SMB-sharing off for the cache-only share and it won't appear as a share.

I bet you made a share called downloads but in one of the plugins you likely put in /mnt/cache/downloads/*** as the location to use. The Exact name including capitalization is important in Unix OS's. Windows doesn't care but it get's awfully confused when it finds network share items with same name but different capitalization.

 

The next issue you have is that you didn't set the downloads and/or Downloads user share to be cache only. So, the mover has moved the data to the array disks.

 

On the server;

Move the contents of downloads to Downloads and move all the Downloads on the array disks to the cache disk.

Delete all the downloads directories and delete the Downloads directories on the array disks.

Start and stop the array to get rid of the downloads share.

Make a user share called Downloads (it actually should exist).

Set it to be cache only.

Make sure all the plugins are using "Downloads" and not "downloads".

 

 

I had this with dropbox... The plugin wrote inside a share and because it did captilization wrong it ended up creating a new share.

Bit late reply but i fixed it, thanks all for the input!

 

I did indeed move everything to the download directory on the cache drive, set it to cache only (i missed this function in the past it seems) and removed the download directories on the other drives.

It was a long and time consuming process (which teaches me to keep my download directory better under control) but everything worked as it was supposed to in the end.

 

Happily using Unraid once again