Frank1940

This is generally a network issue-- Not a SMB one ---when there are transfer speed problems with a single file. Make sure that the MTU is set to 1500 bytes for everything in the entire network. (No jumbo frames) Reboot all the hardware in the entire network. (These are all small computers and a occasional reboot will sometimes 'fix' things...) On the Unraid Dashboard, have a look at the Interface (shown below). Particularly, the Error info. I have circled a dropdown box arrow that reveals a four choices. These are the errors on one of my servers. The other server looks identical. These two servers have been up a combined total of 63 days. I think you have an Intel NIC so I don't know quite what new one do differently but might as well try it when you get it. (I had a streaming problem about seven years that was traced to a RealTek driver issue...) You might also trying streaming directly to a PC and see if that has a issue. Do you have problems with BluRay material? BluRay requires a max of 54Mb/s while UltraHD BluRay requires 54 to 128Mb/s. I am no WiFi expert. (I avoid it with a passion whenever possible!) But I do know that the max speeds quoted are seldom achieved in the 'real' world. Th 2.4GHz band is shared with microwave ovens, wireless phones and countless other 'man toys'. (And I didn't even mention every Cable company modem/router installation in your neighborhood! Last time I looked using my Ubiquiti AP could see eight of these on my WiFi setup.) OH, and do you have a printer on WiFi? The 5GHz band signal is attenuated by anything thicker than a Kleenex and signal strength determines the max data rate.

Maybe I am missing something here. Why don't you just make a backup of the current flash drive to use to make the new flash drive. (I assume it is still working as you didn't say it wasn't...) Open Main tab. Under Boot Device Click on Flash Then do this:

This type of problems are difficult to troubleshoot. Here are a few thing to look at--- First thing is that the Samba was update (again) with Unraid 6.11.5. Not sure what was addressed in that upgrade. (This is still not the latest version as Samba addressed some CVE issues in late December...) You are not using Wifi in any manner in the networking between the Neo and server??? Something to try is the 'Safe' boot mode. See what effect that has on the problem. Does the Neo support NFS? If it does, try using that protocol and see if that changes things. Check the physical connection scheme you have on your LAN. Try to make sure that you have the Neo and the Unraid server on the same switch. (You might have to move the Neo and connect it to a computer type monitor to do this test.) (These are all random thoughts/suggestions and not a 1-2-3 list of items to be tried in order!)

I would suspect that a reboot will be required for this change to take place. I believe you can (still) type reboot on the command prompt to reboot the server. I believe if you click on the 'Advanced' button at this warning, your browser will take you to the GUI. (At least, it will in Firefox.)

Personally, with a fifteen minute interval, I would set the syslog server to mirror the syslog to the Flash/boot) drive. The reason for this is that you can very quickly get to the syslog. Just pull the boot drive from the server and plug it into any type of PC. (You might want to shut the server down but it is probably going to start a parity check on the restart anyway.)

There is a make_bootable_linux file in the root of my flash drive so I assume you can use that file to make the flash drive bootable. Here is a link to the instructions for creating a boot drive: https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method

The system is in the bootup process and it should be no problem created by shutting it down. Try a quick push of the power switch to shut down. (If it does not turn off in two minutes, push that power button again for about ten seconds to force a powerdown.) Then move the server to the location of the monitor.

Was it here that you pressed the update button? The reason for the question is that it is necessary to know if you were updating the flash drive with the files for the new versions or rebooting the server to install the new version of Unraid on the server from that updated flash drive.

Well said! Any RAID solution with parity is not in itself a backup of irreplaceable data if the RAID server contains the only copy of that data. There needs to be an second copy of that data on some other physical storage media to be a backup! (If the data is replaceable from another source, then that source is (by definition) a backup.)

What happens if the server is a victim of a lightening strike? What happens if the server is stolen? What happens is your house/business catches fire and is a total loss? What happens if the server is 'drowned' due a flood or pipe breakage? There are a lot ways to end up with a catastrophic loss of data that no parity system can prevent!!!

Do you need ipv6? (In the back of my mind, I seem to recall a problem with enabling it when it is not available.) In the ''Network settings' section of 'Settings', you will find this:

Post up your diagnostics file. Then make sure that the array is stopped. Then look to see what drives are available to be assigned... Are the drives even being detected? Are the number of drives detected equal to the number of drives installed? Do you have a printout of the old drive assignments? (If you have notifications setup, be sure you look at the sent messages on your notification option(s).)

What are all of those reads on disk1 about???

What the problem with that approach is that both Windows and Samba have implemented changes that effect the way things "used to work"! Particularly with regard to SMBv1, which provides functionality that many folks running simple SMB configuration relied on. (SMBv1 has/had some really nasty security issues that were fixed by banning (or 'eliminating') it. MS is doing its damness to to enforce that policy..)

It has been found that SMB is much more stable if a single computer is the SMB Local Master (The Local Master runs a sort of DNS service for the SMB network.) The best choice for a Local Master is your Unraid server. It works best if you leave the server running 24-7. You make the setting by going to : Settings >>> SMB and look for this section: BTW, the delay you experienced is not unusual, with a large SMB network, it can take up to 40 minutes for changes to propagate through the network. Another thing for you to try is download the PDF file in the first post in this thread: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/ And follow the instructions for "Step 1– Fixing the Windows Explorer Issue" by setting up a 'Network Neighborhood'.

The diagnostics say that eth0 does exist. The syslog says that it does. Your server has an IP address of 192.168.1.203 Exactly what problem are you having? Where did you see the error message? Can you get a screen capture/shot of that message? What is the significance of the two Diagnostics files that you uploaded? What happened in the one minute between that we are looking for? You do have this message in the syslog: Dec 17 18:09:57 Tower login: pam_unix(login:auth): user [root] has blank password; authenticated without it Have you established a password for the root user? (If case you don't know, 'root' is the administrator for your server and I imagine in this case it is you.) I seem to recall that Unraid is getting bit more insistent that the server have a password for 'root' and may not behave properly until you establish one. See here: https://wiki.unraid.net/Articles/Getting_Started#Setting_a_Root_Password

In the /config folder of either flash drive (the new one that you purchased and the old one that your friend purchased), you will find a file named Pro.key. That file is 'bonded' to GUID of the flash drive on which it is installed. (It is critical at this juncture to realize that fact!. Each Pro.key file is unique, tied to and will only active the license for a single flash drive!) Begin by making backup of the contents of BOTH flash Drives. Make sure you name them distinctly so there is no confusion as to which is which. (A safety factor in case something goes wrong. ) Delete everything on the new flash drive. (Remember that you made a backup... right) Then copy everything from the old friend's flash drive onto the new flash drive that you just purchased the key for. Go to that backup of the new drive that you purchased the key for) look in the /config folder for the Pro.key file. copy that file to the /config folder on the new flash drive. (You will be overwriting the current file that is on that drive. Plug the new drive into the server and it should boot and be running with all of your old settings. (If it does not boot, shut the power off, and plug the drive back in your PC. Now run the make_bootable.bat file in the root of the flash drive as Administrator.)

Does the server MB have built-in WiFi capability? If it does turn it off in the BIOS.

Look for a USB flash drive from a name-brand manufacturer that actually manufactures its own memory chips. Purchase the drive from a trusted source. (Make that you are actually buying that trusted source as places like Amazon rent out 'store space' on their site. Apparently, there are a fair number of counterfeit USB drives in the marketplace!) Get a physically large one as possible for maximum heat dissipation. Remember that its size should be 32GB or smaller. (There are ways to use larger drives but they are really hacks.) There no need for the speed of a USB3 flash drive as Unraid only loads about 1GB of data at boot time and then basically ignores the flash drive unless there are software or user configuration updates, and USB2 drives tend to run cooler. (Plus, with some MBs, there are problems with the boot drive being 'lost' when plugged into USB3 ports.)

Read the first post in this thread: https://forums.unraid.net/topic/50397-turbo-write/

I am totally confused at this point. /mnt/storage-server-01 is actually in RAM IF it is on the Unraid server! Please use the GUI terminal and capture the screen shot of the output of the following command: ls -al /mnt It should something like this: Also post up the diagnostics file of your server. I am also going to ping @dlandon to see if he has some insights into what might be happening.

If you are writing directly to the array, you are right-- a 1Gb/s connection is adequate. However the read speed can be (and often is) much faster than that depending on the read speed of the drive itself. (Remember we will have file access time on the server and file creation overhead on the client to consider in the read case.) Remember that Unraid's initial philosophy was that it was to be a storage system intended for applications where the primary use was write-once and read-many! Write speed was not a primary consideration in either its concept or design. What most of us have done to use fast writing SSD cache drives for transferring files to the array after the initial data loading. (You could also use M.2 SSDs for even more speed!) Then the files are moved off of the cache_drive/cache_array by 'mover' when the server is idle. These can accept data much faster than a 1Gb/s Ethernet connection. BTW, if you are writing a large number of small files (say, <1MB), file creation overhead on Unraid will definitely impact the transfer speed.

I would have thought this would do that. Are you actually using SMB to write the data to the Unraid array or you using NFS or a Docker? Both of these latter two will completely ignore the settings in the SMB configuration files. Here is the Link to the parameters for the smb.conf (and by extension to smb-extra.conf or any other 'include' files): https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html It contains information from the true Gurus on the subject of Samba which is the version of SMB used by Unraid...

This may help you with some of your questions:

I have it installed on my servers BUT I only allow to cache my media share which is about 3000-4000 items. If I try to do more shares involving tens of thousands of shares, there is a problem. The RAM allocated for the cache can be needed for other purposes and cached directory information will get reallocated. The disks get spun up to refill the cache-- either when the entries are required or when the RAM becomes available again. It works best when you only cache small number of items for this reason. You can try it to see if it helps. If you do, only cache those shares that you frequently access. You will have to play with the settings to get things to work smoothly with a minimum of disk spin-ups to refresh the cache. I do believe that support for this plugin is minimal as it has been more than two years since it was last updated. Yes, and I already provided you with that information-- See Number 4 above in my last post. Example-- my movie files are under a sub directory called Movies under the Media share and there are sub-directories for the beginning letter of the movie's name--- 0-9, A, B, C, D, etc. This helps to minimize the number of disk being spun up as you don't have spin up all the disks when getting a listings for movies that begin with (say) "A". The scheme also prevents a secondary problem. If you have a flat file system where you have all your movies in a single share directory (In my example-- the 3000-4000 movie items), the server has to send all of that file information over the network to the PC which then has to sort the information in the format that you want to view. This time can be substantial especially if you have to spin up a large number of disks on the server. BTW, if you are using the 'High-water' algorithm to allocate files to the disk and large capacity data disks (say, >3TB) then when you write a large number of files are a single time (Like a back of your Windows data), then everything will most likely end up on a single disk. In fact, using the High-water' allocation scheme, you could end up writing everything to a single disk for a month or two. (Using the 'Most-free' allocation will result in the most chaotic distribution of files against all the disks!) In fact, I had a problem getting more than two disks of a possible four spun at once while browsing a share!