Steviewunda Posted February 5, 2023 Share Posted February 5, 2023 (edited) Hi - I had a problem with my main Unraid server (TOWER) yesterday - the readout on the 'Main' webpage was constantly changing - no array, no Flash drive, no cache pool, all disks unassigned, etc. I tried to download diagnostics, but got a '404 - not found'. So the diagnostics attached are from after a reboot. After rebooting the array, cache pool, and Flash drive came back, and I can access TOWER from the web gui, but not from Windows File Explorer (see attachments). Disk read/write counters were reset. My backup Unraid server (Tower2) has no such problems, so I presume it is a configuration problem with TOWER. I haven't followed Frank1940's SMB troubleshooting guide yet - I thought I would post my diagnostics and see if someone could see something obvious Cheers, Steve tower-diagnostics-20230206-1009.zip Edited February 5, 2023 by Steviewunda Quote Link to comment
Steviewunda Posted February 6, 2023 Author Share Posted February 6, 2023 Can anyone help with this please? I have followed Frank1940's SMB guide ( ) but I still don't have access to all my media needing SMB access in order to play. Any help appreciated. Quote Link to comment
Steviewunda Posted February 6, 2023 Author Share Posted February 6, 2023 I t has occurred to me that I could restore the flash drive to a config that existed before I had to reboot and lost SMB connectivity. My other Unraid server has no SMB connectivity problems, so I assume that flash drive corruption could be ruled out by by restoring an earlier saved flash config. Does this sound reasonable? Quote Link to comment
Frank1940 Posted February 6, 2023 Share Posted February 6, 2023 3 hours ago, Steviewunda said: Can anyone help with this please? I have followed Frank1940's SMB guide ( ) but I still don't have access to all my media needing SMB access in order to play. Any help appreciated. The guide in the above thread was intended for those people who are connecting from one Windows computer to another Windows computer. When you are trying to connect to an Unraid server, you need to be reading this guide: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/ This message suggests to me that your PC has already established a connection to the Unraid server. Try setting credentials in the Credential manager using the section in the guide that begins on page 11, entitled "Setting Up the Unraid Server and the Windows 10 Client". (You may have to reboot your Windows 10 client after making these changes.) Your Unraid server should be designated to be the Local Master and left on 24-7 for the most reliable operation. Quote Link to comment
Steviewunda Posted February 7, 2023 Author Share Posted February 7, 2023 I have followed the Unraid & Windows 10 SMB Setup.pdf you recommended, but I still cannot access this Unraid server via SMB. I have followed the guide to a tee, but still get the failures shown in the accompanying attachments. I can access it by web browser, but I need SMB access for my Windows 11 media player. No problem accessing the other Windows (10 and 11) and Unraid computers by web browser or Windows File Explorer. I have also included another diagnostics file. tower-diagnostics-20230207-1705.zip Quote Link to comment
Frank1940 Posted February 7, 2023 Share Posted February 7, 2023 Let's look at the login to the server in question ---TOWER and its IP address 192.168.51.50 First get a Screen shot of the The Credential Manager for both of both of these (Hopefully, you have only one) as shown below: From the TOWER GUI go to Setting >>> Users Under "Share Access" click on the 'user' named in Windows Credential Manager and take a screen shot of that. It should look like this: Post them both up as I have done. Now for a bit of a secret, here is a command that you can run on your Windows computer (in a Command Prompt box) that will knock down all network connections! net use * /delete (It saves you from having to reboot the Windows machine when you make any changes to the networking configuration.) Two things to check: First, make sure that you only connect tot he server using either the server name (preferred) or the IP address! (Using both was a way to trick Windows into allowing two different users to log into the same server. This backdoor may be blocked now or in the future...) Second, make absolutely the passwords are identical. I usually copy and paste them on both ends (Windows and Unraid) to assure this. Quote Link to comment
Frank1940 Posted February 7, 2023 Share Posted February 7, 2023 (edited) WHOA!!!! I just found something that I have never seen before. From your syslog: Feb 7 16:25:15 TOWER root: Starting Samba: /usr/sbin/smbd -D Feb 7 16:25:15 TOWER smbd[25884]: [2023/02/07 16:25:15.273336, 0] ../../source3/smbd/server.c:1741(main) Feb 7 16:25:15 TOWER smbd[25884]: smbd version 4.17.3 started. Feb 7 16:25:15 TOWER smbd[25884]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 7 16:25:15 TOWER smbd[25884]: [2023/02/07 16:25:15.274734, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Feb 7 16:25:15 TOWER smbd[25884]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096 Feb 7 16:25:15 TOWER smbd[25884]: [2023/02/07 16:25:15.274748, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Feb 7 16:25:15 TOWER smbd[25884]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record Feb 7 16:25:15 TOWER smbd[25884]: [2023/02/07 16:25:15.274757, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) Feb 7 16:25:15 TOWER smbd[25884]: Failed to open /var/lib/samba/private/secrets.tdb Feb 7 16:25:15 TOWER smbd[25885]: [2023/02/07 16:25:15.275774, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Feb 7 16:25:15 TOWER smbd[25885]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096 Feb 7 16:25:15 TOWER smbd[25885]: [2023/02/07 16:25:15.275825, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Feb 7 16:25:15 TOWER smbd[25885]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record Feb 7 16:25:15 TOWER smbd[25885]: [2023/02/07 16:25:15.275847, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) Feb 7 16:25:15 TOWER smbd[25885]: Failed to open /var/lib/samba/private/secrets.tdb Feb 7 16:25:15 TOWER smbd[25885]: [2023/02/07 16:25:15.275859, 0] ../../lib/util/become_daemon.c:119(exit_daemon) Feb 7 16:25:15 TOWER smbd[25885]: exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13 Feb 7 16:25:15 TOWER root: /usr/sbin/nmbd -D Feb 7 16:25:15 TOWER nmbd[25886]: [2023/02/07 16:25:15.288876, 0] ../../source3/nmbd/nmbd.c:901(main) Feb 7 16:25:15 TOWER nmbd[25886]: nmbd version 4.17.3 started. Feb 7 16:25:15 TOWER nmbd[25886]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 7 16:25:15 TOWER root: /usr/sbin/wsdd2 -d Feb 7 16:25:15 TOWER wsdd2[25897]: starting. Feb 7 16:25:15 TOWER root: /usr/sbin/winbindd -D Feb 7 16:25:15 TOWER winbindd[25898]: [2023/02/07 16:25:15.351484, 0] ../../source3/winbindd/winbindd.c:1440(main) Feb 7 16:25:15 TOWER winbindd[25898]: winbindd version 4.17.3 started. Feb 7 16:25:15 TOWER winbindd[25898]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 7 16:25:15 TOWER winbindd[25898]: [2023/02/07 16:25:15.353237, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Feb 7 16:25:15 TOWER winbindd[25898]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096 Feb 7 16:25:15 TOWER winbindd[25898]: [2023/02/07 16:25:15.353250, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Feb 7 16:25:15 TOWER winbindd[25898]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record Feb 7 16:25:15 TOWER winbindd[25898]: [2023/02/07 16:25:15.353261, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) Feb 7 16:25:15 TOWER winbindd[25898]: Failed to open /var/lib/samba/private/secrets.tdb Feb 7 16:25:15 TOWER winbindd[25898]: [2023/02/07 16:25:15.353267, 0] ../../source3/winbindd/winbindd.c:1578(main) Feb 7 16:25:15 TOWER winbindd[25898]: Could not initialize domain trust account secrets. Giving up It appears that SMB never started correctly. I suspect this file has the passwords for Samba. Check on your flash drive in the /config folder for the passwd, shadow, and smbpasswd files. You should be able to open them in Notepad. I am going to ping @JorgeB as he is a real Linux Guru. If he does not know the answer perhaps he can point us in the right direction. Edited February 7, 2023 by Frank1940 Quote Link to comment
JorgeB Posted February 7, 2023 Share Posted February 7, 2023 Samba is a little outside my wheelhouse, maybe @dlandoncan help. Quote Link to comment
Steviewunda Posted February 7, 2023 Author Share Posted February 7, 2023 Thanks guys..I'll hold off on the screenshots until this is sorted Quote Link to comment
Frank1940 Posted February 7, 2023 Share Posted February 7, 2023 5 hours ago, Frank1940 said: I suspect this file has the passwords for Samba. Check on your flash drive in the /config folder for the passwd, shadow, and smbpasswd files. You should be able to open them in Notepad. Make sure you do this ^^^^^ Quote Link to comment
Steviewunda Posted February 7, 2023 Author Share Posted February 7, 2023 (edited) Hi Frank1940 - I can open all 3 files in Notepad++. Should I PM them to you? Or supply screenshots? Edited February 7, 2023 by Steviewunda Quote Link to comment
Frank1940 Posted February 7, 2023 Share Posted February 7, 2023 I sent you an Private message... Quote Link to comment
Steviewunda Posted February 8, 2023 Author Share Posted February 8, 2023 (edited) 16 hours ago, JorgeB said: Samba is a little outside my wheelhouse, maybe @dlandoncan help. Hi @dlandon - Frank1940 and JorgeB suggested that you might be able to help with my problem. Frank's last suggestion (via PM) was to run memtest which is 3 hours in with no errors so far. If you scroll up you will see my diagnostics attachment, and the section that Frank thinks may pinpoint the problem. I have a Flash drive backup from before the problem started, if that's any help? Hoping you can help, Steve. Edited February 8, 2023 by Steviewunda Quote Link to comment
dlandon Posted February 8, 2023 Share Posted February 8, 2023 2 hours ago, Steviewunda said: Hi @dlandon - Frank1940 and JorgeB suggested that you might be able to help with my problem. Frank's last suggestion (via PM) was to run memtest which is 3 hours in with no errors so far. If you scroll up you will see my diagnostics attachment, and the section that Frank thinks may pinpoint the problem. I have a Flash drive backup from before the problem started, if that's any help? Hoping you can help, Steve. I would restore the flash from a backup. Quote Link to comment
Steviewunda Posted February 8, 2023 Author Share Posted February 8, 2023 1 minute ago, dlandon said: I would restore the flash from a backup. The whole flash drive, or just the config folder? Quote Link to comment
dlandon Posted February 8, 2023 Share Posted February 8, 2023 1 minute ago, Steviewunda said: The whole flash drive, or just the config folder? Config folder to start. The rest of it if it still has problems. Most likely config corruption. Quote Link to comment
Solution Steviewunda Posted February 8, 2023 Author Solution Share Posted February 8, 2023 Thanks - i'll try that when memtest has had a good run Quote Link to comment
Steviewunda Posted February 9, 2023 Author Share Posted February 9, 2023 14 hours ago, dlandon said: Config folder to start. The rest of it if it still has problems. Most likely config corruption. Memtest ran for 20 hours with no errors, so I replaced the config folder with an earlier one, and all appears good - even Prowlarr configuration which was done after the backup used, and which I expected to lose. SMB networking is working as it should - many thanks to all! 1 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.