TUMS

needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas. Maybe so but he's definitely still updating it. In fact I just got an update today to 1.4.1.3662 That is the nature of the docker "update" by restarting it. It goes out and gets the latest build from Plex. Needo hasn't touched the docker container code in months. The implication is that the docker code needs to be touched. Is there something about Needo's docker code that needs updating? Good question. Probably nothing wrong with Needo's code. The thing is that if/when any one ever has a problem with Plex and they are running the container from Needo, the first troubleshooting suggestion is to switch to linuxserver or binhex, as those two still actively support their containers whereas everything from Needo is basically without any author/maintainer support at all Thanks squid. I'll probably leave it alone for now. I've had no problems with it.

needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas. Maybe so but he's definitely still updating it. In fact I just got an update today to 1.4.1.3662 That is the nature of the docker "update" by restarting it. It goes out and gets the latest build from Plex. Needo hasn't touched the docker container code in months. The implication is that the docker code needs to be touched. Is there something about Needo's docker code that needs updating? Good question.

Thanks. I should probably try and switch over to linuxserver.io plex docker soon then... Is there a way to switch and have it still recognize my needo created plex library or do I have to delete everything? edit...nevermind, I found it http://lime-technology.com/forum/index.php?topic=40937.msg445818#msg445818

needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas. Maybe so but he's definitely still updating it. In fact I just got an update today to 1.4.1.3662

If you install the needo plex docker it automatically works with plex pass. That's what i'm running....

I'm glad I switched to IBM M1015 cards a while back. Totally worth it not having to deal with all the potential problems and I was able to resell my SAS2LP controllers for close to what I paid. I'm running in a 4u server chassis anyway so cooling is not a problem.

Interesting but hopefully just a coincidence. I'm pretty sure i've swapped around cables in the past before. One thing is APC cables have part numbers on them so you can definitely run the numbers before using to make sure they're compatible with the ups you are using.

I've got literally a pile of APC cables from all the ups's i've bought over the years. And on most of the newer higher end APC models you can just use any old generic USB cable (one with a normal end on it as opposed to the apc rj45 usb) It doesn't have to specifically be a APC usb cable.

I have 11 data drives & 2 parity.

Should work. If it doesn't have usb you can always use the serial port. Just make sure there is a port available on your motherboard.

Thanks for posting. I just did a factory reset of my wdtv live box and now everything is working again.

Feel free to enable the syslog/log level settings and see what the syslog says about why your connection is failing. It may give some insight. Thanks, good idea! I'll try and look at this tomorrow when I get some time.

I'm having the same type of issues with my wdtv live box and private shares. And activating ntlm in the config didn't help either. I'm probably going to have to go back to 6.2.4 till all this is resolved...

You can usually buy 8tb reds for under $300 on ebay fairly easily. I would go there. Just make sure the drives are brand new and the seller has good feedback.

hmmm, that's news to me that people are having issues booting with SM boards. Maybe it could be a bad flash drive? I use 16gb SanDisk Cruzer Fit with both my SM boards. Never had a problem yet. knock knock.

Maybe you just got a bad board. I'd try getting a replacement supermicro board before trying another brand. I've used both X10SLH-F and X10SL7-F boards with unraid and they've both been great.

Modbus with a serial cable works now, but yeah it would be nice to be able to use modbus with a USB cable.

I updated to 6.3 last night. Now on my Wdtv live box it's saying unable to connect to selected source. Running the latest firmware. It sees TOWER just fine but it's just unable to connect via windows share.

Thanks for taking the time to look at my diagnostics John. Hopefully it will just go away. The server is running fine so it's probably nothing to worry about.

Here's the diagnostics file. Thank you! tower-diagnostics-20170201-1553.zip

I just started getting these the other day in my log file. Otherwise system seems to be functioning fine. Anyone have any clues as to what this is? Do you guys think this is anything to worry about? Actually I just introduced a new drive (hgst he8) into my array the other day and that was about the time I started seeing these warnings in my log. Thank you! Feb 1 06:03:06 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:09 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:09 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:11 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:19 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 06:03:23 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:46 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:46 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:46 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed. Feb 1 07:15:47 Tower avahi-daemon[11104]: avahi_normalize_name() failed.

My prediction. Once UHD blurays are able to be ripped there's going to be a whole lot of upgrading going on ... Hopefully it will happen this year.

For gaming i'd probably choose a single e5 with a high clock speed. Probably a Xeon E5-1650v4 Stock @3.6ghz -- turbo 3.8ghz. Passmark 14364 https://www.newegg.com/Product/Product.aspx?Item=274-000A-00083&cm_re=e5_1650_v4-_-274-000A-00083-_-Product https://www.newegg.com/Product/Product.aspx?Item=N82E16813182927&cm_re=x10srl-f-_-13-182-927-_-Product Don't know if it would handle 2 people gaming at the same time plus HD plex streaming though.... Guess it would depend on the games being played.

Yeah it's either your raid controller or your new case/backplane. I use IBM M1015 cards with norco 4224 backplanes and can see drive temps no problem so somethings not right with your setup.

hmm, You should still be seeing disk temps. Somethings not right.