September 23, 201510 yr I just updated from Unraid 6.0.1 to 6.1.3 using the web ui. After booting up, one of my shares is empty save for one folder that has an empty folder inside it. All of my other shares are fine. That share had lots and lots of stuff stored in it...would really like to recover it. Anything I can do?
September 23, 201510 yr 1. Attach the diagnostics zip file to your post. 2. Click on the "View" icon to the right of your disks and browse the disks to see if the content is actually still there. I'll bet it is.
September 23, 201510 yr Author Okay, yeah, I can see the content through the web ui, but not in Windows. I have attached the diag zip. Thanks! mediaserver-diagnostics-20150923-1331.zip
September 24, 201510 yr Author New permissions just finished. Nothing has changed. Anything else I can do?
September 24, 201510 yr New permissions just finished. Nothing has changed. Anything else I can do? post screenshots of what windows is showing within the share and what unRaid's gui is showing within the share
September 24, 201510 yr Author I went in one folder deeper and found a few more files/folders, but nowhere near all of them. I'm running New Permissions again to see if it just missed some for some reason. Once that's finished, I'll post the screens. Thanks!
September 25, 201510 yr Community Expert Have you rebooted the server to check if that fixes the issue?
September 25, 201510 yr Community Expert You could try running the following command from a console/telnet session: ls -l /mnt/disk*/sharename where 'sharename' is the name of the share. The output from that will at least provide a clue as to whether there are any permission/owner issues on the folders in the share.
September 25, 201510 yr Community Expert That screenshot looks OK from a permissions/owner point of view. It shows the 'storage' share containing a single folder called 'backup' - is this what you expect? It might be worth showing screenshots of what you see from Windows, and also what you see from the unRAID GUI as you say you can see what you expect in the GUI, but not in Windows.
September 25, 201510 yr Community Expert I did that a few posts ago. ;-) Missed that - sorry! One anomaly I notice is that when you did the ls command it was for the 'storage' folder. However the GUI shows that the share is actually called 'Storage' (i.e. it starts with a capital S). In Linux 'storage' and 'Storage' are not the same location. Windows is case agnostic but Linux is not. Perhaps you should instead try ls -l /mnt/disk*/?torage to see if you have folders starting both with and without a capital 'S'. If so this could be the root cause of the problem.
September 25, 201510 yr On disk6 you have storage instead of Storage ( small s ) this could be the issue
September 25, 201510 yr Community Expert Okay, can I just change the case in Windows to correct it? No - you will need to correct it from the Linux end (unRAID) and then probably stop and restart the array to pick up the correction. I am guessing that the right solution is going to be to move the contents of the 'storage' folder on the disks that also have 'Storage' (e.g. disk6) to the 'Storage' folder on the same disk. The easiest way to do this will be to use Midnight Commander ('mc' command) from a console/telnet session to browse these two locations to check what you want to keep and then to do the subsequent move. Once you have emptied them the 'storage' folders should be removed so that you only have 'Storage' folders on each disk with exactly the same case in the name.
Archived
This topic is now archived and is closed to further replies.