Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,884

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It does look related since your server has a Matrox, but the driver is loading, and AFAIK that solved the problem for any other server using a Matrox GPU.
  2. JorgeB
    After is fine, but if the console goes blank during boot it's a different issue, post diags so I can see which GPU you have.
  3. JorgeB
    You'll need to move those manually.
  4. JorgeB
    Look at syslog for a list of affected files, delete/restore them from backup.
  5. JorgeB
    Post the output from the xfs_repair.
  6. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  7. JorgeB
    To rebuild again: -unassign disk2 -start the array, check that the emulated disk2 mounts and contents look correct, if yes -stop array -re-assign disk2 -start array to begin rebuild.
  8. JorgeB
    Lots of strange errors, do you use symlinks or hardlinks?
  9. JorgeB
    Looks more like a power/connection problem, if there weren't any writes to the array you can try rebuilding again after checking/replacing the cables on that disk, but only rebuild on top if the emulated disk mounts and contents look correct.
  10. JorgeB
    Go to shares and click on compute for the appdata share to see where it exists, cache pool is showing data corruption, you should run a scrub there.
  11. JorgeB
    Post the diagnostics.
  12. JorgeB
    SMART looks fine, diags might show more, if you didn't reboot yet, also keep in mind that the rebuilt disk will likely have some corrupt data, unless the read errors didn't coincide with used sectors.
  13. JorgeB
    Note same some LSI firmware releases are known to cause CRC errors, IIRC 20.00.04.00 or maybe 20.00.00.00, 20.00.07.00 should not.
  14. JorgeB
    Disk does appear to be failing, xfs_repair cannot repair a disk that returns a read error, hence the input/output error, since there's no parity best bet is to clone it with ddrescue then run xfs_repair.
  15. JorgeB
    Devices dropping offline has nothing to do with btrfs or RAM.
  16. JorgeB
    You should reboot first since there were already a lot of errors.
  17. JorgeB
    You can see some real world numbers with a few different expanders here:
  18. JorgeB
    Upgrade to v6.11.3, reboot, unassign disk8, start array, stop array, re-assign disk8, start array to rebuild.
  19. JorgeB
    Possibly there's a container mapped to Data, check all mappings.
  20. JorgeB
    Diags are not available to download, post again.
  21. JorgeB
    Server is running out of RAM, try limiting it for your containers/VMs.
  22. JorgeB
    Looks more like power/connection issues with multiple devices, check/replace cables or PSU.
  23. JorgeB
    du uses TiB, GUI uses TB, Windows also uses TIB so it should be the same as du.
  24. JorgeB
    Stop VM and docker services and copy everything you can to the array or elsewhere.
  25. JorgeB
    No need for that, as long as no RAID controllers are used.
×
×
  • Create New...