Frank1940
-
Posts
9,879 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Frank1940
-
-
That second post were both minor items and intended more as information. The second item was provided as a possible method for creating a directories on the server uploading a few files from your PC to the server. (Doing so will give you a few directories and files to look when things are finally working properly.)
This first post is the one that you should be concerned about preforming:
9 hours ago, Frank1940 said:First, are you running Windows 10 or Windows 11?
In either case, go to the SHARES tab on the GUI, click on the photos sharename. This should open up the settings page for the 'photos' share. Scroll down to SMB settings. Make that the following settings are as shown:
Click on 'APPLY' as required.
Next, let's try something new--- A replacement for Network Neighborhood. (You are a tiny bit of guinea pig from this point forward...)
1--- Open up Windows File Explorer.
2--- In the Address Bar, type either:
\\ENGTRIAL or \\192.168.1.66
(Which one works will depend on which one you set up with a 'Windows Credential' in Windows Credential Manager)
3--- You should now see a folder icon labeled "photos". You should be able to explore it.
Report back on your results. And we will go on from there with our trial...
EDIT: Reboot your Windows computer before you start. You will also have to reboot Windows if you change any settings on your Windows machine. (Windows network settings are rather persistent and a reboot is the only easy way to guarantee that Windows is in the configuration that you think it is!)
Once you report back on what you find as you go through these procedures, I will have some thoughts about where we go from here. It is especially important that there is a SMB user listed and that you have turned on read/write privileges for that user. (You should also have already set up a Windows Credential for that user on your Windows PC!)
-
12 hours ago, LRBP said:
Here it goes:
One minor item, you are exporting the share appdata and that share is an internal share used by Unraid. You should not be attempting to save any data in it.
The same is true of the shares domains isos and system
Second minor item. If you install (or have installed) the Dynamix File Manager plugin (using the APPS tab), you can upload and download files to Shares using the GUI from your PC. This will work even if you don't have SMB access.
-
First, are you running Windows 10 or Windows 11?
In either case, go to the SHARES tab on the GUI, click on the photos sharename. This should open up the settings page for the 'photos' share. Scroll down to SMB settings. Make that the following settings are as shown:
Click on 'APPLY' as required.
Next, let's try something new--- A replacement for Network Neighborhood. (You are a tiny bit of guinea pig from this point forward...)
1--- Open up Windows File Explorer.
2--- In the Address Bar, type either:
\\ENGTRIAL or \\192.168.1.66
(Which one works will depend on which one you set up with a 'Windows Credential' in Windows Credential Manager)
3--- You should now see a folder icon labeled "photos". You should be able to explore it.
Report back on your results. And we will go on from there with our trial...
EDIT: Reboot your Windows computer before you start. You will also have to reboot Windows if you change any settings on your Windows machine. (Windows network settings are rather persistent and a reboot is the only easy way to guarantee that Windows is in the configuration that you think it is!)
-
7 hours ago, LRBP said:
It has been while trying to use the server's name, not the IP address. The IP address was good to allow me to setup and manage the server, but I haven't been able to make the server visible to my PC or my wife's Mac regardless of which one I use (IP address or server name). This has been the problem since the start. Now, from what I've gathered by Frank1940's reaction to the latest system log, we have corrected a bunch of other issues but the server visibility problem remains.
OK. Years ago, it was possible to access a Unraid by both the IP address and the server-name. (This was a backdoor to allow two connections to the same server from the same client. It was a useful trick in some cases...)
Now for many years, MS has stated that only one connection to a server was to be allowed from any Windows client. (But the above backdoor still existed!) A year or two ago, I noticed that I could no longer do this. I could access the server by either the IP Address or its server-name. As soon as I had a connection with one or the other, the other one was blocked. Now, I don't know if MS finally blocked this backdoor or what else might be going on but since I had no real use for it, I didn't pursue the matter.
It does not make any real difference but you might want to go into your router settings and reserve that IP address for your server so the DHCP process will always assign it to your server. (Most routers have this capability but they implement it in different ways...)
-
@LRBP, Also a screen shot of the SHARES tab. You can redact info as you feel necessary as shown below:
On 3/7/2024 at 4:03 AM, LRBP said:The one issue I still had was with including the server in the Neighborhood Network (following the "Unraid & Windows 10 SMB Setup" instructions) because the Windows File Explorer can't find it.
Are you saying that you are now only having a problem getting Neighbor Network set up and working or or is there a larger SMB issue with accessing your files from your Windows clients?
-
8 minutes ago, Mbeaver5555 said:
The files I'm Syncronising only need to move up one folder.
IF you install Dynamix File Manager and work at the disk level, you can do exactly what you want. See below:
I just tested and it works. Only the files pointers were changed.
-
@bonienl, could the Dynamix File Manager help out in this situation?
@Mbeaver5555, you do have to be careful moving files in Unraid. (Moving files between User Shares and Disk Shares can result in data loss!) It sounds to me that you will need to be working with the Disk Shares to safely do what you want to do. -
I would start by attaching a monitor and keyboard to your server. Restart the server. (Quick push on power button should result in a clean shutdown. Long push will force a unclean shutdown...) During the restart, pick one of the GUI options from Unraid's boot menu.
You should now be able to 'fix' the Docker container.
-
BTW, you can make that backup of the Flash drive directly to your download directory/folder on your PC by clicking on the 'Flash' under "boot Deice" on the MAIN tab of the GUI. Then click here:
I am posting for more for the other Unraid users who are also making backups of their flash drive that end up on the array than for you. If you are doing this, realize that the backup will not be readily available when you most need it!!!!
-
2
-
-
You might want to make a bootable UBS drive with a Live Linux distribution on it. Use it to boot your Unraid server and see if you can find the backup of your Unraid flash drive on one of the data disks.
-
1
-
-
@eras, here is the cost of an official MS license to run Windows 11:
Granted the no OEM would be buying hundreds/thousands of these packages but instead they would approach MS directly to negotiate a bulk purchase of a certain number of licenses. This offering is intended for those folks who assemble a computer using individual components and need/want a legal license for it.
Any other way of installing Windows 11 on a new computer is a violation of the Digital Rights and Copyright acts (in the USA) regardless of the work-arounds that many have used.
And take look at the pricing structure of Adobe Photoshop. It appears that the marketing model that they are using is working in their case.
If Unraid has made a mistake, it is that is advertises what it sells as an OS. They didn't write an OS (the core of their software is a standard Linux distribution). They are selling a NAS with several additional capabilities (plugins, Docker and VMs) merged into it. It is a much more limited market than what MS is serving. The fact that MS is loosely-goosey with their license enforcement of their OS products may actually be a business strategy to sell their other software. (Most Windows computers have trial versions of other MS software installed on it and you have to pay to activate when the trial expires!) Unraid has no side software line that it is selling. It is not collecting data from its users that it is marketing. Its sole stream of income is sale of its NAS software.
The bottom line is that Unraid needs a more steady flow of income than a single purchase of a lifetime license can give. They are attempting to honor a promise to their old clients who purchased their software with that understanding. The problem is now how to price their product to provide an income stream to support, maintain, and provide future enhancements and to attract new customers. No pricing policy is going to make everyone happy. In the final analysis, their new pricing policy has to generate more income than their current plan does. ...And it has to be attractive enough to make enough people willing to buy into the price plan that they finally adopt.
As side case, I use Bitwarden password manager. They have a free version that has virtually all of the features that their $10 per year individual subscription plan does. Those few additional features (two that we use are hardware keys verification and collections) are worth the $20 per year for my wife and myself. There are many password managers-- some free and some with annual fees ---that I considered. I evaluated many of these and make a decision that Bitwarden made the most sense for us. It wasn't the cheapest plan but cost was a consideration.
-
1
-
-
Every BIOS is different-- Even for similiar MB's from the same manufacturer. This makes offering solutions for these types of problems very difficult. Sometimes even a close reading of the manual will not answer some questions. @IWasBornOnAWaterMoon, I would be googling the problem. Keep asking Google with variations of the problem until you find the answer. You can also look at every screen in the BIOS to see if, buried deep down in the menu setup, there is another option for setting boot order.
-
On 3/1/2024 at 4:40 PM, LRBP said:
Also different from your script I don't have any instances of "user" as owner.
'user' is the name (which I choose) for one the Share Access users. (I know it is not an ideal choice for a name when I am attempting to explain something to a third party...) As I said, the 'owner' is not important as each Share Access user is a member of the users group and that users group has the same privileges as the 'owner'. (It can make a difference if the owner is not member of the users group. But, as I see it, that could only happen if a Docker container or VM were set up incorrectly.)
I did not find any errors in this syslog but I am still puzzled by the name. Did you generate this diagnostics file by going to Tools >>> Diagnostics using the GUI and did the file download to the download directory/folder of your PC? Normally, it would be engtrial-diagnostics-20240304-0751.zip but this a side issue....
Let's move on. Microsoft has set up all recent releases of Windows with restrictions for accessing servers. (Remember, that MS is far more interest in the security needs of corporate, government, and business users than people with home networks!) The easiest way is to conform and set things to follow their rules. Here is a link to the way to do this:
https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/
There are instructions in the first post as well a link to a PDF file. You said you were using a WiFi connection. Be sure that you have the Network type (look at the last update in the first post) set to 'Private'. ('Public' is for those times when you make a connection to a 'hotspot' at McDonald's or an airport.)
-
Try this during the POST routine of the MB startup (From the Manual):
-
28 minutes ago, Anon said:
Removed the following files: "passwd", "secrets.tdb", "shadow", "smbpasswd"
Good to know. So all of the SMB settings are in those four files. And deleting them will allow one to completely reset the SMB configuration. (Now, if I can only remember that fact the next time someone posts up with a similiar problem...) Also good to know that the Share permissions are not a part of the SMB configuration.
-
37 minutes ago, Anon said:
- Could it be a viable idea to just make a fully fresh system with the USB-Flash Creator (V. 6.12.8) and then copy the config files from the current backup (V 6.12.6) onto it?
If you go down this route, use a new quality USB drive, install a trial license, and make sure that SMB is working. Then make a back-up that new flash drive. Instructions are here (if you need them):
https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#backing-up-your-flash-drive
(I am suspecting that there are some corrupted files on that flash drive...) When you get that new flash drive working, you can transfer the old license to that new drive.
-
Let me ping @dlandon as he seems to have some knowledge in the area. I don't think he is based in the USA so it may be a while before he responses...
-
You don't have to delete file, just rename it to secrets.tdb.old
-
You do have a secrets.tbd file in the /config folder on the flash drive on both of your servers. (I believe this file is copied from the Flash drive to the RAM disj as Unraid boots up.) I looked at my two servers and the size on both servers is 420KB (430,080 bytes). (Both are these server are configured almost identically so this was not surprising.) On your working server, the size was 430KB. What is the size on the one with the problem?
Here is one result of a Google search on Unraid net for secrets.tdb:
https://forums.unraid.net/topic/149487-how-do-i-fix-these-samba-errors/
And a second one:
https://forums.unraid.net/topic/38469-smbd-fails-to-start/
-
10 minutes ago, Anon said:
Maybe something went bad due to the backup restore? I did take the backup during a phase where unraid put the usb stick in a errored state.
That is a distinct possibility. (I make it a practice to always make a backup of the boot drive any time I update the system as soon as I am sure it is running properly.)
-
Problem is that I suspect that you should not have any reference to the secrets.tdb file in your syslog. ( You could check this on your other server...)
A quick google of the file name confirmed that is involved in the Samba password scheme. With an error message that indicates a problem with that file, I would suspect that you would have a problem.
In the /config Folder on your flash/boot drive, you will find these three files:
You can open then with a straight text editor (Even NotePad with recent Windows releases will handle these files correctly) and have a look at them. All of the should look something like this:
You could also look at these files on your other server.
I know that if you forget the passwords, the following procedure can be used to reset all the passwords for both root and Share Access users:
https://docs.unraid.net/unraid-os/manual/troubleshooting/#lost-root-password
-
Found this:
Mar 3 19:05:07 Tower winbindd[13208]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Mar 3 19:05:07 Tower winbindd[13208]: [2024/03/03 19:05:07.912296, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Mar 3 19:05:07 Tower winbindd[13208]: tdb(/var/lib/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096 Mar 3 19:05:07 Tower winbindd[13208]: [2024/03/03 19:05:07.912313, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Mar 3 19:05:07 Tower winbindd[13208]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record Mar 3 19:05:07 Tower winbindd[13208]: [2024/03/03 19:05:07.912325, 0] ../../source3/passdb/secrets.c:67(secrets_init_path) Mar 3 19:05:07 Tower winbindd[13208]: Failed to open /var/lib/samba/private/secrets.tdb Mar 3 19:05:07 Tower winbindd[13208]: [2024/03/03 19:05:07.912332, 0] ../../source3/winbindd/winbindd.c:1578(main) Mar 3 19:05:07 Tower winbindd[13208]: Could not initialize domain trust account secrets. Giving upOn the GUI, go to USERS and see that you still have the Share Access users in place. ( You might want to recreate them...) Are you using Active Directory?
GUI again, go to SETTINGS >>> Global Share Settings and verify that you have enabled 'User Shares' and 'Disk Shares'
I believe you have a lot of hidden shares. There was an instance a while back where a user had problems accessing hidden shares.
-
1 hour ago, ManBullMoose said:
Seems like I have a bad ground somewhere that may have caused this. Whether it is the UPS or the wall, I'm not sure. I do remember updating every socket in this room a few years ago.
Start with one of these:
(Not an endorsement of this specific device, but an example of a tool available to help you figure out what it going on...)
-
1
-
-
To give the GURUs a bit more information, please attach the diagnostics file to your next post in this thread.
Failure to detect server from PC or Mac
in General Support
Posted
First thing, In that PDF file, "Unraid & Windows 10 SMB Setup.PDF"**, read the section on "Setting Up the Unraid Server and the Windows 10 Client" and use the instructions in Case1, "Case 1– Setting up Unraid and Windows 10 without Using Insecure Guest Access" and use those instructions to set up both your server and Windows PC client.
You will have to reboot the Windows client when you are finished to test that it works. That should allow Windows and Unraid to handshake and log you into the Unraid server automatically the first time you access the server after each client reboot. (This operation will be completely transparent to you!)
When this is working, the next issue to be addressed will be to integrate it into Windows File Manager. I have some thoughts on how to do that. But let's get this step working first...
==========================================================
** Link in this post:
https://forums.unraid.net/topic/155588-failure-to-detect-server-from-pc-or-mac/#comment-1378295
I would suggest actually printing out the file so you have a paper copy in front of you as you perform each step.