Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,831

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It does look like the typical bad RAM scenario, but you appear to be using ECC RAM, so technically it should not be possible, could be some other kernel memory corruption.
  2. JorgeB
    See if you can get the diagnostics using the console.
  3. JorgeB
    This is known to cause SATA link issues with some boards, try disabling that.
  4. JorgeB
    There are some recovery options here.
  5. JorgeB
    Difficult to predict, but a low number like that is usually not a big problem. There's no parity for cache pool, if you mean mirror/raid1 it's mainly for redundancy in case a device fails.
  6. JorgeB
    They are logged as actual disk errors, though possibly only parity has a problem, run extended SMART test on all, make sure spin down is disabled.
  7. JorgeB
    Disable WSD (Settings -> SMB) and see if it makes any difference, but at most that should cause SMB issues, not crash he server.
  8. JorgeB
    Try power cycling the server (not just rebooting) to see if the other device comes back online, if it doesn't there are some recovery options here.
  9. JorgeB
    If the issue follows the SSD it suggests a device problem.
  10. JorgeB
    Looks like there's superblock damage to that device, do you still have the other one?
  11. JorgeB
    If you do it for the share it will fix all folders inside it.
  12. JorgeB
    Please post the diagnostics.
  13. JorgeB
    Disk looks OK, suggest replacing/swapping cables to rule that out and then rebuild: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  14. JorgeB
    Yes, unfortunately nothing there, this usually suggests a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  15. JorgeB
    Please post the diagnostics.
  16. JorgeB
    Run newpermissions on that share, under tools.
  17. JorgeB
    Disk looks healthy.
  18. JorgeB
    Post a SMART report first.
  19. JorgeB
    Btrfs found some data corruption, so first thing I would recommend is to run memtest.
  20. JorgeB
    It just means there was another reason and that won't help, or maybe it could have dropped more often without that if there's more than one reason.
  21. JorgeB
    You can copy what's there to the array.
  22. JorgeB
    Please post the diagnostics.
  23. JorgeB
    If you have SATA available use SATA.
  24. JorgeB
    If you have enough SATA ports see if the old disk mounts with the UD plugin, if it doesn't you can repair the filesystem also using UD.
  25. JorgeB
    If you formatted an unmountable disk it deletes all the data, the usual solution for that is check filesystem, do you still have the old disk? Historical devices are from the UD plugin, but they can be safely removed.
×
×
  • Create New...