Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,893

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Please post the complete diagnostics.
  2. JorgeB
    That suggests some compatibility issue, which would be pretty strange with that board, which released were you upgrading from?
  3. JorgeB
    The GUI uses port 80
  4. JorgeB
    Unassign parity, start array, stop array, assign old parity as data disk, start array.
  5. JorgeB
    You can try xfs but those problems can be a symptom of a problem, not the cause.
  6. JorgeB
    Log is basically filled up with btrfs detecting data corruption on the docker image, for many days before it crashed, so fix that first then clear that log and post a new one if it starts detecting new errors.
  7. JorgeB
    Two of the onboard SATA ports are set to IDE, go into the BIOS and change them to SATA/AHCI, it's a known problem with these AMD chipsets.
  8. JorgeB
    And you are sure it was XFS? Post the output of blkid
  9. JorgeB
    If it keeps getting corrupt there's still a problem somewhere, or it could be the result of the server crashing, enable the syslog server and post the complete log after it crashes again.
  10. JorgeB
    Also re-create the docker image.
  11. JorgeB
    Swap slots with a different disk, then if the problem still follows the disk is likely a disk problem.
  12. JorgeB
    That's filesystem corruption on disk7, check filesystem. Nope, but you can enable the syslog server to it if it happens again.
  13. JorgeB
    Log looks normal, check is going at 125MB/s. There are know issues with Firefox, try a different browser.
  14. JorgeB
    AFAIK this only happens with Firefox, try a different browser, you'll need to reboot first.
  15. JorgeB
    NFS is known to be one of the things that cause this, and it appears to be the reason in your case since the call trace mentions it.
  16. JorgeB
    Call trace doesn't give many clues, at least not to me, if you can boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes could be a hardware problem, if it doesn't start turning on the other services one by one.
  17. JorgeB
    Follow the link. You could use a HBA instead, like an LSI.
  18. JorgeB
    Disk was already disabled on boot, suggesting the problem happened during last shutdown, also because of the RAID controller there's no SMART, enable the syslog server to see if it catches the next time it happens, but RAID controllers should be avoided when possible.
  19. JorgeB
    If you don't need it disable NFS, or if used see if you can switch to SMB.
  20. JorgeB
    You need to copy libvirt.img from the old cache, or restore from a backup.
  21. JorgeB
    Please post the diagnostics.
  22. JorgeB
    Enable disk share
  23. JorgeB
    @nikkyflaxmoved here since it's more appropriate place.
  24. JorgeB
    Since you are recovering disk by disk you also restore to the same disk. And fix this:
  25. JorgeB
    Recently there have been a couple of issues reported with space cache v1, I would expect if that was the problem here it also wouldn't mount manually, but it won't hurt to try, run: btrfs check --clear-space-cache v1 /dev/sdX1 Replace X with correct letter, then try mounting with UD again.
×
×
  • Create New...