Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Hoopster last won the day on May 27

Hoopster had the most liked content!

Community Reputation

216 Very Good


About Hoopster

  • Rank
    Advanced Member


  • Gender
  • Location
    Utah USA

Recent Profile Visitors

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

  1. No, and neither does anyone else 😀 Limetech does not publish roadmaps or timelines. Generally the information about a future release is very sparse unless there is a comment from Limetech in response to an issue that indicates problem X will be solved in version X.X or feature X will be added in version X.X. Like this recent post for example. Usually, there are a few release candidates before an official release and at that time, we get more information regarding what bug fixes and new features will be in the stable release and can guess that the stable release is coming "soon." "Soon" is kind of a running joke in these forums since "soon" has meant "a few days" in some cases and "a few months" in others. We just never really know.
  2. One way to increase disk write speeds in an unRAID array it to enable reconstruct write (turbo write). The disadvantage of this that all disks must be spun up all the time.
  3. @flambot According to Intel Ark for the E2160 neither VT-x or VT-d are supported. It's only a dual-core processor anyway with no hyperthreading so there are not a lot of resources to share.
  4. Write speeds are more a function of disk IO and parity overhead than network speed. Your speeds are normal and good if writing to a mechanical disk on a parity-protected array. A 10G network might help if you are trying to write to an NVMe or other fast SSD that has the capacity to exceed Gigabit network speeds, but, its not going to do anything for you with mechanical disks unless trying to write to a lot of them at once.
  5. Hopefully, you won't have to wait that long. Limetech has already made statements about 6.8 including a 5.x version of the kernel. Unfortunately, they are trying to sort out a lot of issues with 6.7 (primarily SQLite db corruption and disk/process IO issues) at the moment.
  6. The unRAID Wiki is very out of date. Depending on the card you ordered you may be fine. The current recommendation is a card based on LSI chip such as: any LSI card with a SAS2008/2308/3008/3408 chipset in IT mode such as the 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc. or clones like the Dell H200/H310 and IBM M1015. The Dell and IBM cards need to be crossflashed to LSI IT firmware. I have the Dell H310.
  7. This is your problem. The iGPU on the 9xxx Intel CPUs are not currently supported by the i915 drivers in the Linux kernel unRAID uses. You need at least 4.20 Linux kernel and unRAID uses 4.19. This problem should be resolved with a future version of unRAID that uses at least the 4.20 kernel; next version may move on to 5.x.
  8. Yes, your processor must also support VT-x/VT-d and your processor does not support virtualization technologies. https://ark.intel.com/content/www/us/en/ark/products/29739/intel-pentium-processor-e2160-1m-cache-1-80-ghz-800-mhz-fsb.html This is only an issue if you want to run virtual machines on your server. With the hardware you have, that is not really an option anyway. Docker does not require virtualization technologies support.
  9. Does your PCIe SATA card/HBA have a Marvell chipset? If so, this is likely your problem. Marvell drivers do not play well with recent Linux kernels. The result is that attached disks do not appear, or once recognized, they frequently disappear from unRAID. It might be helpful to post your diagnostics (Tools --> diagnostics in the GUI). A while ago I had a similar issue with booting. My server would not boot except in GUI mode; just a flashing cursor on the screen otherwise. It turned out something had changed in the Lunux kernel, drivers, etc, that required that I boot in UEFI and not legacy BIOS. As soon as I made that change in unRAID and my MB BIOS, I have not had an issue. I don't know if this is your issue as I never saw any kernel panics.
  10. @Mike L The Limetech Plex docker container is also no longer supported and they have encouraged users of the Limetech container to move to the linuxserver.io, Binhex or Plex Official docker container. The first two are well-supported in these forums and the Plex Official container is supported through the Plex forums. You need to learn about docker container volume mappings and map your host (unRAID) paths to container paths which will be the paths you specify in the Plex Media Server when adding folders to Plex libraries. Here is a screenshot of my Movies mapping in the linuxserver.io Plex docker container as an example of what you need to do:
  11. Your signature was always visible to those of us who had 'view signatures' enabled. By enabling it for you, you now see everyone's signature including your own 😀 You definitely do not need the fastest RAM available, but, as @Frank1940 said you should check your MB manual to see what RAM speeds your MB supports. Just because RAM is available in a particular speed does not mean your MB will support it.
  12. Do you have 10 SATA ports on your motherboard? unRAID tracks disks by serial number, not by SATA port location whether on the MB or an HBA. I recently moved four of my disks from MB SATA ports to a Dell H310 HBA and all it involves is moving the cables. You don't even need to worry about connecting empty/unallocated disks now, just add them to the array later whether that is on an MB SATA port or the M1015 The slots you see when building your array do not correspond to any particular SATA port order. Even the sdX assignment for each disk does not really matter and does not correspond to any particular array slot. The only thing that matters is which serial number is assigned to each array slot.
  13. Click on {Your Name} --> Account Settings --> Signatures --> View Signatures You don't necessarily need all RAM to be exactly the same. It is best when the motherboard supports dual channel RAM that the paired RAM DIMMS be of the same manufacturer and model number. One thing to consider though is your current RAM configuration. If your motherboard has four RAM slots and you got to your current 2GB with two 1GB sticks of RAM, in the remaining two slots, the maximum you can install is two 2GB sticks bringing total RAM up to 6GB. That is plenty for V6 running just as a NAS. However, if you want to play with multiple docker containers, 8GB would be better and you would need to replace the current 1GB sticks with 2GB RAM sticks for the 8GB capacity. Of course, if your current 2GB RAM was achieved with four 512MB sticks, then you have no RAM slots available and increasing the RAM would require replacing the current RAM.
  14. On the contrary, RAM for that board is still available and cheap. V6 will be much happier with 4GB RAM. If you ever think you will use docker containers, 8GB (the max. capacity of your motherboard) is better. https://www.memorystock.com/memory/ASUSP5BE.html These are US prices, but, you get the idea. Just go to the website for various RAM manufacturers (Kingston, Crucial, Corsair, G.Skill, etc.) and use their configurator to see what RAM is compatible with your motherboard then you can shop around by model number.