Jump to content

limetech

Administrators
  • Content Count

    8578
  • Joined

  • Last visited

  • Days Won

    78

limetech last won the day on July 30

limetech had the most liked content!

Community Reputation

941 Guru

About limetech

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the 'heads up'. "Catalina" not released yet right? Could be it works upon release or could be we'll need to make a change.
  2. Looking in your syslog I see a few of these: Jul 22 19:16:33 Tower kernel: Buffer I/O error on dev md2, logical block 0, async page read Something is broken with your h/w.
  3. We can add this patch to upcoming Unraid 6.8, however note this caveat: From: https://gist.github.com/numinit/1bbabff521e0451e5470d740e0eb82fd#gistcomment-2973568
  4. We include a lowly Atom D510 @ 1.66GHz for all testing and writing to encrypted volumes works just fine - perhaps a bit slower but certainly no hangs or time-outs.
  5. Thank you for the reports. We are monitoring and trying to come up with another plan to isolate the issue.
  6. We have this implemented for 6.8 release.
  7. Please post diagnostics.zip Tools/Diagnostics
  8. Correct. Let me know in an email what you're trying to accomplish: tomm@lime-technology.com
  9. That won't work because it will detect GUID for USB A is already in use.
  10. What I'm looking for is this: Someone who experienced DB corruption after upgrading from 6.6.7 to 6.7.2 and then doing nothing more than revert back to 6.6.7 (without changing any disk/share config or appdata mapping) That person or persons now installing 6.7.3-rc2 to see if corruption happens again.
  11. Probably not Plex since other apps that use sqlite also experience corruption. Let's please retire this topic and switch to new one:
  12. 6.7.3-rc2 is published now. This reverts docker to version 18.06.3-ce. Tools/Update OS/Check For Updates
  13. I considered that but latest reports indicate this was solved, however it remains a possibility. The next test is going to be reverting Docker.
  14. How are you recovering, fixing the DB or deleting and letting it rebuild from scratch?
  15. Thank you for the report. Are you fairly sure this is new corruption and not perhaps has already been there and just seeing now?