DSM-G600, DNS-3xx and NSA-220 Hack Forum

amraam wrote:

Recently I bought the conceptronic CH3SNAS. I installed the 1.04 firmware (because of the 94% problem) and got the system at least working. After that I fun_plugged the device and installed Twonky.

Now I got a strange problem. After a while windows gives a message that the connection is lost with the network disk. When I open a telnet I can see with the ps command that the smbd process is not active anymore. Somehow it is killed. With smb restart I can restart the samba server and the connection is back, but then I can't use telnet anymore....

Has anybody got an idea why the samba process gets killed and how to avoid this?

I'm with a dns 323, but I'm also having problems with samba crashing. It happens about once a week or something like that. The only solution for me is to restart the NAS, very annoying.

Trying to restart samba with "smb restart" gives med the following output:

/etc/samba # smb restart
$Shutting down SMB services: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or kill -l [exitstatus]

$Shutting down NMB services: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or kill -l [exitstatus]

$Starting SMB services: /usr/bin/smb: /usr/sbin/samba/smbd: No such file or directory

$Starting NMB services: /usr/bin/smb: /usr/sbin/samba/nmbd: No such file or directory

I don't have a clue what's causing this, is anyone else having the same or a similiar problem? Would be greatful for a nicer solution than restarting the NAS.

bq041 wrote:

What else are you running?  I have never had samba get killed.  I have had windows give me that error, but that is just because of windows.  A quick retry and back on the disk.

After restarting the NAS(which activates samba again) I have the following processes running:

/ # ps
PID   USER     COMMAND
    1 root     init
    2 root     [ksoftirqd/0]
    3 root     [events/0]
    4 root     [khelper]
    5 root     [kthread]
   11 root     [kblockd/0]
   14 root     [khubd]
   49 root     [pdflush]
   50 root     [pdflush]
   52 root     [aio/0]
   51 root     [kswapd0]
  188 root     [scsi_eh_0]
  189 root     [scsi_eh_1]
  199 root     [mtdblockd]
  216 root     [kcryptd/0]
  217 root     [kmirrord/0]
  228 root     [loop0]
 1364 root     atd
 1612 root     chkbutton
 1632 root     /web/webs
 1665 root     /usr/sbin/samba/smbd -D
 1669 root     /usr/sbin/samba/smbd -D
 1670 root     /usr/sbin/samba/nmbd -D
 1675 root     op_server 3 3 3
 1686 root     -sh
 1728 root     pure-ftpd (SERVER)
 1735 root     lpd Waiting
 1768 root     crond
 1819 Mackan   /ffp/bin/transmission-daemon -f
 1846 Mackan   /ffp/bin/transmission-daemon -f
 1847 Mackan   /ffp/bin/transmission-daemon -f
 1849 root     /ffp/sbin/telnetd -l /ffp/bin/sh
 2034 root     /ffp/bin/sh
 2035 root     [sh]
 2038 root     [sh]
 2056 root     ps

In addition to this I have a editcron.sh which adds some instructions to crond. A script which scans a directory for .torrent files and a script for controlling the fan.

/bin/echo "*/1 * * * * /ffp/bin/sh /mnt/HD_a2/Eskas/torrent_watcher_cron.sh >>/mnt/HD_a2/ffp/log/torrent_watcher.log 2>&1" >> $CRONTXT
/bin/echo "*/1 * * * * /ffp/bin/sh /ffp/cronscripts/ctrl_fan.sh>>/mnt/HD_a2/ffp/log/fanscript.log 2>&1" >> $CRONTXT

Last edited by Eskas (2008-09-12 00:20:48)

bq041 wrote:

Double check your other scripts to make sure there is nothing in them that would interfere with samba.  Actually, you may want to temporarily remove your other scripts and cron jobs to see if samba stays running.  Then add things back 1 at a time until you find out which kills it.

Of course I could shut down everything that I have running, but I think this would be a very long process since the problem only occurs twice or maybe three times a month. I guess I could disable cleanboot, because I think it's after enabling that this problem started.