Frank1940

Got to the SHARES tab (#1). Click on the share name in that tab (#2) and that will take to this screen: Then set #3 to a value large than the largest file you will be copying to that share. Here is the 'Help' for that setting:

Yes, I do. When we get down to these type of problems, we are reduced to witchcraft when attempting to fix them. 👽 (Fifteen years ago, I often said that solving SMB/Samba issues was more witch than science. While today, that is not quite accurate, there are still instances where things are wrong buried down deep in some obscure setting where one would never think to look. That is way Small Businesses pay an qualified expert in Active Directory big dollars money each month to provide them support. )

If you have Windows 10 Pro license you should be able to upgrade to Windows 11 Pro...

One more thing. Don't use your Windows login name as a login name for Unraid. Any special permission setup for that user might carry forward and be applied to the Server. It is always a good idea to reboot the Window's Client anytime time you make a change. I don't even have a Windows Home computer. There are just too many nice features that it is missing. Proper Networking tools being one of them. When purchasing a computer, you can often find a PRO machine for just a bit extra. The difference in cost between a Home and Pro license is minimal for an OEM builder!

I have very mixed emotions about Google AI 'help'. Sometimes it is right and sometimes it is wrong. I suspect that deleting the present Windows Credentials and setting up new ones is required. (Remember to create a new credential Share Access user on the Unraid side.) This might fix the issue depending on how the extra will applied on the Windows side. If they were applied to the user or to the class/group that the user belonged to. If you have mapped a Unraid Share to a drive letter, I might suggest deleting that mapping and setting up a new mapping and don't touch the settings on the Windows side.

https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/#findComment-1058963 It is a problem which crops up from time to time. I have always suspected that it is cause because someone has attempted to control security by using Windows permissions (under the Security Tab on the Properties for the folder/file). The New Permissions utility is suppose to fix but it does not prevent it from happening in the future. I understand that the extended attributes was added for the folks who use Samba in an Active Directory environment. I will be honest at this point. I am not any type of an expert on setting Security in the Windows Environment. I open up that Window's Security tab and dread the thought that I might have to make a change! ☠️ I have put together a thread about peer-to-peer Networking and it is found here: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows The first few posts are background information. The real substance starts with this post: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561580 and continues for the next several posts.

Use this command: ls -al /mnt/user/Torrents/path-to-directory-with-problem Grab two screenshots. First of the command line itself and the next three lines. like this: Second of a file with access problems. This is all, we need to see this much of it:

What Edition and Version of Windows 11 are you running? (Windows 11 Pro 25H2 would be a typical answer. Settings >>> Systems >>> About will get to the spot on your Windows computer where you can find this info. ) Are you using Windows Credential Manager to access your Unraid Server? Why are you using Unraid's 'Secure' security setting rather than 'Private'? (Default Windows 11 Installs normally prevent connecting to a server using 'Guest' credentials but many people have turned off this setting.) Since the issue appears to be related to the Share where you store your Plex data, how familiar and comfortable are you with the Linux command line? (Don't worry, I am not going to have you run a command that would make any change to any Unraid disk. Anything that I suggest will only be to look at the file parameters!)

Because that error is not at the disk level. It is at the data level controlled by the FS driver. When you do a dd level write, you are at the disk level. (If you had introduced the 'error' via btrfs driver which is at the data level, it would have updated the checksum.) Remember that disk algorithms and the btrfs schemes are both working when you are accessing your data. And neither one are aware of what the other is doing.)

Still any time you write to a sector, you are still using the normal disk writing algorithm which will update the error correcting check sums for that entire block of data for that sector. You can't get around using it with anything that sends data via the SATA data cable. Remember the disk does not know what is being written to it expect that it is ones-and-zeros to a certain physical location on the disk. It is up to the OS and file system structure superimposed on the disk that allows the OS to interpret what those ones-and-zeros represent. The disk only reads that entire block of data and hands it over to the OS to 'figure out' what it needs from that block. A file with the famous words "Hello World" as its only data would be eleven bytes of block of (say) 1024 bytes. Bitrot has always assumed that the change happens in the actual magnetic storage media. Something changes the magnetic structure on the disk in such a way that the read data passes the error_detecting/error_correction algorithms but is not the data that was originally written to the file. Like a very high energy cosmic-ray effect... (My assumption is that when if there is a bitrot like situation, the error occurred in non-ECC RAM by some high high energy effect. Then the erroneous data is written to the magnetic media using the normal disk writing algorithm such generates the correct check sums for that data.) I understand that all of these writing/correcting software schemes are proprietary so no one has independently verified that they are mathematically flawness so there is that possibility.)

BUT using dd to write an error into the file is not bitrot because dd writes those bytes using the normal disk writing algorithm which will update the error correcting check sums.

You should get triple bonus points if you can do this. Remember, that you are only allowed to change a single bit in the file and still have the Unraid OS must be able to read the file without error. (All the disk manufacturer's have proprietary error detecting and correcting schemes to prevent this from succeeding. We have come a long, long way from the 1980's CRC detection methods and even the way that data is 'encrypted' before writing to minimize magnetic pole changes to make the comparsion between then and now. I remember that my first hard disk had a capacity of 10MB-- 10,000,000 BYTES --and cost over $400!!! The floppy disk drive only had a capacity of 360K bytes. My wife turning on the sweeper during a data write could result in a corrupted file! A flicker in the room lighting always seem to result in a corrupted floppy disk. I remember most of us turning off MS first attempt to implement the caching of data writing to disks. Its purpose was to prevent the compete stoppage of screen updating during the seconds required to do a disk write operation. There was no cache RAM on a disk drive in those days!)

Don't try and force an error! I am of the opinion that errors in files are the results of glitches during the write operation to the disk or undetected bit changes in RAM which are then written to the physical disk. In my scenario, any corruption in the magnetic data will be detected in the read operation of the physical disk. The error correction routines of the disk may fix them (Correctable read errors happen all the time and the user is completely unaware of them...) or the disk reports a read error. I am looking for the first instance where btrfs or zfs actually found an problem. And what was the outcome of the problem? A real world problem and its outcome, if you will. I have some suspicion that this FS's provide a solution to a problem is virtually non-existent.

Have you ever found an error situation and tried to fix the file. Were you successful?

I believe that XFS has the lowest overhead with regard to disk space required by the file system. ( All modern FS has provision for file recovery/data_integrity_checking built into them. The greater their capability to provide that service that more overhead they required!)

Use the built-in File Manager and look at the cache. See what files remain there. Then go to the Shares tab and use the file manager again to see what the location is for the files that you found while looking at the cache. If that is showing two locations, that is the problem.

Windows SMB has a lot of 'gotchas'. One is that it allows only one connection to each server. (It is not too smart as the IP-address and network name is a way around this restriction.) Furthermore, it will try to connect to a server using a number of different login methods starting with Windows Credentials. (IIRC, it then tries your Windows login credentials.) Unraid permits 'Guest' connections so if all else fails, you can end up logged as guest. (Windows-- by default-- does not allow guest connections but this can be overridden.) That is why I recommend that you always setup Windows credentials on all Windows clients to connect to a defined Share Access user on your Unraid server. You might only need one Unraid Share Access user if all of your client computers have a same access privileges to each Unraid share-- more later on this! As @itimpi said, you can access your Unraid server using either the network name or the IP address of the server. (Windows use to have a lot of problems discovering servers on the LAN but that issue seems to be largely solved these days so the need to use IP addresses is considerably reduced!) Be aware that the discovery process can take some time after the client comes up... I f you want more information on how things work, go to this post: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561580 You might want to read the entire thread for more background information and instructions to set up your Windows computer and Unraid server to work with the current default windows SMB settings. By the way, if you follow this guide, you can set all of your shares to Private and set the permissions to Read/Write and every Windows client computer will behave like the shares are public and everyone is logging as 'Guest'. The only difference is that any intruder on your LAN will not have access to your files!

It should change to 'Protected' as soon as Mover finishes running. Mover can be setup to run on a schedule (I have mine set to run daily at 0340 which is the middle of the night for me.). Settings >>> User Preferences >>> Scheduler >>> Mover Settings One caution. Mover will not overwrite a file!

Set up the Syslog server. https://docs.unraid.net/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs/#persistent-logs-syslog-server In your situation, I would use the Boot disk for storage. Also include your diagnostics file when you post up the syslog after the next crash.

Limited resources prevent instantaneous updates. (Limetech does do QA on all updates before they are released as a general release. Note that this a release candidate– that is what the rc means –so they are waiting to see if there are any problems are found by the early adopters before that general release.)

This is not correct. The permissions have to be -rw-rw-rw for files and rwxrwxrwx for directories for SMB to work. For the reason, se this post: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561580 For info on how to set this up in a Container, see here: https://forums.unraid.net/topic/71764-support-binhex-krusader/page/38/#findComment-1486740 and, here: https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

I would suggest going to this Webpage: https://unraid.net/support And go here: When you contact them, give details about your purchase and and the Active GUID that is showing up on Main >>>> Boot Device Then click on Boot(Flash) to get the page with the GUID.

You have asked a question to which there is no 'right' answer! Many of us run a parity check once a month. It is always our hoped-for- goal to find no errors. Once you have an error(s), you have a potential for a data loss. And you should address the problem at once. You also want to find problems before a second problem occurs. (Once, you have two source of errors on an array, the likelihood of a data loss just jumped astronomically.) Here is link to an old thread that has a look at the problem from a statistical viewpoint. You can read the comments of forum members at that time. Most of the still apply! https://forums.unraid.net/topic/50504-dual-or-single-parity-its-your-choice/ About the long time to run the parity check. Have a look at Parity Check Tuning plugin. It allows to break these long running operations up into chunks that can be run during more convenient hours. Remember that this test is intended to catch problems at their beginning before they become major headaches. PS---- I know that the annual failure rates that I used in the Tables is much higher than we see today! (Thanks for some blessings!!!) But there were a few drives back then that did have annual failure rates of 10%. Today, a drive that has annual failure rate of 2% is the outlier.

Just be thankful that you have a solution to make your old printer/scanner to still work. (A while back there was another user with the similar problem. As I recall, he also found a work-arround.) SMBv1 is all but gone as it has security issues especially for home users. Most people have long abandoned it so getting help to fix issues is now a problem.

Upgraded both servers and no problems. Well, one very minor one, I had to reboot a Windows client after I try to access a server too quickly after it came back online and something went wrong in the login client-server handshaking.