Frank1940

Were you copying a single file--- not a batch copy? Was this only disk-type operation occurring at the time? I just did a Windows to Unraid copy of a single 6GB file to a 'cold' server (Using 'Write Reconstruct' mode) and here are the results: The dip that you see is the array being spun-up! Everything prior to that point is being cached in RAM. The reminder of the copy proceeded at ~ 112MB/s. (Rose is my backup server and you can see the specs in my signature.) The copy was made from a Windows 11 PRO (24H2) client using Windows File Explorer. And what is this entry in your diagnostics file? My reason for asking is that I have never recall seeing it before in a Diagnostics file. You are running Unraid on bare metal???

OH. One more thing. After you make any changes to the SMB settings on the Win11 client, you should reboot that machines so that they are actually being applied! (Stopping and starting the array on Unraid should do the same thing...)

OK... Let's try this. SETTINGS >>> SMB then EDIT: You should not be using SMBv1 unless your hardware has not had a firmware/software update since about 2010!

Check this out: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561581

The parity re-sync will definitely slow things down as you have two disk intensive operations happening at once! The initial speed of 100MB/s is the filling of the unused RAM being used as a cache for the write operation. The transfer will slow down to what the physical disk can handle after that RAM is filled up with data.

I, personally, would not try this. It may confuse the hell out of your router and which may then attempt to send data to the wrong NIC. (Routers don't forget NICs, their MAC addresses and the associated IP address just because they are not active at this very instant!)

I assume that you are asking about SMB/Windows issues. If so, Have a look at this thread: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/ IT is a long thread filled with a lot of information and the important stuff about getting SMB and Windows to work together begins with this post and the following four posts: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561581

Have you cleaned out the case? Best way to to use compressed air (cans or hand held blower). Make sure you do it some place where the resulting dust and dirt storm does upset your wife! Make sure that the fans are not having their speed controlled by some other temperature measurement. Make sure that your fan setup is pulling all the cooling air in from the front of the drive housing(s) and exiting from the back of the case. (No fan behind the drive housing should ever be blowing air in the server case. All fans must be setup to blow air out! Close off any opening in the back portion of the server case that will allow air to leak in without going across the drives. Remember that electronics have far higher temperature specs than the HDs. You may have to opt for noisier case fans (not the ones on the drive housing(s) after that horror story to change out the originals!) and position the server where you can have some sound isolation around it.

I don't have any experience with this type of problem. I will ping @JorgeB who has helped out other folks who have found them selves in a similiar situation. You have a few days before you really need an answer anyway...

Are you saying there are 16 SATA power connectors on one power cable plugged into the PS--- Or are you using either SATA-to-SATA powers splitters or MOLEX-to-SATA power splitters off of the main cable plugged into the PS? (I believe that most 'experts' would recommend that there be only two plugs on the SATA-to-SATA type and four plugs on the MOLEX-to-SATA type...) IF you google for purchase peripheral cables for seasonic prime titanium 650w power supply you can find places that sell the peripheral cables for Seasonic PSU. EDIT: Also look at this video about SATA cables issues: https://www.youtube.com/watch?v=TataDaUNEFc

I would also check that these disks are not on the same power cable-- particularly if that cable is a 'splitter' type cable.

What were the two data disks initially disabled? How long did this rebuilt take? I would suggest that you open up the server and make sure that all of the SATA connectors (both power and data) are securely seated. Then double check them again. (SATA connectors are easy to displace so be gentle and careful on that second check.) The SMART attributes on the disk (disk 5) currently disabled look good. That is the reason I suggested checking the connectors.

If you have an M.2 slot, have a look at these: https://www.amazon.com/Adapter-RIITOP-Expansion-Chipset-ASM1166/dp/B0D8BCWHPT?th=1 (I am not recommending this card. It was the first that popped on the search when I query on Amazon...)

Don't try holding your breath until this issue is resolved. As detailed in the post below, it also exists for Windows client/servers in a Windows peer-to-peer network for several years. I feel that MS will have to a player in resolving this...) https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561585

Here is a post from another Unraid user with this problems and his solution: https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/?tab=comments#comment-1059803 Be aware that this will fix the condition for now but be forewarned that the problem may return. Something (client, VM or Docker container) set up the ACL and it may do it again.

Yes, Pick disk and use the Dropdown list as shown below:

Make sure that you notice this switch for the ls command: It might show more of what is happening... EDIT: Should have check first before posting. The '-e' switch is not implemented in Unraid's Linux disto!

Have a look here: https://www.linuxquestions.org/questions/linux-newbie-8/what-is-in-drwxrwxrwx-915243/ and https://en.wikipedia.org/wiki/Access-control_list and https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/?tab=comments#comment-1059803 The real problem is often figuring out what set up these additional controls in the first place. (With User Shares, the New Permissions tool will usually fix the problem. I am not sure if it will for Disk Shares...)

When you do the above this entry will be generated by Unraid in the /etc/samba/smb-shares.conf file:

What is the problem with setting things up this way-- Right from the GUI? >>>>> Then >>>>>> Repeat for each disk. Remember that disk shares are not turned on by default because disk operations between Disk Shares and User Shares can result in data loss!!!! EDIT: You might as well make the disk share private if you require a login and you are the only user.

Not an macOS user is a necessary disclosure on my part! (I am only responding because no macOS user has had done so...) One thing to realize is that Unraid has some issues when writing large number of small files to User Shares-- True for any file writes regardless of OS. So beware of that issue. Unless you are using 'reconstruct write' setting in Disk Settings, write speed will be appropriately half of read speed when writing directly to the array. (That is the reason that a cache drive was initially added to Unraid in the early days of its development!) Be sure that you have looked at the pinned post in this section of the Forum about setting up both Unraid and your mac client.. Here is the link to that thread: https://forums.unraid.net/topic/146818-optimal-samba-settings-to-get-better-macos-to-unraid-performance/

Look here for the statistical view: https://forums.unraid.net/topic/50504-dual-or-single-parity-its-your-choice/ Note that the 2% failure-rate file is probably more typical of what most Unraid users are seeing today. (I have a WD 3TB drive that the hour-on counter (Attrib # 9) has 'rolled over' and now shows 2 years and 2 months! I would guess it has been in use for, at least, ten years now.) EDIT BackBlaze data for a recent quarter: https://www.backblaze.com/blog/backblaze-drive-stats-for-q2-2025/

My take is that the more drives in a system equals more things to fail. I make if a point to never add a drive to the array just because I physically have it. There has to be a truly valid reason to add it! Adding a second 22TB parity is a matter of your 'comfort' factor in accepting risk. If you will sleep better at night knowing you have it installed, then do it. If you think sky-diving is the best way to get a 'high', then you can probably avoid doing it. (When you have eight to ten data disks in your array, a second parity drive becomes more statistically justifiable from a reliability standpoint.) Look for that BF Deal. That's what I tend to do. (I have two 12TB drives pre-cleared on my shelf waiting for a failure or to be required to provide additional storage space. I am in no big hurry to install them! If you look at my forum signature, you will find that I have dual parity on one server and single parity on the other one. I am willing to accept the risk on that one server...)

I would do the pre-clear but not add it to the array until I needed the space. (Perhaps, you need it now but that info not apparent...) That way if one of your other data disks should fail, you could use it as a immediate replacement. Save to get another 22TB drive for that time when the 10TB will be used.

If you are using a recent version of Unraid, the Dynamix File Manager is now built-in. I understand that it has built-in checks to make sure you can't do this type of file operation. Here is a link to the support thread: https://forums.unraid.net/topic/120982-dynamix-file-manager/ (You will find a link to the manual in the first post...)