Buffalo Forums

Using LinkStation Pro Duo LS-WTGL/R1

The samba server on the linkstation is crashing and I can't connect to my shares from my Window 7 clients.

The linkstation has been working great for years up to a few months ago. I use to see my shares on the NAS and then all of a sudden I couldn't. Until yesterday I didn't dive into the problem. Now after looking around and viewing the log files I see the samba server crash when the client connects. The server comes up initially without a problem.

I haven't modified the linkstation at all. I've added ssh support so I can get on the box and see what's going on. The web interface doesn't show any errors and I can always log on to it. It's my guess is a samba library file, executable or dependency has become corrupt and is causing the samba server to crash when connecting.

I need advice from Buffalo support as how I can restore the samba server and/or it's dependencies to their original state. I can supply you with log files, etc. to help troubleshoot this problem. Please advise.

Thanks


LinkStation Name
LINKSTATION

Model Name
LS-WTGL/R1-V3 F/W 3.10

IP Address
192.168.1.252

Current Date and Time
2016/2/29 9:12:55

HDD Space Used
RAID Array 1
237.42 GB / 923.76 GB (25.70 %)

First reset the unit on the admin page and see how you get on then.

Still got the same problem.

Here's my smb.conf file:

[global]
    dos charset = CP437
    unix charset = UTF-8
    display charset = UTF-8
    netbios name = LINKSTATION
    server string = "LinkStation Pro Duo"
    socket options = TCP_NODELAY SO_SNDBUF=32768 SO_RCVBUF=32768
    os level = 1
    wins server =

    workgroup = WORKGROUP
    security = user
    auth methods = guest sam
    passdb backend = tdbsam:/etc/samba/smbpasswd.tdb
    encrypt passwords = Yes
    passwd program = /usr/bin/passwd %u
    passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
    unix password sync = yes
    guest account = nobody
    null passwords = yes
    guest only = no
    password level = 14
    map to guest = Bad User

    veto files = /.AppleDesktop/Network Trash Folder/TheVolumeSettingsFolder/.AppleDouble/.AppleDB/
    delete veto files = yes

    deadtime = 15
    invalid users = mail, deamon
    admin users = root
    username map = /etc/samba/smbusers

    log level = 1
    max log size = 200

    lock directory = /etc/samba/lock

    dos filetimes = Yes
    dos filetime resolution = Yes
    map archive = Yes
    map hidden = No
    map system = No
    dns proxy = No
    show add printer wizard = No
    host msdfs = no
    disable spoolss = yes
    load printers = no
[info]
    comment = LinkStation Utilities
    path = /mnt/info
    browsable = yes
    printable = no
    writable = no
    guest ok = yes
    csc policy = disable
[share]
    comment =
    path = /mnt/array1/share
    browsable = yes
    printable = no
    writable = yes
    guest ok = yes
    force create mode = 666
    force directory mode = 777
    csc policy = manual
###share###
#####END#####

And I've attached my log.smbd file.

Thought I could attach files, anyway this is what the log.smbd file looks like:

[2016/03/01 07:04:57, 0] smbd/server.c:main(944)
  smbd version 3.0.30-1.4.osstech started.
  Copyright Andrew Tridgell and the Samba Team 1992-2008
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 17286 (3.0.30-1.4.osstech)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(44)
 
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2016/03/01 07:16:55, 0] lib/util.c:smb_panic(1655)
  PANIC (pid 17286): internal error
[2016/03/01 07:16:55, 0] lib/util.c:log_stack_trace(1759)
  BACKTRACE: 0 stack frames:
[2016/03/01 07:16:55, 0] lib/fault.c:dump_core(181)
  dumping core in /var/log/cores/smbd
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 17287 (3.0.30-1.4.osstech)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(44)
 
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2016/03/01 07:16:55, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2016/03/01 07:16:55, 0] lib/util.c:smb_panic(1655)
  PANIC (pid 17287): internal error
[2016/03/01 07:16:55, 0] lib/util.c:log_stack_trace(1759)
  BACKTRACE: 0 stack frames:
[2016/03/01 07:16:55, 0] lib/fault.c:dump_core(181)
  dumping core in /var/log/cores/smbd
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 17317 (3.0.30-1.4.osstech)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(44)
 
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(45)
  ===============================================================
[2016/03/01 07:16:58, 0] lib/util.c:smb_panic(1655)
  PANIC (pid 17317): internal error
[2016/03/01 07:16:58, 0] lib/util.c:log_stack_trace(1759)
  BACKTRACE: 0 stack frames:
[2016/03/01 07:16:58, 0] lib/fault.c:dump_core(181)
  dumping core in /var/log/cores/smbd
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(41)
  ===============================================================
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 17321 (3.0.30-1.4.osstech)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(44)
 
  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2016/03/01 07:16:58, 0] lib/fault.c:fault_report(45)
  ===============================================================
.
.
.

I wanted to update my original post with the solution in case someone else runs into a problem like this. This was for a Buffalo LinkStation Pro Duo LS-WTGL/R1-V3 but the same ideas should apply to other Buffalo NAS systems.

1) If you ever have a strange problem with your NAS, enable ssh and look at the log files which reside in the /var/log directory. There's a wealth of information in there so poke around. I used acp_commander_gui_156 to enable ssh. Google it if you need to.

2) Re-flashing my LS-WTGL/R1-V3 with firmware 3.10 (which is the version I was originally running) fixed my issue. This basically re-installs the Linux OS including the version of Samba that was crashing. Now there are solutions out there that talk about putting the NAS in EM and going through this TFTP process to re-install the firmware. But if your NAS is basically working, don't bother if you don't have to. Just re-flash it. It's so much faster and easier. This won't destroy your data on the NAS (unless you specifically enable it to do so) so don't worry about it.

3) To re-flash your NAS with the same firmware you'll need to turn off version checking when running the LSUpdater. Google "Force Update Buffalo Linkstation NAS" or see http://m1econsulting.com/knowledge-base/force-update-buffalo-linkstation-nas/ for more information.

HTH,
Cheers