Frank1940

I missed one thing: The hardware spec states that the boot drive should be 32Gb or smaller. However, I believe there is small wiggle room on this requirement but I don't recall what conditions have to met. I am going to ping @JorgeB to get his input.

That should be fine. I just want to be sure that the problem is not an obvious file structure problem on the flash drive. (Unraid does not do a lot of reading to the flash drive but S..t does happen occasionally.)

Sorry missed the earlier diagnostics file. What is going on here? Jan 15 04:06:38 unraid root: Starting Samba: /usr/sbin/smbd -D Jan 15 04:06:38 unraid smbd[4156]: [2023/01/15 04:06:38.157092, 0] ../../source3/smbd/server.c:1741(main) Jan 15 04:06:38 unraid smbd[4156]: smbd version 4.17.3 started. Jan 15 04:06:38 unraid smbd[4156]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Jan 15 04:06:38 unraid smbd[4156]: [2023/01/15 04:06:38.157931, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Jan 15 04:06:38 unraid smbd[4156]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 12288 Jan 15 04:06:38 unraid smbd[4156]: [2023/01/15 04:06:38.157950, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Jan 15 04:06:38 unraid smbd[4156]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record Jan 15 04:06:38 unraid smbd[4156]: [2023/01/15 04:06:38.157967, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) Jan 15 04:06:38 unraid smbd[4156]: Failed to open /var/lib/samba/private/secrets.tdb Jan 15 04:06:38 unraid smbd[4160]: [2023/01/15 04:06:38.158945, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Jan 15 04:06:38 unraid smbd[4160]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 12288 Jan 15 04:06:38 unraid smbd[4160]: [2023/01/15 04:06:38.158985, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Jan 15 04:06:38 unraid smbd[4160]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record Jan 15 04:06:38 unraid smbd[4160]: [2023/01/15 04:06:38.159006, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) Jan 15 04:06:38 unraid smbd[4160]: Failed to open /var/lib/samba/private/secrets.tdb Jan 15 04:06:38 unraid smbd[4160]: [2023/01/15 04:06:38.159018, 0] ../../lib/util/become_daemon.c:119(exit_daemon) Jan 15 04:06:38 unraid smbd[4160]: exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13 Sorry for the delay. I have been researching and I (personally) am at a dead end. The secrets.tdb file is one that is apparently generated from some files in the /config directory on your flash drive when Unraid boots up. I would suggest that you shutdown your server and run chkdsk on the flash drive to make sure that there is no obvious problem with those files (passwd, shadow and smbpasswd are the files that I think are involved..). I am going to ping @limetech and @jonp to see if they will jump in at this point. What is going on here?

What are the other "client devices"? This is what one would expect to see: Please attach another Diagnostics file to your next post.

See here: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default Notice that error Code is identical. (I will also say that Windows is famous for throwing up a default error code when it does know what is the problem...) and here (from a few years back...): https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392 And from that post, this quote: Your problem is looking a bit like a User Share password issue. (I don't what your User Share password looks like (and I don't want to know) but I would suggest that you use only letters and numbers as a trial. Avoid symbols as they can some times certain have special meanings to shell programs and their use can result in things not being processed as you thought they should. Remember you have to use the net use * /delete command between any changes that you make.

From my previous post: Or (I should have included in this post) SMB is restarted which has to occur whenever one of the .conf files are modified! Any user modification must be in the smb-extra.conf file. You can find this at Settings >>> SMB and look for the "SMB Extras:" section. This is where the user modification go. These are saved in the smb-extras.conf file and used to configure SMB every time it starts up. If I were you, I would be testing the following idea about adding that parameter in the SMB Extras to see if it might work...

You said you can see the server name under the 'Network' icon in Windows File Explorer. What happens when you click on the server name in the left pane of Explorer? (I would expect the share ("data" in your case) to appear in the right pane...) If it does, what happens when you click on that share name in the right pane?

One more thing to try. Open up a Windows Command prompt window, then at the prompt type net use * /delete This removes all network connections on your Windows computer. (Note the spaces around the "*"!)

Hook up a monitor to your server. It should have a login prompt at the bottom of the screen. A few lines above that you should see a line that says Starting SMB /usr/sbin/smbd -D Then two more indented lines of commands and then unRAID Server OS version: 6.11.5 Following that will be the IP addresses of the server. Are you seeing this? If not, attach a new Diagnostics file in your next post. This happens if you establish a login/connection to a computer on the network even with SMBv1 turned off. It is a hit-and-miss situation. I have noticed that both of my servers are showing up this morning but it is really not a completely dependable situation. (I have an ad hoc windows peer-to-peer network setup to eliminate sneaker netting but those computers never show up unless I 'hit' them from my Network Neighborhood setup. Then they are there..) MS has never (to my knowledge) explained how the 'Network' in Windows Explorer works or fixed it so it is reliable. As a result, I tend to ignore it. (Remember, MS considers that the Windows Server Software is the way to deploy networking for Windows computers. What most folks (including the two of us) is a peer-to-peer networking scheme that goes back to Windows for Workgroups 3.11 introduced back in 1993.)

UPDATE: I believe the parameter should be: server min protocol = SMB2_02 and not

Check to see if the HP printer requires SMBv1. Recent installs of Unraid and Windows 10/11 have SMBv1 turn off. This has been a problem in the past. I seem to recall that Unraid defaults to SMB 2.1 and there was one printer that would only work if the following item was added to smb-extra.conf server min protocol = SMB2.01 So go to the user manual and do some research on exactly what SMB version is support by your printer.

I am going to link you to the smb.conf document. Search this document for hosts allow parameter. I believe it is a 'share only' parameter and you will have to add it to the smb-extra.conf file on your flash drive. (The edited contents of /etc/samba/smb-shares.conf file are lost when the server is rebooted.) https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#HOSTSALLOW (Disclosure: I have never tried to do this but I believe you have to add a [SHARE] section (for the share in question) to that file. Test with the Linux command testparm before starting the array after modifying the file to see that the syntax is correct.) IF the syntax is not correct, SMB will not be started!!!)

Looks good. It looks like the Unraid server is now running SMB and you appear to have your share setup using either Secure or Private sharing. I am assuming that you have a Windows credential setup to log you onto Unraid as coner (A windows credential to automatically log you onto your Unraid server at startup will go a long way to addressing many SMB problems. Windows has recently implemented a setting where it won't allow 'guest access' to a server. I am not sure how restrictive this restriction is.) Shut the Windows PC down and wait ten minutes. (If you have other clients connecting to this server, it would be a good idea to shut them down also.) Leave your Unraid server running. Then start up your Windows PC and see if things are working. This allows time for your Unraid server to end up as the Local Master. It is also a good idea to leaving your server 24-7. Having a consistent Local Master solves most SMB problems with 'lost' resources. (SMB polling times are very long-- tens of minutes --- and it can take a large Windows network up to forty minutes to everything to finally stabilize.) I am going to direct you now to a PDF file with a tutorial on how to setup a simple Windows_Clients/Unraid_server network that has worked for most people in your situation. IF you are still having problems, go through the PDF file that is in this post: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/#comment-1009109 It contains a lot of explanations as to how and why samba works (and doesn't). I see that you have a "fruit" variable in your configuration. This would imply that you are using MacOS PC also. If you are having issues with these clients, I would refer to this thread: https://forums.unraid.net/bug-reports/prereleases/macos-optimization-r2087/

I suspect you have an extra character (perhaps, a <space>) after the "s" in 'yes '. NOTE: This file has a Linux/Unix file format (The EOL-- end of line -- character is a LF only where windows is a CR-LF.) and requires a Unix 'aware' Editor if you are editing the file on a windows computer. I use EditPad Lite. It is free for home use and very friendly for use with Windows, Unix/Linux, and MacOS files which are CR. It figures out (automatically) what is required regarding the EOL character(s). I did double-check both of smb-extra.conf file on each of my servers to verify the format. EDIT: I suspect that smb.conf is one of those configurations files where syntax errors will cause the using program to crash somewhat ungracefully...

In the Terminal window, type this: testparm Your out output should look like this: Load smb config files from /etc/samba/smb.conf lpcfg_do_global_parameter: WARNING: The "null passwords" option is deprecated Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback) Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] disable netbios = Yes disable spoolss = Yes load printers = No logging = syslog@0 map to guest = Bad User max open files = 40960 multicast dns register = No ntlm auth = ntlmv1-permitted null passwords = Yes passdb backend = smbpasswd printcap name = /dev/null security = USER server min protocol = SMB2 server multi channel support = No server string = Test Bed and Backup Server show add printer wizard = No smb1 unix extensions = No workgroup = HOME fruit:nfs_aces = No idmap config * : range = 3000-7999 idmap config * : backend = tdb acl allow execute always = Yes aio read size = 0 aio write size = 0 case sensitive = Yes create mask = 0777 directory mask = 0777 hide dot files = No include = /etc/samba/smb-shares.conf invalid users = root map archive = No map readonly = yes use sendfile = Yes wide links = Yes [flash] case sensitive = Auto comment = Unraid OS boot device force user = root path = /boot read list = smbuser user valid users = smbuser user [cache] case sensitive = Auto path = /mnt/cache valid users = smbuser user write list = smbuser user [Backup] case sensitive = Auto comment = Current Data Backup path = /mnt/user/Backup read list = smbuser user valid users = smbuser user [Media] case sensitive = Auto comment = Media for Test Bed Server Testing path = /mnt/user/Media read list = smbuser user valid users = smbuser user Let's see what yours looks like....

First, Open the Main tab of the GUI. There should be not a red X or any other color then green or light-gray in the left column. The array should be started. The reason for this question is that disk2 had a write failure about 15 hours ago. In my opinion, this failure should have disabled the disk. ================== Other wise proceed here: =========== Open open a Terminal Window (The >_ icon on the Toolbar of the GUI) and type the following two commands: ls -al /etc/samba and cat /etc/samba/smb.conf Do a screen capture of both outputs. Not that I am aware of. Realize that Unraid installs itself from scratch every time you reboot the system. Stopping and Starting the array will stop-and-start samba which forces a re-read of all the samba configuration files which might be considered a 'resetting' of samba.

This plugin is "semi-broke". As I recall, it will only be able to identify the name of the Local Master if SMBv1 is running. (BTW, if you google looking for a way to find the Local Master, you will not find a way to do it--- period. Not even from Windows. So don't be surprised when LANscanner did not find the name of the Local Master!) See below: Neither of my two Unraid servers are even showing up on this screen shot! And I can access them both. (What is showing up are my two PCs that are currently on and two always-on networked printers. Near the bottom of your syslog is the following: Jan 14 05:29:07 unraid root: Can't load /etc/samba/smb.conf - run testparm to debug it This is the file (/etc/samba/smb.conf) that defines all of your samba configuration. For some reason, it does not exist or is not readable. (BTW, this location is on a RAM disk...) I would suggest that you backup your Unraid flash/boot drive. See here for how. Then shutdown the server. Pull the flash drive and run a chkdsk on it. If no errors are found, plug it back into the server and boot it up again.

I would think this thread would be a good place to start: https://forums.unraid.net/topic/36647-official-guide-restoring-your-docker-applications-in-a-new-image-file/#comment-351611

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...