Jump to content

Kilrah

Members
  • Posts

    2,025
  • Joined

  • Last visited

Posts posted by Kilrah

  1. 1 hour ago, mathgoy said:

    I can see this in the Corefreq plugin but am not sure what I shoudl inderstand

    Shows low effective clock and high C7 residency which is good, still a bit weird that there's no C2-3-4-6, might be something else to enable in BIOS.

    You can press space and show the Power page, bottom will have package power. If that's low that'd mean there isn't much to save on the CPU and it's the rest of the HW.

     

    Oh and remembering now, install the Tips and Tweaks plugin and set governor to powersave.

     

  2. 2 hours ago, mathgoy said:

    Maybe may PCIE cards are preventing the system to reach high C-Levels.

    Install the corefreq plugin to check, it's much more readable than powertop.

     

    Also I believe Frigate is "expensive" on ressources, so "idle" may not be much idle if it's constantly running. Could try stopping things to see how much they contribute to total draw.

  3. 2 hours ago, SpencerJ said:

    you got it! Thanks

    Would slightly object to featuring something that was admittedly developed aginst a > 1 year old "Older / Non-Recommended Release".

    Why develop something an not validate it against current?

     

    Unrelated, but it seems the manual install download page only lists the latest in a branch now, that's kinda problematic in circumstances like now where 6.12.9 has a serious issue with remote mounts.

  4. Is this a joke? :D

     

    1 hour ago, TRusselo said:

    1. USB flash is likely to die within a year.  My USB dies every year.

    A hardware failure of any kind would lead to the same result. Data's still there on the drives if anyone wanted to access it.

     

    1 hour ago, TRusselo said:

    2. No "hot-spare" feature to auto rebuild a failed drive.

    If there was one nobody would notice or care when it gets switched to, then a 2nd would fail and back to square one.

  5. Try using something like glances or netdata with persistence to see what container caused that runaway increase in RAM usage.

     

    EDIT: Seems it could be immich, try limiting the amount of RAM it's allowed to use

  6. Well they aren't "for sale" yet, crowdfunding just started. So they also "don't exist" as it is, although it's at least an established brand this time.

  7. 3 minutes ago, patrickstigler said:

    since I wanted to remove one disk, I converted it back to single. 

    Single in btrfs is between RAID0 and spanning, i.e. one big "drive" made of both, so both are required. 

    Should have removed one while in RAID1 (only config that actually tolerates a drive loss), and THEN converted afterwards.

     

    Can you still add the 2nd drive back? If so it should just work again.

  8. You have tdarr and tdarr_node accessing the same folders, one changed a file while the other was being backed up. Put both into a group so they're both stopped together.

    • Like 1
  9. By default the log is written into the data location. You should be able to move it into the appdata folder by adding a line in config.php.

     

    https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/logging_configuration.html

     

    The "appdata_instanceid" folder might be a problem too, don't see a way to move it from a quick search but you could always cobble together an additional Docker mount for it. 

×
×
  • Create New...