Congles

perfect, thanks!

Much appreciated insight. If I delete my domains share and recreate it with the correct settings and copy files back. Will that be sufficient to fix this issue going forward?

Thanks @JorgeB, a short time ago I realised the data on the pool was lost. Thankfully I did actually have recent backups. I've just finished restoring everything, sans one of the nvme's which I think is dead. It is my "Domains" share that is set to NOCOW because, as per the Unraid GUI help it says "We recommend this setting for shares used to store vdisk images, including the Docker loopback image file. This setting has no effect on non-btrfs file systems." As my domains share is used solely for vdisks, I presumed this was the right approach? Should I set it back to Auto? And if so, would I need to empty the share, recreate it and copy files back so they inherit the COW attribute?

Hey All, I have two 2TB nvme drives in a RAID1 btrfs and am getting errors. I've tried doing a scrub but it seems to immediately be aborted. Since I have a RAID1 setup, can I simply remove the problematic drive and replace it later this week when a new one arrives? Diagnostics are attached. diagnostics-20230506-1013.zip

We just moved to TrueNAS Core (virtualised on Unraid) in September to support our bandwidth needs... Looking like it won't be long before we move back (Core sucks for the unfamiliar). As a side note, having support for 30+ drives would be nice for us. Our ZFS pool is 24 drives and we have a JBOD case to add another 36 drives over the next 12 months. We can manage otherwise though.

Same here, 6.9.2 and NVME temperature setting won't save - normal disks will though. Tried firefox and edge

+1 I have email alerts turned on and don’t see a way to remove the alerts from arriving in my email other than having the temperature thresholds actually remain. I've tried deleting the cfg file and setting the values again but the the GUI resets to default and I still get notifications (cfg file has the correct settings) Curiously, it only happens on my nvme cache drives (raid0 btrfs) and not with my spinning disks.

Thanks @ChatNoir and @JorgeB for your help, Your discovery fixed my problem and the log events have now gone and everything seems to be stable again. Thanks!

Ahh thanks, so it seems like an amd/architecture thing and not an Unraid OS / Server thing. I'll have a further read. Hopefully this fixes the recent instability I've been having. Thanks guys

@ChatNoir thanks for pointing that out. Do you know, or have a link to, why we can't run the RAM at even spec speeds? I'm about to set it to 2667 but kinda bummed I didn't know about this before I purchased the ram because I could have saved myself a big of $$ going for slower ram (especially 128gb of the stuff) Thanks again!

Oh wow... thank you. I didn't realise the RAM was overclocked, it shouldn't be. I must have got confused one day (as I have multiple machines) and set the ram at 3600 instead of 3200. I'll be fixing that ASAP. I'll report back if I continue to get the error

I have two Sabrent 2TB NVME drives in a btrfs raid 0 cache array called "Rocket" Does anyone know what the below errors mean? I started getting this last week, I wiped the cache and recreated it and it's come back. I've attached the unraid diagnostics too. Thanks in advance! tower-diagnostics-20210614-1412.zip

Hey @primeval_god, thanks again for all the help on this. I've reached a resolution, albeit not what I set out to do, but a better result: We're now using Syncthing instead of Resilio - which has the bonus of being free but also some recent improvements (since we last tested it about 2 years ago) has meant it's easily twice as fast as Resilio, probably 3 times faster. As for the container mappings, I ended up moving everything to a single share and am going to now look into how to have a single folder within that share, available on the cache for my own working. I suspect this will require another local-sync program to create and maintain a mirror of the data in said folder, on the cache drive. Any thoughts you have there to steer me in the right direction would be appreciated, but I'll do my research and open another thread if I need. Thank you a tonne again!

Oh I see what you're saying. I'll give that a try at some point in the next week or so. For now it'll have to wait as I have about 10 sync jobs I would need to redirect before removing the /sync binding.

Oh yep, I did try that but unfortunately it's baked into the container. I also noticed someone discuss it on the linuxserver resilio thread. Basically you can bind /sync to anywhere you like, but all the subfolders for sharing need to be child folders of that /sync location.

Hmm, yeah I think I know what you're getting at... it would be a pain to setup because I would effectively have to add every mapped folder I want to sync to, but that's at least a one time setup. Currently I'm waiting to see if the UI file-transfer bug I mentioned earlier goes away before trying anything else. If I understand you correctly, I should set the main container path, /sync, to something like mnt/user/Photo Sync and then set the extra container paths to: mnt/user/Photo Sync/1_New mnt/user/Photo Sync/2_Import ... I'll give that a go at some point...

Thanks for the heads up, I am definitely aware of that. Unfortunately with the way Resilio works and my needs to have one of the shares loaded into cache, I don't have another option. It appears there may be a small visual bug with the way I've set things up currently (as per my previous post) because Resilio now says there's ~200k files needing to be sync'd, but isn't syncing them (because they're already there)... Gotta leave it for a few more days to see if it clears up. If this idea fails I'll probably just have to create a single share "off cache" for the resilio sync and then do a local sync to another on-cache share of just the folders/files I want to be working on

Thanks for the suggestion! I didn't realize you could map multiple folders to a "sub" container path in the way you've suggested. After a bit of fiddling around I discovered resilio won't show any container path unless it's a child of the primary hostpath /sync. So in the below screenshot, I had to nest the extra host paths under /sync/photos/<folder> in order to have them appear. (Actually I first tried manipulating the sync.conf file to do it another way and that worked but is messy and don't recommend it to anyone stumbling upon this) Before I'm confident, I still have to test whether it will sync properly with a small test folder locally. Resilio's own business support told me it wasn't possible so I'll report back if it's all running smoothly. (They also said syncing files from difference logical disks isn't possible but here we are (Unraid), so I take what they say with some salt)

Bump* I have tried a few things since posting, Unfortunately Resilio has got back to me on a support ticket and has informed me that they don't support syncing of symlinks from linux machines. So I'm left now wondering if anyone out there knows a way I could achieve what I need - a single share for resilio to reference, while still having separate unraid shares?

Hi everyone, I have an obscure question for you. As you can see in the image below, I have a few shares in a waterfall structure. They house about 15 TB of photography and the "Archive" folder has all my offline photography (another ~15TB) I have 2 other locations I'm constantly syncing the files to using Resilio Sync. (pic below) My issue is the files in stage 1-3 get moved through the stages and resilio isn't able to see outside of its individual share, so in effect, if I move 500GB of photos from stage 1_New to stage 2_Import, this results in 500GB being deleted from the first sync and then re-sync'd via the sync sync. Obviously that's a waste of bandwidth. Unfortunately, using a single share is not an option. I need different cache settings for each share and since there's no option to elect a single folder inside a share to use cache (confirmed in this thread) I'm forced to have 3 shares. --- So, with my use case out of the way, I'm thinking of creating another share (called "resilio") and then symlinking the 3 folders from above to that location so that the path would look like this: /mnt/user/Resilio /1_New /2_Import /3_Processed Then I could create just one Resilio sync job, point it at /mnt/user/Resilio and it'll be able to track the movements of files across the 3 folders. Does anyone know 1, if this is possible and 2, how to go about it? Thanks!

I'm glad I found this thread. I'm in a similar situation with files on Unraid (having recently moved from Qnap). @nuhll In my case I'm working with often 500gb-1500GB of data that I want to be on the cache allocation. I think the solution you mentioned above will work, but I'm hoping to find an easier way for my pipeline still. UX-wise something like a "cache this folder" menu item is the kind of thing I'd like (but won't happen). Ultimately I want to have a single share for the top-level folder (e.g. "Photos") and then be able to select sub-folders of that to be on the cache or not depending on my current task. Folder-tree might look like: Photos (Unraid Share) Import Client 4 Client 5 Processing Client 1 Client 2 (Cached) Client 3 Archive Client 0 Any advice on this kind of structure or OP's question is doubly appreciated.