I have a serious problem with samba and my RN 104. Since a few days I cannot Access the shares from my Rn 104. I installed the actual firmware 6.1.8 again, but the shares only visible after the first restart after flashing. When a cold start is happened the shares not appear.
When I connect with ssh and start a samba command e.g. smbtree the following is shown:
###:~# smbtree smbtree: /usr/lib/arm-linux-gnueabi/samba/liberrors.so: version `SAMBA_4.1.11' not found (required by /usr/lib/arm-linux-gnueabi/libndr.so.0) ###:~#_
If anybody has an idea what is wrong with the samba conf or something else, plz give me a note.
Yes, I didn't know that I don't have to. But ís there any help to get samba work again. I only use the samba Shares at the readynas. Can Samba be reinstalled and uses the netgear share config? And why it works after flashing and not after cold boot?
Also if you download your logs zip file, apt-history.log should indicate what packages have been installed via apt-get (some of which you may have installed manually). This should give some clues as to which packages you replaced assuming you did it via apt-get.
You may wish to backup your data and do a factory reset (wipes all data, settings, everything) then restore your data from backup.
We include updates to packages in firmware updates.
For example 6.1.9 includes samba 4.0.21 whereas 6.1.8 has samba 4.0.16
Thanks for the answer. Factory reset is not an Option, because it is filled with more data which I can backup. The upgrade today to 6.1.9 doesn't change anything.
Here some outputs with hope for help:
dpkg -l | grep samba:
ii libsamba-credentials0:armel 2:4.0.21-netgear1 armel Samba Credentials management library ii libsamba-hostconfig0:armel 2:4.0.21-netgear1 armel Samba host configuration library ii libsamba-util0:armel 2:4.0.21-netgear1 armel Samba utility function library ii samba 2:4.0.21-netgear1 armel SMB/CIFS file, NT domain and active directory server (version 4) ii samba-common 2:4.0.21-netgear1 all common files used by both the Samba server and client ii samba-common-bin 2:4.0.21-netgear1 armel Samba 4 common files used by both the server and the client
initrd.log: [2014/02/27 09:52:58] Factory default initiated due to new disks (no RAID, no partitions)! [2014/02/27 09:53:16] Defaulting to X-RAID2 mode, RAID level 1 [2014/02/27 09:53:41] Factory default initiated on ReadyNASOS 6.1.6. [2014/03/13 12:49:14] Updated from ReadyNASOS 6.1.6 (1391111179) to 6.1.7 (1394646198). [2014/03/18 12:31:05] Updated from ReadyNASOS 6.1.7 to 6.1.6. [2014/04/15 12:28:23] Updated from ReadyNASOS 6.1.6 (1391111179) to 6.1.7 (1396977042). [2014/05/18 12:06:25] Updated from ReadyNASOS 6.1.7 (1396977042) to 6.1.8 (1398980083). [2014/06/29 02:14:01] Updated from ReadyNASOS 6.1.8 (1398980083) to 6.1.9 (1403301897). [2014/07/21 12:48:03] Updated from ReadyNASOS 6.1.9 (1403301897) to 6.1.9 (1405706270). [2014/08/14 11:07:26] Updated from ReadyNASOS 6.1.9 (1405706270) to 6.1.9 (1407979333). [2014/08/29 12:32:10] Updated from ReadyNASOS 6.1.9 (1407979333) to 6.1.9 (1408568742). [2014/09/04 14:21:42] Updated from ReadyNASOS 6.1.9 (1408568742) to 6.1.9 (1408568742). [2014/09/04 14:28:09] Updated from ReadyNASOS 6.1.9 (1408568742) to 6.1.9 (1408568742). [2014/09/08 11:53:02] Updated from ReadyNASOS 6.1.9 (1408568742) to 6.1.9 (1408568742). [2014/09/14 12:41:24] Updated from ReadyNASOS 6.1.9 (1408568742) to 6.1.9 (1408568742). [2014/09/15 12:00:54] Updated from ReadyNASOS 6.1.9 (1408568742) to 6.1.8 (1398980083). [2014/09/19 09:58:11] Updated from ReadyNASOS 6.1.8 (1398980083) to 6.1.9 (1409791183).
So I've screwed up my samba install too via apt-get upgrade. n00b mistake, I didn't realize until further reading that this is not recommended. So is there really no other way of fixing this besides doing a factory reset?
I can launch smbd from the cli but any changes made to shares in the gui kill the process and I have to restart it again and it doesn't show that samba is running on the settings/services page. Any tricks or thoughts on how I can repair the samba install to have it function normally would be greatly appreciated.
If anyone comes across this thread, if you want to use samba 4.1.x (but have not yet installed it), a better option than installing it manually would be to try 6.2.0 beta.
Please read the Release Notes carefully before trying this release and also be sure to make sure your backup is up to date before installing the update.
Thanks so much, this was a life saver! I had this same problem after running apt-get recently. (Well almost the same, it was complaining about SAMBA_4.0.22.) Running the above commands worked perfectly.
Just for my curiousity, what happened that broke it? I had run apt-get update before to install text editors, etc., and never had any problems.
Yes I did :oops: Not the best idea I'm learning. I'll avoid this in the future. But I was curious what specifically happened with it that would break this. I was under the impression that apt-get was set to point to specific Netgear repos that were kosher to upgrade against. I guess that is incorrect.
It does point to our repos, but also standard non-NETGEAR ones. We do pin some packages but not everything. Furthermore the 3rd party repository may get updated frequently and it would be impossible to keep up with all the changes.
It's not the upgrade that's the problem, at least on OS6 boxes. It's just if you install a firmware update afterward (or do an OS reinstall, etc) that includes an older version of some shared libraries, then the system will end up eventually re-linking the shared libraries to their newest versions. So mismatches between programs (like Samba) and the shared libraries that they depend on can arise. Our 6.2.0 release will do some additional housekeeping to get rid of those additional files as part of the update process, so this particular situation wouldn't happen in the future.
