Frank1940

You have a static address (192.168.0.33) assigned to your 10Gb card. Did you reserve that address on the Router? You are using the same 10Gb card as in the old system? (A new card would have a different MAC address which confuse the router.) Look on the Main page of the GUI and verify that the array is started. Make sure you have your Unraid server set up to become the Local Master. (Settings >>> SMB >>> Workgroup Settings) What error messages are you getting back from your client computer. PS--- My assumption is that you are accessing the GUI from a client computer.

I think this is a problem with definitions... A "post" is an single message in a "thread". This message by me is a 'post' in this 'thread' entitled "Replaced Motherboard/CPU but now cannot access shares from any PC?". On this Forum, threads are officially called "Topics". (Understand that I started out back in the early 1990's with dial-up and local BBS's. The Internet came later!) The reason for a new post is so that people realize that you have added more information to the thread. IF you put that diagnostics file in the (for example) in your first post, no one will realize that you did so as that is not considered by the BBS software as new information to the thread and it does not flag the thread as having new information. The volunteers who monitor this board will never realize that you provided the requested information unless they were to reread the entire thread! To summarize you always want to add new information to a new post at the end of the thread. If you must edit an early post (other than the last one) for anything but grammar, you should consider a new post indicating that you did modify an earlier post.

Get the diagnostics file and upload it in a NEW post in this thread.

I3 or I5 or I9 processor? As the 13600K is available in all three lines. (I could also ask if you are overclocking this processor as that has an impact of power consumption...)

Check your Junk/Trash/Scam folders for your e-mail program. And I will ping @SpencerJ as he is generally the person who fixes these issues.

I believe there are real security issues if you are using NFS to access your files or you have allowed access directly to the Array from a Docker or VM. (More simply put, in any situation where you are allowing access to the files on the array and not using SMB.)

Look carefully at the BIOS setup for boot option settings. You may find two or three 'pages' where the boot parameters can be set. Be sure the Unraid boot drive is plugged into to a USB2 port when looking through the BIOS settings. I seem to recall that some folks have had to designate/assign the flash drive as a hard drive. Some times there is an option to boot from a USB device. You could also google the problem. (You are probably not the only one who has wanted to boot that PC from a USB drive-- and this desire is probably for some other OS than Unraid...)

It would be my guess that a Docker (or perhaps, a VM) is using this /tmp directory as a place to store files not realizing that it is actually in RAM. You must have a reasonable idea of what application on your server is doing trancoding (Look at the name of the child directory. Check the configuration of the applications and specify that it using a physical device. That will be one that begins with /mnt (and I would recommend using the cache drive or a cache pool.) IF you have more questions, you might get a quicker answer from the Support forum for the application.

You must set a value for this variable for every share on your server to prevent the problem you have just encountered. If you don't, Unraid does not 'know' the size of the file (in advance) you are attempting to write. IF there is not enough disk space for a file, the write will fail. (In this case, I have set 50GB because I know I will will be writing computer image files to this share and I further know that they will be smaller than that value.)

Does it change to an IP address that starts with 172.xxx.xxx.xx or 127.xxx.xxx.xx?

I would be looking at where these torrents are storing their files-- both temporary and permanent. The paths should begin with /mnt as that is where Unraid puts physical devices in its file structure. (Unraid stores its OS files on a sort of RAM disk. If your torrent is mapping any of its files on that device, it can quickly run out of space and crash.) It is also possible to create a RAM disk in /mnt so have a look with the GUI terminal by using the following command: ls -al /mnt Your output should look something like this: If you have cache pools or the Unassigned Devices plugin installed, there will be entries for those devices. If you have an questions about what you see, just post up a screen capture of what the command gives you. /mnt/user/appdata is the normal place where Dockers will store their configuration and a few other files as it is on a physical device.

I just check using my binhex-krusader and I think I know the reason why. When I went to in Krusader to /usr/loxal, I got this: And when I used the GUI terminal and did a listing of the files with it, I go this: Notice that Krusader is missing emhttp directory and The GUI terminal is missing the games directory! What krusader is showing is file structure for the Linux system that is running in the Docker container. Here is what the root of Krusader Docker looks like: The two designated directories are actually the mount points for the file system on the Host system (Unraid OS) that the Docker is running on. Here is the command that mounts the media directory (second one marked) onto the Krusader file system: IF I remember correctly, this originally was /mnt/user but I also want access to the Disk Shares so I modified it. I added the Flash (first one marked)on because I want quick access to the Flash Drive because I often need a quick look at the boot drive contents when assisting on the forum. You should now have enough information to mount the entire Unraid OS as a directory on the binhex-krusader by adding another Host Path.

Also see the YouTube video. It is a bit out dated but this is what I used to figure things out...

Are you running binhex-kruader? If so, did you change these parameters as I suggested in the link provided? That seems to force the process to run with root privileges (for me at least). By the way, this plugin is setup to a file manager for only the Unraid array (that is why the PUID and GUID defaulted to the nobody/users numbers)--- Not the entire Linux OS if that is what you are trying to make it be.

Does this help? https://forums.unraid.net/topic/71764-support-binhex-krusader/page/17/#comment-780475 If it does not, as for help in that support thread.

Does this thread help? https://forums.unraid.net/topic/132136-update-your-legacy-ssl-certificate-now/ If you still have a question, ping SpencerJ in this thread.

Setup the syslog server. Instructions are here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601 In your case, I would suggest using Mirror syslog to flash: option. After the problem occurs again, Shut the server down by pushing the powerswitch for about one second and wait for the server to shutdown normally. (~ 1-2 Minutes). Pull the flash drive and upload the file in a new post.

You have screwed around with virtually all of the security settings that MS and SMB have had to implement in the past half dozen years to keep out the bad guys. You need to think about security if you have any exposure at all. (And I suspect you do after looking up tailscale...) There is a thread that does go through how to set things up to work in the environment that MS considers to be secure. (Occasionally, MS will set/reset SMB security parameters via their monthly auto-updates-- They 'owe' the SMB spec --and people who try to run outside of the box get bit.) You will find a white paper about it in the first post of this thread: https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-10-smb-setup/

Be sure that you try \\vault in Windows Explorer. Right now, \\IP_Address does not work on my computer...

SMB is tricky once you get an error message. One thing to do is to open a Windows 'Command prompt' Terminal and type the following command net use * /delete This will knock all current server connections.

Did you make a credential for this user to this server in the Windows Credential Manager? (Type 'Credential Manager' in the search widow on the Task Bar...) EDIT: Note that you must always access the server with either the server name or the server's IP address depending on which one you used in the credential.

Many installs of Windows10/11 now block 'guest' access privileges to servers. You have to have a valid SMB on the server account for the Windows client to allow access.

You should be posting about this problem in the Support thread for this Docker. When you righticlick on the icon, you will see ? Support --click on that. If you get a page not found error, google unraid.net <NameOfSupportThreadInURL> (I use a <Ctrl-C> to capture this...)

Setup the syslog server. Use these instructions. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601 Since the problem happens rather quickly, use the Mirror syslog to flash method. After the next time it happens-- pull the flash drive, look for the syslog file in the /logs folder/directory. Upload it in a NEW post.

I looked over your diagnostics file and it appears that your new (?) NIC card is being recognized and the driver installed. What I would suggest now is that you shut your server down properly. (A quick push of the power switch should do that. It will take about a minute or two.) Then pull the Flash driver from the server and put it in your PC. Open up the Flash Drive and enter the /config folder/directory. Rename these two files network.cfg and network-rules.cfg by adding .OLD to the end of each file name. Eject the flash drive and put it back in the server and start it up. (During the boot process those two files will be regenerated since they were found missing.) Hopefully that will fix it