Jump to content
Scottathon

[SOLVED] Samba is stopped, Shared drives will not be visible on the LAN.

11 posts in this topic Last Reply

Recommended Posts

Hello,

 

My first unRAID system has been going swimmingly ever since I put it together a few weeks ago, but I've hit a snag when I rebooted this evening. I can't access any network shares, as it appears that Samba stopped working. In unMENU, it says this at the top: "STARTED, 11 disks in array.    Parity is Valid:.   Last parity check < 1 day ago with no sync errors.   ; SAMBA is STOPPED, Shared drives will not be visible on the LAN."

 

I've read through the forum for solutions, and I have tried the following:

 

Running chkdsk on the flash drive on my Windows machine (There were no errors)

Verifying that I can write to the flash drive (I can)

Hitting the Start Samba button in unMENU

Running "/root/samba restart" over PuTTY

Rebooting several times

 

Can someone suggest something else to try? I have attached my log; though, there aren't any red entries when I view the syslog in unMENU.

 

I am running version 4.7-beta1.

 

Thanks for any advice,

Scott

syslog-2011-02-02.txt

Share this post


Link to post

Hello,

 

My first unRAID system has been going swimmingly ever since I put it together a few weeks ago, but I've hit a snag when I rebooted this evening. I can't access any network shares, as it appears that Samba stopped working. In unMENU, it says this at the top: "STARTED, 11 disks in array.    Parity is Valid:.   Last parity check < 1 day ago with no sync errors.   ; SAMBA is STOPPED, Shared drives will not be visible on the LAN."

 

I've read through the forum for solutions, and I have tried the following:

 

Running chkdsk on the flash drive on my Windows machine (There were no errors)

Verifying that I can write to the flash drive (I can)

Hitting the Start Samba button in unMENU

Running "/root/samba restart" over PuTTY

Rebooting several times

 

Can someone suggest something else to try? I have attached my log; though, there aren't any red entries when I view the syslog in unMENU.

 

I am running version 4.7-beta1.

 

Thanks for any advice,

Scott

I don't see anything in your syslog either.

 

Have you tried typing the

testparm

command to verify the samba config files?

 

Have you performed a memory test? 

 

Share this post


Link to post

Here is the output from testparm. I'm not that familiar with Linux, so I can't tell if anything seems out of the ordinary.

 

root@Tower:/boot# testparm

Load smb config files from /etc/samba/smb.conf

rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)

Processing section ""

Processing section "[disk1]"

Processing section "[disk2]"

Processing section "[disk3]"

Processing section "[disk4]"

Processing section "[disk5]"

Processing section "[disk6]"

Processing section "[disk7]"

Processing section "[disk8]"

Processing section "[disk9]"

Processing section "[disk10]"

Processing section "[Anime]"

Processing section "[Film]"

Processing section "[MP3]"

Processing section "[Television]"

Loaded services file OK.

Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

 

[global]

        server string = unRAID

        map to guest = Bad User

        null passwords = Yes

        passdb backend = smbpasswd

        syslog = 0

        syslog only = Yes

        unix extensions = No

        load printers = No

        printcap name = /dev/null

        disable spoolss = Yes

        show add printer wizard = No

        local master = No

        force user = root

        create mask = 0711

        directory mask = 0711

        guest only = Yes

        guest ok = Yes

        use sendfile = Yes

        map hidden = Yes

        map system = Yes

        msdfs root = Yes

 

 

        path = /boot

        read only = No

        create mask = 0777

        directory mask = 0777

        map archive = No

        map hidden = No

        map system = No

 

[disk1]

        path = /mnt/disk1

        read only = No

 

[disk2]

        path = /mnt/disk2

        read only = No

 

[disk3]

        path = /mnt/disk3

        read only = No

 

[disk4]

        path = /mnt/disk4

        read only = No

 

[disk5]

        path = /mnt/disk5

        read only = No

 

[disk6]

        path = /mnt/disk6

        read only = No

 

[disk7]

        path = /mnt/disk7

        read only = No

 

[disk8]

        path = /mnt/disk8

        read only = No

 

[disk9]

        path = /mnt/disk9

        read only = No

 

[disk10]

        path = /mnt/disk10

        read only = No

 

[Anime]

        path = /mnt/user/Anime

        read only = No

 

[Film]

        path = /mnt/user/Film

        read only = No

 

[MP3]

        path = /mnt/user/MP3

        read only = No

 

[Television]

        path = /mnt/user/Television

        read only = No

 

 

I have yet to attempt a memory test; I'm going to let one run overnight when I go to bed. Any other suggestions barring that?

Share this post


Link to post

No, not really.

 

The line at the top of unMENU is the result of

ps -ef | grep /usr/sbin/smbd | grep -v grep

returning no output, indicating that smbd is not running.

 

I see no evidence of it being killed, so I was asking about a memory check.

 

Joe L.

Share this post


Link to post

Well, I'll let the memory test run overnight, and I'll see what happens in the morning.

 

Thanks for the quick replies, Joe.

Share this post


Link to post

Well, the memory test revealed that there are no problems with the memory.

 

The only other thing I could think of was to type out what was showing on the monitor of my unRAID box:

 

tdb(/etc/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096

tdb(/etc/samba/private/secrets.tdb): tdb_transaction_recover: failed to read

 

recovery record

Failed to open /etc/samba/private/secrets.tdb

PANIC (pid 1479): could not open secrets db

BACKTRACE: 6 stack frames:

#0 /usr/bin/smbpasswd(log_stack_trace+0x2d) [0xb749318d]

#1 /usr/bin/smbpasswd(smb_panic+0x5d) [0xb4932bd]

#2 /usr/bin/smbpasswd(get_global_sam_sid+0x69d) [0xb73aa93d]

#3 /usr/bin/smbpasswd(main+0x4e9) [0xb734a589]

#4 /lib/libc.so.6(__libc_start_main+0xe0) [0xb701b390]

#5 /usr/bin/smbpasswd [0x7349ba1]

Can not dump core: corepath not set up

smdb: no process killed

/boot/config/snap/snap.sh: All shares mounted.

 

 

 

Welcome to Linux 2.6.32.9-unRAID (tty1)

 

Tower login:

 

I hope someone has an idea of what I should try next. Perhaps reformatting my flash drive?

 

Share this post


Link to post

Well, the memory test revealed that there are no problems with the memory.

 

The only other thing I could think of was to type out what was showing on the monitor of my unRAID box:

 

tdb(/etc/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096

tdb(/etc/samba/private/secrets.tdb): tdb_transaction_recover: failed to read

 

recovery record

Failed to open /etc/samba/private/secrets.tdb

PANIC (pid 1479): could not open secrets db

BACKTRACE: 6 stack frames:

#0 /usr/bin/smbpasswd(log_stack_trace+0x2d) [0xb749318d]

#1 /usr/bin/smbpasswd(smb_panic+0x5d) [0xb4932bd]

#2 /usr/bin/smbpasswd(get_global_sam_sid+0x69d) [0xb73aa93d]

#3 /usr/bin/smbpasswd(main+0x4e9) [0xb734a589]

#4 /lib/libc.so.6(__libc_start_main+0xe0) [0xb701b390]

#5 /usr/bin/smbpasswd [0x7349ba1]

Can not dump core: corepath not set up

smdb: no process killed

/boot/config/snap/snap.sh: All shares mounted.

 

 

 

Welcome to Linux 2.6.32.9-unRAID (tty1)

 

Tower login:

 

I hope someone has an idea of what I should try next. Perhaps reformatting my flash drive?

 

No, don't reformat the flash drive.

 

Does

/etc/samba/private

exist?

Type

ls -l /etc/samba/private

If it does, type

smbpasswd -a -n root

It will set the root SMB password to none.

 

Then, type

mv /boot/config/smbpasswd /boot/config/smbpasswd.old

cp /etc/samba/private/smbpasswd /boot/config/smbpasswd

Then, try to re-start samba ( or reboot )

 

I'm guessing the smbpasswd file in the config folder on the flash drive is corrupted or missing.

 

Joe L.

 

 

Share this post


Link to post

root@Tower:~# cd /etc/samba/private/
root@Tower:/etc/samba/private# smbpasswd -a -n root
tdb(/etc/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096
tdb(/etc/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record
Failed to open /etc/samba/private/secrets.tdb
tdb(/etc/samba/private/secrets.tdb): tdb_oob len 16408 beyond eof at 4096
tdb(/etc/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record
Failed to open /etc/samba/private/secrets.tdb
PANIC (pid 2732): could not open secrets db
BACKTRACE: 6 stack frames:
#0 smbpasswd(log_stack_trace+0x2d) [0xb748918d]
#1 smbpasswd(smb_panic+0x5d) [0xb74892bd]
#2 smbpasswd(get_global_sam_sid+0x69d) [0xb73a093d]
#3 smbpasswd(main+0x4e9) [0xb7340589]
#4 /lib/libc.so.6(__libc_start_main+0xe0) [0xb7011390]
#5 smbpasswd [0xb733fba1]
Can not dump core: corepath not set up

 

I'm not entirely sure, but I don't think it set the root SMB password to none. Am I wrong?

 

root@Tower:/etc/samba/private# ls /boot/config/
Pro.key*   go*         network.cfg*  share.cfg*  smb-extra.conf*   snap/
disk.cfg*  ident.cfg*  secrets.tdb*  shares/     smb-extra.conf~*  super.dat*

 

Also, I don't have a smbpasswd in my /boot/config/

 

What should I do now?

 

Share this post


Link to post

From what I've read, the secrets.tbd file is corrupted.

you can simply rename it and samba should re-create it.

mv /etc/samba/private/secrets.tbd /etc/samba/private/old_secrets.tbd

then try starting samba.

Share this post


Link to post

Hmmm... I don't have an old_secrets.tdb. What do you think about replacing it with /boot/config/secrets.tdb?

 

Edit: I made a backup of the corrupted secrets.tdb and replaced it with the one from /boot/config/, but it still didn't work.

 

Gah, this getting annoying.

Share this post


Link to post

Huzzah!

 

I fixed it. I ended up deleting secrets.tdb in /etc/samba/private/, and then unMENU gave me an option to reload the Samba configuration. Now Samba is running again with no problems.

 

Thanks for all your help, Joe. I wouldn't have gotten this far without your suggestions.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.