gcleaves

I tried that, no dice

So I've started 6.3.5 in safe mode. I opened the GUI and the array was offline. I brought it online, which took some time, but Samba still doesn't work. Same Mac error as always: There was a problem connecting to the server “TOWER”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator. I'm sure I'm in safe mode: System running in safe mode

Nope, but will try it now! ....

Downgraded to 6.1.9 and Samba works again. Pretty frustrated to be stuck on such an old version.

Thanks puweyxil, but unfortunately this hasn't worked for me. I removed that file and upgraded to 6.3.5 but Samba is still unavailable. Let's see if I still remember how to downgrade...

Can I request the addition of GNU Parallel to the NerdPack, please! https://www.gnu.org/software/parallel/

Indeed the private folder is missing in 6.2, but copying it back and restarting Samba did not work. I see that an identical /etc/samba/private/smbpasswd files is located in /boot/config/smbpasswd, so I guess they've just moved the file. So I'm back to 6.1.9, also. I still haven't tried resetting my Share settings or reconfiguring from scratch as those involve more effort than I have time for at the moment.

I had removed the 32bit inotify plugin by hand and SNAP via the GUI during my troubleshooting. This did not solve the problem. As for not being aware of the repercussions of the <=6.1.x -> 6.2.x upgrade path, I did peruse the documentation before upgrading and only saw the Docker changes as likely to affect me. I don't have multiple NICS or VMs. Maybe my share settings, which have been mentioned, somehow break Samba when moving to 6.2. I will provide answers to @kode54 post when my kids (and wife) give me some time! I have not tried booting in SAFE mode since the box is in a closet with no keyboard or monitor near. Will try that eventually, but will first look at the share settings. P.S. I installed Community Applications, too!

You can download the release from here: https://lime-technology.com/download/ . Unzip it and then copy the bzimage, bzroot and bzroot-gui files to the /boot/ directory of unRAID. Reboot and you'll be on the latest version. More info here:http://lime-technology.com/forum/index.php?topic=49360.0

This update failed for me coming from 6.1.9. Samba shares became inaccessible from Android, Linux and MacOS devices. Even a loopback Samba attempt from the server itself fails. I tried installing 6.3.0 RC4 and Samba still didn't work. I also tried 6.2.1 unsuccessfully. I couldn't find a download for 6.2 stable. I finally reverted back to 6.1.9 and Samba once again worked. I opened a thread in General Support but nobody helped me. Can anybody help me here? I see that the 6.2 releases included some security fixed for Samba, could that be a clue? Weird that I'm the only person reporting this though... Thanks! Geoff

I upgraded to 6.3.0 RC3 and SMB still didn't work. I downgraded to 6.1.9 and SMB works agains. Now I'll try 6.2.1. Samba on 6.2.1 doesn't work for me either. So I'm back on 6.1.9. Let's see if Docker images are working... They are! I read something about the API changing between 6.1.9 and 6.2, maybe that only affects unRAID's web GUI controlling the images and containers.

The server can't even connect to itself. From the command line on unRAID: root@TOWER:~# smbclient -L \\\\localhost --no-pass WARNING: The "null passwords" option is deprecated WARNING: The "syslog" option is deprecated WARNING: The "syslog only" option is deprecated protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED C'mon friends, any ideas?!?! root@TOWER:~# netstat -tulpn | egrep "smbd|nmbd|winbind" tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1390/smbd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1390/smbd udp 0 0 172.17.255.255:137 0.0.0.0:* 1388/nmbd udp 0 0 172.17.0.1:137 0.0.0.0:* 1388/nmbd udp 0 0 192.168.167.255:137 0.0.0.0:* 1388/nmbd udp 0 0 192.168.167.35:137 0.0.0.0:* 1388/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 1388/nmbd udp 0 0 172.17.255.255:138 0.0.0.0:* 1388/nmbd udp 0 0 172.17.0.1:138 0.0.0.0:* 1388/nmbd udp 0 0 192.168.167.255:138 0.0.0.0:* 1388/nmbd udp 0 0 192.168.167.35:138 0.0.0.0:* 1388/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 1388/nmbd

How do I get Samba to start logging so I can look for clues? All the log files are completely empty. Ok so I see the logs are sent to the syslog. Everything looks normal in the syslog, yet I can't connect to SMB shares from any of my devices. Nov 5 13:42:01 TOWER emhttp: shcmd (15074): /etc/rc.d/rc.samba start |& logger Nov 5 13:42:01 TOWER root: Starting Samba: /usr/sbin/nmbd -D Nov 5 13:42:01 TOWER root: /usr/sbin/smbd -D Nov 5 13:42:01 TOWER root: /usr/sbin/winbindd -D Nov 5 13:42:01 TOWER emhttp: shcmd (15075): cp /tmp/emhttp/smb.service /etc/avahi/services/smb.service Nov 5 13:42:01 TOWER avahi-daemon[5312]: Files changed, reloading. Nov 5 13:42:01 TOWER avahi-daemon[5312]: Service group file /services/smb.service changed, reloading. Nov 5 13:42:02 TOWER avahi-daemon[5312]: Service "TOWER" (/services/smb.service) successfully established. Is it expected to have several processes running at the same time? root@TOWER:/var/log/samba/cores# ps ax | grep smb 5255 ? Ss 0:00 /usr/sbin/smbd -D 5257 ? S 0:00 /usr/sbin/smbd -D 5258 ? S 0:00 /usr/sbin/smbd -D What next? Revert to 6.1.9? Will I need to recreate my docker containers? Or a fresh install of 6.2.3 overwriting my current install? Geoff

No problems on disk2 either: root@TOWER:~# reiserfsck --check /dev/md2 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sat Nov 5 09:12:24 2016 ########### Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 445691 Internal nodes 2829 Directories 2968 Other files 30330 Data block pointers 446914974 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Sat Nov 5 10:24:20 2016 ###########

No problems on disk1. Checking disk2 now. It doesn't feel like a filesystem problem since AFP works... root@TOWER:~# reiserfsck --check /dev/md1 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Fri Nov 4 23:58:50 2016 ########### Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 608436 Internal nodes 3833 Directories 275806 Other files 234222 Data block pointers 583131092 (5328152 of them are zero) Safe links 0 ########### reiserfsck finished at Sat Nov 5 01:29:51 2016 ########### Any other ideas? Still can't access SMB shares.