What's new

SMB not working unless it's been several hours after reboot AC68U 384.14

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Maybe other Entware packages that might conflict, as Colin alluded to?
Code:
opkg list-installed

So here's an odd one, opkg list-installed is not being recognized now that Samba is working fine. However, Diversion, connmon and transmission are still working as they should.
 
It looks like you pasted the contents of log.nmbd into your terminal session?

I don't remember doing that tbh, but maybe I did by mistake. I've closed/re-opened Putty a few times now so I can't tell for sure. Would that create the extra nmbd processes that Dave asked about?
 
Would that create the extra nmbd processes that Dave asked about?
Probably, because it contains that text which starts with nmbd so the router will think it's a valid command being entered.
Sure thing:

4L13NW4R3@RT-AC68U-15E0:/tmp/var/log# cat log.nmbd
[2018/05/04 23:05:18, 0] nmbd/nmbd.c:861(nmbd_main)
nmbd version 3.6.25 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2018/05/04 23:05:18, 0] nmbd/asyncdns.c:157(start_async_dns)
started asyncdns process 389
:
[2020/01/01 13:39:03, 0] nmbd/nmbd.c:66(terminate)
Got SIGTERM: going down...
[2020/01/01 13:39:06, 0] nmbd/nmbd.c:861(nmbd_main)
nmbd version 3.6.25 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2020/01/01 13:39:06, 0] nmbd/asyncdns.c:157(start_async_dns)
:
[2020/01/01 13:39:25, 0] nmbd/nmbd.c:66(terminate)
Got SIGTERM: going down...
[2020/01/01 13:39:28, 0] nmbd/nmbd.c:861(nmbd_main)
nmbd version 3.6.25 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2020/01/01 13:39:28, 0] nmbd/asyncdns.c:157(start_async_dns)
:

I suggest you reboot your router to clear up any mess and then do a fresh "ps w".
 
Probably, because it contains that text which starts with nmbd so the router will think it's a valid command being entered.


I suggest you reboot your router to clear up any mess and then do a fresh "ps w".

Absolutely, that makes sense! Here's the ps output after a reboot:

Code:
4L13NW4R3@RT-AC68U-15E0:/tmp/home/root# ps -w
  PID USER       VSZ STAT COMMAND
    1 4L13NW4R  5748 S    /sbin/preinit
    2 4L13NW4R     0 SW   [kthreadd]
    3 4L13NW4R     0 SW   [ksoftirqd/0]
    4 4L13NW4R     0 SW   [kworker/0:0]
    5 4L13NW4R     0 SW   [kworker/u:0]
    6 4L13NW4R     0 SW   [migration/0]
    7 4L13NW4R     0 SW   [migration/1]
    8 4L13NW4R     0 SW   [kworker/1:0]
    9 4L13NW4R     0 SW   [ksoftirqd/1]
   10 4L13NW4R     0 SW<  [khelper]
   11 4L13NW4R     0 SW   [sync_supers]
   12 4L13NW4R     0 SW   [bdi-default]
   13 4L13NW4R     0 SW<  [kblockd]
   14 4L13NW4R     0 SW   [kswapd0]
   15 4L13NW4R     0 SW   [fsnotify_mark]
   16 4L13NW4R     0 SW<  [crypto]
   24 4L13NW4R     0 SW   [mtdblock0]
   25 4L13NW4R     0 SW   [mtdblock1]
   26 4L13NW4R     0 SW   [mtdblock2]
   27 4L13NW4R     0 SW   [mtdblock3]
   28 4L13NW4R     0 SW   [kworker/u:1]
   35 4L13NW4R     0 SW   [kworker/0:1]
   36 4L13NW4R     0 SW   [kworker/1:1]
   37 4L13NW4R     0 SW   [mtdblock4]
   38 4L13NW4R     0 SW   [mtdblock5]
   40 4L13NW4R   668 S    hotplug2 --persistent --no-coldplug
  103 4L13NW4R  5596 S    console
  109 4L13NW4R     0 SWN  [jffs2_gcd_mtd4]
  115 4L13NW4R  1416 S    /sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 256 -l 8
  117 4L13NW4R  1420 S    /sbin/klogd -c 5
  205 4L13NW4R  5604 S    /sbin/wanduck
  210 4L13NW4R  4932 S    nt_monitor
  211 4L13NW4R  2096 S    protect_srv
  212 4L13NW4R  5620 S    /sbin/netool
  219 4L13NW4R  5620 S    /sbin/netool
  220 4L13NW4R  5620 S    /sbin/netool
  221 4L13NW4R  1128 S    dropbear -p 10.7.7.1:22 -j -k
  225 4L13NW4R  2096 S    protect_srv
  226 4L13NW4R  2096 S    protect_srv
  227 4L13NW4R  4932 S    nt_monitor
  228 4L13NW4R  4932 S    nt_monitor
  230 4L13NW4R  5088 S    nt_center
  233 4L13NW4R  5088 S    nt_center
  234 4L13NW4R  5088 S    nt_center
  235 4L13NW4R  1276 S    /bin/eapd
  237 4L13NW4R  1932 S    /bin/wps_monitor
  238 4L13NW4R  5600 S    wpsaide
  239 4L13NW4R  2140 S    /usr/sbin/wlc_nt
  246 4L13NW4R  1924 S    nas
  253 4L13NW4R  2268 S    /usr/sbin/wlceventd
  254 4L13NW4R  4932 S    nt_monitor
  256 4L13NW4R  1672 S    nt_actMail
  257 4L13NW4R  1672 S    nt_actMail
  258 4L13NW4R  1672 S    nt_actMail
  260 4L13NW4R  1448 S    /usr/sbin/acsd
  276 4L13NW4R  1444 S    crond -l 9
  277 4L13NW4R  6160 S    httpd -i br0
  278 4L13NW4R  1240 S    /usr/sbin/infosvr br0
  280 4L13NW4R  1280 S    sysstate
  281 4L13NW4R  5600 S    watchdog
  282 4L13NW4R  5600 S    check_watchdog
  286 4L13NW4R  2828 S    rstats
  293 4L13NW4R   732 S    /usr/sbin/snooper -b br0 -s vlan1
  304 4L13NW4R  1284 S    lld2d br0
  306 4L13NW4R  7240 S    networkmap --bootwait
  309 4L13NW4R  5508 S    mastiff
  310 4L13NW4R  5600 S    bwdpi_check
  311 4L13NW4R  5600 S    hour_monitor
  312 4L13NW4R  5600 S    pctime
  394 4L13NW4R  1484 S    lldpd -L /usr/sbin/lldpcli -I vlan1,eth1,eth2,wl0.1,wds0.*,wds1.*,wds2.* -s RT-AC68U
  398 nobody    1460 S    lldpd -L /usr/sbin/lldpcli -I vlan1,eth1,eth2,wl0.1,wds0.*,wds1.*,wds2.* -s RT-AC68U
  400 4L13NW4R  4476 S    cfg_server
  416 4L13NW4R  5616 S    amas_lib
  464 4L13NW4R  5508 S    mastiff
  465 4L13NW4R  5508 S    mastiff
  466 4L13NW4R  5508 S    mastiff
  525 4L13NW4R     0 SW   [khubd]
  634 4L13NW4R  4476 S    cfg_server
  635 4L13NW4R  4476 S    cfg_server
  776 4L13NW4R  5616 S    amas_lib
  780 4L13NW4R     0 SW   [scsi_eh_0]
  781 4L13NW4R     0 SW   [usb-storage]
  906 4L13NW4R  5600 S    usbled
  908 4L13NW4R  2456 S    u2ec
  909 4L13NW4R  1316 S    lpd br0
  920 4L13NW4R     0 SW   [scsi_eh_1]
  923 4L13NW4R     0 SW   [usb-storage]
  946 4L13NW4R  2456 S    u2ec
  947 4L13NW4R  2456 S    u2ec
  966 4L13NW4R   688 S    /usr/sbin/igmpproxy /tmp/igmpproxy.conf
 1003 4L13NW4R     0 SW   [jbd2/sdb1-8]
 1004 4L13NW4R     0 SW<  [ext4-dio-unwrit]
 1046 4L13NW4R     0 SW   [flush-8:16]
 1050 4L13NW4R  1436 S    /usr/sbin/ntp -t -S /sbin/ntpd_synced -p pool.ntp.org
 1122 nobody    5928 S    pixelserv-tls 10.7.7.2
 1139 4L13NW4R 13296 S    transmission-daemon -g /opt/etc/transmission
 1157 4L13NW4R  5600 S    disk_monitor
 1686 4L13NW4R     0 SW   [flush-8:0]
 1688 4L13NW4R  4184 S    /usr/sbin/stubby -g -C /etc/stubby/stubby.yml
 1701 nobody    6716 S    dnsmasq --log-async
 1702 4L13NW4R  3288 S    dnsmasq --log-async
 1905 4L13NW4R  2968 S    wred -B
 1906 4L13NW4R  2968 S    wred -B
 1907 4L13NW4R  2968 S    wred -B
 1943 4L13NW4R  5600 S    bwdpi_wred_alive
 1963 4L13NW4R  2968 S    wred -B
 1964 4L13NW4R  2968 S    wred -B
 1965 4L13NW4R  2968 S    wred -B
 1966 4L13NW4R  2968 S    wred -B
 1967 4L13NW4R  2968 S    wred -B
 1968 4L13NW4R  2968 S    wred -B
 1969 4L13NW4R  2968 S    wred -B
 1970 4L13NW4R  2968 S    wred -B
 2204 4L13NW4R     0 SW   [tntfsiupdated]
 2516 4L13NW4R 10036 S    minidlna -f /etc/minidlna.conf -R
 2569 4L13NW4R   664 S    tcd
 3338 4L13NW4R  1432 S    /sbin/udhcpc -i eth0 -p /var/run/udhcpc0.pid -s /tmp/udhcpc -O33 -O249
 4160 nobody    1540 S    avahi-daemon: running [RT-AC68U-15E0.local]
 4443 4L13NW4R  5848 S    /usr/sbin/nmbd -D -s /etc/smb.conf
 4447 4L13NW4R  5528 S    /usr/sbin/nmbd -D -s /etc/smb.conf
 4479 4L13NW4R  6048 S    /usr/sbin/smbd -D -s /etc/smb.conf
 4490 4L13NW4R   688 S    /usr/sbin/wsdd2 -d -w -i br0 -b sku:RT-AC68U,serial:f832e48515e0
 4533 4L13NW4R  4068 S    vsftpd /etc/vsftpd.conf
 5585 4L13NW4R 10040 R    minidlna -f /etc/minidlna.conf -R
 5691 4L13NW4R 10040 S    minidlna -f /etc/minidlna.conf -R
 5692 4L13NW4R 10040 S N  minidlna -f /etc/minidlna.conf -R
 6377 4L13NW4R  1152 S    dropbear -p 10.7.7.1:22 -j -k
 6392 4L13NW4R  1432 S    -sh
 6400 4L13NW4R  1420 R    ps -w
12079 4L13NW4R  6876 S    /usr/sbin/smbd -D -s /etc/smb.conf
14398 4L13NW4R  6736 S    /usr/sbin/smbd -D -s /etc/smb.conf
19893 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
19894 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
19895 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
19896 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
19897 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
19898 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
19907 4L13NW4R  1812 S    dcd -i 3600 -p 43200 -b -d /tmp/bwdpi/
25772 4L13NW4R     0 SW   [flush-mtd-unmap]
4L13NW4R3@RT-AC68U-15E0:/tmp/home/root#

opkg is still not recognized though. When I enter amtm I see the option to install Entware as if I haven't done that before. I still have the entware folder in the ext4 hdd that's plugged into the router so that's kind of weird.
 
It is working just fine now as it takes just a few minutes, not hours, for the shares to be back online after a reboot. The only major change I did was renaming the postconfig file so that was probably causing the issue as you suggested.

I don't mind about opkg not being recognized for the time being as I'm not going to be installing/uninstalling anything in the near future. Besides that re-installing it is not a big deal so that's ok.

Thank you @ColinTaylor and @dave14305 for your help! You guys are awesome!
 
I get the feeling this is a disk mounting issue, if entware isn't available. Use amtms disk check utility to see what's going on.

Are there any disk mounting errors in syslog?
 
I get the feeling this is a disk mounting issue, if entware isn't available. Use amtms disk check utility to see what's going on.

Are there any disk mounting errors in syslog?

Yes, there were. So this is what I realized after looking at the mounting sequence on the logs: I have two HDDs connected to the router, one is a Toshiba formatted as NTFS and the other one is a WD ext4.

Back in the day, I only had the Toshiba connected and I had asusware stuff installed on it. I then decided to use Entware and connected the WD to the router so that I could use the WD for Entware and the Toshiba for storage.

Apparently, the Toshiba boots up faster then the WD since it always shows up before the WD in the mounting logs. But that shouldn't cause any issues, right? Well, not quite. Turns out I forgot to remove the asusware leftover files and folders from the Toshiba so my wild guess is that the router was trying to use that before it had time to mount the WD which contains everything Entware.

I removed all the leftover files via SSH from the Toshiba, rebooted the router and now everything seems to be working fine as the "opkg" command is being recognized, my shares are online and the rest of the stuff I'm running on the router is also working as it should reboot after reboot.

Thank you @Jack Yaz for pointing the mounting issue and helping me sort it out and thanks to everyone in this community for being so helpful!
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top