Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,459

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    This is a problem with the UD plugin, and it will be corrected on the next update:
  2. JorgeB
    Yes, writes are flushed after a few seconds to protect against for example a power loss, but all available RAM is used for read cache. https://www.linuxatemyram.com/
  3. JorgeB
    That's RAM used for read cache, all writes are flushed to disk after a few seconds.
  4. JorgeB
    If it doesn't grab diags before rebooting/shutting down.
  5. JorgeB
    In case I wasn't clear I was saying to try again to re-syn parity with the new disk. There's no much point in doing this, might as well try to sync parity (to the new disk), it will take the same time.
  6. JorgeB
    Never a good sign but those errors might be a one time thing, run an extended SMART test on the disk, if it fails replace, if it passes I would give it a second chance, but more similar errors in the near future replace.
  7. JorgeB
    Yes: Formatted with type 2 protection See here: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078
  8. JorgeB
    Probably formatted with some protection type but please post the diagnostics to confirm: Tools -> Diagnostics
  9. JorgeB
    Have you swapped the ports on the HBA? That model is known to only have a working port when incorrectly flashed to IT mode.
  10. JorgeB
    That's expected, once a disk gets disable it stays disable, you can still try to re-sync the new parity with that disk, but do it in maintenance mode to avoid any more changes. -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments are correct -check the "maintenance mode" checkbox and start the array, depending on what Unraid release you're using you might need to click "sync" to begin the parity sync, if there are errors again post diags.
  11. JorgeB
    Best bet is to post on the preclear plugin support thread.
  12. JorgeB
    Most likely it won't work, due to different size or invalid partition error, possibly even no data since some WD enclosures encrypt it, but you can still try.
  13. JorgeB
    It's an issue with the UD plugin, already reported and it should be fixed on the next update.
  14. JorgeB
    It's just a warning that there were previous SMART issues, doesn't mean the drive is currently not good, but a good idea to run an extended SMART test and also keep an eye on that attribute.
  15. JorgeB
    It's possible to re-use the old parity (but note that unless you did the rebuild in maintenance mode it will be a little out of sync due to mounting all the disks, though usually not a big deal) but the disable disk looks fine, most likely a connection issue, do you have the logs from when it happened?
  16. JorgeB
    It could but it should be unnecessary if all is working correctly.
  17. JorgeB
    Disk1 dropped offline so there's no SMART, check/replace cables and post new diags.
  18. JorgeB
    Where did you have that data? Cache pool is basically empty and based on the transid both the docker and VM images where newly created.
  19. JorgeB
    I'm seeing the same thing, some servers worse than others: Traced it back to the UD plugin, @dlandonplease check it when you can.
  20. JorgeB
    You can use the parity swap procedure.
  21. JorgeB
    There should be, but brand name servers can sometimes not accept all HBAs, you can ask or search on the hardware or storage sub-forums.
  22. JorgeB
    If it happens again grab the diags before rebooting.
  23. JorgeB
    Try typing "diagnostics" on the console.
  24. JorgeB
    See if this helps, or try another slot and/or look for a BIOS update.
  25. JorgeB
    You just need to rebuild to a new or the same disk, but recommended using an internal device.
×
×
  • Create New...