Jcloud

Now you have my attention, and blew my mind. Not on the PCI-E slot? Time for me to go look at the specifications. I'd prefer keep my slots for GPU's. Thanks.

Exactly what this is. Six years on my last combo, although I was on my second mobo. Probably could have ran my old system for another year, but Threadripper came out and boy did I have an itch that couldn't to be scratched! SSDs are on the motherboard, was planning on keeping the SAS card just hard drives. I should redo the cabling for all my sata cables; that's about when I got impatient with myself and just wanted it on. System is on, phone's flash washed it out.

Most recent edit date: Mar, 4th, 2018. My new build, much like the hydra, is one part old bits, and the hacked off bits only to have grown back stronger and more wild. Also, like the metaphorical comparison of unRAID (and what it offers to the user) and that of the hydra: One head is HD protection and array; another head is Docker app server; another KVM; another NAS shares -- again split off from array. It's neck. And now this hydra has more head, ThreadRipper. The metaphor just fits for me. OS at time of building: 6.4.1 Stable OS Current: 6.7.2 CPU: AMD Ryzen Threadripper 1950X Heatsink: Noctua NH-U14S TR4-SP3 Motherboard: ASUS PRIME-X399-A , BIOS 0407 (at build), Running BIOS 1002 RAM: 128GB HyperX Fury DDR4 2666MHz , (2x) HX426C16FBK4/64 Case: AZZA Solano 1000R Drive Cage(s): (2x) ICY DOCK 5 Bay 3.5 SATA HotSwap Power Supply: Antec 900W HCG SATA Expansion Card(s): LSI Internal SATA/SAS 9211-8i Parity Drive: 4TB Western Digital "gold" WDC WD4002FYYZ-01B7CB1 Array Disk1: 3TB Western Digital "red" WDC WD30EFRX-68EUZN0 Array Disk2: 3TB Western Digital "red" WDC WD30EFRX-68EUZN0 Array Disk3: 3TB Western Digital "red" WDC WD30EFRX-68EUZN0 Array Disk4: 4TB Western Digital "red" WDC WD40EFRX-68N32N0 Array Disk5: 4TB Western Digital "gold" WDC WD4002FYYZ-01B7CB0 Array Disk6: 4TB Western Digital "blue" WDC WD40E31X Array Disk7: 3TB Western Digital "red" Cache Drive0: 250GB Samsung 850 EVO SSD Cache Drive1: 120GB OCZ-VERTEX460A SSD Cache Drive2: 500GB Samsung 850 EVO SSD Total Hard Drive Array Capacity: 24TB Total Cache Drive Array Capacity: 870GB (JBOD, not protected storage) Primary Use: To be my, "Fort Kick Ass." Gaming and mucking around with VMs; secondary protected data storage, nas functionaly, application server notes (wiki), handbrake, BT. Likes: I Linux distro powerful enough to do everything I wanted out of my computer, but easy enough for me a relative linux newb could use it. Dislikes: I'll have to come back to this one (even as a 2-year user). Yes, there can be, and often are some limited functionality of VMs, but that's not unRAIDs or dev's fault -- just the state of Linux technology, and microcode. First time I tried to touch Linux was in '98, what we have now . . . omg, NO complaints! LOL It's also more fun to accept the VMs quarks as a hobbyist than to tank the server, especially with the gains in protected storage. Plugins Installed: Community Applications; Dynamix Active Streams, File Integrity, Local Master, Scheules, SSD TRIM, System Information, System Statistics; Fix Common Problems; Nerd Tools; Unassigned Devies, unBALANCE Docker Containers: couchpotato, Sonarr, DokuWiki, Dolphin, dupeGuru, Handbrake, Netdata, RDP-Calibre, Transmission, Storj, QDirStat Future Plans: Going to get a VIVE-pro it will work on the VM. Case was chosen for the nine external 5.25" bays, so as time progresses the plan is to add 1-2 more of the drive bays for a total of 15 drives. If I get this full, the SSDs will be moved down to the bottom area where there is space of two more internal 5.25" bays. For port expansion I have the card, and my thought was to get an Intel RES2CV360 RAID Expander. The documenation on the SAS card says it can support like 64 devices, but just has the ports for 8, so I thought why not this direction? Updated HBA instead . No, seriously, if anyone knows if this will not work, I'll like to hear it. Answered, thank you. The Intel device just looks like SAS port replicator board, and has nothing to do with RAID protocol. POWER USAGE: Edit1: Just got power meter as of, Febuary ninth, so I now have values. Instantaneous readings/values, not avg over time. Boot (peak): 161.3 W Idle (avg): VM off: 149-153 W GPU VM On: 134-136 W Active (avg): Running STEEP in VM: 330-360 W vm idle (12 threads), 12 thread Handbrake trans-code: 300-330 W STEEP and continuation of Handbrake trans-code: 450-475 W Light use (avg): ## To be filled in later ## Thank you Lime-Tech developers and community developers who put in their time and expertise. I've been a very satisfied user, you all do good work. EDIT0: Been lurking a lot more on forums last month or two, came to conclusion that I under-utilize my cache on user shares. Added 500GB Samsung EVO to my cache pool, now reporting 870GB. Changed some user shares to include cache pool, which I had previously excluded use before. Next task, I need to finish cabling, drive cables are a mess and need to be redone. Next technical task, is try moving the LSI card back up in the PCIe slots, get working; then source a gpu card for player2, since previous card went to friend - current thought was to use the old Radeon 6800 as concept proxy, seeing how it hardly gets used. Still need to go shopping for a Killer-Watt. EDIT1: New SAS HBA is installed, another drive enclosure added. Upgraded parity drive from a WD blue to a WD gold drive, once the new parity drive was swapped, I added the old blue drive to the array for more storage. The parity check time from blue to gold cut about four hours off. Also got a GTX1050 to start testing a second VM, since that seems to be issue on Threadrippers, still. Although first boot with a simple GTX1050 has been very positive (ie its working).

This thread is huge, and I haven't been following it, but to go full circle @coppit brought the latest proposed PCI patch (linux kernel folks) for Threadripper to my attention on another post. For those folks, who would be interested in testing it, in 6.4.0-unRAID, have a look here -- it's been compiled.

Old post is old, I could see this as a handy resource, but the link is dead now. I mention this, as I was thinking about buying another copy for myself at work - this thread comes up as first hit when one searches for "find USB GUID."

VLC for other PC computer's. Otherwise RaspberyPI and OrangePI with KODI for my TVs - which I don't actually use that much.

I own one. The Antec 900 is a solid case, it would be a decent buy. The main CON I found with it, there is no room to run cables behind the motherboard or motherboard tray. So be sure to run good lines with your cabling, and also it can get cramp in cabling because you can't go behind, example the 12-volt CPU power cable, best route for that is to have it go over your motherboard, but under your graphics card -- if the header is located in the back of the case (or top left corner, looking inside) otherwise if the header is on the right you go around the board, but depending on your power supply this route could get a tad short; and you take up more room you'll need for enclosures.

Woh, wave of nostalgia seeing those sorts of beasts in Lawyer offices or cdr cloning days of old. Queue, the South Park detectives, "Niicce!"

Actually I just bought this case. General impressions: it's exactly what I wanted ATX, 9x 5.25" bays that you mentioned, the metal used is good gauge, it's not flimsy. CONS: This S.O.B. IS BIG! Really big! By BIG I mean the height, you look at it and you find yourself asking, "Am I over-compensating for something? Sigmund?" I personally don't like the top bit, The plastic is like a 90's computer front-panel cover. Functionally I like it, and as you said it's inexpensive. Aesthetically I perfer it with out the plastic top and front cover, but that's me. Also note below the 9x 5.25 external bays there are two more INTERNAL 5.25" bays below it with some 2.5" to 3.5" shims it's a good place for cache/SSD drives. My grand scheme is to couple the case with three of these Icy Dock 3x(5.25" bays) 5x(3.5" drive tray less enclosure) I have one, need to buy/grow into the next two. Forgot to mention, if you want to go with the trayless Dock I suggested, you'll need to do some case modification (dremel with a number of disc cutters) to remove the bottom holding tabs for each of top two slots (out of the three the bays take up).

Steam, a user share and a folder on my cache drive. I'm too old, lazy, and have better things to do with my time then to find; verify clean; and cobble Windows executive to working order to save on something I can get for an On-sale price on Steam platform. Also, I don't have any news-net accounts, which most scrapers seem to utilize, so little point for me to trying one of these Dockers. Steam is currently the only DRM platform I tolerate for personal use.

Current server is 64GB; next week's TR upgrade will also be 64GB, until price of ram goes back down which point I'll go to 128G -- Totally overkill for unRAID itself, but I like and play with VM's.

+1 I have a Tripp Lite, and was using the built-in support. I quit using the built-in support due to USB devices on my VM would cause discommunication with UPS. I thought it was a VM/IRQ sort of "bleed." Unsure of exact cause, but after learning of only APC support, I've let the computer run without UPS communication. I wasn't aware of macester's plugin, I'll have to take a look. Thank you for your hard work.

My attempts to help TS fell flat, I guess this is the level of OC I can provide : Cropped sample from a background I downloaded.

/tmp/emby does not stay on reboot. Rather its recreated at the time of the emby docker restarting. And after its created is when you'd have to do the chown. Hence why I'm suggesting to create the folder first. Otherwise the chown in go will do nothing, because the folder doesn't exist at that point. Ah that makes since. I think last time I tried, I started Emby got an error with transcoding. Looked back and saw /tmp/emby/ owned by root and thought, "okay it's permissions issue, I just need to do chown." You just just saved me the step of having the error one more time and going, "Ah that's why Squid mentioned both commands." Thanks for helping me skip a step, shame on you robbing me of an "Ah HA!" moment. No, seriously, thanks.

Ok, good to know. Will try it when I'm back at home tonight. When interim question though, is helping me understand users and how authentication works. When I created another second user account (let's call it "bob"), it didn't prompt me for a password anywhere. When i download the profile, and send to my device, how does it know who I want to auth as? While you are making "bob" or have made it, in User Permissions on OPEN-AS webui, to the right you should see a show link, click on that, from that dialog box you can change/set user passwords for VPN client. If the server is running you'll have to go to the top of UI an push the changes to the server. So now in your browser if you go to: https://foo_myIP.orDOMAIN:943/ you put in "bob" and password. This will get you DL's to OpenVPN client (if you don't have it already) and the client config files. Grab your config file and VPN client and go. If you already have your VPN client installed and configured, you can just open that put in bob and password. Unless it's the autorun profile which case your VPN client should autoconnect without username and password.

Thank you sir. Actually all that I need is line-2; if I'm remembering what occurs correctly (it's been a month since my last reboot). You'll need them both, because without the mkdir, when it hits the chown it will error out if the directory isn't already made (and since emhttp starts in the background and whenever it gets around to it starts up the docker apps, the odds are really against the directory existing no matter where you put the chown in the go file unless you add appropriate waits. Understood, but that's what I was trying to say before, /tmp/emby had stayed on reboot but the ownership reverted back to root. Minor point - the information you provided me earlier is enough for me to get that working (regardless of the actual behavior). Thanks again for your time and post.

Thank you sir. Actually all that I need is line-2; if I'm remembering what occurs correctly (it's been a month since my last reboot).

This can be corrected in the Go file so it "appears" to be persistent on reboot. Sorry for being obtuse, I still consider myself an "end user" making my way towards "power-user." Can you, or someone in the community, point me to either the Go file, or to the link of documentation which outlines the Go file (so I can RTFM)? I'm assuming the go file is something other then rc.d scripts?

The same idea for Emby. I added container volume /transcode and /tmp/emby host path for Dockers Volume mappings. Afterwards I then had to: [*]ssh into my unRAID: #: chown nobody:nobody /tmp/emby [*]open Emby webui >> go to: /web/encodingsettings.html [*]change "Transcode temporary path " to: /transcode Note: one downside, if you reboot unRAID the /tmp/emby folder's ownership changes to root, so you have to go in and change ownership back to nobody. #Edit: hopefully this is useful to people.#

For any of those interested, and haven't done so themselves, I took jonp idea of Plex Transcoding and applied the same idea to Emby. I added container volume /transcode to /tmp/emby host path for Dockers Volume mappings. Afterwards I then had to: [*]ssh into my unRAID: #: chown nobody:nobody /tmp/emby [*]open Emby webui >> go to: /web/encodingsettings.html [*]change "Transcode temporary path " to: /transcode Note: one downside, if you reboot unRAID the /tmp/emby folder's ownership changes to root, so you have to go in and change ownership back to nobody. #edited for better grammar#

+1

root@HYDRA:/mnt/disk1/DockerApps# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 0 (Ethernet) RX packets 376918292 bytes 545599728025 (508.1 GiB) RX errors 0 dropped 213548 overruns 0 frame 0 TX packets 35516033 bytes 6243595662 (5.8 GiB) TX errors 0 dropped 12 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.101 netmask 255.255.255.0 broadcast 192.168.0.255 ether 10:c3:7b:6f:43:ae txqueuelen 0 (Ethernet) RX packets 85104066 bytes 554801007870 (516.6 GiB) RX errors 0 dropped 13916 overruns 0 frame 0 TX packets 39609148 bytes 126332393253 (117.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 46:e0:a9:09:01:15 txqueuelen 0 (Ethernet) RX packets 52898 bytes 14164401 (13.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 53867 bytes 30521239 (29.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 1000 (Ethernet) RX packets 376704744 bytes 545585615783 (508.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35516033 bytes 6243595662 (5.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 1000 (Ethernet) RX packets 213548 bytes 14112242 (13.4 MiB) RX errors 0 dropped 213548 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xfbf00000-fbf20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 137464 bytes 25960421 (24.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 137464 bytes 25960421 (24.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth17b05fb: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 8e:b6:70:ea:a8:35 txqueuelen 0 (Ethernet) RX packets 2115 bytes 859529 (839.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1924 bytes 1218400 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth638c205: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether a6:2a:88:78:4c:66 txqueuelen 0 (Ethernet) RX packets 19556 bytes 2062340 (1.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 21441 bytes 9256959 (8.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetha052b41: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 46:e0:a9:09:01:15 txqueuelen 0 (Ethernet) RX packets 699 bytes 548224 (535.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 897 bytes 705751 (689.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:fb:a4:f1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether fe:54:00:7c:e6:b8 txqueuelen 500 (Ethernet) RX packets 12455171 bytes 31394587093 (29.2 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 89716902 bytes 129283508307 (120.4 GiB) TX errors 0 dropped 5018 overruns 0 carrier 0 collisions 0 I'm a noob, but guessing from the ifconfig my docker needs to be pointed at br0 and not eth0 (default)? And if correct, I don't know how to go about doing that but I guess I can keep digging. I suspect it's down to the fact you've got bonding enabled on your Unraid machine as that's the only difference I see between my setup and yours. I went into webUI - edit page for docker; added a variable INTERFACE with a value of bond0 -- I can now access port 943. So I think my issue is resolved, but before I get too comfortable I just want to ask is this fix kosher? Also before this, I didn't realize I could do this. I.e. is there a technical reason it's mapped to eth0, or it's just default (you have to start somewhere)? Again, thank you for your assistance and time (not to mention patience to deal with this noob).

root@HYDRA:/mnt/disk1/DockerApps# ifconfig bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 0 (Ethernet) RX packets 376918292 bytes 545599728025 (508.1 GiB) RX errors 0 dropped 213548 overruns 0 frame 0 TX packets 35516033 bytes 6243595662 (5.8 GiB) TX errors 0 dropped 12 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.101 netmask 255.255.255.0 broadcast 192.168.0.255 ether 10:c3:7b:6f:43:ae txqueuelen 0 (Ethernet) RX packets 85104066 bytes 554801007870 (516.6 GiB) RX errors 0 dropped 13916 overruns 0 frame 0 TX packets 39609148 bytes 126332393253 (117.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0 ether 46:e0:a9:09:01:15 txqueuelen 0 (Ethernet) RX packets 52898 bytes 14164401 (13.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 53867 bytes 30521239 (29.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 1000 (Ethernet) RX packets 376704744 bytes 545585615783 (508.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35516033 bytes 6243595662 (5.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 10:c3:7b:6f:43:ae txqueuelen 1000 (Ethernet) RX packets 213548 bytes 14112242 (13.4 MiB) RX errors 0 dropped 213548 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xfbf00000-fbf20000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 137464 bytes 25960421 (24.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 137464 bytes 25960421 (24.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth17b05fb: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 8e:b6:70:ea:a8:35 txqueuelen 0 (Ethernet) RX packets 2115 bytes 859529 (839.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1924 bytes 1218400 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth638c205: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether a6:2a:88:78:4c:66 txqueuelen 0 (Ethernet) RX packets 19556 bytes 2062340 (1.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 21441 bytes 9256959 (8.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vetha052b41: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 46:e0:a9:09:01:15 txqueuelen 0 (Ethernet) RX packets 699 bytes 548224 (535.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 897 bytes 705751 (689.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:fb:a4:f1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether fe:54:00:7c:e6:b8 txqueuelen 500 (Ethernet) RX packets 12455171 bytes 31394587093 (29.2 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 89716902 bytes 129283508307 (120.4 GiB) TX errors 0 dropped 5018 overruns 0 carrier 0 collisions 0 I'm a noob, but guessing from the ifconfig my docker needs to be pointed at br0 and not eth0 (default)? And if correct, I don't know how to go about doing that but I guess I can keep digging.

I deleted my container in webUI; ssh and deleted the folder I was using on the user share. Made a new Docker Container, pointed /mnt/disk1/FOO per suggestion. Same issue as before, error connection refused. Tried https://192.168.0.101:943/ (correct IP) and https://localhost:943/ Also have the same error in openvpn.log. What else should I try? Thanks.

Just installed docker. Tried to launch webui received the error: connection refused. Docker setup is all defaults, as shown in screen shot. http://hydra/mnt/user/DockerApps/openvpn//log/openvpn.log reports: ... 2016-01-14 21:10:29-0800 [-] Server agent initialization failed (6/6 attempts) because the following network resources are unavailable: set(['eth0']) 2016-01-14 21:10:29-0800 [-] Server Agent is inactive due to the following errors: {'errors': {'admin_ui.https.ip_address': [('error', "LOCAL_ADDR eth0 : bad local address name or interface is not up; must be 'all', 'localhost', a local IP address, or an interface name: What do I need to change to fix this? Thank you for your help ###EDIT### Resolved. See reply #45 for fix.. /closed ticket/