unraid userr

That breaks hardlinks and atomic moves. It would also require completely redoing volume mappings.

The unraid mover tuner plugin has its moments but it has also become way more then I need and unnecessarily complicated imo. If the native mover could support folder and file exclusion, and maybe a scheduler. That would be perfect. I just need to exclude my linux torrents folder and all subfolders and items contained within from the mover operation. I can press the start button myself

Oh I got it! For anyone who finds this, In my case the disk designation is sdd and it shows up in the disk log because the log is pattern-matching and finds wsdd2, unrelated, and matches on the sdd. Linux what even. Anyway, it's harmless and that explains why it's only in the one disk log. https://forums.unraid.net/topic/141858-wsdd2-shows-up-in-one-particular-disk-log/

I had a disk stuck in an emulated state. No errors thrown, SMART check would work but fail near the end. I tried quite a bit to fix it over a six month period but I ended up getting new drives to replace it, and in the process created a New Config, preserve all removing the disabled drive, stopped the parity-sync, a new config preserve all and added the new drive, and then stopped the parity-sync, did a new config again preserve all and it let me add the disabled disk into a different drive slot where it was unmountable and from there I was able to format and use the disk. The only thing I can think of is that something had damaged the zfs filesystem on the disk and the format (instant format) corrected it. I was very lucky that the disk didn't have anything I needed to be concerned with keeping as moving items from an emulated disk to a new hard drive took FOREVER (hours and hours to move 500 gigs of items - with 15TB remaining to transfer I decided the data loss was worth avoiding 1+ week it was going to take).

I have a disk, disk 4 of 5 in my array (so not the first, last, or only disk in my array) which has a line in the disk log not in any of the other disk logs. This is a SAS disk, there is also one other SAS disk in my array and that does not also start this wsdd2 process. Feb 13 13:05:25 ServerName rc.samba: /usr/sbin/wsdd2 -d -4 -6 Feb 13 13:05:25 ServerName wsdd2[6675]: starting. mdcmd import command Does anyone have any insight? I have checked the manpage but I'm not understanding what it's being used for that wouldn't have it in either the other disk logs or if a standard practice, as part of the last disks disk log.

@Reynald Rather then fix synchronize first, if you can fix Ignore files and folders listed inside of a text file: & File list path: you will fix the biggest obstacle to use using the plugin. That would give you more time to fix synchronize. Also, I suspect the ignore files and folders will be an easier fix.

Caddy has been ...rough. Especially given how easy its supposed to be. Can someone look over this & provide clarifying information? Port forward external 80 and 443 in the router to internal 80 & 443, Caddy's unraid paths should be what? Caddyfile should be something like what I have now or different? DomainName.com { reverse_proxy :8096 } How to get it using 443 for SSL? I'm only interested in getting Jellyfin working at the moment. Yes I looked at Jellyfin's documentation but they lack critical information on Caddy's path mapping.