Frank1940

try this:

Here is a instruction course in Bash: https://en.wikiversity.org/wiki/Bash_programming

First thing, you need to trap the error code on exit. (All proper behaving Linux commands will have an exit code on completion which 'tells' if it completed successfully. A properly written BASH script should 'trap' this code and test it for proper execution if there is any possibility of failure. OF course, it is up to the script writer to figure out a way to gracefully handle this.) What I also can't remember is exactly where the 'go' file executes in the boot process. It could be that you are executing the modprobe command before the OS is fully installed. There is a plugin called 'CA User Scripts' which can be used to run user scripts. It might be the solution to your problem. You might also have to learn a bit of programing. The shell used by Unraid is named BASH (Bourne Again Shell) and, if you google it, you can find tutorials to help you write a script for your use. It is very powerful scripting language! (The preclear script is written in BASH!) These tutorials could also provide you with the knowledge of a way to integrate your commands (or call another 'script' from it) into the 'go' script and have it work. Now for the disclaimer. It has been forty years since I had a course in Shell language and it was for the Bourne Shell. (BASH came along in the late 1980's.) I forgotten so much that I would be starting over in attempting to provide assistance in helping you write one.

have a look at this post and the next several after it: https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392 Have a look at the Credentials Manager (in Control Panel) settings and see if you have any at all. If you do, try deleting them. (Sorry, I have no idea how to get to the Control panel in WIN8...) Windows provides for ways to automate the login procedure and then things happen in the background. Also, you are only allow ONE login to a server for each computer connected to it. So if you get logged in automatically, you usually can't establish a second connection. Another caution, 'root' is also not allowed as a SMB user.

Have a look at this YouTube video for the type of SATA connectors to you should be looking for:

+1 (That would be a bad as those folks who (for what reason) think a new configuration will rebuild a drive!)

Can you log in via terminal session (using, perhaps, PuTTY)? IF so, type the the following commands: diagnostics poweroff Remove the flash drive and plug into a PC to get the file off of the drive. As a bit of insight, Unraid will use available RAM to buffer writes. This will take and store data as fast as your network connection can deliver it. After that, the transfer will slow down to the write speed of the cache drive. My experience was that a HD (320GB-5400RPM) can be substantially slower than an SSD especially if there are a large number of very small files. (File creation overhead (both SSD's and HD's) plus drive latency to get the head in position for HD's.) But appearing to be frozen is not expected in any case...

Begin by posting up your diagnostics file. Tools >>> Diagnostics in a new post. Have you recently upgraded from one version of Unraid to a later release?

Are these examples of currently available products? https://www.newegg.com/samsung-960-evo-1tb/p/N82E16820147595 and https://www.newegg.com/intel-750-series-400gb/p/N82E16820167359 The first, I believe, will work if you get a board with the appropriate NVMe socket for it. But I have not seen any MB's with more than two sockets. The second one would require the proper PCIe sockets and the proper configuration of the PCIe busses for maximum throughput.

It depends. Look at my two servers. The Test Bed Server idles at 47W and hits 71W when all the drives are spun up. If I start a non-correcting parity check it increases to 81W with peaks of 85W. The Media Server idles at 36W and hits 72W when all the drives are spun up. (Note that both of these servers are using an i3 Intel processors in different CPU 'families'.) Plex is considered to be a CPU hog and requires about 2000 PassMarks for each 1080p stream when transcoding video. As I recall, the i3 can handle about one transcoding a 1080p stream easily and possibly two if conditions are optimal . And when it is doing so the power consumption will increase. So you want to minimize the power consumption, pick an CPU/MB combination for each server that has just enough horsepower to do the job that you need it to do. Pick a recent CPU family that is optimized for power consumption. Pick a CPU that has built-in graphics capability to avoid the overhead of a separate video card. You will probably pay a bit more in purchase costs and you may be forced to upgrade the CPU if what you want to use the server for changes in the future.

You can also submit a 'Feature Request' in this sub-forum. It might be time to revisit this feature again. https://forums.unraid.net/forum/53-feature-requests/

Yes, the boot flash drive must be plugged into the server at all times. Otherwise, it can 'lose' its link to the OS. While the flash drive is not accessed much during normal operation, there are occasions when it must be accessed and it is always written to during shutdown or reboot.

There are a lot of us you do not really trust MS, Firefox and Chrome to be our password manager! They already have told us that they snoop into our personal lives and collect as much data about everyone of us as they can accumulate and that they plan on marketing that information. . Perhaps, we are paranoid but with their history and business plan, I would rather err on the paranoid side then truly trusting them with 'protecting' the passwords to my financial and personal life!

What do you mean by this "sometimes"? IF it does not always work when you run it manually, why would you expect it to work in a script environment?

If I understand what you are doing, I would suggest this approach. Setup the HD share (Call it --Long_Term) and restrict it to the HD's. Setup the SSD's share (Call --Short_Term) and restrict it to the SSD's. By using the shell script, you can easily tailor it to copy from the Short_Term share to the Long_Term share. You just have to determine at what age, you want to make the move from one to the other to minimize having to go the long term storage side of things for work-in-progress files.