Frank1940

HERE: There is a help for each setting which can be toggled by clicking on the description: Make sure that "Minimum free Space" (top figure) is set to be a bit larger than the largest size file that will ever be written to the share.

In addition to what @itimpi saw, when I looked at the tower-diagnostics-20251123-2347\system\testparm.txt file which is the output of a Samba diagnostics tool, I saw that the "permission" share was not in the list of shares that Samba was servicing. You need to open up that share under SHARES on the GUI and on its settings page, set it for access by whatever sharing protocols you need. (I believe the default permissions for any new share is for no access--- period!)

First, please post up the diagnostics file in a NEW post in this thread. (Otherwise, we receive no notification that you have responded with additional information!) Next, either name the share that has the problem or give us the first and last letter of the Share with the issue.

There is no general setting to prevent writing to the Flash Drive. You have to search the configuration files for entries that begin with /boot and that is the flash drive. Understand that heat and writes are the USB flash drives killers. Further understand that today manufacturers are trying to pack more and more GB's in the basically the same size package. (I can remember when 1GB was as big as you could buy.) They do this by reducing cell size which has the effect of increasing the temperature rise in cell itself when a write operation occurs. With more storage capacity, slow write speeds can make a 256GB flash drive virtually useless as it takes (what seems like) forever to finish large data transfers. So faster write speeds are being implemented. Faster write speeds = more power required = higher temperatures. (That is why USB2 drives are often recommended for use as Unraid boot drives. But USB2 drives have almost disappeared from the market.) What we have today is the perfect storm! Best advice for increasing boot drive live is to minimize activity. Leave your Unraid server on 24-7. Minimize the number of Dockers, plugins and VM's you install. Don't be doing continuous updates and trials of dockers and VM's. Disclosure: I don't use USB flash drives as my boot drives. I have two USB adapters that have a unique GUID back from the 2010-2015 era that hold SD memory cards. At the present time, I have an 8GB and 16GB SD cards in them. They have lasted for at least five years from when I upsized them from 1GB SD cards. BUT--- I run a very simple Unraid setup. I have only two Docker containers installed and no VM's. So I am probably not the typical Unraid user...

Another observation: Noted that you are looking at a terminal from a Docker container. How does the normal GUI Terminal (The one that you open from the toolbar of the GUI) behave?

With the terminal window open and with it being the active one, hold down on the <CTRL> key and roll the scroll wheel on your mouse. That changes the font size on my Firefox browser. (PLus, Firefox remembers the last zoom setting for each URL...)

Absolutely NOT!!!! This is almost always a problem with data corruption during the transmission of of the data from the disk to the HBA (99.99% of the time). Loose connections and SATA data cables are usually the cause. Most of the time the problem is fixed by cable replacement. This problem can be occasionally caused by cross-talk between SATA cables if they are tightly bundled together--usually done for neatness by OCD people. For me, this is NOT a panic situation and would be a last resort only if I was getting hundreds of errors a week. There are two or three threads each month on the forum by people with problems that were caused by working inside of their cases and accidentally loosening a SATA connector. (The design of the SATA connector system is the post child on how not to design a connector!!!) IF you do dive into the case, double and triple check every SATA connector when you are done before you restart the system. I use single drive HD enclosures (often called hot-swap) and I have had an occasional problem with a one or two. I just replaced them. (I currently have three disks disks with more than more than 100 CRC errors--- one with more than 1800 ---and I am not taking any action at this time. It has been months since the last one. It is not a panic situation.) Look at the appdata backup plugin. But I don't believe it does VM's... IF you are considering buying a new SATA drive, have a look at creating cache-pool with redundancy.

Did you note this restriction on Formatting your 64Gb flash drive: If the trial version is working on your flash drive, then your purchased license should work properly. (I have never heard of an instance where this is not the case.)

https://www.amazon.com/Gavemi-Molex-Adapter-Cooling-Splitter/dp/B0CG2X3DFZ/?th=1

Have you tried without using a mapped drive. You can get to your server by typing \\server-name into the address on Windows File Explorer. Then navigate down to the files you want to rename.

Not really. Except that tmux is a part of a LimeTech Plugin that is supported on an active basis so it is quick and easy for most folks to install. I used screen many years ago when it was a part of tool set plugin (not longer supported) and it worked just fine. I prefer to suggest the Unassigned Devices plugin as I don't want to have to figure out how to find a non CA plugin, and then write up instructions to get and install it. (Plus, a fair number of folks already have Unassigned Devices installed..) I can remember back when there was no Docker in Unraid and everything had to be added via the plugin route. There were always problem with common dependencies (probably wrong term) being updated to a new version which would either break Unraid or a plugin. Those memories make me very hesitant to recommend any non-support plugin.

Most interesting. Your suggestion change fixes the problem for User Shares. But what about Disk Shares? Don't think a Lot of users are still using Disk Shares these days but will a chmod 777 /mnt/diskX fix the disk permissions also? (Inquiring minds will always want the answers to these edge cases... 😉)

I suspect it is because you have these permissions on your disks: Whereas I have these: Again notice that the 'execute' bit is not set on the permissions. This blocks access to the drive for most operations by most users. You can see that the only share that I found in the Diagnostic file was testingshare whose owner and group were root and root. From what you are saying, you are reusing these disks from another server and/or a very early edition of Unraid. (I seem to recall that the user 'root' was used in the array for versions earlier than 5.0.) That prompts me to suggest that you might want to run the new permissions tool and see if that helps. Observe the suggestion to NOT run it on the appdata share!!!

Let's wait until tomorrow when, hopefully, @JorgeB will have had a chance to revisit this thread. (I believe he is based in Europe and is probably off-line now until in the morning.) You are running Unraid on bare metal and you have not been using the command line to do any operations on the disks??? You should be able to do a complete Unraid setup and management from the GUI once you have the Unraid OS installed on the USB flash drive. Having to run an command (other than a information/diagnostic command) from the command line is a sign of a very serious situation indeed.

Let's see the output of ls -al /mnt/disk1 ls -al /mnt/disk2 ls -al /mnt/disk3 ls -al /mnt

Your problem starts here: The permissions for user directory should be drwxrwxrwx Without the execute bit being set for group and other, only the root user can see these directories... I have no idea what could have caused this problem. A reboot should fix it but why was it not correct in the first place is the question! And all of the directories in the user directory should have the owner be nobody and the group be users

First thing, you do have a share set up. Shown as 't------g' in the Diagnostics file. I am trying to duplicate your problem using 7.2.0. I go to SHARES and click on button. That opens up this screen and I add the share name (#1 in the screen capture below). Then I click on the "ADD SHARE" button-- #2. In a few seconds, the screen now expands to include this new section. And I than select the Export: function. And click on the "APPLY" button. The share is now available on my Windows 11 (24H2) client and show up on the SHARES page of the GUI...

IF you do a bit of Googling on rsync, you will find that the "-a" option is the one most widely used because it does what most people want--- Copy all new or updated files. It preserves most of the source's original properties of each resource as you would expect in an archive. The "-v" tells it to verbose as it does each step. (You probably would not want this if you are using it in a shell script!) The "-h'" option makes the numbers easily human readable. The "-P" option keeps any partially transferred file(s) on the destination so they can be completed later. (This is in case you have a 'flakey' and, perhaps, slow connection situation. If you transfer 90% of the file before interruption, you only have to transfer the remaining 10% on the next pass. Usually not an issue for most Unraid users...) The '-X' option is for preserving the extended attributes. This is the one option that I don't think is really needed unless your Unraid server is running in an Active Directory environment. (Active Directory is part of Microsoft's server/networking package.) My first use of rsync was when I switched from reiserfs file system to XFS file system and I was using following a set of 'How-to' instructions. I just reused the same set of switches for my backups as i did for the conversion. IF you haven't found it, here is a link to the manual page for rsync: https://linux.die.net/man/1/rsync IF you want to try out rsync, setup a small transfer of small part of the data set and see if it delivers what you want. Then you can play around with the various parameters and see that it is doing what you want. In my initial backup of my one server to the other I moved almost 20TB of data using rsync. I did break it up into more manageable chunks of about 1TB each but looking back, doing it in one move would have been simpler and perhaps faster! (The only caution here is how much bandwidth rsync might being consuming if you try to use either server for something else.) In a more general note, I do have my backup server set up to use 'reconstruct write' mode and I do not have a cache drive for the backup shares. The cache drive (500GB) could easily fill up when the backup is being done. These settings often allow the backup speed to be about 100MB/s depending on file size.

I am confused by your posts and the subject of this post. You seem to be asking two different questions. First, if you have installed a Docker container and you have questions about that container, you should be asking itin the support thread for that Container. You can find that by clicking on the 'Support' link for that Container. See here for an example: IF nothing else, you should name the specific Container that you are having issues with. I don't use any container to do exactly what you seem to be wanting to do. I use rsync however. I use the Unassigned Devices plugins. (All three of them so that I had tmux so that I could shut down Unraid's GUI terminal and allow rsync to run in the background. You can find info on tmux by googling.). It is necessary to have rysnc in stalled on both devices. This is not normally not a problem as rysnyc has been ported to virtually every OS in existence. The rsync command is formatted like this: rsync -Options source destination It works in either a push or pull mode. If the source is remote, you are pulling. If the source is local, you are pushing. You can find much info and tutorials on rsync on the web. I know it might seem bit overwhelming initially but it is fairly easy to use once you do a bit of research. (If you can think of a set of conditions that you want to apply rsync can probably implement them...) Simple task are very easy to implement as there are some switches (like "-a") that combine many common backup features into a single switch!) I use the Unassigned Devices to mount the remote server. (This plugin does all of the really confusing stuff behind the scene which make the use of rsync so much easier!) My command line looks like this. I have it stored in a text file on my Windows desktop. When I want to do a backup, I copy-and-paste it from the file to the GUI terminal and run it. (If I run it in tmuc session, I can then close the GUI terminal and even shut the Windows machine down and rsync will continue to run.) rsync -avhPX /mnt/remotes/ELSIE1_Media/All\ Movies/ /mnt/user/BackupMedia/All\ Movies/ In this case, it is pull operation since the source is on the remote machine. (It is really hard to say what is a 'pull' vs a 'push' operation with rsync since rsync is running on both machines. I believe it is more in the mind of the user rather than true definition.) PS: In my command, only new and changed files are copied so it does an incremental backup each time it is run. It does display the progress on the terminal screen so you can watch what is happening. There is a 'switch' which will allow you to delete files in the distinction that are not in source. (By default, it does not auto-delete files so a bit of stupidity by the user on the source does repeat itself in the backup!)

Unless I am missing something, this sounds like a 'Parity Swap' would work. See here for those instructions: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#parity-swap

From the Add Share page: As you can see, <space> is not a part of this list. I believe this restriction is more of a ZFS system requirement than a Linux requirement. (PS-- you are not the only one you has reported seeing this warning. I believe this is a new 'warning' was added in one of the recent releases.)

You probably should post up your Diagnostics in a new post in this thread. Those files will provide the Gurus with more information to figure out what is going on..

Start reading beginning at this post and the next two posts and make sure that everything is set up as described: https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561581 MS is infamous for changing SMB settings in their monthly updates and not revealing what they have done. (I saw that your Shares--- that I looked at ---are all set to Public which indicates to me that you are trying to have a very simple networking setup. The MS world has moved beyond 'simple' to being 'secure' in its place.)

I would start with parity swap. see here: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#parity-swap (I would also do a party check before I started--- I would want to know that all the drives and the array are without issues before I started. The only way I would consider skipping this is if the system had previously completed a routine parity check in the month of November.) You could delay swapping out the other small data drive for a few weeks unless you need the space immediately. (It will take about 30-40hours to complete a restore the data on a 16TB data drive.)

Most CRC errors are the result of data corruption in the transfer from the hard disk to the HBA interface. Basically, we are talking about the SATA data cable and the SATA connectors. And the error is always corrected by resending the data. It does slow down the data transfer rate but unless you are having hundreds of errors per hour, you would never realize that. It will keep popping up a notice which is much more annoying than any other effect of it. I believe the notification can be suppressed in the ARRAY section of the Dashboard. But the notification will reactivate should the count increases again.