Anon

Yeah the names are stored here: After deleting the other files it still had the references to those names saved in those files. So once I recreated the user it read that information and set the perms accordingly.

Hello everyone. I got it working again. Step taken: - Took the USB Stick and saved the config colder - Flashed the USB Stick with the USB-Creator - Copied the config folder back onto it -> Same Error - Removed the following files: "passwd", "secrets.tdb", "shadow", "smbpasswd" - Restarted -> SMB Working Then I just had to recreate the users. But the awesome thing was I only need to set the name and password. The exact permissions on the shares were retained in the share config. So it only took ~2 min to get all users back and now its happily chugging along. Thanks so so much for all your help

I did the Upgrade via the internal updater. The update was succcessfull but the error is sadly still there Idea: Is it possible to just delete all contents of the config? If so I would back up the current config. Then delete everything. Reboot. Set up one share to export and create one test user. That way I could test that smb at least works if I start completely fresh. Then I either go from there and manually configure everything again. Or I can copy over a few of the backed up files (depending on which are safe to copy back and which could be related to the smb error)

As I created the USB Stick from a backup that might have already been corrupt: - 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? Another Idea would be to use the internal Upgrade System that is available. It is showing me that the new version is available but I am not sure if it will be as fresh of a system as writing it completely new.

Hello dlandon, I have now switched to a totally new USB-Drive as the other one didn't recognize anymore on my windows PC when I went to analyze it further. I redid your steps above and still getting the same error. With the Port 445 -> I fully disabled Docker to test around and have zero VMs running on that machine. I do believe the error is somewhat related to the corrupt secrets.tdb as its a totally different size than my other 2 servers and to franks. But deleting it only makes it recreate the same corrupt version..

Hello Dlandon, thanks for your reply. The Gateway and DNS ist correct. I could change to static IP but I have also just set my router to give it a static IP via MAC-Address And yes I can ping the Unraid Server both via IP and Name. And the Access does not work neither with IP nor Name. The Domain was indeed loesle but currently I do not want to use it via AD. I have turned SMB Support fully off and back on again. which sadly didn't change it. So now I have disabled/enabled netbios for SMB and disabled and reenabled bridging for Network. Afterwards I started the array back up => Still same error on main PC and VM I tested it with. The troubleshooter still gets me the following error: If I do the same with a known wrong IP to cause the same error message it gets me a different result: So it is detecting something. I also turned on the HTTPS support thanks!

Thank you. My most critical services run as a docker and those can still access the files so its not too bad for now. I'll go to bed soon anyways and check back in tomorrow. Thanks so much for your help so far! I hope I can find out how exactly this secrets.tdb is being created and fix it at the root.

Sadly the secrets.tdb gets recreated to the same wrong size after reboot. And the error still appears.

Thanks the size difference does seem to be a great indicator that the secrets.tdb is the problem. All my servers and old backups have it at the 430 size. Thanks I will rename it to old and see what happens after a reboot => After stopping array it recreated the same secrets.db with the wrong size. I deleted that one and then restarted. Lets see what happens

I am not quite sure what the best way forward would be. I could let the USB creator just flash a working happy version without problems onto my usb-drive. But if I then just copy almost everything from the config folder to the drive I am not sure if it will solve the issue. And if I do not copy it over I would probably have a lot of configuration that would get lost..

Regarding the 3 files: "passwd, shadow & smbpasswd they do look like in your example. Is there a way to maybe just reset all of it? I have no problem with just starting fresh and recreating all necessary users. I have all saved in a password database and could easily recreate them all and associate them to my shares That said I did recreate 2 users already and then used a Testing VM to try accessing the SMB Shares but no luck

Here the contents of the WORKING Unraid Servers config folder:

On my Flash drives config I have the following files: On my other Server that is working perfectly I do not have a "share.cfg" file. Could this be a potential cause? (I could try deleting it / renaming it?) I do not know why this file was created and what exact job it has. I do have disk2 disabled currently for shares and am wanting to replace it soon due to some errors.

Hi Itimpi, yes they are all still exported. Some hidden, some normal export and some public export. I even made a new test share -> exported -> public I have also disabled and reenabled SMB in this menu (+ Server restart) sadly error message is still stayin the same. I do have a second and third unraid server running. Those still work as expected. 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. But aside from the smb not working all else seems to be okay...

Hi Frank, thanks for the reply. I am able to see all my users. Following your advice i deleted and recreated 2 of them for further testing. => Rebooted VM -> Same Error. Added the user back to the credential manager + reboot -> Same Error. A while back I had once activated the Active Directory feature in unraid though I had problem so I turned it back of. I currently have some PCs that are in the Domain and some that are not. Before the read only incident the shares where working on both types of PCs. Global Share Settings has Disk on Auto and User on Yes. (This is analog to a second Unraid maschine that I am using that still works just fine.

Hi, this morning after shutting down my Unraid server to do some changes I corrupted my boot drive. Because of this it went to read only mode. I shut my server back down and repaired the drive via checkdisk from windows. Because Checkdisk detected a few problems with the drive I then decided to restore a backup I had previously made. So I ran the usb creator and used the backup file that I took when the usb drive went into read only mode. The server booted fine. No Errors that I could see. All dockers came up and are happily running. After a while I noticed that none of my windows PCs can access any of the SMB shares. Steps tried: - Rebooted a few of my VMs - directly tried to open \\TOWER and \\192.168.50.3 of my Server (as well as directly tring a public no password share) - pinged both tower and 192.168.50.3 -> worked - removed my stored credentials in the credential manager The Error I get: If I click on Diagnose and let it run for a while this shows up: Anyone got an idea what I could try? tower-diagnostics-20240303-2106.zip

Heyo, I personally use ESXI and virtualise a Unraid within it. I find Unraid awesome for the Data storage option with their way of handling a very flexible "unraid". ESXI on the other hand gives me very high flexibility when it comes to actually hosting lots of things in my home lab with failover clusters etc. But to be honest most extra features ESXI offers are not needed for most people. Overall the choice depends on what you want: 1. Focus on Storage / Focus on easiness of use -> Unraid 2. Focus on Hosting / VMs etc. -> ESXI Community Edition Then there is also Proxmox that could be worth a view depending on your needs. Its a bit like ESXI just open source and more homelab suited while ESXI is more Enterprise focused.

Hi, as you still have the backup you can install it to the new usb-stick. The general guide is listed here: https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/ The specific part of the guide that explains how you can put the backup onto the new usb-stick:

Hi, this part of the official guide covers it: https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/ search for "What if I can't backup my device?" If you still have further questions feel free to ask.

Hello, I am currently facing a problem where the mover is seemingly not working anymore. I have also posted a detailed description with logs etc. here: TLDR: Mover runs as a process. Errors are sometimes thrown. But no write activity to array. In the logs I get the following error multiple times: Feb 5 11:21:17 Tower move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 356: ((: TOTALCACHESIZE += : syntax error: operand expected (error token is "+= ") Can anyone tell me what the cause of this could be? Or in general just some more information on what I could do to hunt down the underlying problem that is preventing the mover from actually moving stuff. Edit: After manually moving most of the files the mover should have moved via "unbalance" I restarted the mover to further troubleshoot. It brought the same error as above a few times but then actually started moving files. Can someone maybe explain how this could have happend? Does the Mover first have to go through and check each file before it starts moving? Or why did it not move a single file for over a hour when running with lots of files needing to be moved vs. starting to move files after only a few seconds when the cache is not very full?

Thanks. I was not sure if this error was a real problem or just expected part. But I will ask in those threads

Thanks for the advice. I have also added the diagnostics

Hi I am having a recent problem where the mover seems to not actually be moving any files. I have the following settings in the mover tuning: tower-diagnostics-20240205-1235.zip I also activated mover loggin in general. I have attached the log I have been getting since I started the mover (log_System.txt) I have also attached my moverignore.txt (moverignore.txt) While looking at the processes and logs the mover does seem to be doing things. Its always around 15% CPU but did run a few error log entries as well. The process running is called "age_mover" which I assume comes from the mover tuning plugin itself. I can't actually detect any movement happening as most of the time my array states no write activity on the array at all. Can someone help me? Or help me raise the log level to get even more detailed logs to see what the mover is actually trying to do? I have no Age setting enabled so I would have thought it would just start moving some files once I start the process. And the shares in question are set to move the files to the array:

Hello, I have recently activated the Active Directory Integration via SMB with Unraid. With this I am able to set permissions for the different shares with active directory accounts. Since I added this I am having lots of difficulties getting it to work as I want it to... Example: I set Unraid to default use Administrator as Owner and "Enterprise Admins" as Creator Group. I set it to be exported but as private with nobody having access At this Point I can access the Share from any of my windows maschines no matter what Active Directory account. I now go into "Permissions" of the Share from a Windows Maschine and delete the "Everyone" entry to reduce access to only my admin Accounts. After I press delete and Apply it reappears immediately. But now I can access it with my admin accounts but not with my other ad-users (in this example my "plex" user) I now add "plex" as a new user and give them read and write permissions. This causes "Creator Owner" "Cretor Group" to also appear. At this point I can still not access the folder with that plex user. I tried playing around with it more with deleting everyone creator etc. and then lost full access so I repared the permissions with the included tool in the unraid webui and now "nobody" is owner of the share again. At some point with my tests I also got it to sorta work but when removing permissions for my plex user I was still able to delete the files he created as he was still set as the owner. All this is really frustrating and I feel I am doing something fundamentally wrong. Can somebody tell me how to correctly manage unraid share permissions with active directory accounts? Goals: - Local Unraid Users can still access it if their permissions are set - The set Admin Groups can always read / write - Specific Users can be set to read and or write and might also be switched around occaisonally. (e.g temporarily giving a user write access but afterwards disabling it again to protect against encyption viruses)

Alright it ran through without Errors: Smart Report: ST18000NM003D-3DL103_ZVT4RXT3-20230428-0826.txt Does this mean I can just ignore this and assume this could have been a one time thing? From what I understand the extended Test goes through the whole disk so all sectors should work?