Because the movie has already been added. Go to that movie in radar, then files, and you will see that it probably was added as an incorrect match Sent from my NSA monitored device
Fixed. Technically, it was a quirk of GitHub where if you change a file / folder only by the case (which is what happened due to you changing dev to Dev, the cached icon for the feed was uploaded to a different folder which the CA knew about, but GitHub never actually changed the case, so it was giving a 404). Switched the cache to instead be completely lowercase all the time.
Include or Exclude disks on each individual share. But not 100% sure if split levels override this setting. Personally, I just split everything, and could care less if as an example, all episodes are all stored on one disk. When the disks as a whole get full, I add another or expand one of them.
Download https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.6.7-x86_64.zip
Open it up, and extract all of the bz* files (bzfirmware, bzimage, bzmodules, bzroot, bzroot-gui) in the root of the zip to the root of the flash drive
Reboot
FWIW, instead of entering in the command that might scare people off, you can also get the info via Tools - System Devices. And also via the various ACS override options, you can also potentially separate devices that are natively in a single IOMMU group to their own.
May or may not be related, but you need to run File system checks on the cache drive
Jul 07 03:08:44 shoebox kernel: XFS (sdg1): Metadata corruption detected at xfs_dinode_verify+0xa5/0x52d [xfs], inode 0x40a71b6a dinode
Jul 07 03:08:44 shoebox kernel: XFS (sdg1): Unmount and run xfs_repair
FYI for anyone else (since its a seemingly minor problem) is that you would not have been able to install or update any plugin while it was in that state.
Because it's not a .cfg file
But, is that a standard file that is executed by unRaid itself when stopping the array? If so, then I've missed the memo there.