Alyred

Ohh, I think I see part of my confusion. Your original reply said to make sure the share was NOT set to nocow. Somehow I missed the "not" in your post, so I wasn't following. It was early for me, sorry for sounding dense and thank you for the help! I'll make sure nocow is set to auto on that share.

Yes, so with nocow set to "auto", it will determine if nocow should be set for specific files, like the VM disks I'm asking about? And other files on the same share would work as normal using cow? Does data integrity suffer in a block write operation if a file is set to nocow? Maybe I'm confused by the terminology, where if copy-on-write is disabled via nocow it doesn't seem that things would be written in a timely enough fashion to keep both copies in sync? Or does nocow just make writes happen in a different method? And yes, as I mentioned, I am backing up, I'm more concerned about downtime if I have failures. They're not critical business VMs but would take annoying amounts of time to restore, so I'd prefer to keep them running with redundancy and get new drives in for replacement rather than doing restores if there is a hardware failure. I understand RAID is about uptime, not backup.

I'll check to make sure it's set to auto. With it set that way, will it just avoid cow on certain types of files, such as vm disks? How are vm disks handled to ensure they're mirrored in case of failure? Should I switch to a different cache filesystem for vm disks? Read your other post, thanks for the information on checking for errors. I do have it set up to scrub and rebalance monthly and have seen no errors there (though I am seeing an interesting rebalance note that I'll post about later), but good to know how I can confirm the states.

Thanks, @JorgeB. It all runs very fast and I am using the built-in domains share set to prefer cache with nocow. But if one of the cache drives fail, it'll continue to run with no data loss until I can get the drive replaced (assuming the second drive doesn't fail of course)? I'm not familiar with the underlying tech of btrfs and curious to learn more. Like does the nocow setting actually pause and write changes in chunks? How does it maintain a redundant copy of a file that's constantly changing like a vm disk? Thanks!

Hi all, Looking for some expertise here. I have VMs running on some SSD cache drives in BTRFS RAID 1. Yes, I am backing up, but If I lose a drive should I be able to expect it to run ok until I get the drive replaced? Or are there any limitations in BTFRS' file system that would cause problems until rebuild? Just read a few conflicting things that made me want to clarify. Thanks!

Thanks, I looked into it a while longer last night and got the permissions set back to nobody:users on the folder structure which fixed that for the Plex docker (which is now re-running the thumbnail previews and skip intros on all that "new media" it found (sigh) so I'm just going to let that finish again. That, of course, broke the shares from my Windows workstations using AD credentials. So I think that'll be my next "figure it out" project on this new server. Previously it was running almost against the domain almost as an IDp and if the domain validated it, the access was allowed, but that doesn't appear to be working anymore with the ACLs in the directories still being there but not being honored. I'll have to dig into the forums when I get done with the workday. Again, I appreciate both of your assistance!

Thanks, that got the drive working! Thanks for the clear steps. Unfortunately... my Plex container now doesn't see the share it was pointing to properly. This appears to be a permissions issue with the shares however. Not sure why that came up but I did just upgrade from 6.9 to 9.10.2 so maybe something shook loose in the AD connection config. Exciting times!

Thank you both. Interestingly, nvme2n1 was actually the original second drive that was assigned to the protected pool, and nvme0n1 was the drive I recently added. So it looks like something went wrong when I built the pool at the beginning. I'll give these steps a shot and report back.

Hi all. Running 6.10.2, and just purchased the pro version of Unraid today. Just now hit my first real stumbling block in the configuration. 😅(I'm taking some time to slowly work through plugin and docker configuration... but it's getting there). I have a board with 3 NVMe drive slots on it. Originally I configured a cache pool with two 1TB NVMe drives in it, and one single-drive 1TB NVMe in a separate cache just for speed. This worked as expected with 2x1TB pools, one protected with RAID1 and one unprotected. After reconsidering, I decided to move the single drive into the protected NVMe pool, so I broke down the drive out of the separate pool, reformatted it to btrfs with the unassigned devices plugin, and added it to the new pool. However, I'm still showing with both the GUI and dh -h that that cache pool partition is only 1tb in size. I re-balanced the pool and forced RAID1, and even scrubbed the pool, but can't get the size to get to the 1.5tb I expected to see as a "mirrored" 3-drive array. Is there something else i need to do to re-size the partition? Otherwise it seems to be working fine, there is data copying over to that drive in the pool during the rebalance, but it's almost as if it thinks it's in raid1c3 mode - but leaving drive 2 almost empty. Any assistance is appreciated. Thanks. Diagnostic files are attached.

I'm still new to Unraid and I've forgotten more about linux than I like to admit, so I'm probably doing something wrong here. I am running Unraid 6.10.2 and trying to get the OpenRGB and Dynamix System Temp plugins working, focusing on System Temp in this post. I'm detecting the same sensors as JAnguita posted, but as soon as I click "save", pick a sensor for the CPU (Tctl) and hit apply, the settings vanish and no temperatures are reported. Furthermore, the sensors themselves are gone until the next reboot, whereafter I can select them again but the same behavior happens. Attaching my diagnostics. Running sensors-detect finds a lot of stuff but then tells me to copy the file somewhere and I cannot find either the file it wants me to copy from or the folder to copy it to. Any assistance in getting this working would be appreciated. Still re-learning a lot of lost knowledge, as well as a lot of new things from the past 15 years. diamond-diagnostics-20220607-1658.zip

And thanks for answering this as well. Figured this might be the case (in case you needed or accidentally removed a docker you could get the data back) but wanted to make sure this was the proper way to go about it.

Thanks! Got that in the share config (all disks is selected) but I selected the split option to be at 4 instead of 3 (I miscounted) so instead of (in this case) allowing the television folder to split different shows (but keeping each show on the same disk), it put them all on one disk. So the share is configured correctly (and now has the proper split level defined), but I was wondering if I moved the shows manually (cli, krusader, or dynamix - thanks for the tip) if the share would then see them or not. It hasn't yet created a directory there and I don't have anything new to copy to it at the moment. I'm considering just setting up a new share specifically for TV and the like and may just copy share->share and have it re-distribute it automatically. Just considering the most efficient way to do these for future, and what's possible. And again... learning a bit how the system works in the process. So far as moving, I did use Krusader and it wouldn't remove the old directories, period. The files moved successfully from an old cache drive to a new one after the share location changed, but it would NOT remove the old directories on the old share and "Fix Common Problems" continued to throw warnings on it. Removing the folders from the cache manually got it cleared up, but couldn't figure out why Krusader wouldn't remove those folders. I'll give Dynamix a shot!

Thanks. I don't really have diagnostics because I'm not having a problem. I'm asking some questions I had before problems occur. As I said, I'm not having any hardware issues at this time. I'll keep that in mind that most of the time I won't need to work with Unraid that the cli. However, it does appear that some movement of files in and out of the system without specifically utilizing the shares interface is desirable (per SpaceInvaderOne's videos), so long as I don't move share to disk or vice versa, only disk to disk or share to share. So one of my questions was regarding moving files and how the filesystem worked to cover that with shares - will creating the folder on disk3 automatically be picked up by the share, or do I need to adjust the share setting somehow? Your answer indicates I shouldn't be doing that at all. Currently, my data on my UnRAID system is all duplicate. And yes, I'll be running VMs for actual Linux knowledge growth, configuration, and exploration of security concepts in Linux. I just wanted to state where I was currently at, that I'm not a complete neophyte with all this, but the system is unfamiliar to me at this point still. Good to know that it's a stripped down Slackware distro. That's actually one of the distros I used back in the day when I was first working with it.

Hi all, a bit of a preface for my questions here. I'm a IT Security specialist but have been stuck in the Windows/AD side of the sector for about 25 years. That means unfortunately, I've skipped "Linux day" for about that long and my neophyte *nix skills have atrophied pretty badly. That being said, I'm starting to fix that by learning UnRAID and moving my home lab over to an UnRAID system. Built myself a fairly decent machine and the hardware has been working fairly decently so far, waiting on a new Power Supply to arrive to route my cables properly and button it up. I've been watching SpaceInvaderOne and JuanMTech's videos and have been finding them very informative, but as always, the more I learn the more questions I have. I'm moving an older stand-along Plex server into a docker in Unraid. Some questions I have: First, I created a share for all of my Plex media, but didn't allocate them between drives very well due to mis-counting the . Currently, disk1 and disk2 have a /plex folder, but disk3 does not - everything was allocated to disk1 and disk2 via the plex share. If I create a folder on disk3 named /plex via cli under /mnt/disk3, will I need to adjust my plex share, or should it pick it up and see disk3's /plex folder automatically as part of the "collection" of folders inlcuded in the share? I'm still learning how the btrfs file system works here. Question 2: To completely refresh a docker app and install it new, it appears I need to manually remove the docker's files under the appdata share. I uninstalled the Plex docker but it left those files behind. Question 3 (might be more of a Linux question): When I do a "move" command, it appears that it's leaving empty folders behind in the old location that I have to remove manually. Is this normal? It seems I'm probably just missing a command line switch. Thanks for helping a old tech dog learn (and re-learn) new tricks.