electron286

One of the things that Microsoft did was to disable older networking support, so I had to re-enable the service to allow connectivity with my older computers. There are many things that they do with each major update, to be inline with the new "current" security model. This includes setting networking option to higher security levels, and disabling older features no longer needed, (if you are in an all Windows 10 Networking environment). Registry keys are changed, moved, and renamed to make it harder for remote scripting hacks to work. There are good reasons, but they just do not work for me because I still network my older computers also. I need to do things to allow my Windows 9x and newer computers to all just work together like they always have. Of course then there are also the various game systems, and linux computers too... Windows 10 is like the ever invading army trying to push new methods to force the old fully usable computers to be retired and replaced with newer ones. I have decided with the latest aggressive onslaught, that any new upgrades or replacements definitely with NOT be Windows based as a result. So, with all the changes with each update, all I can say is you need to look into ONE symptom at a time that is impacting your use of Windows 10. Do some searches on-line, making sure to try looking at more recent posts, as older ones for the same type of problem may no longer have solutions that will work for you. You may need to do any number of registry key changes, advanced networking configuration changes, and also re-enable or even re-install a removed service to regain full functionality with other computers. Good luck. I would help more if I could, but each time the changes are different, and take significant time to dig into Windows to find the cause, then the resolution is usually not to bad... And where everyone uses their computers differently, it would not be unusual for you to need different "fixes" than I have needed. If you would like to post a little more about your specific issue(s) I could make an attempt to help you move in the right direction. Also, when looking at posts for solutions, you may want to actually look at the most recent first, and work backwards with all the changes Microsoft keeps making. It may speed up your solution.

I always preferred my nice warm Amber monitors over the harsh green ones myself.

Sounds great! For your use, I think you will be much happier with what you bought than you would have been with the old Supermicro Server. I guess I need to look at my old servers and consider making some updates myself. Newer controllers would be a big boost on my Athlon(tm) 64 X2 server for sure. I have always loved how easy it is to upgrade hardware with Unraid, even the older 4.x versions were VERY good I felt, just had to move the drives, and/or cables around to make the array valid there. But CPU, M.B., Chipsets, Controllers, NICs, most everything will work!

Just two days ago, I had a problem at work where the USB Keyboard would not work on one of the computers. It worked for initial boot, BIOS, Wndows boot selection (F8), but after that it would do NOTHING and there was no way to log into Windows. The USB Mouse was still happy though. Then I found out the computer had been moved, then hooked back up. I then started realizing that the cable for the keyboard probably had been switched to a different USB port. I looked at the motherboard, and realized that two of the rear USB ports were from the MAIN CHIPSET, and the other 4 USB ports were going to an additional support chip. In this case, it was a driver issue for the add-on chip for the 4 USB ports that the keyboard and mouse were both plugged into. Windows, as pretty much every other OS, loads and uses the drivers it has configured for the hardware on the mother board, INCLUDING ALL hardware that may already have been functional before the OS fully loads. I moved the cable for the USB Keyboard from one of the 4 ports on the add-on chip, to one of the two USB ports on the main chipset, booted the computer again and everthing started to work normally again. This is just one of many times over the years I have seen this type of behavior with USB Keyboards. There are other times, when I have not been able to find ANY USB port on the mother board that would work fully with a USB keyboard always. In one case, I had a multi-boot computer that one USB port set would work with the Keyboard in Windows but not Linux, and the other USB port set on the motherboard would work in Linux, but not Windows! Luckily, this motherboard did also have the PS2 type connections, that worked well in ALL the boot states and OSes that were loaded so all USB keyboards removed and an older PS2 type keyboard installed. I have also seen more issues with USB Dongles, than with hardwired USB keyboards. You may also have better results by moving the USB dongle to another USB port on the mother board. I always recommend to, IF USB MUST BE USED, to try to make sure the keyboard is plugged into a USB port connected to the MAIN CHIPSET not an add-on chip. USUALLY this would also mean that you would be wanting to use a USB port on the BACK of the computer, NOT one on the front of the case, or via a USB hub. The trick is which ports on the back are on the MAIN CHIPSET? Usually the motherboard manual can help you out to know which USB ports are on which chip... As a side, but related note, I have also seen better compatibility with USB keyboards with INTEL chipsets and associated drivers (including BIOS), than with other chipsets. I have not paid attention to USB DONGLES and chipset compatibility, as I really try to avoid them unless absolutely needed, and then I usually try to still have a hardwired keyboard there also as a second keyboard for when the dongle does not work... It does seem, from what I have encoutered, that the USB Dongles usually have a better chance of working well AFTER an OS has loaded and taken over than in the pre-OS environment with the BIOS drivers running however.

Sadly, I have also had some new big name power supplies that were bad out of the box. It does not happen often, but it does happen.

hat22, It looks like you have a Gigbyte board... G41-ICH7-6A79PG0WC G41M-Combo FB 1st, I would go into your BIOS settings, and under your "Advanced BIOS Features" screen near the bottom you will likely see a setting called; "Delay For HDD (Secs)" Change it from the default setting of "0" to the maximum of "15". This will allow the BIOS to wait before attempting to send commands to the hard drives to initialize the communications between the chipset and the drives. This will insure the drives are fully ready to talk, unless there is a real problem. 2nd, if not already enabled, also enable "HDD S.M.A.R.T. Capability" on the same screen. 3rd, MAKE SURE THE "Backup BIOS Image to HDD" feature is already "DISABLED" - IF NOT YOU MAY WANT TO STOP HERE FOR A LITTLE BIT AND RESEARCH THE NASTY FEATURE AND THE HAVOC GIGABYTE HAS CAUSED US UNRAID USERS BECAUSE OF IT!!! 4th, press F10 to save... (this may not be needed here, but some BIOS versions require you to save before moving to antother screen to not loose the settings you just changed.) 5th, after looking to see of anything else needs to be changed anywhere, esc to leave the BIOS setup screens. It looks like there is a problem with the hard drive on ATA2 to me. The above steps MAY have helped, with the added delay for the hard drive to perform power up diagnostics before the mother board starts asking for responses. Another possibility could be as easy as a loose connector/bad connection. So I would next unplug the cables, then plug them back in to see if it makes any difference. You could also move the cables between drives and ports on the mother board to identify a bad cable or port on the mother board. In the BIOS settings again, you can also DISABLE any unused ports to make sure they are not also checked during POST. This can speed things up some. You can do some quick tests also by unplugging all the drives, and seeing how the system POSTs then try ONE drive at a time with additional POST time tests. You can either unplug the Unraid FLASH drive during these tests (suggested), or power off the computer after the DMI POOL has been checked when the Lime Technology Boot Selection Screen pops up. You probably should do a quick SMART test on all the drives after Unraid is booted. Then you can see a little more than the normal SMART reporting will show. A long test may also be advisable for the drive that seems suspect. If all else looks good, you may want to replace the drive, and rebuild the data on a new one.

Pretty cool if you can also still use the keyboard. I do not think I could make myself do that, I love my Atari computers too much. Plus many of my Atari computers also have been upgraded with RAM and other upgrades. :-) ok... sorry for the off-topic

I would hook up a monitor to the server, and watch it. Then you can see what is actually happening during bootup, POST, etc. If you would like to make a detailed list of what happens, including times for each phase of booting up to the point the console login is presented. Then after that how much time before the web GUI is available on a networked computer. After that we can see what we can talk about to possibly speed things up. The time you are seeing may be NORMAL for the hardware you have, but there may be some settings that could speed some phases up.

I will need to agree, while it sounds nice, there are just too many things that need to work together for this type of a setup for a client. The only way I would do this for a client, is if part of the fee paid was living in the guest bedroom. You are going to live there anyway with this setup. Now... Basic concept I can agree with. Intel NUCs are great for a TV device. However, the cheap but very capably Chromecast Ultra works very well with PLEX, as long as you want to use a tablet or phone to cast from. I like the Tablet option since you can get nice large tablets for cheap that make for great controllers for casting PLEX and other apps to the Chromecast units. It all depends on if you also need 5.1 or 7.1 surround at each TV also. The NUC is a better choice for full surround, BUT... you need to make sure which one works well for your audio set-up! if you want the highest quality possible, why would you need Handbrake? Normally people only use Handbrake to compress video to reduce the size, which also reduces the quality. Unraid is great, and works well for many things, I love it as a video storage server. XBMC (now KODI) is my favorite for a video player. Plex is great for transcoding and watching server based video content to a wide range of devices. Most people would NOT want to use KODI and Plex, they each have advantages and disadvantages compared with each other. Unless you plan to also use one of the "hacks" to merge them together functionally, I would suggest sticking with Plex and forgetting KODI. I would suggest getting a copy of Unraid and Plex to try them out to see if they will work the way you desire. Try them on any compatible hardware to start with and go from there. It looks like you may have a real bottle-neck issue with that external drive enclosure however. Yes I think you could get it to work, but the bandwidth would be limiting on parity checks and rebuilds it seems.

Everytime there is a Windows 10 update, it breaks many things I need. I need to go in and reconfigure all my network privileges, and find where they moved things in the registry "this time" and whatever else they changed in their NEW default security model... I think I am giving up on Windows 10 the next time. It took me over 2 hours to make my Windows 10 system usable after the last forced update. And that still happens sometimes, EVEN WITH THE REGISTRY KEYS CHANGED TO KILL UPDATES!!!!

Pretty cool! I think some people will really enjoy this! Not for me sadly, I just do not spend enough time before the web UI to really feel a need. But I really did enjoy watching the process you went through!

If timing from pressing the power button, I am wondering how much time is actually spent from when the Unraid image is loaded till the shares are available. I have a few server hardware unraid installs that I think take close to 6 or 7 minutes just to go through the disk controllers and then start the normal MB Bios memchecks... I also have some installs that load the image from USB in about 10 seconds, and others that take a good 2 minutes just to load the image from USB. Add to those times bios checks, and loading the os after the image is in RAM, then the array startup checks...

Performance... I just saw this thread that also may have also been related to the initial problems... https://forums.unraid.net/topic/76834-please-help-cpu-spiked-to-100-plex-unusable/

I do not use Sonarr, so I may be wrong, and can not test it... But, look at your Season Folder Format setting, it is set to: Season {season} I think it will work as you desire if you change it to: Season {season:00} I think setting it in the normal screen, will also allow it to show with the new setting in the advanced settings, if not change it there too. I think this is the same as going from a null, or undefined folder configuration to a defined format for the folder configuration for the season number xx folders.

If the problems have been resolved GREAT! but... I thought from the initial post that Radarr was causing an issue, as that was when the crawl popped up... In looking into it, and some related Radarr posts, it seems there have been some memory leaks, that should be fixed now in the current builds, and also some configuration problems some people have seen performance issues with, the biggest one being; Quality profiles - Be sure to set your CUTOFF settings appropriately for EACH Quality profile to allow Radarr to stop looking for better versions of downloads. Followed by not setting up Delay Profiles, to allow for a longer delay before looking again for matching downloads. I know some people really do not like the word WRONG, so that may be the source of the issue as seeing the replies as unfriendly. While I also use the word, I try to use the words incorrect, or incorrectly, when writing to an unknown audience. Wrong is often taken personally, regardless of how it was used or intended. Add to that how many times the word wrong did appear in multiple postings, and... well you get the general idea. No matter why the emotions are ignited, it is hard to look at any other part of a conversation without them getting in the way. The Unraid forums have been the BEST forums I have ever seen as far as keeping things civil, and while we all make mistakes at times, all the guys here really do care and try to help each other. We all have a love for computers, and the wonderful solution that Unraid has provided for many years, and now the many MORE solutions it provides! I would like to say WELCOME titanarchon, and I hope you can enjoy your Unraid server and feel better about this forum. We are all new at some point, and even newbies on some aspects of Unraid with all the changes that have been rolled out over the years. I am still mostly way back on version 4.5.3 for an example. I have set up newer versions, but mostly 4.5.3 is my work horse. (NO I WOULD NOT RECOMMEND ANYONE USE 4.5.3 UNLESS THERE IS A REAL NEED, DUE TO THE MANY POTENTIAL USER ISSUES THAT COULD LEAD TO DATA LOSS! These problems were all resolved nicely in newer releases.) I am also the ONLY one that touches my old units. If I had anyone else touch my servers, I would be running newer versions just for the safety and peace of mind. Anyway, with each new Unraid server I set up for other people, I always use the newest stable version, and always need to learn what changes were made since the last server I set up. Sometimes the new features do have a bit of a learning curve, (such as setting up shares to work properly in a PLEX Docker..).

I think that is the same as one of my SuperMicro servers. Mine seems to work very nicely so far, using it for testing a new Unraid installation with Plex in a Docker. Mine came with two processors though and 32 GB of RAM. I love the Supermicro cases, for the quality build of the cases, drive caddys, redundant power supplies, cooling, and very stable hardware! THEY ARE NOT QUIET HOWEVER! You can normally configure the fans to run slower than full speed, which helps, yet due the large number of fans, these are still loud cases. Depending on what you have in use for storage and work load, you can unplug a "few" fans and still keep the temperatures nice and low with the fans running at low speed! You do not get the safety net of cooling well if a few fans fail without being noticed however that way. The one you linked to also does NOT include the drive caddies, so they would need to be bought seperately as an added cost. Also over the years, Supermicro has used a few different Caddy designs, so while not hard, it is a little extra work to make sure you get the correct caddies if you buy a chassis without them. I like front mounted drives, which can be done with the Supermicro, and Norco cases, as well as quite a few nice drive bay options for large standard cases. Redundant power supplies, while nice, may really be overkill for home. :-)

I have had many issues with USB keyboards over the years not working at one point or another during the boot and handoff processes between bios, extended bios, boot selection kernal, OS.... I still try to use mother boards that have dedicated PS2 style Keyboard and Mouse ports as a result. I did have one mother board that did like a USB to PS2 keyboard/Mouse adapter MUCH better than a USB keyboard though. It never worked right with a USB keyboard, no matter how many different one I tried. When I switched to the adapter and a PS2 Keyboard, I never had another problem with it. I think it was either an Acer or an HP computer if I remember right... I have seen similar symptoms on a few Dell computers though. Anyway, over the years I have found the main reason on my machines for the screen to go black, or any other "lockup" to be power supply related. Just popping in a nice new beefy power supply has almost always fixed my problems with unstable systems. This has been on computers that had previously been running with no problems and then start to be non-operational randomly. The next common problem I have seen is memory, as was already mentioned by "trurl". It could be failing memory that can be found by a memtest, or it may be a low resource level, meaning not enough memory is available for what demand is being placed on the hardware. If the memory is good, adding memory could be the fix. Another thought, some BIOSes have some strange power saving options, (I think mostly older ones), that actually will shut down parts of the motherboard and chipset if enabled and the computer is not actively used with an input device. Come to think of it, I think it is on mother boards like that, where I seem to have had the largest issues wit USB Keyboard compatibility... but that may be simply a co-incidence.

Don't laugh... My two main servers on 24/7 used for adding to, editing and compressing video and active content sharing only have 1GB RAM each (total only 28TB of storage between the two). They work great and are really only file storage, and all work is done on other computers. Multiple drives are almost always being accessed either by me and my working data munching computers, or by family remotely watching content remotely somewhere using Plex. Plex is also running an a separate server looking at my unRAID shares. My main ARCHIVE server is a bit heftier, and much newer. It has 8GB of RAM, has 30TB of storage, and is also on 24/7, and is also seen by my Plex server. NOTE: I only use Plex outside the home, and always use XBMC or KODI internally. My other less used specialty backup servers I think are now all up to 1 GB of RAM, but some may have less. They are only powered up when I need to access much older data, files, and machine drive images and such. Many of these are not x64 capable either. I do not like upgrading, and feel if it is working well let it keep running as it is. If I need more, I look at what my future/new need is, and usually just build a new machine to add to the pool/farm. I did pick up a new (actually old surplus) server that has 4 CPUs, and I think 32GB of RAM, but I have not had a chance to really play much with it yet. I was planning on setting it up with all the new bells and whistles and run a Plex server on it after I get a new unRAID key for it.

I think you both may be slightly talking on different topics, or aspects without realizing it. So yes, as Squid said, "Assuming that you have a share named VM + Plex with a subfolder named Plex that contains your media files, you tell Plex to add your libraries from /MyMedia" I might have said it differently, such as; as long as the mount point VM + Plex exists in your Linux environment, with a sub-directory named Plex that contains your media files, you tell Plex to add your libraries from /MyMedia Again, so I hopefully do not cause additional confusion in the matter... Many people say subfolder, but I still think of them as sub directories. I also think there are various names and descriptions for what I call Mount Points in Linux, but I am not sure what they would be so, short description follows of a Mount Point (as far as how I think of it at least); The virtual mounting place in the Linux file structure tree, where devices are virtually placed to provide a logical access point to reference file access from. The devices which are virtually mounted can include physical storage and other virtual storage devices, either locally existing, or externally over various mapped network paths. jjackstar, I played with plex about a month ago under docker. I was at first seeming to have the problems you seem to be describing. I thought I was doing things correctly, but no worky... Then I put my mind back in to very basic LINUX mode. I looked at the configuration settings, and it dawned on me... "good grief! I am linking to a mount point that I have never set up so it does not exist!" So I actually created a mount point to match what I was setting up in the PLEX docker configuration, and IT WORKED! I then played with setting up various mount points that were actually other computer resources on my network, and they also proper worked and could be added to the PLEX docker server libraries!

Just a quick note on speed performance... I have various unRaid builds, on various hardware. I have now fully switched my NICs in my unRaid servers from realtek Gb to Intel Gb NICs. Running speed tests to and from Windows clients, also running Intel Gb NICs in ALL of these specific tests, I was able to get a very consistent speed increase FROM the unRaid servers of 5-15%, depending on the drives and other hardware. Write speeds to the unRaid servers were pretty much un-affected due to the parity writing overhead and calculations. One more thing, I ONLY use SMB...

My mind saw it in reverse... yes it improved, but still I would watch it...

ok, it looks like the pre_clear did show a concern, but there were NO re-allocated sectors still at that point... During pre_clear cycle, the Raw Read Error rate increased, reducing the FAITH in this drive. ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 95 85 16 ok 327685 9.8 POWER ON days after the pre_clear cycle, there was an error, that looks like was the action that may have been when the re-allocation occured. Error 2 occurred at disk power-on lifetime: 28340 hours (1180 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 d0 58 31 57 00 Error: UNC 208 sectors at LBA = 0x00573158 = 5714264 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 28 2f 57 e3 08 49d+00:01:26.724 READ DMA EXT 25 00 00 28 2b 57 e0 08 49d+00:01:25.918 READ DMA EXT 25 00 00 28 27 57 e3 08 49d+00:01:25.905 READ DMA EXT 35 00 08 a0 0c 57 e3 08 49d+00:01:25.875 WRITE DMA EXT 35 00 b8 68 08 57 e3 08 49d+00:01:25.858 WRITE DMA EXT I would get a drive ready for replacement, to make a swap when convenient. It may be ok for a while, but with how much change there was in the Raw_Read_Error_Rate parameter with a pre_clear cycle, I would not trust that drive much longer.

I think this is the correct forum... The cages you bought look like they should work well. They look easy to replace the drives, and they also have the ability to support a front mounted fan, which seems to cool drives better, and shold also make it easier to replace fans in the future. Personnaly I would probably go with the Antec 1200 case, I have two and love them. The only issue you will have will be that the little tabs in the case will need to be smashed down flat to allow your new cages to fit in the case properly. But this is true of MOST computer cases on the market today, at least that I am aware of. The AOC-SAS-MV8 is a good card, but the AOC-SAS2-MV8 is newer and faster, and usually about the same price. http://www.newegg.com/Product/Product.aspx?Item=N82E16816101792 Either one will need SAS Breakout cables to "breakout" the mini-sas connections to the multiple SATA connectors. You would need two cables per SAS-MV8, such as: 0.5 meter - http://www.newegg.com/Product/Product.aspx?Item=N82E16816132039 0.6 meter - http://www.newegg.com/Product/Product.aspx?Item=N82E16816132040 1.0 meter - http://www.newegg.com/Product/Product.aspx?Item=N82E16816132041 You do NOT want the Reverse Breakout cables, which COMBINE SATA ports from a controller to connect to a mini-SAS connector on a backplane drive cage. Don't forget the fans if you have not already ordered them, or have in hand. Sounds like it will be a nice upgrade!

That looks like a very easy case to work with! I don't look at me unRAID servers all the time anyway, so to me it is fine if it has red and blue flashing lights, or even looks like a UFO, as long as it works well for my system and keeps the drives cool, it is GREAT!

With the change in name from oom_adj to oom_score_adj was anything else changed, is the functioing all the same?