Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by limetech

  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?
  16. You can click the Log icon on the webGUI menu bar to start a tail of syslog in your browser. You can also type this command at console: tail -f /var/log/syslog
  17. re: Trying to get to the bottom of this... First we have not been able to reproduce, which is odd because it implies there may be some kind of hardware/driver dependency with this issue. Nevertheless I want to start a series of tests, which I know will be painful for some since every time DB corruption occurs, you have to go through lengthy rebuild process. That said, we would really appreciate anyone's input during this time. The idea is that we are only going to change one thing at a time. We can either start with 6.6.7 and start updating stuff until it breaks, or we can start with 6.7.2 and revert stuff until it's fixed. Since my best guess at this point is that the issue is either with Linux kernel, docker, or something we have misconfigured (not one of a hundred other packages we updated), we are going to start with 6.7.2 code base and see if we can make it work. But actually, the first stab at this is not reverting anything, but rather first updating the Linux kernel to the latest 4.19 patch release which is 4.19.60 (6.7.2 uses kernel 4.19.55). In skimming the kernel change logs, nothing jumps out as a possible fix, however I want to first try the easiest and least impactful change: update to latest 4.19 kernel. If this does not solve the problem (which I expect it won't), then we have two choices: 1) update to latest Linux stable kernel (5.2.2) - we are using 5.2 kernel in Unraid 6.8-beta and so far no one has reported any sqlite DB corruption, though the sample set is pretty small. The downside with this is, not all out-of-tree drivers yet build with 5.2 kernel and so some functionality would be lost. 2) downgrade docker from 18.09.06 (version in 6.7.2) to 18.06.03-ce (version in 6.6.7). [BTW the latest Docker release 19.03.00 was just published today - people gripe about our release numbers, try making sense of Docker release numbers haha] If neither of those steps succeed then ... well let's hope one of them does succeed. To get started, first make a backup of your flash via Main/Flash/Flash Backup, and then switch to the 'next' branch via Tools/Upgrade OS page. There you should see version 6.7.3-rc1 As soon as a couple people report corruption I'll publish an -rc2, probably with reverted Docker.
  18. Where did you see this, on our forum? This was an issue several years back where some USB flash devices had a config bit set to "this is a removable device" and others had the bit set to "this is a hard disk". I think the HP tool was able to flip that bit and solve the problem, which was due to HP bios not allowing boot from a USB flash with the bit set wrong as a security measure (can't remember which state it wants the bit to be).
  19. That's the problem right? Something about your win10 PC is incompatible with our Flash Creator tool. Our flash creator needs to write the boot sector of the device, which is also one method to transmit malware, maybe there is a setting in Windows that is stopping this on your PC? - just a guess. I hope your experience with Unraid goes a little better. I think you find this a friendly and helpful Community.
  20. Trial does not use system time or motherboard clock, instead it contacts a LimeTech server upon server reboot. Your server not having internet access explains both Trial not validating and NTP not being able to set the time. Please check Settings/Network Settings. Perhaps default gateway is not right.
  21. Well it's either kernel, driver, docker, weird bios interaction (and use of hacks like that fit-headless), or something else. Hard to know where to begin.
  22. Trying to build driver results in this: If you want to correspond with highpoint to find out how to build against a generic kernel, I'll try again. Better yet: ask them why they don't adhere to nvme spec and/or include their driver in Linux source tree.
  23. We can attempt to add this driver; however, realize, if we need to update to a newer Linux kernel and the driver no longer compiles, it will be omitted. In this case, the onus is on users of the driver to lean on the vendor to update their code.