gcleaves

Members
  • Posts

    41
  • Joined

  • Last visited

Everything posted by gcleaves

  1. 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
  2. Downgraded to 6.1.9 and Samba works again. Pretty frustrated to be stuck on such an old version.
  3. 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...
  4. Can I request the addition of GNU Parallel to the NerdPack, please! https://www.gnu.org/software/parallel/
  5. 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.
  6. 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!
  7. 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
  8. 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
  9. 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.
  10. 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
  11. 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
  12. 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 ###########
  13. 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.
  14. Ah, I have now found the https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later instructions and will follow them and report back.... (It's late here and it looks like this will take a long time, so I'll report back in the morning.)
  15. Hi and thanks for your advice. I've interpreted your suggestion to mean that I should run fsck.reiserfs but I'm not getting very far. See output below. What is the correct way to check the filesystem on disk1? Separately, the following is appearing now and then on the terminal: kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1 Could that have anything to do with my problem or is it just being caused by taking the array offline over and over again? fsck.reiserfs With the array online: fsck.reiserfs /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:28:54 2016 ########### Partition /dev/md1 is mounted with write permissions, cannot check it With array offline: fsck.reiserfs /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 Failed to open the device '/dev/md1': No such file or directory Again with array offline: fsck.reiserfs /dev/sdc1 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/sdc1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/sdc1. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb.
  16. Today I upgraded unRAID to 6.2.3 via the Web GUI and my Samba share are no longer accessible. The shares exported via AFP are accessible. I have rebooted several times. I have disabled/enabled SMB from the Setting tabs to no effect. I don't get any errors in the Web GUI, everything looks good. But I can't access the shares from OSX, Android or Linux devices after the upgrade. I've attached a diagnostic file for any kind soul to have a look at. Thanks in advance! Geoff tower-diagnostics-20161104-2304.zip
  17. I have a single cache drive which is used by all my shares. Why is it so slow to mv a file (/mnt/cache/non-share-folder/bigfile.mov) from a random folder on the cache drive into /mnt/user/Movies? Since the destination of bigfile.mov is on the same drive, it should be near instantaneous. Yet it takes a very long time, as if unRaid were moving the file to a different disk. I can confirm that the file is NOT moved into the array but into the cache drive. Doing a mv /mnt/cache/non-share-folder/bigfile.mov /mnt/cache/non-share-anotherfolder is instantaenous, as expected. Thanks, Geoff unRAID Server Plus 6.1.3 Model: N/A M/B: - CPU: AMD Turion II Neo N54L Dual-Core @ 2200 HVM: Enabled IOMMU: Disabled Cache: 256 kB, 2048 kB Memory: 8192 MB (max. installable capacity 8 GB) Network: eth0: 1000Mb/s - Full Duplex Kernel: Linux 4.1.7-unRAID x86_64 OpenSSL: 1.0.1p Uptime:
  18. Hello, I used to run rescan-scsi-bus when attaching an external escsi drive in order for unRaid to detect it. The process took about 1 second. This no longer works . The process gets stuck and just hangs: root@TOWER:/mnt/user/Files# rescan-scsi-bus -l Host adapter 0 (usb-storage) found. Host adapter 1 (pata_atiixp) found. Host adapter 2 (pata_atiixp) found. Host adapter 3 (ahci) found. Host adapter 4 (ahci) found. Host adapter 5 (ahci) found. Host adapter 6 (ahci) found. Scanning SCSI subsystem for new devices Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, LUNs 0 1 2 3 4 5 6 7 Scanning for device 0 0 0 0 ... OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SanDisk Model: Cruzer Fit Rev: 1.27 Type: Direct-Access ANSI SCSI revision: 06 Scanning for device 0 0 0 3 ... NEW: Calling udevadm settle (can take a while) Any ideas?
  19. Thanks RobJ, look forward to the next release then. I see other, non-unRaid users, with the SYN flood issue on Serverfault: http://serverfault.com/questions/294209/possible-syn-flooding-in-log-despite-low-number-of-syn-recv-connections .
  20. Turns out I had not really rebooted, issuing "reboot" at the command prompt only disconnected my SSH session but did not reboot. I did a hard reset and the server started responding again. But something weird is happening, this is the second time this week that I had to reboot to server.
  21. Is someone attacking me? TCP: request_sock_TCP: Possible SYN flooding on port 6891. Sending cookies. Check SNMP counters. mdcmd (82): spindown 0 mdcmd (83): spindown 1 mdcmd (84): spindown 2 UDP: bad checksum. From 131.221.255.221:1038 to 192.168.1.35:6891 ulen 111 mdcmd (85): spindown 2 mdcmd (86): spindown 1 mdcmd (87): spindown 2 mdcmd (88): spindown 0 mdcmd (89): spindown 2 mdcmd (90): spindown 1 UDP: bad checksum. From 2.103.156.39:60950 to 192.168.1.35:6891 ulen 1410 UDP: bad checksum. From 2.103.156.39:60950 to 192.168.1.35:6891 ulen 1410 UDP: bad checksum. From 2.103.156.39:60950 to 192.168.1.35:1034 ulen 1410 UDP: bad checksum. From 2.103.156.39:60950 to 192.168.1.35:1034 ulen 1410 UDP: bad checksum. From 2.103.156.39:60950 to 192.168.1.35:1034 ulen 28 mdcmd (91): spindown 2 mdcmd (92): spindown 1 mdcmd (93): spindown 2 mdcmd (94): spindown 1 mdcmd (95): spindown 1 INFO: rcu_sched self-detected stall on CPU { 0} (t=6000 jiffies g=8598756 c=8598755 q=41101) Task dump for CPU 0: shfs R running task 0 31679 1 0x00000008 0000000000000000 ffff88021fc03da8 ffffffff8105e0b5 0000000000000000 0000000000000000 ffff88021fc03dc8 ffffffff81060780 0000000000000001 ffffffff81834400 ffff88021fc03df8 ffffffff8107845f ffffffff81834400 Call Trace: <IRQ> [<ffffffff8105e0b5>] sched_show_task+0xbe/0xc3 [<ffffffff81060780>] dump_cpu_task+0x35/0x39 [<ffffffff8107845f>] rcu_dump_cpu_stacks+0x6a/0x8c [<ffffffff8107acb5>] rcu_check_callbacks+0x1db/0x4f9 [<ffffffff81088601>] ? tick_sched_handle+0x34/0x34 [<ffffffff8107ca53>] update_process_times+0x3a/0x64 [<ffffffff810885ff>] tick_sched_handle+0x32/0x34 [<ffffffff81088638>] tick_sched_timer+0x37/0x61 [<ffffffff8107cf9b>] __run_hrtimer.isra.29+0x57/0xb0 [<ffffffff8107d48a>] hrtimer_interrupt+0xd9/0x1c0 [<ffffffff8102f72e>] local_apic_timer_interrupt+0x50/0x54 [<ffffffff8102fb0b>] smp_apic_timer_interrupt+0x3c/0x4e [<ffffffff815fdf7d>] apic_timer_interrupt+0x6d/0x80 <EOI> [<ffffffff8114c555>] ? __discard_prealloc+0xb1/0xb3 [<ffffffff8114c5bb>] reiserfs_discard_all_prealloc+0x44/0x4e [<ffffffff81168de0>] do_journal_end+0x4e7/0xc78 [<ffffffff81169ad0>] journal_end+0xae/0xb6
  22. My server just stopped working a couple of minutes ago. I can SSH but no :80 web interface, 8080 works. I've rebooted to no avail. Can somebody please look at the log and help? Dmesg output found here: http://pastebin.com/Ta5QL7gk I'm running 6 beta 14. Thanks! Geoff