Esaias Tilly

Hi! I'm not sure if this is a feature or not, but I'll try my luck either way. I'm currently running two servers, but both are using the same UPS. One server is running UNRAID 6.8.3 and the other one is running Ubuntu Server 20.04.2 straight on bare metall. The UNRAID server currently is the one which is connected to the UPS and can see the status, but of course I want to be able to safely shutdown my Ubuntu server as well. I probably could buy another cable and plug it in, but before doing that, as I am a student currently, I would like to check if there is a *free* way of doing this. Is there a way for me to communicate the UPS status via Ethernet between the two servers? The switch they're both connected to is also running on the UPS, so communication between them should work even in a power-outage.

I've done that multiple times. I did install the latest beta, but with no luck. One thing I did get to work is installing a Samba docker, but even that crashed when I loaded all my thousands of thousands of files on it. And to be clear, when I've tried to get Unraids SMB I didn't use all my files directly, just after getting the Samba docker to work. So the cause is not my amount of files.

Yeah, no. It's a problem with Unraid. Nothing can connect. Not Windows, Mac or Linux and according to the SMB service it self in Unraid, it won't start. So, no, it's not Windows.

It's so sad that this great OS just can't get something as simple as SMB to work reliably. I still have this problem and I've done everything I could even come up with to find a solution. Currently thinking of just changing OS instead.

Hi! I've had this problem with my UNRAID server for a while now and I've tried to get help earlier in this post, but nothing has really changed. I've now done a full reinstall of my entire UNRAID server and can still not get the SMB server to work. Attached you have the entire diagnostics, but the part I found interesting is: Jul 11 08:43:43 KNORRHANE emhttpd: shcmd (12): /etc/rc.d/rc.samba start Jul 11 08:43:43 KNORRHANE root: Starting Samba: /usr/sbin/smbd -D Jul 11 08:43:43 KNORRHANE kernel: traps: smbd[3806] general protection ip:14b9e19d1f94 sp:7ffdead50920 error:0 in ld-2.30.so[14b9e19c6000+20000] Jul 11 08:43:43 KNORRHANE apcupsd[3795]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Jul 11 08:43:43 KNORRHANE apcupsd[3795]: NIS server startup succeeded Jul 11 08:43:43 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 3806 Segmentation fault /usr/sbin/smbd -D Jul 11 08:43:43 KNORRHANE root: /usr/sbin/nmbd -D Jul 11 08:43:43 KNORRHANE kernel: traps: nmbd[3809] general protection ip:1475f06f7f94 sp:7ffd5b39ffd0 error:0 in ld-2.30.so[1475f06ec000+20000] Jul 11 08:43:43 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 3809 Segmentation fault /usr/sbin/nmbd -D Jul 11 08:43:43 KNORRHANE root: /usr/sbin/wsdd Jul 11 08:43:43 KNORRHANE kernel: traps: testparm[3812] general protection ip:152259071f94 sp:7ffdb568a340 error:0 in ld-2.30.so[152259066000+20000] Jul 11 08:43:43 KNORRHANE root: sh: line 1: 3812 Segmentation fault testparm -s -l --parameter-name="netbios name" 2> /dev/null Jul 11 08:43:43 KNORRHANE root: sh: line 1: 3814 Segmentation fault testparm -s -l --parameter-name="workgroup" 2> /dev/null Jul 11 08:43:43 KNORRHANE kernel: traps: testparm[3814] general protection ip:15260098cf94 sp:7ffc2b21b620 error:0 in ld-2.30.so[152600981000+20000] Jul 11 08:43:43 KNORRHANE root: /usr/sbin/winbindd -D Jul 11 08:43:43 KNORRHANE wsdd[3816]: Failed to listen to UDP port 3702 for WSDD Jul 11 08:43:43 KNORRHANE kernel: traps: winbindd[3817] general protection ip:14ce7c00ff94 sp:7ffe841cd2d0 error:0 in ld-2.30.so[14ce7c004000+20000] Jul 11 08:43:43 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 3817 Segmentation fault /usr/sbin/winbindd -D Jul 11 08:43:43 KNORRHANE emhttpd: shcmd (12): exit status: 139 Here I get some kind of a "Segmentation Fault", which from all my googling, still can't understand what it means. What I do know is that because of this Windows 10, Ubuntu and Mac OS X can't see the SMB server. Does anyone have an idea? And YES, I've read and followed the Windows issues with unRAID. knorrhane-diagnostics-20200711-1744.zip

Hi! Earlier this year I updated my UNRAID server to 6.8 from 6.7 and my SMB shares stopped working, so I googled and found nothing that worked. So I downgraded back to 6.7 where SMB workes great! Now, yesterday I got a critical error in UNRAID which made me need to reinstall UNRAID and create a whole new USB-drive, so I just copied over the config files to the new USB-stick. Now I'm back on 6.8.3 and SMB isn't working again, this time I can't downgrade though. When I go to Tools > Update OS, there is no downgrade option. Either way that is not the problem I want to fix, I need SMB to work since I use it for all my work and always work straight towards the server. I have tried everything that I can find on Google and I'm sure it's not a Windows 10 security option since it doesn't work on any operating system. It doesn't work on Windows 10, Ubuntu or Mac OS X. knorrhane-diagnostics-20200623-1340.zip