icarus69

"Invalid folder cache contained within /mnt" Diagnostics attached. Appreciate any help! nas-diagnostics-20250812-1758.zip

My directory in Unraid is a bit of a mess: root@NAS:~# tree -L 1 /mnt/user /mnt/user ├── Games -> ../zfs/Games ├── Google Drive -> ../zfs/Google Drive ├── Media -> ../zfs/Media ├── Movies -> ../zfs/Movies ├── Music ├── MyRekordboxCollection -> ../zfs/MyRekordboxCollection ├── TV Shows -> ../zfs/TV Shows ├── appdata -> ../zfs/appdata ├── appdatabackup -> ../zfs/appdatabackup ├── appdatabackup_tmp_20241004112536 -> ../zfs/appdatabackup_tmp_20241004112536 ├── appdatabackup_tmp_20241004112536_tmp_20241023111607 ├── data -> ../zfs/data ├── data_tmp_20241003014612 -> ../zfs/data_tmp_20241003014612 ├── data_tmp_20241003014612_tmp_20241004112543 ├── data_tmp_20241003014612_tmp_20241004112543_tmp_20241023111616 ├── domains -> ../zfs/domains ├── downloads -> ../zfs/downloads ├── flashbackup ├── guacamole -> ../zfs/guacamole ├── isos -> ../zfs/isos ├── mac_music_mount -> ../zfs/mac_music_mount ├── movies_friends -> ../zfs/movies_friends ├── nextcloud -> ../zfs/nextcloud ├── nextcloud-backup -> ../zfs/nextcloud-backup ├── photos -> ../zfs/photos ├── photos_immich -> ../zfs/photos_immich ├── system -> ../zfs/system ├── tm -> ../zfs/tm └── vm_data -> ../zfs/vm_data I have two questions: 1. How would you suggest storing things differently? For example, moving some of these folders into others, making them subfolders instead 2. How do I move these folders, which are all shares? Is it just as simple as moving it from the Unraid GUI? Or do I need to make some extra considerations so things don't break? I assume I'll need to re-map some shares I have set up in various docker containers, but I wonder if there's anything else I'm not thinking about.

Yeah I actually also realised this too. It's a bit confusing. I was going to share this update. The issue I now have (probably same as you) is that I'm now unable to access the share via SMB. Before, I could access my Music share on my Mac via SMB, logging into my user account that is 100% set up with read/write permission. Now, it says I don't have permission when trying to click on the Music folder on my Mac.

@Kilrah @SpaceInvaderOne I figured out how to enable local storage with this setup, but there are severe limitations: Before hitting apply on the SpaceInvaderOne docker container to build it for the first time, you need to add this Variable: Type: Variable Name: NEXTCLOUD_MOUNT Key: NEXTCLOUD_MOUNT Value: /mnt/the_directory_you_want_to_mount_as_local_storage Hit save, then apply. Then, once you have set Nextcloud up and enabled the external storage app, you will be able to mount that local storage location. I had to completely remove the install and start from scratch to get that to work. The problem with this is that I don't see how you could then add a second location as an external storage mount.

root@Tower:~# docker exec nextcloud-aio-mastercontainer id www-data uid=33(www-data) gid=33(www-data) groups=33(www-data),33(www-data),281(docker) root@Tower:~# I have tried doing this as the Admin user and Local is still unavailable as a selection. What is the alternative to local? SMB?

As this documentation recommends, I ran the following commands (including commands to first verify what the user and group IDs were: "root@Tower:~# sudo chown -R www-data:www-data /mnt/zfs/Music chown: invalid user: ‘www-data:www-data’ root@Tower:~# docker exec nextcloud-aio-mastercontainer id www-data uid=33(www-data) gid=33(www-data) groups=33(www-data),33(www-data),281(docker) root@Tower:~# sudo chown -R 33:33 /mnt/zfs/Music root@Tower:~# sudo chmod -R 750 /mnt/zfs/Music root@Tower:~# " I then restarted the container and went to the External Storage settings again. Unfortunately nothing has changed and "Local" is still not available as a choice.

I just followed @SpaceInvaderOne's video for setting up Nextcloud AIO in Unraid. I'm posting this here in General Support as there isn't yet a dedicated topic for this version of Nextcloud. Now I would like to mount some shares to it. But for some reason, "Local" is not showing up as a dropdown option in the External Storage administration settings: How can I enable local storage as a mount option? tower-diagnostics-20241031-1255.zip

Ok great, things are back up and running! Do I just need to wait some time before "NAS" is restored as the device name rather than "Tower"? Is there anything else I should do, or any checks or tests I should run?

Ok, so just before I go ahead and do that (so I don't make a mistake) I just need to re-add the drives to a ZFS pool and hit add pool? Does it matter which drives go in which ZFS device (ZFS, ZFS 2, ZFS 3)?

" root@Tower:~# zpool import pool: zfs id: 11624769833213067975 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: zfs ONLINE raidz1-0 ONLINE sdb1 ONLINE sdd1 ONLINE sde1 ONLINE root@Tower:~# " Something else I'm noticing is that the name of the device "Tower" is not what the device was called before this mess happened it was called "NAS" before...

After doing some tinkering around deleting shares by moving their contents to temporary folders, and messing around with Docker settings, I went to reboot my NAS, but found that it got hung on the reboot and wouldn't come back on. I then rebooted it directly from the machine itself, pressing the power button once to reboot it. It now loads up the Unraid service, but my ZFS pool is missing. I use Unraid with 3x HDDs in RAIDZ1 and don't use any other main arrays or pools for use/storage, besides the compulsory array drive (a small SSD I installed) plus a flash drive. It now shows that my 3x HDDs are "unassigned devices", which is obviously really concerning. I don't know if this means I have somehow wiped the drives clean, or if there's anything I can do to restore things how they were. I'm attaching the diagnostics of my NAS: 1 - BEFORE I messed things up this morning 2 - AFTER messing things up Advice and support on how to (hopefully) restore everything would be really appreciated! tower-diagnostics-20241030-1753 (after problems).zip nas-diagnostics-20241030-1046 (before problems).zip

Hi, I am relatively new to Unraid (been using for 6 months with no prior experience with NAS/homelab stuff). I had originally followed the SpaceInvaderOne setup guides for Nextcloud, however where he used reverse proxies/port-forwarding, I used cloudflared tunnels. I did however also use a MariaDB container to set up. Anyway, I was trying to set up OnlyOffice on Nextcloud but was encountering errors with regards to HTTPS - I can't remember exactly what, but I think it was saying that it needed to use HTTPS rather than HTTP? Not entirely sure. Anyway, after doing too much tinkering with configuration files with the (unhelpful) help of ChatGPT, I got to a point where I had messed around with the Nextcloud config so much that I just wanted to remove the container entirely and start over. Installing the Nextcloud container again from scratch, I want to make sure I'm setting it up correctly. Unfortunately my setup seems to deviate from a lot of the guides out there enough that I feel I need more tailored setup guidance. 1. I want to set Nextcloud (and OnlyOffice) up with cloudflared tunnels rather than reverse proxies/port-forwarding 1a. But perhaps the advice from here might be that I should also incorporate reverse proxies/port-forwarding alongside tunnels? I'm not saying that, but I'm open to being told I should consider them if there is some kind of benefit to security etc. 2. I want to set this up to use HTTPS rather than HTTP. 2a. But perhaps someone here is going to tell me I don't need to do that. 3. In case this is relevant/helpful, my NAS setup comprises: ZFS pool of 3x HDDs in RAIDZ1 (no standard array) No cache drives - everything is done on the ZFS pool Support on setting this up again following best practices, including how to configure the Nextcloud container when installing, how to configure the settings in Cloudflare, and anything else, would be massively appreciated. nas-diagnostics-20241030-1046.zip

I use Unraid, and have been using Immich to store my photos. I also use the Immich Android app to upload photos to the photo share that points to Immich. Admittedly I don't know a whole lot about how this all works under the hood - I followed this tutorial to set Immich up in the first place. This is a shortened version of how the photo directory Immich manages looks: ". ├── encoded-video │ └── c26556d6-2981-4807-943e-da1daf03decf │ ├── 00 │ │ ├── 10 │ │ └── d5 │ └── ff │ ├── 09 │ └── f1 ├── library ├── profile ├── thumbs └── upload └── c26556d6-2981-4807-943e-da1daf03decf ├── 00 ├── d0 │ ├── 01 │ ├── 05 │ ├── 06 │ ├── 07 ├── d1 │ ├── 00 │ ├── 01 │ ├── 05 │ ├── 08 │ ├── 09 " Anyway, I want to now instead use Nextcloud as the storage location for my photos, and just use Immich as a place to view them etc. Then I will find a way to have my camera roll on my phone automatically upload to this new Nextcloud folder. However, I don't know: - How Nextcloud will organise photos uploaded to it. - How (if at all) I should reorganise the current Immich photo directory to be compatible with this. - Anything else I am not yet considering because of my lack of knowledge. Any advice?

I am struggling to pinpoint why individual docker container images are taking up so much space. I watched the SpaceInvaderOne tutorial on how to fix Docker image size, but in that tutorial, his example shows his "Local Volumes" size being high. In my case, running his script instead showed this: There are 30 Images taking up ......30.74GB There are 30 Containers taking up ......718.9MB There are 49 Local Volumes taking up ......2.797GB There are 17 Build Cache taking up ......11.16MB When looking at the configuration settings for one example, Binhex-Nicotineplus, I can't spot what's wrong about my config for it. I understand that I need to be looking for path mappings that don't correctly map to a location on my server, but I feel like I'm staring at the config file and missing something obvious. Any help appreciated. SpaceInvaderOneDockerScript.txt nas-diagnostics-20240906-1642.zip

Ah awesome, that worked! Thanks a lot