Squid

Community Developer
  • Posts

    28625
  • Joined

  • Last visited

  • Days Won

    314

Squid last won the day on March 3

Squid had the most liked content!

Retained

  • Member Title
    What would Chode do?

Converted

  • Gender
    Male
  • Personal Text
    AKA Flesh Gordon

Recent Profile Visitors

70960 profile views

Squid's Achievements

Grand Master

Grand Master (14/14)

  • Great Support Rare

Recent Badges

4.9k

Reputation

282

Community Answers

  1. It's a catch-all notification. To separate them into individuals, you'd potentially get multiple notifications simultaneously. Once you see the notification, if you're comfortable with ignoring it, then hit Ignore and FCP won't send a notification if that's the only thing found. FWIW, I classify them as warnings or errors, and you have have it not send notifications for anything, or only for errors, or for everything
  2. It's not the contents of your flash drive. That is /boot. Likely you've set the backup plugin to use /mnt/user/flash as a destination
  3. There's more than one person who looks at stuff here to help users, and contrary to popular belief there are other things I do in life I would look at the settings for the proxy editor, or ask wherever the support is for that plugin. The problem started immediately after updating the plugin
  4. Basically, in order to determine (without being the owner of the container itself), you have to pull it to be able to grab the date of it. IE: Catch 22. To determine whether its X days old and then update what you've got installed, you have to update what you have installed.
  5. /dev/sdb1 512M 436M 0 100% /mnt/cache Looks like the root of your problem is that the cache pool while it may be on a 120G drive thinks that it's a 512M device. @JorgeB is the one to wait for to advise.
  6. What happens if you manually hit apply update on one of them?
  7. Never watched it during a parity check to see where it winds up. But, when it is zero then it is done...
  8. Mar 11 20:52:44 TowerShowers kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 There's some corruption on one of the members of your cache pool. First thing to check would be to run a memtest for a couple of passes from the boot menu as most causes of corruption are memory related. After that, wait for @JorgeB the resident BTRFS guru to advise further
  9. what do you mean by this? Transferring from another system to the server, or downloading something via SabNZBD?
  10. rename the wireguard folder (in /config) on the flash drive to something else as a test
  11. You need to post your diagnostics. Grab them AFTER both of those problems occur before you reboot
  12. MCE's you need to post your diagnostics The edac message is informative and doesn't actually mean anything
  13. Docker - Container Size will show you mostly where all the space it being taken up