Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,674

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    If that is the old libvirt.img just copy it on top of current one, VM services must be stopped first.
  2. JorgeB
    Also note that running it on the device will make parity out of sync, when you use the console always run xfs_repair on the md device, e.g., disk2 is md2.
  3. JorgeB
    Check the power on the backplane, if it's powered using molex it's not that difficult to connect one upside down, inverting the voltages.
  4. JorgeB
    It's logged as a disk problem, but the sectors were successfully re-written, hence the disk remaining enable, good idea to run a SMART extended test, and if it passes monitor this attribute, you can add it to the SMART attributes monitored by Unraid for any WD disk, if it continues to increase there will likely be more errors soon: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 35
  5. JorgeB
    Use the console, start the array in maintenance mode and type: xfs_repair -v /dev/md1
  6. JorgeB
    Assuming it was xfs, I see you have a btrfs fs also.
  7. JorgeB
    You can still run a filesystem check, using the console or GUI, for the latter first and with the array stopped click on it and set filesystem to xfs.
  8. JorgeB
    That all looks good, though it could still be a controller issue that manifests itself only during a parity check, I have no experience with that controller, do you have another one you could test with, like an LSI HBA?
  9. JorgeB
    Unless I missed it logs don't show what happened, but disk changed ID, so it dropped offline and reconnected, try replacing both SATA and power cables.
  10. JorgeB
    Server shutting down, instead of crashing/locking up, is almost always a hardware problem, start by checking cooling and fans, could also be a PSU/board issue.
  11. JorgeB
    First see if this helps.
  12. JorgeB
    Could be a kernel incompatibility with that hardware, you can try a previous Unraid release to see if it's any different.
  13. JorgeB
    It's normal with Seagate drives: https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888
  14. JorgeB
    You need the previous libvirt.img, see if it's still there, also you should always have a backup of that file.
  15. JorgeB
    Not that I know of. Unlikely.
  16. JorgeB
    Shutting down by itself, instead of just crashing or locking up, is almost certainly a hardware issue and unlikely there will be something logged about that, start by checking temps and fans, could also be a PSU or board problem.
  17. JorgeB
    Diags are after rebooting so we can't see the problem, try again and post new diags before rebooting if the same thing happens.
  18. JorgeB
    No, with dual parity you can lose two drives, with single just one.
  19. JorgeB
    Look for the 9211-8i, in the legacy section.
  20. JorgeB
    It means there's likely a failing DIMM, System/IPMI event log might have more info on exactly which one it is.
  21. JorgeB
  22. JorgeB
    I would start with board/CPU.
  23. JorgeB
    Usually yes.
  24. JorgeB
    Using USB is possible, but not recommended for array or cache devices, USB is usually very bad at error handling.
  25. JorgeB
    Did you try installing the intel-gpu-top plugin like mentioned in the other thread above?
×
×
  • Create New...