BRiT

I dont use this, yet, but DZMM has shared many of his setups and others have said they have separate setup because the number of files, especially for music or personal backups.

That's what many already do, use multiple team drives.

Did you send any PM or email to @limetech or @jonp or @eschultz first?

Thumbs Up Where?

Try: find /mnt/disk2/Kino -type f -name \*.m4v -print if that produces what you what then: find /mnt/disk2/Kino -type f -name \*.m4v -exec chattr +i "{}" \;

It looks like you have parity checks setup for every single day at 08:30, or at least the syslog indicates it running consecutive days. On one day it also kicked off at ~ 20:00 or so. Most users use a strategy of scheduling Parity Checks Once a Month. Then running parity checks before and after any substantial hardware changes or moving of the system.

You also had actual WRITE errors. Jun 9 01:26:13 Tower kernel: XFS (md11): writeback error on sector 1991695272 Jun 9 01:26:18 Tower kernel: XFS (md11): writeback error on sector 4082030256 Jun 9 01:26:33 Tower kernel: XFS (md11): writeback error on sector 1991821992 Jun 9 01:26:33 Tower kernel: XFS (md11): writeback error on sector 1991695488

My initial response: You need better hardware, not sure if it's power cables or drive cables or power supply is too small, but you're having a MFT of read failures from a vast handful of drives. My closer look, Are you certain you have everything on a UPS? Right after your UPS did a self test your disks dropped offline and could not be read from. Jun 9 01:26:10 Tower apcupsd[53882]: UPS Self Test switch to battery. Jun 9 01:26:13 Tower kernel: md: disk10 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk12 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk13 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk14 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk15 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk16 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk17 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk18 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk19 read error, sector=1991694760 Jun 9 01:26:13 Tower kernel: md: disk20 read error, sector=1991694760 Also somewhere inside this mess you have filesystem issues, likely from drives dropping entirely offline. Jun 9 04:37:58 Tower kernel: XFS (md10): metadata I/O error in "xlog_iodone" at daddr 0xe8eb669b len 64 error 5 Jun 9 04:37:58 Tower kernel: XFS (md10): xfs_do_force_shutdown(0x2) called from line 1271 of file fs/xfs/xfs_log.c. Return address = 0000000015e00dc7 Jun 9 04:37:58 Tower kernel: XFS (md10): Log I/O Error Detected. Shutting down filesystem Jun 9 04:37:58 Tower kernel: XFS (md10): Please umount the filesystem and rectify the problem(s)

The SSD drives will/should support deterministic trim, so a slight tweak to the md drivers used by unRaid and all will be fine.

Norton and Symantec are absolute trash. So many better alternatives out there. I still wouldn't use it when it was free from my ISP. But I understand the temptation to use what's free.

If you want protection for write once read many media (video or music), look into using the Immutable File attribute, mentioned many times on these forums.

The name Tardis would be more applicable if you were using a Cloud service like Team-Drives with the RCLONE plugin and scripts. The storage is larger on the inside!

Raid 1 does NOT give you any more space, it gives you copies of the same data.

Ask in the WireGuard thread.

It looks like you have multiple issues. Your Disk3 has WRITE errors. May 16 22:10:33 Executor kernel: md: disk3 read error, sector=55075048 May 16 22:10:34 Executor kernel: md: disk3 write error, sector=55075048 Mar 14 11:34:27 Executor kernel: md: import disk3: (sde) WDC_WD100EMAZ-00WJTA0_2YJ0ZABD size: 9766436812 You also have a corrupt NTFS filesystem on one of your Unassigned Devices. Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6427 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5224): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6438 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5905): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6438 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5905): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6419 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5069): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6567 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (6034): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6567 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (6034): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6465 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5396): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6568 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (6033): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6568 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (6033): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6443 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5340): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6487 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (1040): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6487 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (1040): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6506 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (1036): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6411 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5055): Input/output error Apr 8 18:13:47 Executor ntfs-3g[27436]: Trying to read non-allocated mft records (6411 > 6400): Illegal seek Apr 8 18:13:47 Executor ntfs-3g[27436]: Inode is corrupt (5055): Input/output error

IIRC, unRaid only Disables Device on Write Errors.

- Encryption, but I suppose you mean limited scope of content to subscriber levels. - No maximum size limits. See the thread Guide: How To Use Rclone To Mount Cloud Drives And Play Files You may want to use RCLONE anyways on your colo server so you won't need massive drive storage.

Possibly far easier to move your library into Google Team Drive then hand out read-only accounts to that library so everyone can direct play from there.

A main concern you're possibly overlooking is Upstream Bandwidth, especially Internet Upstream Bandwidth.

Then you're running Plex Plugin and not Plex Docker ?

Compiling is the easy part. It's the bundling back into unraid's bzroot, bzimage. and bzmodules that's more detailed. On the forums and likely even in this very thread was a few discussions and scripts mentioned but from older moments in time. Best of luck searching and finding them, but they exist somewhere. General guide: https://www.wikihow.com/Compile-the-Linux-Kernel OLD guide from OLD unraid on HDD - https://wiki.unraid.net/Installing_unRAID_on_a_full_Slackware_distro#Build_a_new_Linux_kernel

No need to stop sharing SMB, just stop using WSDD. It's an option in the UI.

There's general instructions and scripts linked to from earlier posts in various threads that can serve as general guidelines for your own attempts.

To be pedantic, it depends on how CA intends to function and what "compatible" means, considering the DVB and the Nvidia plugins entirely replace unRaid. 🍻

Diagnostics.