conermurphy Posted January 14, 2023 Share Posted January 14, 2023 (edited) Hey all, Hoping I can get some help with some issues I'm having with shares. Earlier today I was moving some files around in a share from my Win 10 laptop, then I checked the Unraid dashboard and I'm not sure what was happening but it seemed the UI was glitching out and kept refreshing and the cache drive had a gray warning regarding the Array next to it. I stopped the array and restarted it and that resolved the warnings and UI issues but ever since then shares have not worked on my Win 10 laptop/PC or on my MacBook. I may be wrong but my initial thoughts on the cache warning was because I transfered more data then the cache had spare capacity but because I was just moving files within the same share, just between directories would that matter? Anyway, I've spent the last few hours trying to resolve the issue but to no avail. Below are the things I've tried. - Tried the steps outlined here for using `gpedit.msc` - Installed the "Dynamix Local Master" plugin to see the elected master, it shows the Yoda icon but no name? Not sure if this is correct? See the screenshot below. - Also shown in the screenshot below, I added the SMB Extras I found in this comment. - I've tried running Scotties LANscanner but I think I have a seperate issue for this becasue I'm seeing the error output 6118 (screenshot below) - Tried recreating users on Unraid and validating the SMB settings but I believe they are correct for local sharing with a user configured? - Tried clearing credentials in Windows but there seems to be no credentials linked to Unraid in there - Tried rebooting into safe mode but that didn't resolve the issue either. Looking in the attached logs, I can see in the shares folder, the share that should be called "data" is called "d--a", is this on purpose due to the "Anonymize diagnostics" or something else? In the course of trying to debug this issue, I now have 2 unraid devices showing in my Windows network panel? (See below) I did try renaming the server to see if that resolved it from "unraid" -> "tower" and then back to "unraid". However, when I click on either of these I get the error shown below. As it stands, the share I have configured doesn't connect on any of the 3 devices listed above. Apologies for the long post and if this is in the wrong location, it's my first time posting so not 100% sure where to put it. Any help is much appreciated. Thank you. Edited January 16, 2023 by conermurphy Quote Link to comment
Frank1940 Posted January 14, 2023 Share Posted January 14, 2023 14 minutes ago, conermurphy said: Installed the "Dynamix Local Master" plugin to see the elected master, it shows the Yoda icon but no name? Not sure if this is correct? See the screenshot below. 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. Quote Link to comment
conermurphy Posted January 14, 2023 Author Share Posted January 14, 2023 42 minutes ago, Frank1940 said: 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. So, I tried pulling the flash drive and running cdkdsk on it as you said and it didn't find any errors. I then put it back in and booted up the server again and still getting the same issue. Is there a way I can reset the SMB configuration in Unraid? Apologies if that's a stupid question I'm quite new to SMB and Unraid in general. Quote Link to comment
Frank1940 Posted January 14, 2023 Share Posted January 14, 2023 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. 24 minutes ago, conermurphy said: Is there a way I can reset the SMB configuration in Unraid? 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. Quote Link to comment
conermurphy Posted January 14, 2023 Author Share Posted January 14, 2023 4 minutes ago, Frank1940 said: 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. All green for the devices in the array as per below. I did notice some errors for Disk 2 yesterday around the time you mention. Although these errors disappeared in the UI and went to 0 so I wasn't sure if that meant they were resolved or not? Outputs of the commands below. Quote Link to comment
Frank1940 Posted January 14, 2023 Share Posted January 14, 2023 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.... Quote Link to comment
conermurphy Posted January 14, 2023 Author Share Posted January 14, 2023 (edited) 1 hour ago, Frank1940 said: In the Terminal window, type this: testparm I think we've found the issue. Do you know what could be causing the error? Edited January 14, 2023 by conermurphy Quote Link to comment
Frank1940 Posted January 14, 2023 Share Posted January 14, 2023 (edited) 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... Edited January 14, 2023 by Frank1940 Quote Link to comment
conermurphy Posted January 14, 2023 Author Share Posted January 14, 2023 10 minutes ago, Frank1940 said: I suspect you have an extra character (perhaps, a <space>) after the "s" in 'yes '. So I double checked the "Samba extra configuration:" in the Unraid UI and there was an extra space as you said, I've removed it, restarted the array and ran `testparm` again and got the below output. Hope it points to a potential fix as the issue is still present in Windows with this change. 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 domain master = 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 os level = 255 passdb backend = smbpasswd preferred master = Yes printcap name = /dev/null security = USER server min protocol = SMB2 server multi channel support = No server string = Media Server show add printer wizard = No smb1 unix extensions = No 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 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 [data] path = /mnt/user/data valid users = coner vfs objects = catia fruit streams_xattr write list = coner fruit:encoding = native Quote Link to comment
Frank1940 Posted January 14, 2023 Share Posted January 14, 2023 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/ Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 11 hours ago, Frank1940 said: 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.) So, I shutdown all my client devices (both Win 10 and OSX) and left the Unraid server running overnight (approx 9 hours) to hope this would give it enough time to allow the Unraid server to become the Local Master. Unfortunately, I just tried connecting again with my Win 10 laptop and I'm still getting the same issues as yesterday. Windows Network Diagnostics says the issue is "The remote device or resouce won't accpet the connection" but I find this interesting because I can ping the IP and access the Web GUI from the device. 11 hours ago, Frank1940 said: 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.) I have doubled checked and I have a windows credential configured for the IP of the Unraid server with the username and password configured for the coner user in Unraid. I've also tried adding one with the server name to be sure but neither of these approaches worked. 11 hours ago, Frank1940 said: 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 went through these PDFs (the overall one and the step-by-step ones ) a couple of times to check the settings all line up and all the Group Policy and Registry Edits match the PDFs, the network sharing centre settings also line up. Something I did notice which I'm not sure is of note or not but my WIndows Explorer matches the "With SMBv1 Turned On" example on Page 5. That is to say I can exapnd the Network field and see the Network devices including my Unraid Server. But, as per below, SMB 1.0 is turned off on my machine. Not sure if it could be anything or not but could the System Error 6118 I get from Scotties LANScanner be relevant here? I also get this error when running net view. Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 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. 42 minutes ago, conermurphy said: Something I did notice which I'm not sure is of note or not but my WIndows Explorer matches the "With SMBv1 Turned On" example on Page 5. 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.) Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 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 "*"!) Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 (edited) On 1/15/2023 at 11:36 AM, Frank1940 said: 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 Not sure why but I had to restart the server to get any video output from it? I tried connecting to the dedicated GPU in it and the iGPU and got no video signal output. Rebooted and got one. Anyway, I can't see that line, I have a starting Samba line. I'll attach a photo of the screen below. On 1/15/2023 at 11:36 AM, Frank1940 said: unRAID Server OS version: 6.11.5 Following that will be the IP addresses of the server. I do have both of these outputs as well. On 1/15/2023 at 11:52 AM, Frank1940 said: 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 "*"!) Just tried doing this and then accessing the share again but no luck, same error as before. Edited January 16, 2023 by conermurphy Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 10 minutes ago, conermurphy said: Just tried doing this and then accessing the share again but no luck, same error as before. 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? Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 (edited) 12 minutes ago, Frank1940 said: 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? Unfortunately not, here is a recording of what happens. Same as if I click on the UNRAID item in the main panel itself. Edited January 15, 2023 by conermurphy Updated image size Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 (edited) 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: Quote Now, after above, you click on a Private share where the only unRaid user with access is "curly". Samba will see the request to the share as user "larry" and tell Windows that the connection is unauthorized (because larry is not in the list of users for the Private share). Windows sees this and presents you with a username/password dialog box. So you enter "curly" as the user. But now Windows sees that you already have a connection to the server as user "larry" and it DOES NOT ALLOW multiple connections to the same server via different user names. This is a well-known limitation/bug in Windows. 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. Edited January 15, 2023 by Frank1940 Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 6 minutes ago, Frank1940 said: See here: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default I just followed the steps outlined in the "Resolution" portion of this document and still getting the same issue as before. 7 minutes ago, Frank1940 said: 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. So, I've updated my user share passowrd to be just numbers and letters. It's an interesting point this because prior to events I described in my original post I was using a password with symbols, letters, and numbers without issue. Anyway, I updated the password in both Unraid and Windows and ran the net use * /delete command again but still no luck, same issue as before. Interestingly when I run that net use command I always get the below output even if I try to connect to the server between runs of it. For each time I try to connect to the server, I only ever see the error shown in the video in my previous post. I'm just at loss for what it could be, I never changed anything on any client devices, just moved some files on the share and restarted the array when the UI was glitching out and now no device can connect to the server through explorer/finder. Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 18 minutes ago, conermurphy said: I never changed anything on any client devices, What are the other "client devices"? This is what one would expect to see: Please attach another Diagnostics file to your next post. Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 (edited) 19 hours ago, Frank1940 said: What are the other "client devices"? So, I've only ever connected to the share successfully on my Win 10 laptop. I have tried unsuccessfully since the original issue described with another Win 10 PC and a MacBook. In the case of my Win 10 laptop, all I ever did the was the normal setup that is create an unraid user, goto \\UNRAID in Win explorer, enter the credentials and then it worked. Although, I have no evidence to prove otherwise, my instinct is something is wrong with the Unraid server as that's what had issues and then everything else stopped connecting to it after those issues described. Saying this I may be completely wrong as I have limited knowledge in Unraid and network shares. 19 hours ago, Frank1940 said: This is what one would expect to see: I saw an input like this, the first time I ran the command and that was removing my WSL2 Network Connection to Ubuntu. Since then I've only gotten the output in my previous post saying "no entries". Edited January 16, 2023 by conermurphy Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 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? Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 1 minute ago, Frank1940 said: 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 No worries at all and I'm not sure what's happening but it doesn't seem good whatever it is. 2 minutes ago, Frank1940 said: 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..). Is there any particular paramaters I should use with chkdsk, I ran it yesterday with /f and it reported no errors (see post earlier in the thread) but happy to try again with the same or other parameters if you think any are worth a shot in particular? Although we're not quite there yet with the solution, just wanted to say thank you for all the help, I appreciate it. Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 11 minutes ago, conermurphy said: Is there any particular paramaters I should use with chkdsk, I ran it yesterday with /f and it reported no errors (see post earlier in the thread) but happy to try again with the same or other parameters if you think any are worth a shot in particular? 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.) Quote Link to comment
conermurphy Posted January 15, 2023 Author Share Posted January 15, 2023 4 minutes ago, Frank1940 said: 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.) Just ran chkdsk, seems to be all okay, see the output below. Quote Link to comment
Frank1940 Posted January 15, 2023 Share Posted January 15, 2023 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. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.