TexasUnraid

Yes, I still can not get TMM to work on anything, it refuses to write to anything even though I can happily write to the folders from the docker console. It just suddenly broke one day and I can't figure out why.

No, I was hoping to avoid having to re setup all the settings but that might be needed lol

Yes, I tried that as well, I am out of ideas as well.

Yeah I considered that as well which is why I tried editing/writing/moving files from the docker console, so inside the TMM instance. It all works fine in there so the docker instance itself is not the issue, it has to be something with TMM it would seem. I also ran the docker safe permissions script from the unraid tools menu as well to make sure permissions were not an issue. The strange part is it used to work fine, it just stopped working for some reason.

I have it set to the standard 100 and 99

So I am trying to use this version of TMM but anytime I try to do anything with it, it just throws errors complaining about not being able to rename/move files. Seems like it does not have write permission? Yet if I go into the console for the container I can write, move, rename etc into the folders perfectly fine?

Yeah, I was surprised by this as well, seems like one of the more vital things I would want to monitor, all I really look at in netdata are temps, fan speeds and then the basic cpu/ram/disk etc

I have no idea but I am interested in what you find out. I used hddtemp for awhile and it works but I found it broke drive spinddown. I would like to get drive temps back into netdata. The better place to ask about this type of stuff is the github, they have been real good when I have had questions over there.

Interesting, was not aware of that catch. I will just remove the snapshots before I suppose.

Thanks, at one point I messed with manual compression and found that you can run a "defragment" operation to force the compression of existing data, I suppose unraid is just not using that option? Maybe it could be added before 6.12 official? If not I suppose I could run the defrag manually and it would not hurt anything? I guess I can just move all the data off and then move it back, just seems like a lot of wasted effort lol.

Great, that should work!

Ok thanks, as long as there is something to control my fans that is all I am worried about and I need some of the nerdpack tools. 6000rpm fans and the living room do not mix lol.

I am waiting until the stable release comes out to try this myself but noticed that the ipmi plugin seems to not be working with 6.12? Anyone know if it will be fixed? I got to have it to control my fans. It also seems that nerdpack is broken this time? Anyone know if it will be updated? Lastly, will BTRFS compression be able to be applied to existing shares/drives?

Yes, all the temps show up fine.

I didn't feel safe using the wireguard tunnel so I just stuck with the individual docker VPN's. Have not had any issues with those.

Yes it is, that is why I would prefer to use ZFS but until that add it in to the stable release that is not really an option in this case.

Ok, guess I will see where things stand once the hardware is ordered.

Thanks for that, I didn't read the whole thread but looks like it is getting close? Is there any indication when it would be put into a stable release? month? 6 months? A year? If it is semi-soon I think I will just have his collect the hardware and wait on actually setting things up until ZFS is supported. That will work a lot better.

Long story short, someone wants me to build them a killer NAS with all the fixins. The issue I am running into is that this server will be a VERY high end system, having more then the 30 drives that unraid allows in the array is highly likely. They also plan to have many users using it at once (plex), so the normal array will not be ideal from a bandwidth perspective either. This leaves me with using BTRFS raid 5 pools or the ZFS plugin (which I have not done a tone of research on). Raid1 is not practical at this scale. Is there any indication of when official ZFS support will be added to unraid? Suggestions for the best option?

It always checks for the keyfile before starting the array, if it is there it tries it first and complains if it doesn't work. If it is missing it prompts for you to enter the password

Taking snapshots of each disk is simple. They will also be combined together just like unraid does to everything else if viewing remotely. You are saying you want them exported to windows so you can see them under the previous versions? That can be done but sadly I have not been able to get it to work personally. If someone knows how it would be FANTASTIC if this plugin could make the necessary config changes automatically.

I can understand the reasoning, same reason I made it optional on one of the scripts I posted sometime back. I think that under some kind of advanced menu with a warning it should be ok though.

Why is that? You con convert shares into sub volumes so they can be snapshotted indivdually quite easily. IMHO it should be added to the plugin but it can be done manually with a few basic commands.

Opps, my bad, that is my custom path for my server, I have a separate cache pool just for the dockers and my normal cache is on raid5 15k drives. Yes, just swap it to whatever your cache path is. Although I don't actually use the write cache for the array to be honest. I like controlling which disk the data is put on so I move most data to the array manually using the disk paths. Most of the network usage is either reading or directly to the cache. The stuff that is not are generally backups and that is limited by SMB due to small files, so no reason to use cache.

Are you using a "stop" script like in that guide? I do not have any issues when using that, it stops all the dockers and then syncs the ramdisk back to appdata before the rest of the shutdown process is started. I did have to extend the total shutdown timeout for the server some to make sure everything finished (think the setting is settings > disk settings > shutdown timeout). That said I have not paid attention to is all the dockers are shut down nicely, never really noticed that one.