Jump to content

Squid

Community Developer
  • Posts

    28,772
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Phoque Sent from my NSA monitored device
  2. Post one of the applicable xmls from /config/plugins/dockerMan/templates-user Sent from my NSA monitored device
  3. Then just delete the existing entry and reimport Sent from my NSA monitored device
  4. 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
  5. 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.
  6. It's something happening in the app feed I'll check it out Sent from my NSA monitored device
  7. Not until if the dashboard gets opened up for other cards Sent from my NSA monitored device
  8. 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.
  9. 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
  10. 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.
  11. contact the drive manufacturer or ignore the warning from FCP
  12. 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
  13. 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.
  14. ok. Added. I'll take this up with management
  15. Or if you only use the card for passthrough to a VM.
  16. This is honestly the first I've heard of it. 🤔
  17. @1812 is the most knowledgeable one around here on HP
  18. 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.
  19. 0 4 1 1,3,5,7,9,11 * At 00 minutes past 4:00 on the 1st day of Jan, Mar, May, Jul, Sep, and Nov
  20. Not currently. Pause is implemented, but it won't pick up where it left off if you reboot
  21. You also have to reboot. AB hasn't been compatible since 6.3.5
×
×
  • Create New...