Jump to content

Appdata is not a shared folder -- how to reset with default shares

This topic contains 21 posts with an estimated read time of 43 minutes. A summary containing the most significant posts is available with an estimated read time of 2 minutes.
View summary
BlackhammerTech
in General Support

Featured Replies

Posted

So I moved my server to a new system.   I wanted to start fresh completely.

 

I had an open afternoon so I decided to do this at work.  My cubicle neighbor walked over, bumped my cubicle and stepped on my usb stick.  I had to get my license ported over to a new stick.  When I boot it up, folders like appdata, iso, etc are not readable and there are no disk shares.

 

How can I start fresh and get this back?

 

Thanks 

  • Quote

    • Solved by BlackhammerTech

    Go to solution
    • Author

    Can you be more specific?   Surely you don't mean the whole file?

  • Quote

    Direct quote from the diagnostics link.

    Quote

    Using this tool will result in a zip file being produced that can be downloaded and then attached to forum posts.

     

  • Quote
    • Community Expert
    1 hour ago, BlackhammerTech said:

    OK.  Attached.


    That is not the diagnostics zip file!

  • Quote
    • Author

    Sorry, I did that previous upload remotely.  I missed that I had downloaded 2 zipped files, and sent the wrong one.

     

  • Quote
    • Community Expert

    This is in your diagnostics from /shares/shareDisks.txt : 

    appdata                           shareUseCache="no"      # Share does not exist
domains                           shareUseCache="no"      # Share does not exist
isos                              shareUseCache="no"      # Share does not exist
n-s                               shareUseCache="no"      # Share does not exist
system                            shareUseCache="no"      # Share does not exist

     

    This indicates that the shares have not been created on the physical disks.  If they did you would see something like this: 

    appdata                           shareUseCache="only"    # Share exists on cache

     

    You could access the disks and generate a directory(folder) in the root of a physical drive for each share.   (EDIT:  Make sure you follow the capitalization of all the letters as Linux is case sensitive!)

     

    (This probably happened because you are using the settings/configuration from an old server on completely brand-new hardware.  Most folks when they do this are moving over the data disks which already have these directories on them...)

    Edited by Frank1940

  • Quote
    • Author

    Thanks Frank1940.  I would have thought that a new install would have created these for me.  

  • Quote
    • Community Expert
    3 minutes ago, BlackhammerTech said:

    Thanks Frank1940.  I would have thought that a new install would have created these for me.  

    It does but yours was not a new install.  The existence and contents of certain files in the /config folder says that that process has already occurred. 

  • Quote
    • Author

    Yes, I foolishly tried out Truenas Scale and found how much more difficult it was compared to unraid.  My Nas shares and Nextcloud worked perfect.   Truenas always had permission errors.  This is my third Unraid install as I increased my drive size and changed physical servers.  I thought that moving the license to a new usb stick would trigger a clean install.  I am just missing it somewhere.  I will do what you said and manually make those if I don't find what I am after.  Thank you for the help.

     

  • Quote
    • Community Expert

    The reason diagnostics shows those shares do not exist is because the array is not started, and therefore no shares existed at the time the diagnostics were taken.

     

    Start the array and post new diagnostics.

  • Quote
    • Author

    I have wiped out completely that set up.  I now have the same issue.  Do I have to wait until the parity sync is done to create /mnt/user/appdata?

     

  • Quote
    • Author

    Array is started.   Went to Settings, Docker, Changed from No to Yes to start Docker.    I get the error message /mnt/user/system/docker.img  "Path does not exist"   /mnt/user/appdata/  "Path does not exist"

     

     

  • Quote
    • Community Expert

    Are the disks formatted? If they aren't the default shares cannot be created.

  • Quote
    • Author
    • Solution

    I started all over, including the reformatting the USB drive.  Installed the array, then took it off line.  Removed the drives and formatted them using Unassigned Devices.  Put the drives back, started the array and all of the shares are there now.

     

  • Quote
    • Community Expert
    On 6/28/2024 at 2:44 PM, BlackhammerTech said:

    Removed the drives and formatted them using Unassigned Devices.

    No need to format disks with Unassigned Devices.

     

    Formatting drives after you assign them is the usual way, and the only way to get a new drive into the array and formatted without rebuilding parity.

     

    https://docs.unraid.net/unraid-os/manual/storage-management/#data-disks

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing