A terrible mistake with Samba. Help!

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • A terrible mistake with Samba. Help!

      Today I was having problems with Win8 and my OMV server. Until today my OMV installation was working fine for a couple of years, including samba.

      But I stupidly did:

      Source Code

      1. apt-get install samba
      :(

      now samba is broken, and apt-get remove samba produces the horrible warning:

      The following packages will be REMOVED:

      Source Code

      1. openmediavault openmediavault-forkeddaapd openmediavault-minidlna openmediavault-mysql openmediavault-omvpluginsorg
      2. openmediavault-processlist openmediavault-transmissionbt openmediavault-website samba


      I can see that would be a very very bad thing, so I didn't proceed with the remove.

      What can I do to repair the damage? The server seems ok apart from samba, but I have no idea what to do to undo my horrible stupidity...
    • Re: A terrible mistake with Samba. Help!

      What the hell did you do? "apt-get install samba" should not have caused any issue at all, because it is already installed.

      Whats the output of the following command:

      Source Code

      1. service samba status


      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Re: A terrible mistake with Samba. Help!

      Thanks for your quick responses. It was quite late when I ran into this problem. I'd been configuring 2 Windows 8 machines all day, and one of them started acting strange when accessing my samba shares. I read that this could be caused by an old version of samba, so I did the apt-get install samba without checking much, thinking that it would upgrade samba and shouldn't cause any problems.

      Source Code

      1. service samba status


      returns

      Source Code

      1. nmbd is running.
      2. could not access PID file for smbd ... failed!


      after

      Source Code

      1. /etc/init.d/samba restart


      it shows the same.

      Source Code

      1. find / | grep -i smbd.pid


      sits for ages and doesn't show anything. at least not yet.

      Source Code

      1. testparm /etc/samba/smb.conf


      shows my proper smb.conf file, with just one little warning

      Source Code

      1. WARNING: You have some share names that are longer than 12 characters.


      After a good nights sleep I'm not so panicked, but samba's still not up..
    • Re: A terrible mistake with Samba. Help!

      Sadly, I'm still getting nowhere with this. log.smbd is empty, no other logs show anything useful. I still get

      Source Code

      1. service samba status
      2. nmbd is running.
      3. could not access PID file for smbd ... failed!


      and

      Source Code

      1. pgrep -l mbd
      2. 446 smbd
      3. 637 smbd
      4. 1338 smbd
      5. 1598 smbd
      6. 1874 smbd
      7. 3099 smbd
      8. 3708 smbd
      9. 4260 smbd
      10. 4490 smbd
      11. 5506 smbd
      12. 6476 smbd
      13. 6478 smbd
      14. 6841 smbd
      15. 7356 smbd
      16. 7545 smbd
      17. 8894 smbd
      18. 9766 smbd
      19. 9819 smbd
      20. 10260 smbd
      21. 11217 smbd
      22. 11689 smbd
      23. 12265 smbd
      24. 12688 smbd
      25. 12795 smbd
      26. 13117 smbd
      27. 13572 smbd
      28. 13583 smbd
      29. 13913 smbd
      30. 13969 smbd
      31. 14173 smbd
      32. 14335 smbd
      33. 14456 smbd
      34. 14567 smbd
      35. 14636 smbd
      36. 14798 smbd
      37. 14906 nmbd
      38. 14983 smbd
      39. 15146 smbd
      40. 15152 smbd
      41. 15262 smbd
      42. 15268 smbd
      43. 15376 smbd
      44. 15688 smbd
      45. 15797 smbd
      46. 15911 smbd
      47. 16212 smbd
      48. 16219 smbd
      49. 16331 smbd
      50. 16452 smbd
      51. 16492 smbd
      52. 16772 smbd
      53. 16891 smbd
      54. 16934 smbd
      55. 17046 smbd
      56. 17154 smbd
      57. 17317 smbd
      58. 17422 smbd
      59. 17428 smbd
      60. 17696 smbd
      61. 18033 smbd
      62. 18268 smbd
      63. 18379 smbd
      64. 18621 smbd
      65. 19041 smbd
      66. 20030 smbd
      67. 20517 smbd
      68. 20725 smbd
      69. 21733 smbd
      70. 22474 smbd
      71. 22568 smbd
      72. 22755 smbd
      73. 23117 smbd
      74. 28364 smbd
      75. 28789 smbd
      76. 31720 smbd
      Display All
    • Re: A terrible mistake with Samba. Help!

      Just out of curiosity, did you try to reboot your system inbetween trying to start samba?

      I only find suggestions to look for the pid file, obviously you did not find it yet?

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Re: A terrible mistake with Samba. Help!

      I didn't find the process, how ever I did find lots of processes with status -D (disabled, deep sleep), which I could not kill, no matter what technique I used. There were also lots of locked files (listed using the sambastatus command, I think).

      What started all these problems was a decision to make my laptop my work/music computer, with my desktop becoming my HTPC. This involved upgrading both machines to Windows 8, as I want to use windows games and possibly SteamOS on the HTPC. Anyway, this meant moving a lot of files around, and I was using my OMV server as a middle-man. That all went fine until I tried to move my biggest 'work' folder to the server. The mapped server drive kept going offline, and after I lost patience with that happening, I tried upgrading samba.

      In the end this spells the end of my use of OMV. I became disillusioned with it a while ago when I realised how outdated the kernel was, and how non-standard the whole thing is. This could be the root of my problem because at some point I changed the kernel and installed some backports packages. I'm no Linux expert, but I was led to understand at the time that there were some risks in doing that.

      When I decided I wanted a NAS, I started with Freenas, which I found extremely unreliable, so moved to OMV, which has - on the whole - served me well for 2+ years. But, as my linux skills have improved I've felt more confident about setting up a vanilla Debian server. To that end I already had an installation ready. These samba problems precipitated the move away from OMV. So yesterday I removed the OMV disk and replaced it with the Debian 7 one, with all the services I want already set up. After some mounting and samba config with webmin my server is now back up. Now all I have to do is properly configure all my other services..

      So, this is goodbye from me to OMV :( Thanks to everyone involved there for all the hard work. I'm pretty sure I donated at some point :)