How to add NAS to casaos

It looks like CasaOS is recognizing your network storage in the “Files” app, but it’s not showing up on the homescreen or being found by apps like Nextcloud and Jellyfin under /mnt/. Here are some steps you can try to resolve the issue:

1. Check Mount Points and Permissions

First, let’s ensure that the network storage is correctly mounted under /mnt/:

  1. Open a terminal and run:

    df -h
    

    This will show you all mounted filesystems. Verify that your network storage is listed and properly mounted under /mnt/.

  2. Next, check and adjust the permissions of the mount point:

    sudo chmod -R 775 /mnt/your-network-storage
    sudo chown -R your-user:your-group /mnt/your-network-storage
    

    Replace your-network-storage, your-user, and your-group with your specific names.

    Note: The 775 permission gives read/write/execute access to the owner and group, and read/execute access to others. Be cautious when changing permissions, as it can affect system security.

2. Check Docker Bind Mounts

Ensure that the network storage is accessible within the Docker containers running your apps:

  1. Locate the Docker Compose files for your apps (typically in /var/lib/casaos/apps).

  2. There’s a script available to make editing these files easier:
    Added an edit CasaOS apps script

  3. Modify the volumes section to include the storage path as a bind mount:

    volumes:
      - /mnt/your-network-storage:/mnt/your-network-storage
    
  4. Alternatively, you can add this bind mount through the CasaOS web interface:

    • Go to the app’s settings page
    • Look for an option to add or modify volume mounts
    • Add the path /mnt/your-network-storage:/mnt/your-network-storage

Additional Resources

For more advanced mounting options, including how to migrate CasaOS data to a new drive and mount it permanently, refer to this community guide:

Next Steps

After applying these changes:

  1. Restart the affected Docker containers or the entire CasaOS system.
  2. Check if the apps can now access the network storage.
  3. If issues persist, check the system logs for any error messages related to mounting or permissions.