Frank1940

You really need to explain in detail what it is you want to do. (From your description, I can think of three different solutions to various hardware and software arrangements.) You need to provide what is going to be done with present server, what new hardware is being acquired, what new Unraid licenses (if any) you are getting, how much data you need to move, what is the current configuration (plugins, Dockers, VMs), and what will be the proposed new configuration.

Another potential candidate would be the power supply...

I would suggest the you post up your Diagnostics file in a NEW post. The Gurus really need those files to figure out what is going on. Another question--- Did you run a long diagnostics test on the 4TB drive? (This will probably take 8-12 hours to finish...)

Did you google * **Directory Bread Errors found** ? That gives a lot of results including at least one thread (from unraid.net) that the problem has been solved...

Try to backup the flash drive now! On the MAIN tab of the GUI, click on 'Flash' under 'Boot Device', look for the 'Flash Device Settings' and click on the 'FLASH BACKUP' button. That will download the backup to your PC's browser's 'Download' directory.

IF that old disk had the file with the data problem in that file (Regardless of how the file was corrupted) and parity was totally rebuilt for any reason, rebuilding that disk from parity would have restored the corrupted file to the new disk. Remember what rebuilding parity does. When parity is rebuilt, (1) all of the data disks are read byte-by-byte, (2) a new parity information is calculated, and (3) that results of that calculation are written to the parity disk. (Having said that allow me to say that if a parity error is found during a non-correcting parity check, the standard recommendation to check the logs and SMART data for any possible reason for the error. If none is found, then a parity rebuilt is that proper action. This recommendation is based on the assumption in the next paragraph about data corruption on Hard Disks.) What we don't know is where and when that file was corrupted. The HD manufacturers have a lot of proprietary error detecting and error correcting software to prevent it from happening on the hard disk. I am one of the folks who believe that a HD will always return the exact data that was originally written to it or it returns an error code. I am convinced that any error that corrupts data occurs when the data in some place besides on the HD. The statements in the previous two paragraphs have logic flaws in them. There are folks who believe in "bit-rot" (which I consider to be folk lore) but I can not completely rule it out as I have never seen that any HD manufacturer software code have been audited/analyzed to guarantee that silent errors might not slip thorough undetected and what the probability of such an occurrence from happening IF the algorithms might allow such situation. With regard to something like your wedding video, might I suggest that you consider multiple backup on several different media materials if its retention is of prime concern to you. Consider using not only that USB drive and a hard drive in a parity protected server, but also consider using burning the files to DVD and uploading them to the cloud. Consider an off-site storage for one (or more) of your physical copies in case you have a natural or man-made disaster at your home. Be careful of the storage conditions. I have writable DVDs that are over ten years old that are still playable but they are stored at room temperature in a dark environment. Do a bit of research on media life and ideal storage conditions for any storage media that you use. Nothing can guarantee that you won't lose critical files but you can minimize the risks. Test that each copy is readable when you make it and periodically test that it is still readable. Make new copies on new media as time passes. (Thing about the problem of trying to find a floppy disk reader today...)

Copy the files off that USB drive to your PC. Check that those copies play. Then copy them up to the Unraid server again. (You can either delete those original copies that don't play and copy replacements to the same point on your Unraid file structure-- or to a new diectory on the server.) Again, check to see that they play. It is very unusual. (Data errors that are on a HD are (1) either corrected by error-correcting algorithms or (2) flagged as read errors. A HD will only send out the exact bits that were written to it or it sends an error message.) There are a lot of checks on data integrity during the movement of data between storage devices. As @Michael_P indicated, when these errors occur, it is usually attributed to data being corrupted in RAM. It could happen either on your PC or in the server. There is a Unraid bootup option to check server memory using MEMTST that will check standard RAM. (ECC RAM requires that you go to the MEMTST website and download the free testing suite for this type of RAM.) Run the test for 24 hours. You should have zero errors. PS--- Don't overclock memory or the CPU on your server. Either of these can cause silent crashes...

Was there any error when you copied the the file from your server to your PC? If you can, this would indicate that the actual data in the file is the problem and not an error in the file itself. Do you still have access to the original source? IF nothing else, try to move past the stopping point and see of you can play the balance of the file. (I know that VLC will allow to position the start point for play by "pulling" the circle when playback is stopped...) Please be advised that the parity protection in Unraid is not a backup if the only version of a file is on the server. You need at least two copies of anything which is irreplacable! And for even more security, one of those copies should be off-site.

Have you see this thread? https://forums.unraid.net/bug-reports/prereleases/macos-optimization-r2087/ PS--- I do not run MACOS so I am no expert on getting things set up so that they work....

That would seem to indicate that you have a problem in your network. As a test, I am assuming that you have a login prompt on the monitor and a keyboard connected to your Unraid server. Login into the server using your root credentials. Make sure the PC (from which your tried to ping the server) is on. Type the following command: ping 192.168.1.12 If this does not work, it would appear that there is some problem with network hardware. Try switch the Cat5 cable. Try a different port on the switch. Double check to see that you have reserved the IP address of 192.168.1.100 for use by your Unraid server. (If you didn't, the router's DHCP service may have assigned it to another computer on your network.

Surprising! I wonder if a Docker (or some other process) has got them permanently open. You might also want to go further down the directory tree of those two directories and see what you find with regard to owner/group and permissions. You might try stopping the Dockers and run the script again. Check before you restart the Docker to see what happens regarding this situation. What I would do at this point is to go to the support threads and see if you can get help there. You can get to the support thread by clicking on the individual Docker icon on the Docker Container page and looking for Support in the dropdown menu. Hopefully, someone there will be able to help you. The old updated-and-now-it-doesn't-work saga is an very old one. I am usually hesitant to update but, eventually, I succumb and pray for the best. (Being too far behind has its risks too.) Unraid has been updating its security approach recently. (Pressure being brought on two fronts-- The folks who want to use it an business environment and those who want to use Unraid with its VM feature and use the hardware as their personal PC as well as a simple NAS. Both of these groups want a secured and locked down system for protection against the bad guys!) These Unraid upgrades may have broken the Dockers you are having problems with. Plus, there are the security updates are in the Linux kernel which address CVEs over which Unraid has no real control if Unraid is to have a secure software base.

I am assuming that Screen capture was before you run the New Permissions tool. Hopefully, running that tool did fix the permissions on unzipped torrents directory and the owner/group on the YT directory. With Dockers, you want the Docker to write to all Unraid Shares and Data Disks as 'nobody' (PUID = 99) as the owner and 'users' (GUID = 100) as the group. The permission for all directories should be 777 and for files should be 666. (I have reason to suspect that these are not the default permissions for a 'normal user' in other Linux distributions for security reasons.) There is a third parameter called UMASK and I believe this should be set to 000. Look at your Docker configuration and see if you have 'Container variables' for PUID, GUID and UMASK. If so make a note of their current settings and change them as indicated above to see if that will fix things. Now, I know that the owner does not have to be 'nobody' for SMB to work properly. I am not completely certain about the group having to be 'users'. However, I do know that all of the 'Share Access Users' that write to my Unraid Shares are members of the 'users' (GUID = 100) group. I have reason to suspect that the permissions for 'others' are involved in controlling access to Unraid shares via SMB but no real information as to how. I am no Docker expert but I suspect that a lot of the Dockers in the repository are not really being thoroughly tested to make sure that they work properly with Unraid. IF they were, we would not be seeing owners not being 'nobody', groups not being 'users' and permissions not being 777 or 666...

OK. Now run that command on the downloads directory. Post up the screen capture of that command. Let's see what the permissions for its contents. Then, I would suggest going to Tools >>> New Permissions against only the downloads Share. That will probably fix it for time being. You next need to determine what Dockers (or VMs) write to the directory. After rereading your first post, make sure that list includes any Dockers that work with the data inside of that Share.

Run the following command from the terminal that is a part of the GUI: ls -al /mnt/user This will give an output that looks like this: You then push the <UP-ARROW> on the keyboard. Edit (by adding to) the path and navigate down to the directory which has the problem. (Capitalization is important with Linux. IF you have a <SPACE> in a directory, you must type a \ before the space!!!) Do a screen capture of the directory with the problem. (Screen captures are preferred. If you must capture text, be sure to format it as Code--- The </> on the reply format toolbar.)

@SpencerJ Nope--- Not at 3:56PM EST.

First person who finds the certificate provisioning server is back running normally, Please post a notice in this thread! Thank you in advance. @SpencerJ

I see nothing in the diagnostics file to indicate a problem. (BTW, the diagnostics file generated by using the command line also has sensitive data removed!) Your IP address for the server is 192.168.1.100 Try pinging it from your PC.

Get the diagnostics file first and shut the server down with the following commands typed on the keyboard. After each command, type an <ENTER> keystroke. diagnostics powerdown Now pull the boot drive after the server shuts down. The Diagnostics file will be in the /logs folder. Upload it in a new post in case it is needed. Make a full backup of that Flash Drive right NOW!!!!! (That is your insurance policy!) Open the network.cfg file in the /config folder with a straight text editor (Like Notepad). (Ideally, you want a Linux, MacOS, Windows aware editor...) Find the following line: USE_DHCP[0]="no" Change the no to yes Now save the file. Do NOT enter or make any other changes unless you are using that Linux, MacOS, Windows aware editor. (I use EditPad Lite for all my text file editing as it is Linux, MacOS, Windows aware...)

Yes. When the Unraid server is in its boot process, there is an boot option menu that appears on the console screen. Just select one of the two that indicate that a GUI will be installed. The 'Safe' mode will will boot-up without Plugins, Dockers or VM's. The other boots up your 'normal' Unraid configuration except that you will have a GUI on the console. Be sure that you check to see that you have an IP address and what that address is.

Try running the New Permissions tool (Found under the Tools Tab). If this works, you probably have a Docker or VM setup to write with the wrong permissions to the array. Did you setup a new credential (under Windows Credential Manager) and setup a user on Unraid to automatically log you into your Unraid server? Windows has become quite picky about allowing access to shares without being logged into a server! Many problems can be solved by setting your Windows access to remote servers and shares by working with MS rather than trying to 'fight' them. See here for how to do this: https://forums.unraid.net/topic/89452-windows-issues-with-unraid/page/12/#comment-1126564

Another option might be to use a Windows Mini/Micro computer and run KODI on it. (These computers start at $200US. Even the cheap ones have more than enough performance. Do check on the Video Chip specs if you are planning on running 4K streams.) I also use a mysql Docker for the KODI database (which is stored on an always-on SSD cache drive) which can be accessed from any of the five computers whic have KODI installed. This means that any of the KODI installs always have the most current database for all the media on my server. This also means I only have to update the database once as new media is added.

Recent versions of Unraid will not install (?)/enable SMBv1 IF it is a new install. IF it is a update from an earlier version of Unraid where SMBv1 was enabled, SMBv1 will still be available. However, you can still set up Unraid shares as 'Secure' and SMBv1 device will still have read access to the files. That way you can make both MS and the Dune player happy. (I hope you are realizing that you don't want to make anything except those files that SMBv1 devices will access be available via a 'Guest' access account.)

Please post up your diagnostics file in a new post.

Not an uncommon problem. One thing to consider is that Windows 10 (and 11) versions now prevent (by default) establishing a connection to a server using 'Guest' type credentials. You have to have a credential (login) to access a server. (Count on SMB to be inconsistent in its behavior...) Plus, MS wants to prevent you from using SMBv1---Period! One thing I would suggest is to stop trying to stop fighting MS. Embrace their want/need to bring some semblance of security to SMB. Look at the first post this thread and set things up to make Windows happier with what you are doing: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/#comment-1009109 By the way, the only real reason to use SMBv1 is if you have a piece of hardware so old (media boxes for the 2010 era) that they don't support SMBv2. I know that the 'Network' section of Windows Explorer does not get populated when you turn off SMBv1 but that is what the 'Network Neighborhood' is for. (It also appears that the Network section Of Windows Explorer is populated with the Unraid servers when the Credential Manager establishes its 'login' to the Unraid servers as the Windows boots up--- at least that is my experience.) One more thing--- I now suspect that MS now considers Peer-to-Peer networking to the 'natural child' of SMB. They want you to use the Windows Server software and Active Directory (AD). And I believe you need a degree/certificate from MS to be able to set up this type of Network!

You didn't give much info about what hardware you are using to access your unraid server. What I have done with Windows 10 Pro computers is to 'map' as a Windows drive--- (The automatic assignment of these drive letters begins at Z:\ ) ---to the point in the Unraid Share's file structure where I need my access point to be.) As an example I have mapped a Drive Z:\ to the point on an Unraid share named Data at ELSIE1\Data\ShareData\Pimax for use by our Address Book program. When the address book program starts up, it looks for its data on Z:\ and it never realizes that it is using a network resource which makes it as happy as a clam. In this case, the Unraid share Data is shared as a Private Share and thus Z:\ has the same usage permissions as the whatever the SMB user from that computer has to that base Share. (In this case, it is Read-Write as I want all users of the Address Book to be able to update the database.)