Cannot start Samba after fsck

punkmikey · 2013-04-24 20:10:32

After a kernel upgrade a few days ago, I got an fsck error after rebooting. fsck repaired (cloned?) a number of files. Ever since then I have been unable to start samba.

[mikey@homer ~]$ sudo systemctl status smbd
[sudo] password for mikey: 
smbd.service - Samba SMB/CIFS server
   Loaded: loaded (/usr/lib/systemd/system/smbd.service; disabled)
   Active: failed (Result: exit-code) since Wed 2013-04-24 19:49:19 BST; 1h 12min ago
  Process: 4896 ExecStart=/usr/sbin/smbd -D (code=exited, status=127)

Apr 24 19:49:19 homer smbd[4896]: public:
Apr 24 19:49:19 homer smbd[4896]: PDFDoc *buildPDFDoc(const GooString &uri, GooString *ownerPassword = NULL,
Apr 24 19:49:19 homer smbd[4896]: GooString *userPassword = NULL, void *guiDataA = NULL);
Apr 24 19:49:19 homer smbd[4896]: GBool supports(const GooString &uri);
Apr 24 19:49:19 homer smbd[4896]: };
Apr 24 19:49:19 homer smbd[4896]: #endif /* LOCALPDFDOCBUILDER_H */
Apr 24 19:49:19 homer smbd[4896]: , version HEIMDAL_CRYPTO_1.0 not defined in file libhcrypto-samba4.so.5 with link time reference
Apr 24 19:49:19 homer systemd[1]: smbd.service: control process exited, code=exited status=127
Apr 24 19:49:19 homer systemd[1]: Failed to start Samba SMB/CIFS server.
Apr 24 19:49:19 homer systemd[1]: MESSAGE=Unit smbd.service entered failed state.

I've tried reinstalling the samba package and also ran "findbrokenpkgs" and reinstalled all the packages it suggested. The "buildPDFDoc" part suggests it might be something to do with poppler so I reinstalled poppler and poppler-glib. Still get the same error.

What to try next?

Last edited by Inxsible (2013-04-24 21:22:11)

Inxsible · 2013-04-24 21:21:55

use code tags as opposed to quote when pasting snippets. I have edited your post this time.

WonderWoofy · 2013-04-25 00:49:53

You know there was an update to samba recently? Is it possible that you just happened to get this update when you had these fsck adventures?

punkmikey · 2013-04-25 08:57:34

Yes. I believe there was an update to Samba at the same time I updated the kernel and rebooted.

I've just SSH'd in and cleared pacmans cache with -Scc and then refreshed the databases with -Syy. After that I looked on the pacman wiki and used the command to re-install all packages on the system in the hope that it would overwrite any thing that's corrupted.

Halfway through, I got an error about some cache being corrupted and the start of what looked like a memory dump (lots of hex address). Putty froze, and now I can't get back in.

As I've had a number of files get corrupted in the last few weeks, I've decided to RMA the drive. Thankfully the WD Raptors have a 5 year warranty (bought this one in 2009).

WonderWoofy · 2013-04-25 15:32:41

Well, I hope a new drive works out for you. The suddenly not working samba is to be expected if you updated from 3.* to 4.*. You need to go through making the necessary users and whatnot with pdbedit. Then use the new /etc/samba/smb.conf.default as a template to recreate your configuration. It is nearly identical, but there are few importnat differences, so you need to recreate it.

If you don't wnat to use the Active Directory stuffs, then that is all you need to do. But if you do want to use it, then you can check out the Samba wiki, as there is much information there. TBH, I don't really understand why a Linux user would want to have all that stuff (though my home is windows-less environment, so maybe there is something amazing that I'm totally missing out on but I doubt it).

punkmikey · 2013-04-25 15:53:20

I had upgraded to Samba 4 earlier and it was all working. I'm quite sure the error I posted has nothing to do with the smb.conf file or samba users.

I went home for lunch today so I could reboot my server machine while I was there. It will no longer boot :'( . Even with the fallback kernel. Thankfully, this drive is just an OS/cache drive. My data is on a separate ZFS array. Just need an hour or so to download, re-install and reconfigure.

WonderWoofy · 2013-04-25 22:07:41

I just started playing with ZFS. It is very neat. I also recently switched back to btrfs, so it is pretty cool to be able to make a comparison between the two in terms of features and whatnot. ZFS is defintiely more featureful, but btrfs is waaaayyy easier to get a system installed to on Linux.

As far as the WD Raptor is concerned, have you tried to run SMART tests on the thing? Re-installation might help in the short term, but if that thing is still under warranty, you might as well try to find out asap if it is the drive that is doing you wrong.

Arch Linux

#1 2013-04-24 20:10:32

Cannot start Samba after fsck

#2 2013-04-24 21:21:55

Re: Cannot start Samba after fsck

#3 2013-04-25 00:49:53

Re: Cannot start Samba after fsck

#4 2013-04-25 08:57:34

Re: Cannot start Samba after fsck

#5 2013-04-25 15:32:41

Re: Cannot start Samba after fsck

#6 2013-04-25 15:53:20

Re: Cannot start Samba after fsck

#7 2013-04-25 22:07:41

Re: Cannot start Samba after fsck

Board footer