Leaderboard

Popular Content

Showing content with the highest reputation on 12/06/19 in all areas

  1. A fairly large kernel update was published yesterday as was a new WireGuard release and I thought it important to update and sanity-check. We'll let this bake over the weekend and if no new big issue shows up we'll publish to stable. Then we can move on to the 5.4 kernel in Unraid 6.9. -rc9 summary: Update kernel to 4.19.88. Update to latest WireGuard release Other package updates. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, when accessing webGUI you'll now see a nice login form. There still is only one user for Unraid so for username enter root. This form should be compatible with all major password managers out there. We always recommend using a strong password. [-rc2] There is no auto-logout implemented yet, please click Logout on menu bar or completely close your browser to logout. Linux kernel [-rc8] Remains on 4.19 [-rc6/-rc7] include latest Intel microcode for yet another hardware vulnerability mitigation. default scheduler now 'mq-deadline' [-rc2] but this can be changed via Settings/Disk Settings/Scheduler setting. enabled Huge Page support, though no UI control yet binfmt_misc support added "Vega 10 Reset bug" [-rc2] and 'navi-reset' patches removed [-rc5] [-rc2] added oot: Realtek r8125: version 9.002.02 [-rc3] additional md/unraid changes and instrumentation [-rc6] fix chelsio missing firmware [-rc8] removed Highpoint r750 driver [does not work] md/unraid driver Introduced "multi-stream" support: Reads on devices which are not being written should run at full speed. In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite". Parity sync/check should run at full speed by default. Parity sync/check is throttled back in presence of other active streams. The "stripe pool" resource is automatically shared evenly between all active streams. As a result got rid of some Tunables: md_sync_window md_sync_thresh and added some tunables: md_queue_limit md_sync_limit [-rc2] md_scheduler Please refer to Settings/Disk Settings help text for description of these settings. WireGuard support - available as a plugin via Community Apps. Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel. Full WireGuard implementation will be merged into Unraid OS itself in a future release. I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you! I also should give a shout out to @NAS who got us rolling on this. If you don't know about WireGuard it's something to look into! Guide here: WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery. This feature is configured on the Settings/SMB Settings page and enabled by default. Also on same settings page is Enable NetBIOS setting. This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off. When turned off, Samba is configured to accept only SMBv2 protocol and higher. Added mDNS client support in Unraid OS. This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): ping tower.local instead of ping tower Note the latter will still work if you have NetBIOS enabled. User Share File System (shfs) changes: Integrated FUSE-3 - This should increase performance of User Share File System. Fixed bug with hard link support. Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files. This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)". [-rc2 ] Fixed the default value Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No. [-rc5] Fixed not accounting for devices not mounted yet. Note: if you have custom config/extra.cfg file, get rid of it. Other improvements/bug fixes: Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion. Encryption - an entered passphrase is not saved to any file. Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1. Several other small bug fixes and improvements. [-rc5] Fixed bug where quotes were not handled properly in passwords. Numerous base package updates [-rc2] including updating PHP to version 7.3.x, Samba to version 4.11.x. Known Issues and Other Errata Some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem. [-rc6] this is fixed: If you are using Unassigned Devices plugin with encrypted volumes, you must use the file method of specifying the encryption passphrase. Note that a file containing your passphrase must consist of a single null-terminated string with no other line ending characters such as LF or CR/LF. In another step toward better security, the USB flash boot device is configured so that programs and scripts residing there cannot be directly executed (this is because the 'x' bit is set now only for directories). Commands placed in the 'go' file still execute because during startup, that file is copied to /tmp first and then executed from there. If you have created custom scripts you may need to take a similar approach. AFP is now deprecated and we plan to remove support in Unraid 6.9 release. A note on password strings Password strings can contain any character however white space (space and tab characters) is handled specially: all leading and trailing white space is discarded multiple embedded white space is collapsed to a single space character. By contrast, encryption passphrase is used exactly as-is. Version 6.8.0-rc9 2019-12-06 Base distro: btrfs-progs: version 5.4 ca-certificates: version 20191130 ebtables: version 2.0.11 gnutls: version 3.6.11.1 gtk+3: version 3.24.13 iproute2: version 5.4.0 iptables: version 1.8.4 keyutils: version 1.6 libepoxy: version 1.5.4 libnftnl: version 1.1.5 librsvg: version 2.46.4 libtasn1: version 4.15.0 lvm2: version 2.03.07 nano: version 4.6 pcre2: version 10.34 pkgtools: version 15.0 build 28 wireguard: version 0.0.20191205 xorg-server: version 1.20.6 Linux kernel: version 4.19.88
    4 points
  2. Hello, would it be possible to bake in Nvidia and AMD GPU drivers directly into unRaid? Or maybe an easy way of activating the drivers? The folks over at LinuxServer are doing an amazing job with their Plugin (Which I do use) but it would be really nice if you could provide this out of the box, or an easy driver store to install from. The unRaid nvidia plugin is pretty popular, I am sure I am not the only one wishing for this. Of course I have no clue what kind of licensing this would require
    1 point
  3. tldr: If you require hardware support offered by the Linux 5.x kernel then I suggest you remain on 6.8.0-rc7 and wait until 6.9.0-rc1 is published before upgrading. The "unexpected GSO type" bug is looking to be a show stopper for Unraid 6.8 using Linux kernel 5.3 or 5.4 kernel. We can get it to happen easily and quickly simply by having any VM running and then also start a docker App where Network Type has been set to "Custom : br0" (in my case) and I've set a static IP for the container or toggle between setting static IP and letting docker dhcp assign one. There are probably a lot of users waiting for a stable release who will see this issue, and therefore, I don't think we can publish with this bug. The bug does not occur with any 4.19.x or 4.20.x Linux kernel; but does occur with all kernels starting with 5.0. This implies the bug was introduced with some code change in the initial 5.0 kernel. The problem is that we are not certain where to report the bug; it could be a kernel issue or a docker issue. Of course, it could also be something we are doing wrong, since this issue is not reported in any other distro AFAIK. We are continuing investigation and putting together a report to submit either to kernel mailing list or as a docker issue. In any case, an actual fix will probably take quite a bit more time, especially since we are heading into the holidays. Therefore this is what we plan to do: For 6.8: revert kernel to 4.19.87 and publish 6.8.0-rc8. Those currently running stable (6.7.2) will see no loss of functionality because that release is also on 4.19 kernel. Hopefully this will be last or next to last -rc and then we can publish 6.8 stable. Note: we cannot revert to 4.20 kernel because that kernel is EOL and has not had any updates in months. For 6.9: as soon as 6.8 stable is published we'll release 6.9.0-rc1 on next release branch. This will be exactly the same as 6.8 except that we'll update to latest 5.4 kernel (and "unexpected GSO type" bug will be back). We will use the next branch to try and solve this bug. New features, such as multiple pools, will be integrated into 6.10 release, which is current work-in-progress. We'll wait a day or two to publish 6.8-rc8 with reverted kernel in hopes those affected will see this post first.
    1 point
  4. I thought this was big enough to post here to create awareness. I don't expect anyone here can do anything about it though as I assume it needs to be resolved at the network / kernel level. https://www.zdnet.com/article/new-vulnerability-lets-attackers-sniff-or-hijack-vpn-connections/?ftag=TRE-03-10aaa6b&bhid=10041925
    1 point
  5. Yes is definitely wrong, since Yes means move from cache to array. Prefer is OK or Only. Prefer is the only setting that can help you get it moved to cache. Prefer means move from array to cache, but you can't move open files so more would need to be done to make that work. Specifically, while docker service and VM service is enabled you can't move docker and libvirt images. Simplest is probably to just disable and delete those images, set system to cache-only, and recreate them so they will go on cache.
    1 point
  6. I would test them, then put them back on the shelf until you need the capacity. Fewer drives = fewer points of failure, and plenty of spares means if you do have a failure it's painless to replace. For a media server, it's much better to mostly fill the drives and add as needed vs. putting them all in and filling all of them gradually. Because of the way most people obtain and consume media, and the fact that unraid lets drives stay spun down if not being read, you are better off keeping older stuff together and adding newer stuff to a single drive at a time.
    1 point
  7. There are two issues and the sample code has a section for each (preceded by a comment header) Part 1 of the code is getting listings. That seems to be slower on 6.8.0 for all directories and is noticeable to a human on a single call without concurrency starting with a couple thousand files. Part 2 of the sample code is only calling stat. I can only reproduce this issue for very large directories, but maybe that's because it requires large directories to produce a measurable difference.
    1 point
  8. Start from scratch. Download the Unraid USB Creator. For version select Next -> 6.8.0 RC5. Click customize. Check Allow UEFI boot. Insert your new unraid usb into the white port on your motherboard labeled BIOS. Boot your computer into the bios. Reset all settings to factory optimized/default settings. Save and reboot back into the bios. Make ONLY these changes: Tweaker -> Advanced CPU Settings -> SVM Mode -> Enable Settings -> Miscellaneous -> IOMMU -> Enable Settings -> AMD CBS -> ACS Enable -> Enable Settings -> AMD CBS -> Enable AER Cap -> Enable Save and reboot. Assuming you don't have any other boot media attached it will boot unraid. From the web gui Main menu, click the name of your Boot Device (flash). Under Syslinux Config -> Unraid OS, add "video=efifb:off" after "append initrd=/bzroot". The line should now read "append initrd=/bzroot video=efifb:off". Reboot unraid. Create a new vm using win10 template. Use the latest win10 install iso and virtio driver iso. Use the Q35 chipset, and the rest default/usual. Get windows installed/working with vnc graphics. Download appropriate vbios from https://www.techpowerup.com/vgabios/. Pass it along with your gpu video/sound. If you haven't seen it already, spaceinvader one has a video specific for the 5700 XT. The long and short is you need to pass a vbios, and you need to use Q35 to get the drivers to install properly. I would try doing everything fresh and in the order I suggested.
    1 point
  9. I never call a directory listing in that directory. I only open specific files by naming convention. So, adding subdirs would make things more inefficient because I would have to check for a file in each subdir. My current setup works very fast using a normal Samba server eg 6.7.2 or Ubuntu. The first issue is a problem for much smaller directories (a few thousand).
    1 point
  10. -rc8 summary: Revert kernel to 4.19.87 for reasons described in this post. Update Intel 10Gbit (ixgbe) to out-of-tree driver version: 5.6.5 Update to latest WireGuard release Other package updates. Misc. webGUI fixes. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, upon boot you'll now see a nice login form. There still is only one user for Unraid so for username enter root. This form should be compatible with all major password managers out there. We always recommend using a strong password. [-rc2] There is no auto-logout implemented yet, please click Logout on menu bar or completely close your browser to logout. Linux kernel [-rc8] Remains on 4.19 [-rc6/-rc7] include latest Intel microcode for yet another hardware vulnerability mitigation. default scheduler now 'mq-deadline' [-rc2] but this can be changed via Settings/Disk Settings/Scheduler setting. enabled Huge Page support, though no UI control yet binfmt_misc support added "Vega 10 Reset bug" [-rc2] and 'navi-reset' patches removed [-rc5] [-rc2] added oot: Realtek r8125: version 9.002.02 [-rc3] additional md/unraid changes and instrumentation [-rc6] fix chelsio missing firmware [-rc8] removed Highpoint r750 driver [does not work] md/unraid driver Introduced "multi-stream" support: Reads on devices which are not being written should run at full speed. In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite". Parity sync/check should run at full speed by default. Parity sync/check is throttled back in presence of other active streams. The "stripe pool" resource is automatically shared evenly between all active streams. As a result got rid of some Tunables: md_sync_window md_sync_thresh and added some tunables: md_queue_limit md_sync_limit [-rc2] md_scheduler Please refer to Settings/Disk Settings help text for description of these settings. WireGuard support - available as a plugin via Community Apps. Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel. Full WireGuard implementation will be merged into Unraid OS itself in a future release. I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you! I also should give a shout out to @NAS who got us rolling on this. If you don't know about WireGuard it's something to look into! Guide here: WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery. This feature is configured on the Settings/SMB Settings page and enabled by default. Also on same settings page is Enable NetBIOS setting. This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off. When turned off, Samba is configured to accept only SMBv2 protocol and higher. Added mDNS client support in Unraid OS. This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): ping tower.local instead of ping tower Note the latter will still work if you have NetBIOS enabled. User Share File System (shfs) changes: Integrated FUSE-3 - This should increase performance of User Share File System. Fixed bug with hard link support. Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files. This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)". [-rc2 ] Fixed the default value Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No. [-rc5] Fixed not accounting for devices not mounted yet. Note: if you have custom config/extra.cfg file, get rid of it. Other improvements/bug fixes: Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion. Encryption - an entered passphrase is not saved to any file. Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1. Several other small bug fixes and improvements. [-rc5] Fixed bug where quotes were not handled properly in passwords. Numerous base package updates [-rc2] including updating PHP to version 7.3.x, Samba to version 4.11.x. Known Issues and Other Errata Some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem. [-rc6] this is fixed: If you are using Unassigned Devices plugin with encrypted volumes, you must use the file method of specifying the encryption passphrase. Note that a file containing your passphrase must consist of a single null-terminated string with no other line ending characters such as LF or CR/LF. In another step toward better security, the USB flash boot device is configured so that programs and scripts residing there cannot be directly executed (this is because the 'x' bit is set now only for directories). Commands placed in the 'go' file still execute because during startup, that file is copied to /tmp first and then executed from there. If you have created custom scripts you may need to take a similar approach. AFP is now deprecated and we plan to remove support in Unraid 6.9 release. A note on password strings Password strings can contain any character however white space (space and tab characters) is handled specially: all leading and trailing white space is discarded multiple embedded white space is collapsed to a single space character. By contrast, encryption passphrase is used exactly as-is. Version 6.8.0-rc8 2019-12-04 Base distro: mozilla-firefox: version 71.0 (CVE-2019-11756, CVE-2019-17008, CVE-2019-13722, CVE-2019-11745, CVE-2019-17014, CVE-2019-17009, CVE-2019-17010, CVE-2019-17005, CVE-2019-17011, CVE-2019-17012, CVE-2019-17013) wireguard: version 0.0.20191127 Linux kernel: version 4.19.87 [revert from 5.3.12] CONFIG_SCSI_MQ_DEFAULT: SCSI: use blk-mq I/O path by default CONFIG_IP_VS: IP virtual server support CONFIG_IP_VS_NFCT: Netfilter connection tracking CONFIG_IP_VS_PROTO_TCP: TCP load balancing support CONFIG_IP_VS_PROTO_UDP: UDP load balancing support CONFIG_IP_VS_RR: round-robin scheduling CONFIG_IPVLAN: IP-VLAN support CONFIG_IPVTAP: IP-VLAN based tap driver CONFIG_NETFILTER_XT_MATCH_IPVS: "ipvs" match support CONFIG_NET_CLS_CGROUP: Control Group Classifier CONFIG_CGROUP_NET_PRIO: Network priority cgroup CONFIG_DUMMY: Dummy net driver support oot: Intel ixgbe: version 5.6.5 oot: Highpoint rr3740a: version: v1.17.0_18_06_15 Management: Upgrade noVNC to git commit 9f557f5 webgui: Diagnostics: Remove OSK info from VM xml webgui: Diagnostics: Adjust for timezone from webGUI webgui: Add support for the self-hosted Gotify notification agent.
    1 point
  11. *Should* be fine, as long as parity1 slot is used, when sync is done do a new config and check "parity is already valid" before starting the array. Alternatively clone the disk with dd then do a new config and also trust parity.
    1 point
  12. Ok wow, I need to read more of the documentation. Don't know why I didn't think the cache wasn't counted. I have been messing around with freenas for a couple of months, and its a great project and all, but for my needs, I think unraid probably works better. I just need some simple NAS storage and the ability to run plex and possibly a few other things via the NAS. Ill download the trial, and give it a whirl once I move my hardware to my new case. Regardless, thanks for the answer!
    1 point
  13. No. All attached storage devices (except the flash drive used for booting Unraid) count (even if not being used by Unraid).
    1 point
  14. If you go into the settings for the share you can add disk2 to the list of excluded drives. This will stop new files for that share being written to the that disk (although any existing ones will still show up for read purposes).
    1 point
  15. Only for metadata, i.e., you'll lose data if one of the devices fails.
    1 point
  16. Not related but I noticed some FCP warnings in your syslog. You shouldn't ignore these unless you know exactly why they don't apply to your specific use (and these do apply): Dec 5 21:10:01 Tower root: Fix Common Problems Version 2019.11.22 Dec 5 21:10:01 Tower root: Fix Common Problems: Warning: Share Disk2 test is set for both included (disk2) and excluded (disk1,disk3,disk4) disks Dec 5 21:10:01 Tower root: Fix Common Problems: Warning: Share Films is set for both included (disk2) and excluded (disk1) disks .... Dec 5 21:10:06 Tower root: Fix Common Problems: Warning: Dynamix SSD Trim Plugin Not installed Dec 5 21:10:06 Tower root: Fix Common Problems: Warning: Syslog mirrored to flash You shouldn't set both include and exclude and there is never any good reason to do so. Include means ONLY and Exclude means EXCEPT, so using one or the other not both, covers all possibilities. Remove one or the other. In fact, your setting for Films isn't even consistent. And I don't know why you would even have a share named Disk2. It doesn't appear in your user shares, and include / exclude settings don't make any sense for a disk share. Maybe you removed that share after it was logged. Hope you can clarify this one for me. And you don't want to mirror syslog to flash permanently since you will wear out your flash drive. That should only be done temporarily as a troubleshooting measure. Better yet set syslog server to write to one of your user shares. Also, your system share has files on the array instead of all on cache where they belong, so your dockers won't perform as well due to parity and they will keep array disks spinning.
    1 point
  17. From your screen capture of the Main tab, nothing is being written to any device on the array. (I am assuming that it was taken when this activity was going on.) Now, 7.2Mbps is not very fast (for a data transfer). I would suspect that it is GUI activity. Did you have more than one GUI screen open? Were you 'watching' the preclear progress on those three drives?
    1 point
  18. @RyanBorh If you already have installed some dockers or VMs, disable docker and VMs first in the settings, set both shares to PREFERED, run the mover so all existing data is moved to the cache. Check if the files are moved over to the cache and check if the shares don't exists on any array drive. Simply click the folder icon on the far right behind the drive in Unraids main tab. After that change both shares to ONLY and startup the docker and VMs again in unraids settings. Every new Docker or VM you install now will always been stored on the cache drive now and newer will be moved by the Mover to the array. For daily backups for the Dockers you can use the "CA Backup / Restore Appdata" plugin from the community applications. For backing up your VMs there are a couple ways to do it. You can use the following script for example and configure a daily schedule for it with the "User Scripts Plugin" Or in case you wanna use the BTRFS snapshot feature you can use a script to do this. This only works if the source and target drive is using BTRFS
    1 point
  19. you could either: Remove WebUI\Password_SHA1 from your config temporarily so you can log in without a password and set it again Get another clean qBittorent (Dektop, new container), generate a Password with it and copy WebUI\Password_PBKDF2 from its config. Not sure if you need to remove WebUI\Password_SHA1. Hash you password like qBittorrent does and insert it into your config
    1 point
  20. In short, you can't. In long, it kinda is possible simulate it by having 2 separate sets of dockers and a set of bash script but it's not true isolation.
    1 point
  21. That's good enough for me, I don't really mind when users don't say thank you, I do appreciate when people at least respond to say if it helped or worked.
    1 point
  22. From the official changelog: I'm not sure any future versions will include a "fix" for this.
    1 point
  23. Not sure how I obtained this as I thought I got it from community apps. However....got binhex and all is good....thx for the help....(I'll get this yet!) lol
    1 point
  24. Hey @binhex. Trying to install the remove plugin for Deluge however looks like it won't enable in the new version. There is already a bug report on the plugin git. https://github.com/springjools/deluge-autoremoveplus/issues/3 Any chance we can get this module included in the docker container? Thanks
    1 point
  25. Yes, until there are less than 2TB free, then it will start filling the other disks.
    1 point
  26. Cache. You can use this.
    1 point
  27. RC8 ha revert kernel back to 4.19, so it might be the issue
    1 point
  28. unRAID is hardware agnostic. The only hardware that matters for licensing purposes is the flash drive used to boot unRAID. Change hardware all you want. You can also extend the trial twice for 15 day each.
    1 point
  29. Have you read and followed the application setup guide on the github or docker hub link in the first post of this thread?
    1 point
  30. No but Samba team changes defaults all the time from release-to-release (kinda maddening they do this). Please type this command running 6.7.2: testparm -sv > /boot/smb672.txt and then boot 6.8-rc8 and type: testparm -sv > /boot/smb680.txt You now have those two text files on your flash which you can post here. Note: those files will contain your share names, if you don't want to post here then send to me via PM. Also would be helpful to describe to me how to reproduce this issue.
    1 point
  31. With High Water allocation and with the largest disk being 4TB I would not expect the 2TB drive to start being used until all other drives are down to 2TB (or less) free.
    1 point
  32. Cache file system is corrupt, best way forward is to backup, re-format, restore data.
    1 point
  33. That's normal for high-water. https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
    1 point
  34. So as I understand from reading your post, these are your requirements: IPMI, lots of PCIe slots, cores for VM's, and somewhat power consumption conscious...correct? If that's the case, then your really have two paths that aren't going to cost an arm and a leg (so no Xeon Scalable and AMD Epyc) and give you the PCIE slots you want (so no Xeon E and AMD Ryzen). The two paths you are left with are LGA2011-3 Xeon (older but has USB 3.0, DDR4 ECC, and is becoming cheaper very quickly) and AMD Threadripper. Here are prospective choices with those paths. LGA2011-3 Xeon - CPU: If you want VM's or lots of Docker containers running, then you need to go with the E5-26XX v3 series and probably not the E5-16XX v3 series (they have less cores but higher frequency and single thread rating). I'd stick with a single CPU since you're wanting to go lower in power consumption and it will save you money in both motherboard and CPU cost. The E5-2640 v3 is a really nice lower power CPU (it will idle much lower than its 90W TDP) to use for you. It has 8 cores/16 threads, 13,864 Passmark, and can be found Used on eBay for around $75. You could also go up to the E5-2680 v3 (18,426 Passmark, 120W TDP, 12 cores/24 threads, $150) and the E5-2690 v3 (19,240 Passmark, 135W TDP, 12 cores/24 threads, $200) if you want more power. Not to mention that any motherboard that can have a v3 processor can also take a v4 one. The E5-26XX v4 is still really expensive but these will decrease over time and give you a decent upgrade path. **Side Note: Don't buy QS/ES samples or ones from China. There are plenty of good, regular, used ones around so don't be drawn in by slightly lower costs.** - Motherboard: The X10SRL-F is pretty much the standard. It has a ton of PCIE lanes, USB 3.0, IPMI, fantastic support, and plenty of used ones on eBay. This seller: https://www.ebay.com/itm/SuperMicro-X10SRL-F-ATX-Single-Socket-LGA2011-v3-DDR4-Motherboard-X10/123818059106?hash=item1cd421a562:g:n3sAAOSwwrlckRA- regularly takes around $60 lower for a one than what is listed. The I/O plate can be found on Supermicro's website for only a couple of dollars. If you want to buy it new, Provantage has them for around $260 which will also come with a warranty which is nice. Just beware that if you pick this board, you'll need to find a heatsink that fits the LGA2011-3 Narrow socket. Noctua has a 3U one that would be perfect for your Supermicro chassis (I actually have the exact chassis as you!). - RAM: DDR4 ECC RDIMM's are dropping considerably in price. If you look on the Used market (eBay, ServeTheHome, or r/homelabsales), you can get some great deals. Hard to say what you'll pay because you didn't specify how much RAM you were planning on using. If you're going to do VM's and Docker containers, more is better. Also, take into account that this is a Quad Channel CPU so you'll want to use at least 4 sticks to really get your money's worth. AMD Threadripper - CPU: The 1900X is actually not a bad choice if you're planning on getting started with this setup but don't want to spend a bunch of money. It has 8 cores/16 threads, 16,108 Passmark, and can be found for about $150. You could also go with a 1920X ($250) if you want more cores. All threadripper CPU's will come with a higher idle power consumption though (starting at 180W TDP with an idle around 100W). You do, however, get higher Single Thread Ratings and a bigger upgrade path. - Motherboard: If you want IPMI, this leaves you with exactly one choice: ASRock Rack X399D8A-2T. This one is actually pretty hard to find and is damn expensive. It costs about $550 (I know! Crazy right?!) and it can be found on eBay and a couple of other sites. NewEgg is out right now but it'll probably come back relatively soon. Although it costs a ton, this motherboard has everything. PCIE lanes, IPMI, 10Gig, you name it. - RAM: DDR4 ECC UDIMM's are starting to go down in price and Provantage has some nice 2666mhz Kingston ram sticks for a decent price. You can also do non-ECC dimms and get better speeds if ECC isn't important to you. The only issue with Threadripper and RAM is that it really likes to have overclocked higher speeds to get the most out of the CPU. Since this is a NAS we're talking about, I don't condone overclocking ram but some people on here think it's worth it for the performance boost. Conclusion You can build a damn nice LGA2011-3 build for a lot lower cost than a Threadripper build while only suffering a little in high end performance. **Personally, I really want to do a LGA2011-3 build but I just don't have the need for all those PCIE lanes so I'm probably going to go AMD Ryzen instead.**
    1 point
  35. Master Version: Not sure what is going on, just updated, and now it crashes without much in the logs. Debug mask set to true or false comes up with same logs I will install and test dev, as I no longer see a master version, only 2 dev versions available. < ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-12-04 17:03:37.527209 [info] System information Linux 642928f489f4 5.3.6-Unraid #2 SMP Wed Oct 16 14:28:06 PDT 2019 x86_64 GNU/Linux 2019-12-04 17:03:37.565416 [info] PUID defined as '99' 2019-12-04 17:03:37.760181 [info] PGID defined as '100' 2019-12-04 17:03:38.047748 [info] UMASK defined as '000' 2019-12-04 17:03:38.082860 [info] Permissions already set for volume mappings 2019-12-04 17:03:38.125948 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info' 2019-12-04 17:03:38.160930 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info' 2019-12-04 17:03:38.197591 [info] VPN_ENABLED defined as 'yes' 2019-12-04 17:03:38.245688 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/** >
    1 point
  36. First time Adata SSD dropped offline: Dec 3 12:06:09 TOWER kernel: ata4.00: qc timeout (cmd 0xec) Dec 3 12:06:09 TOWER kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) Dec 3 12:06:09 TOWER kernel: ata4.00: revalidation failed (errno=-5) Dec 3 12:06:09 TOWER kernel: ata4.00: disabled Second time it dropped again: Dec 4 09:03:48 TOWER kernel: ata4.00: link online but device misclassified Dec 4 09:04:18 TOWER kernel: ata4.00: qc timeout (cmd 0xec) Dec 4 09:04:18 TOWER kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) Dec 4 09:04:18 TOWER kernel: ata4.00: revalidation failed (errno=-5) Dec 4 09:04:18 TOWER kernel: ata4.00: disabled Adata devices don't have a very good reputation, but it can also be a connection issue, suggest you try again with the SSD in a different slot/cable/port, if it happens again replace with a new device, preferably from a different brand
    1 point
  37. You should let limetech know about your issues and concerns. After all, it's really limetech who should be providing you with a solution, not a third party like us. We do what we can (chbmb and bassrock put a lot of work into it) but there is only so much an outsider can do when they only have partial info and have to reverse engineer everything. As an example, qnap worked directly with plex employees to make sure their OS included the necessary drivers and packages to make sure transcoding worked with plex on their devices. We are neither the OS provider (limetech) or the client (plex/emby). We're just folks trying to give back to the community.
    1 point
  38. Rather than 'backed up', think 'moved' from the cache drive to the array. So Yes, you lose all data that is still on the cache drive. However there a utility that will create a back up of certain system information about Docker Apps and VM's for this type of scenario. If you set up the mover to run once a day (it defaults to 3:00AM), you would only lose that day's files. Yes Yes but ask (or find the instructions for doing it). Also see answer to next your question. (I started with a 320GB HDs for the cache drive in both of my servers and switched them both out for an SSD's. It was simple enough that I don't even remember exactly what steps were involved.) Yes. See the following link. Be sure to read the 'NOTE:' under Cache Pool Operations about the required disk format if you start with a single drive! https://wiki.unraid.net/UnRAID_6/Storage_Management#Cache_pool_operations EDIT: Just took a quick look at the mover settings, you can also set the mover to run hourly should you feel that necessary.
    1 point
  39. Again as per the readme, it states `need to change both sides` aka the container port and host port to match and you haven't done this.
    1 point
  40. Has anyone revisited this since a while back? Refurb models of these have come down quite a bit in cost
    1 point
  41. FYI this is a bit older but make sure to to the Config in Sab and go to "Special" and scroll down to the bottom. There's a section for a whitelist, make sure it reads "tower" or "Tower" depending on how you are trying to access it (or whatever hostname you use for your Sab box) The case sensitivity is key -- it matters.
    1 point
  42. How do I replace/upgrade my single cache device? (unRAID v6.2 and above only) This procedure assumes that there are at least some dockers and/or VMs related files on the cache disk, some of these steps are unnecessary if there aren't. Stop all running Dockers/VMs Settings -> VM Manager: disable VMs and click apply Settings -> Docker: disable Docker and click apply For v6.11.5 or older: Click on Shares and change to "Yes" all cache shares with "Use cache disk:" set to "Only" or "Prefer" For v6.12.0 or newer: Click on all shares that are using the pool you want to empty and change them to have the pool as primary storage, array as secondary storage and mover action set to move from pool to array Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page When the mover finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share) Stop array, replace cache device, assign it, start array and format new cache device (if needed), check that it's using the filesystem you want For v6.11.5 or older: Click on Shares and change to "Prefer" all shares that you want moved back to cache For v6.12.0 or newer: Click on Shares and change the mover action to move from array to pool for all shares that you want moved back to cache On the Main page click "Move Now" When the mover finishes re-enable Docker and VMs
    1 point