Frank1940

Do you have any ideas of what is happening then? If you are not having a problem, I suspect that the OP must have an issue with some file parameter-- like a forbidden character in the file name. But I don't know a way to find it. I looked at the 'File Modified' date and May 3, 2008 showed up but there did not seem to be a complete correlation that as the times on the two lists didn't have a pattern. @wishie, consider copying off all the files onto a Flash drive or a external HD (probably faster) using NFS and see if you have any problems with either the copy operation or file listing after that. If you find nothing there then make a new share--- or a new directory in Music (like, BackMP3) ---and copy them back using SMB.

Now one more thing--- under SHARES, export disk 2 as a Disk Share. Then look and what you see find there. (I really don't care at this point as it should be a part of what I am suggesting you to do. I believe that 'User Shares' are handled differently than 'Disk Shares' on the Unraid side...) I think you need to create a 'Bug' report. (There aren't many people with 6000 items in a single share so you have may uncovered a long latent one!) You can do this in this Sub-forum: https://forums.unraid.net/bug-reports/stable-releases/ Include the results of all the things you have tried and looked at in a coherent manner. Reference this thread if you need to.

OK. Now make sure that you have installed the "Dynamix File Manager" plugin on your Unraid server. Then go to 'SHARES'. You see see this Icon on the left side. Click on the one for your 'Music' share. Look for the 'MP3s' and then look for the disks that contain files for this share. Write them down. Then click on the 'MP3s' folder/directory and see how many files are listed. If you have only 59, then look to see what disk they are on. Otherwise, try and find one of those 59 files in that list and check to see what the disk number is. Now do some exploring with the 'ls' command in the GUI terminal and Dynamix File Manager on the Disk Shares. The ls command would looks like this: ls -alh /mnt/diskX/ (replace the "X" with the number of the disk.) Then just add on the Share--- Music ---name. Look at those shares. Then add on the directory--- MP3s ---and look at those files. What I am suspecting is that you may find those 59 files are on one disk...

When you run the following command on the Unraid GUI terminal ls -lah /mnt/user/Music/MP3s | more you can verify the 6000 files and all the permissions are correct and 'group' is "users". (You do not have to look at all 6000 but two or three hundred should be enough.) -----> It will take a <Control-C> and then an <Enter> to exit from 'more'. <---- My experience suggests that the owner is not that important if the client is logged in as a valid 'Share Access' user and the permissions on the directories is 777 and files is 666.

Use the Windows Credential manager to setup a credential for your client computer to a valid Unraid 'Share Access' user on your Unraid sever and you should avoid this problem entirely. (Windows allows one-and-only-one login from the client to a server. If you establish a Guest connection to any user server, any attempt to log on with a valid user name and password to that server will always fail!)

I don't believe that anyone thinks that you don't have a problem. It is just that no one has seen anything that you (and we) have looked at so far that might be the cause of what you are experiencing. I must admit that I have no experience in the MacOS arena. Have you had a look at that SMB share using a Windows computer? There is also a sub-forum on this Forum where MacOS problems are discussed. (Apple SMB does not seem to behave like other versions of SMB from Samba Org and MS...) There is also a single thread started by LimeTech on MacOS SMB solutions. You can find them here: https://forums.unraid.net/forum/103-macossmb/ and https://forums.unraid.net/bug-reports/prereleases/macos-optimization-r2087/ I also seem to recall that there may be an issue with MacOS, SMB, and directories with large numbers of files in them...

And let us see the result of: ls -al /mnt/user/Music/MP3 Have you run the TOOLS >>> "New Permissions" on just the Music share?

You really need to provide complete details about what your specific issues are. (What you have told us so far is similiar to saying, "I have a problem with my car and I want it fixed!" Without details, we don't know if the engine won't start or if the radio doesn't work or if the left rear window won't go down...)

Does the server boot up to the GUI in the Safe Mode? (it is an option in the Unraid boot menu--- that you can see on an attached monitor ---during the boot phase.) If it dows, got Settings >>> VM Manager and set the 'Enable VMs' option to "No".

Try starting the server in the Safe Mode. If it starts, disable that VM from starting. Then try a reboot to see if Unraid will now load...

Reboot in safe mode. Then set up the Syslog Server to log things to the flash (boot) drive, and start it running. Push the start array button. Wait at least ten minutes before you push the power switch. Then pull the flash drive and get the syslog file (Use dates and time on the files if necessary) off the drive and upload it to a new post.

And what happens after that? Is the GUI still responsive? How are you shutting down the server--- GUI, quick push of power switch, or long push of Power switch? By "getting the same results.", you mean that the array is not starting???

Try starting in the 'Safe Mode'. (A boot option on the Unraid boot-up screen on the monitor.)

What is the size of the files that are being transferred. (There is file overhead related to generating the file creation/location and finding the physical space where the storage/retrieval ---on both the Windows and Unraid sides that can slow down transfer speed. No files are transfer on either side when these processes are completed.)

The same physical disks are used to store both Disk Shares and User Shares. There is a just a layer of software that assembles into a 'collection' (called a User Share) of the resources for all the contents of the directories in the root directory of each data disk (i.e, Disk Share if you like ) having the name of the User Share. When you change the permissions of using either the Disk Share or the User Share, you will make that change on those underlying physical disk(s). (That is one of the reasons why Disk Shares are normally not exported in the GUI as most folks do not understand what problems can occur when one uses both Disk Shares and User Shares in file operations!)

Use Dual Parity to provide some additional insurance against non-availability due to disk failures. But remember that nothing can protect against unexpected downtime as much as a vigilant System Administrator, frequent parity checks and prompt action if problems occur.

Thanks @ConnerVT! That is a most important point. Any data that is truly irreplaceable (and valuable to you) should be duplicated and stored off-site. There are many, many more ways to use data than the failure of a hard drive-- fire, theft, storms, vandalism, floods, lightning, etc. Read this forum thread from a few years ago: https://forums.unraid.net/topic/50504-dual-or-single-parity-its-your-choice/ Be careful with statistics. They predict what will happen in large populations. If you are concerned about a single event occurring, they are useless. (If you are the only person the USA be hit and killed by a meteor in 2024, you will still be dead. Devil hang the probability of that happening to you!) @jhyler, what we don't at this point is what the infant mortality is for these drives. (The manufacturers consider this to be proprietary information.) Is it 1 in 2000 or 1 in 1,000,000? As a matter of fact, it does not matter! You got a defective drive. Period. Were you simply unlucky and got the 1 in 1,000,00 drive or a drive from a production lot with a failure rate of 1 in 1000? We simply don't know... All you can do, is to read the user reviews at the one-star reviews on vendor websites and make a judgment based on what it happening there. In recent years, I have purchased HD's only from vendors who have a 30-day no-questions-asked refund policy.

I am confused by what you are trying to do. This confusing may be totally my fault...). But never the less, please provide complete paths to files and directories from the root of (the Linux file system. Example: /mnt/user/BackupMedia/All\ Movies/ ) Next thing, if the shares were generated by Unraid rather then 'you', have you turn on the export of the share using SMB? (the default is 'No'!) See below:

This not a definitive answer to your question! It is only my opinion... A quote from you in another thread: A possibility: There is a design flaw or a defective manufacturing process in this model of hard drive that is causing an excessive number of early drive failures. (Remember, Preclear was not initially designed to force failures in drives but rather to find drives that were presumably defective when first received. The detection of infant morality in the drives was a side benefit. Infant Mortality failures--- by definition ---are assumed to occur in the first few hours of operation. A random disk with the issue could fail at 5 hours or 150 hours. Several years ago, it was recommended that a new disk be subjected to three preclear cycles. I doesn't know if this was to put more hours on the disk to get through the Infant Mortality period or if it was found that there were disks that failed a basic read-write operation on subsequent cycles--- probably a combination of the two.) This would not be the first time that this has happened. In fact, Seagate was sued over the high failure rates on its ST3000DM001 drives back in 2016. You can read about that here: https://www.extremetech.com/extreme/222267-seagate-faces-lawsuit-over-3tb-hard-drive-failure-rates The drive in question was introduced about four years prior to the date of this article. I actually used several of these drives at the time in my servers and I did have a couple fail. But the 'survivors' run for another ten years. I just pulled the last one about a month ago. It was not because it failed but I needed more storage space. (I don't know the actual running hours of that last drive because the SMART "Power on hours" counter had rolled over!) When one buys on the leading edge of technology, there is always a higher risk that you could encounter unexpected issues that were not fully appreciated at the time when they are first introduced. (Remember that NASA used ~10 year technology when selecting CPU's for its deep space craft for years to avoid problems many years after launch!) It may be several years until the reliability of your 22TB model is finally determined. (I am not singling out Seagate. There have been other HD models from other companies that don't have good quality marks. The ST3000DM001 was just a standout because its modest cost and other features made it very attractive to all types of users and, thus, it had a very high and long production run.)

Run this command in the GUI terminal: ls -al /mnt Capture a screenshot of the output. (All of the directories present should be default directories that Unraid sets up for all installs.)

Have look at the Parent directory and any child directories involved. (Sometimes, the problem is not with the permissions of the current directory but with the parent directory and perhaps with permissions on the child directories.)

One thing I did not explain is that these permissions are setup (using the Windows Security settings) on the Windows computer where the resource is stored. (In the peer-to-peer file sharing mode, any Windows computer can be a server, a client, or both a client and server.) I am not a Windows SMB Guru. (That takes considerable formal training to even get started and years of actual experience to become a Guru.) Windows file sharing is divided into two separate areas--- peer-to-peer and AD. Peer- to-peer is used by home users and some very small businesses. AD is used by the Business and Corporate world. Guess which one is treated by MS as the ugly step-child...

With Unraid if you go to Shares, then click on the 'User Share' that you want to set up permissions on, you will find these sections/ tabs on that GUI page: (I have turned the 'Help' so you can see that basically, you can set up permissions for each 'Share Access' user. (Windows does provide a lot more options but Unraid's choices will suffice for most folks.)

You are trying to set permissions using Windows security on a Linux file system. If you are not running AD (Active Directory), this is probably a mistake. You can basically set the permissions required using the 'Public', Secure' or 'Private' settings on the Unraid GUI. (In fact,, it seems that it is possible to screw thing up on the Unraid side by doing this...) There is a section on this forum for Active Directory: https://forums.unraid.net/forum/102-active-directory/ You might want to ask your question there. There is a set of instructions (PDF) for how to set things up for Windows-Unraid security. You can find it here: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/ IF you find that you have the problem described here: https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/#comment-1058963 You can restore things by running the 'New Permissions' Tool in the Tools menu of the GUI on the affected share(s). I really try to avoid using Windows security settings as I find them very confusing. (I do setup some Windows Peer-to-Peer file sharing to totally trusted users so I have a few restrictions on those shared Windows-to-Windows shares.)

Your Unraid server has an IP address of 10.55.73.190 and you logged into the server from a computer with an IP address of 10.55.73.104 What is the IP address of the Win11 client that you can't connect to SMB? (I seem to recall that if the Unraid server and client computer are not on the same subnet, there can be connection problems. If your troublesome client does not have the identical first three sets of numbers--- 10.55.73 ---as these two IP addresses, you may have problems...) Can you log into the GUI from this WIN11 client?