JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61345

  • Joined

  • Last visited

  • Days Won

    643

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    There's nothing relevant logged, and the server still crashing in maintenance mode points more to a hardware issue, could just be overheating, or power related, since a rebuild will use more power/cause more heat. Reformatting the emulated drives will delete all data there, and IMHO nlikely that the disks are the problem, I would check CPU temps and/or try again with a different PSU, if available.
  2. JorgeB
    Check filesystem on disk4, run it without -n, and if it asks for it use -L
  3. JorgeB
    Yes, and my suggestion was to try the above to see if the issue returns or not, or wss this a one time thing?
  4. JorgeB
    I would recommend resetting the current stats and monitoring the pool for future issues, since it can be much harder to resolve a problem if a bad or dropped device goes undetected for some time.
  5. JorgeB
    Please post the diagnostics.
  6. JorgeB
    More zfs related crashes, I would recommend backing up and re-formatting the zfs pool.
  7. JorgeB
    If you really need Wi-Fi why not use an AP with client mode?
  8. JorgeB
    I would recommend updating, it's not complicated: https://forums.unraid.net/topic/97870-how-to-upgrade-an-lsi-hba-firmware-using-unraid/
  9. JorgeB
    You should delete those files if possible, though don't know if it will affect Plex.
  10. JorgeB
    Look in syslog for a list of corrupt file(s), those should be deleted/restored from a backup, then re-run a scrub to confirm there aren't any more errors.
  11. JorgeB
    That won't work, abort and run it again using the GUI, but without -n.
  12. JorgeB
    Try a different flash drive, just to test, no key needed, also look for a BIOS update.
  13. JorgeB
    Possibly, could still be a RAM issue since memtest is only definitive if it finds errors, since you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
  14. JorgeB
    Yes.
  15. JorgeB
    Try running another filesystem check, that still looks like a filesystem problem to me, if it doesn't help, I would backup and re-format that disk, to make sure the issue is resolved.
  16. JorgeB
    This is a new array disk right? New disks added to the array need to be formatted before use, next to array stop button.
  17. JorgeB
    Run a correcting scrub on the pool and post the results. P.S. you should change the docker network to ipvlan, since there are macvlan call traces.
  18. JorgeB
    Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, 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.
  19. JorgeB
    You just needed to check the "I'm sure" box, next to the array start button.
  20. JorgeB
    Not surprisingly there's nothing relevant logged, also suggesting a hardware issue.
  21. JorgeB
    Server rebooting on its own it's almost always a hardware issue, but enable the syslog server and post that after a crash in case there's something logged.
  22. JorgeB
    You didn't need to do a new config, just what I've posted above, but that will also work.
  23. JorgeB
    Let the rebuild finish.
  24. JorgeB
    Make sure the emulated disk is mounting and contents look correct before rebuilding on top.
  25. JorgeB
    You cannot have a new parity a a new disk at the same time, what was the original array state? If there's no data to recover do a new config