October 26, 20241 yr from what I can see samba is constantly starting, failing, and then restarting again. I have no idea why this is happening. I recently updated from 6.8 to 6.12 so im sure that has something to do with it but Ive reset settings to default on everything as far as I can tell and it still is like this. any help would be appreciated. syslog.txt
October 27, 20241 yr Community Expert Oct 20 19:40:46 Drakas1 emhttpd: error: put_config_idx, 610: Invalid argument (22): fopen: /boot/config/shares/?.cfg Check the /config/shares on the flash drive, and delete that file or any invalid looking cfg file.
October 27, 20241 yr Author so i did that and theres this one share named '?' that keeps coming back for some reason. i delete it and it comes back on restart.
October 28, 20241 yr Community Expert You likely have a container with a wrong mapping creating that, stop the docker service, and see if it still comes back, if it doesn't, then start enabling one container at a time.
December 3, 20241 yr Author sorry for not updating, life got in the way, but I've removed all my docker containers (except for plex and this esp home container I can't get rid of) now trying to figure out what's going on. I can access it from my Macbook over the network but not my windows pc, so that's an improvement I guess? attached is the most recent syslog syslog.txt
December 4, 20241 yr Community Expert 11 hours ago, miniclip1371 said: I can access it from my Macbook over the network but not my windows pc Do you mean the GUI or shares?
December 5, 20241 yr Community Expert That suggests a Windows problem, if you are using W11 24H2 see here: https://forums.unraid.net/topic/177975-formatted-my-pc-and-installed-fresh-windows-11-now-cant-access-smb-shares/?do=findComment&comment=1478526
December 10, 20241 yr Community Expert If it's working with the Mac it still suggests a Windows issue, take a look at this thread:
December 13, 20241 yr Community Expert Try with another Windows PC/Laptop, or you can also reinstall Windows.
December 26, 20241 yr Author Solution On 10/28/2024 at 5:02 AM, JorgeB said: You likely have a container with a wrong mapping creating that, stop the docker service, and see if it still comes back, if it doesn't, then start enabling one container at a time. this was the original solution and the network issue for my windows machine did fix itself. i think resetting stuff with my vpn fixed it, though to be honest im not 100% sure. thanks again for your help
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.