Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


limetech last won the day on October 21

limetech had the most liked content!

Community Reputation

527 Guru

About limetech

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. limetech

    Unraid OS version 6.6.3 available

    Were you drinking beer?
  2. limetech

    Unraid OS version 6.6.2 available

    Thank you, please provide a link and I'll move it to the 'stable' bug list so we can continue discussion of this topic there.
  3. limetech

    [6.2.2] <vm template vdisk error>

    Changed Status to Retest
  4. limetech

    Unraid OS version 6.6.3 available

    lol a true Unraid OS user!
  5. To upgrade: If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Refer also to @ljm42 excellent 6.4 Update Notes which are helpful especially if you are upgrading from a pre-6.4 release. BIOS: Especially if using Virtual Machines, we highly recommend keeping your motherboard bios up-to-date. Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. Version 6.6.3 2018-10-20 Base distro: libvirt: version 4.7.0 (fix: virsh believes VMs are down when they are up) Linux kernel: version 4.18.15 Management: Add the 'tss' user and group to keep libvirt from complaining create /root/.docker folder symlink to flash /boot/config/plugins/dockerMan webgui: Diagnostics: add totals in btrfs usage information webgui: Docker: fix button color in alert messages webgui: Update CPUvms.page help text webgui: Code change to prevent CA from modifying system file webgui: Fix container log size webgui: Improve private docker registry support (correctly pulling and updating containers) webgui: VM: upon editing vm allow adding vdisk after having none
  6. limetech

    Need Help with Too many attached devices

    All attached storage device are counted at time array Starts, no matter how they are utilized in the server. After the array is Stated you can hot-plug devices if you desire.
  7. limetech

    Need Help with Too many attached devices

    Appears you have 14 storage devices attached (not counting usb boot flash). If you have Plus key, that's 2 too many.
  8. limetech

    [6.6.2] upload problems

    Changed Priority to Annoyance
  9. limetech

    Unraid OS version 6.6.2 available

    Is there a Bug Report for this?
  10. limetech

    Unraid OS version 6.6.2 available

    What exactly would you have us do? Send a strongly worded email to Gigabyte?
  11. limetech

    6.6.0 Realtek Nic Losing All Network Connectivity

    There are more Realtek patches in kernel 4.18.15 which will be in Unraid OS 6.6.3.
  12. limetech

    6.6.1 Crashes

    @rjstott still around? Has latest release fixed your Realtek NIC issues? You make a good point about not having complete documentation re: known issues, bugs fixes, workarounds, etc. However we are like 1/10000 the size of Microsoft so maybe can cut us some slack? Besides, how many Microsoft engineers, who directly work on the actual software, are you able to communicate with directly? I bet we outnumber that count.
  13. limetech

    2 Drive System: Mirror or Parity?

    What do you think, worthwhile improvement?
  14. limetech

    2 Drive System: Mirror or Parity?

    If only we had a wiki....
  15. limetech

    2 Drive System: Mirror or Parity?

    To clarify: in the case of a single "disk1" and either one or two parity devices, the md/unraid driver will write the same content to disk1 and to either or both parity devices, without invoking XOR to generate P and without using matrix arithmetic to calculate Q. Hence in terms of writes, single disk1 with one parity device functions identically to a 2-way mirror, and with a second parity device, as a 3-way mirror. The difference comes in reads. In a typical N-way mirror, the s/w keeps track of the HDD head position of each device and when a read comes along, chooses the device which might result in the least seek time. This particular optimization has not been coded into md/unraid - all reads will directly read disk1. Also, N-way mirrors might spread reads to all the devices, md/unraid doesn't have this optimization either. Note things are different if, instead of a single disk1, you have single disk2 (or disk3, etc), and also a parity2 device (Q). In this case parity2 will be calculated, so not a true N-way mirror in this case.