Hallo,

jetzt ist es soweit

Eigentlich wollte ich nur 2 Hdd´s auf meiner DM520 einbinden und mit Samba Freigabe darauf zugreifen. (Windows Freigabe)
Habe mir das Samba Config Editor Plugin installiert undbeim durch zappen habe ich den Punkt Arbeitsgruppe (global config) gefunden und mir gedacht super allesin einer Gruppe.
Nach dem ändern ist jetzt das Share über Windows nichtmehr zu erreichen.
Auch wieder zurück zum STD "DreamBOX" gibt es keinShare mehr. Ein Reboot brachte keine Erfolg. Jetzt brauche ich Hilfe
Eigentlich wollte ich doch nur auf beide Hdd´szugreifen . Muss ich jetzt überPutty was basteln ?


Gruß Mecky76

Hi Fred,

hier ist die smb.conf


login as: root

##############################################################################
# #
# This is a Dreambox #
# #
# with newnigma2.to #
# #
# Unauthorized access to this system is prohibited ! #
# #
# This system is actively monitored and all connections may be logged. #
# By accessing this system, you consent to this monitoring. #
# #
##############################################################################

root@dm520:~# cat /etc/samba/smb.conf
# automatically generated by smb.conf Plugin
# do NOT change manually!

[global]
load printers = no
guest account = root
log file = /tmp/smb.log
security = user
server string = dreambox%h
workgroup = DreamBOX
netbios name = DreamBOX
client code page = 850
character set = iso8859-1
case sensitive = yes
preserve case = yes
short preserve case = yes
encrypt passwords = no

[Harddisk]
comment = The hard disk drive
path = /media/hdd
read only = no
public =
guest ok = yesroot@dm520:~#

Hallo Fred,

Ein Reboot habe ich gemacht mit dem Windows Rechner, auch testweise mit meinem Laptop über die \\Ip kein share

Die Box kann ich bei beiden Rechner über Ping erreichen

Mecky76

Hallo Fred,

ja Samba starte nicht

root@dm520:~# systemctl status samba.service
● samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; disabled; vendor preset: e
Active: failed (Result: exit-code) since Sa 2017-01-21 21:18:30 CET; 1min 58s
Process: 893 ExecStart=/usr/sbin/samba $SAMBAOPTIONS (code=exited, status=203/
Main PID: 893 (code=exited, status=203/EXEC)

Jan 21 21:18:30 dm520 systemd[1]: Starting Samba AD Daemon...
Jan 21 21:18:30 dm520 systemd[1]: samba.service: Main process exited, code=exite
Jan 21 21:18:30 dm520 systemd[1]: Failed to start Samba AD Daemon.
Jan 21 21:18:30 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 21 21:18:30 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.
lines 1-11/11 (END)...skipping...
● samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sa 2017-01-21 21:18:30 CET; 1min 58s ago
Process: 893 ExecStart=/usr/sbin/samba $SAMBAOPTIONS (code=exited, status=203/EXEC)
Main PID: 893 (code=exited, status=203/EXEC)
---------------------
root@dm520:~# systemctl restart samba
Job for samba.service failed because the control process exited with error code.
See "systemctl status samba.service" and "journalct -xe" for details.
root@dm520:~#

-------------------
root@dm520:~# journalctl -xe
-- The process /usr/sbin/samba could not be executed and failed.
--
-- The error number returned by this process is 2.
Jan 21 21:25:07 dm520 systemd[1]: samba.service: Main process exited, code=exited, status=203/EXEC
Jan 21 21:25:07 dm520 systemd[1]: Failed to start Samba AD Daemon.
-- Subject: Unit samba.service has failed
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has failed.
--
-- The result is failed.
Jan 21 21:25:07 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 21 21:25:07 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.
Jan 21 21:25:08 dm520 enigma2[756]: nr_read 307 nr_write 1
Jan 21 21:25:08 dm520 enigma2[756]: sum 308 prev_sum 308
Jan 21 21:25:08 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:08 dm520 enigma2[756]: [IDLE] 482.990171909 300 True
Jan 21 21:25:08 dm520 enigma2[756]: nr_read 15217 nr_write 4730
Jan 21 21:25:08 dm520 enigma2[756]: sum 19947 prev_sum 19947
Jan 21 21:25:08 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:08 dm520 enigma2[756]: [IDLE] 59.9999680519 300 False
Jan 21 21:25:38 dm520 enigma2[756]: nr_read 307 nr_write 1
Jan 21 21:25:38 dm520 enigma2[756]: sum 308 prev_sum 308
Jan 21 21:25:38 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:38 dm520 enigma2[756]: [IDLE] 512.990043879 300 True
Jan 21 21:25:38 dm520 enigma2[756]: nr_read 15217 nr_write 4730
Jan 21 21:25:38 dm520 enigma2[756]: sum 19947 prev_sum 19947
Jan 21 21:25:38 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:38 dm520 enigma2[756]: [IDLE] 89.9998679161 300 False
Jan 21 21:25:39 dm520 enigma2[756]: [EPGC] cleanupOutdated
lines 1060-1090/1090 (END)
-- The process /usr/sbin/samba could not be executed and failed.
--
-- The error number returned by this process is 2.
Jan 21 21:25:07 dm520 systemd[1]: samba.service: Main process exited, code=exited, status=203/EXEC
Jan 21 21:25:07 dm520 systemd[1]: Failed to start Samba AD Daemon.
-- Subject: Unit samba.service has failed
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has failed.
--
-- The result is failed.
Jan 21 21:25:07 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 21 21:25:07 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.
Jan 21 21:25:08 dm520 enigma2[756]: nr_read 307 nr_write 1
Jan 21 21:25:08 dm520 enigma2[756]: sum 308 prev_sum 308
Jan 21 21:25:08 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:08 dm520 enigma2[756]: [IDLE] 482.990171909 300 True
Jan 21 21:25:08 dm520 enigma2[756]: nr_read 15217 nr_write 4730
Jan 21 21:25:08 dm520 enigma2[756]: sum 19947 prev_sum 19947
Jan 21 21:25:08 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:08 dm520 enigma2[756]: [IDLE] 59.9999680519 300 False
Jan 21 21:25:38 dm520 enigma2[756]: nr_read 307 nr_write 1
Jan 21 21:25:38 dm520 enigma2[756]: sum 308 prev_sum 308
Jan 21 21:25:38 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:38 dm520 enigma2[756]: [IDLE] 512.990043879 300 True
Jan 21 21:25:38 dm520 enigma2[756]: nr_read 15217 nr_write 4730
Jan 21 21:25:38 dm520 enigma2[756]: sum 19947 prev_sum 19947
Jan 21 21:25:38 dm520 enigma2[756]: hdd IDLE!
Jan 21 21:25:38 dm520 enigma2[756]: [IDLE] 89.9998679161 300 False
Jan 21 21:25:39 dm520 enigma2[756]: [EPGC] cleanupOutdated
~
~
~
~
~
lines 1060-1090/1090 (END)




mecky76

Hallo ,

jetzt habe ich die Config von dreamedge genommen ,aber leider startet Samba immer noch nicht !


root@dm520:/etc/samba# cat smb.conf
# automatically generated by smb.conf Plugin
# do NOT change manually!


[global]
load printers = no
guest account = root
security = user
server string = dreambox%h
workgroup = DREAMBOX
map to guest = Bad User
max log size = 50
dns proxy = 0


[Harddisk1]
comment = The hard disk drive
path = /media/hdd
read only = no
public =
guest ok = yes
----
root@dm520:/etc/samba# systemctl status samba.service
● samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; disabled; vendor preset: e
Active: failed (Result: exit-code) since So 2017-01-22 11:51:21 CET; 43s ago
Process: 744 ExecStart=/usr/sbin/samba $SAMBAOPTIONS (code=exited, status=203/
Main PID: 744 (code=exited, status=203/EXEC)

Jan 22 11:51:21 dm520 systemd[1]: Starting Samba AD Daemon...
Jan 22 11:51:21 dm520 systemd[1]: samba.service: Main process exited, code=exite
Jan 22 11:51:21 dm520 systemd[1]: Failed to start Samba AD Daemon.
Jan 22 11:51:21 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 22 11:51:21 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.
lines 1-11/11 (END)...skipping...
● samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since So 2017-01-22 11:51:21 CET; 43s ago
Process: 744 ExecStart=/usr/sbin/samba $SAMBAOPTIONS (code=exited, status=203/EXEC)
Main PID: 744 (code=exited, status=203/EXEC)

Jan 22 11:51:21 dm520 systemd[1]: Starting Samba AD Daemon...
Jan 22 11:51:21 dm520 systemd[1]: samba.service: Main process exited, code=exited, status=203/EXEC
Jan 22 11:51:21 dm520 systemd[1]: Failed to start Samba AD Daemon.
Jan 22 11:51:21 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 22 11:51:21 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.

---
root@dm520:/etc/samba# journalctl -xe
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/sbin/samba could not be executed and failed.
--
-- The error number returned by this process is 2.
Jan 22 11:53:20 dm520 systemd[1]: samba.service: Main process exited, code=exited, status=203/EXEC
Jan 22 11:53:20 dm520 systemd[1]: Failed to start Samba AD Daemon.
-- Subject: Unit samba.service has failed
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has failed.
--
-- The result is failed.
Jan 22 11:53:20 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 22 11:53:20 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.
Jan 22 11:53:22 dm520 enigma2[180]: nr_read 248 nr_write 1
Jan 22 11:53:22 dm520 enigma2[180]: sum 249 prev_sum 249
Jan 22 11:53:22 dm520 enigma2[180]: hdd IDLE!
Jan 22 11:53:22 dm520 enigma2[180]: [IDLE] 4621.97634101 300 True
Jan 22 11:53:22 dm520 enigma2[180]: nr_read 421 nr_write 1
Jan 22 11:53:22 dm520 enigma2[180]: sum 422 prev_sum 422
Jan 22 11:53:22 dm520 enigma2[180]: hdd IDLE!
Jan 22 11:53:22 dm520 enigma2[180]: [IDLE] 4621.97684622 300 True


mecky76

Hi,

jetzt habe ich doch ein anderen weg eingeschlagen Daily von heute.Rücksicherung von heute Share geht wieder.
Aber wenn ich jetzt die 2 HDD hinzufüge über den Samba Config ist das Share wieder nicht erreichbar.

hier die Konfig:

# automatically generated by smb.conf Plugin
# do NOT change manually!

[global]
load printers = no
guest account = root
log file = /tmp/smb.log
security = user
server string = dreambox%h
workgroup = DREAMBOX
netbios name = DreamBOX
client code page = 850
character set = iso8859-1
case sensitive = yes
preserve case = yes
short preserve case = yes
encrypt passwords = no

[Harddisk]
comment = The hard disk drive
path = /media/hdd
read only = no
public =
guest ok = yes

[Harddrive2]
comment = the hard disk drive 2
path = /media/hdd2
read only = no
public = yes
guest ok = yes

-----------------------------------------------------
root@dm520:/etc/samba# systemctl restart samba
Job for samba.service failed because the control process exited with error code.
See "systemctl status samba.service" and "journalctl -xe" for details.
root@dm520:/etc/samba#
-----------------------------------------------------
root@dm520:/etc/samba# journalctl -xe
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has begun starting up.
Jan 22 14:14:38 dm520 systemd[436]: samba.service: Failed at step EXEC spawning /usr/sbin/samba: No such
-- Subject: Process /usr/sbin/samba could not be executed
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/sbin/samba could not be executed and failed.
--
-- The error number returned by this process is 2.
Jan 22 14:14:38 dm520 systemd[1]: samba.service: Main process exited, code=exited, status=203/EXEC
Jan 22 14:14:38 dm520 systemd[1]: Failed to start Samba AD Daemon.
-- Subject: Unit samba.service has failed
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit samba.service has failed.
--
-- The result is failed.
Jan 22 14:14:38 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 22 14:14:38 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.
Jan 22 14:14:59 dm520 enigma2[194]: nr_read 462 nr_write 1
Jan 22 14:14:59 dm520 enigma2[194]: sum 463 prev_sum 463
Jan 22 14:14:59 dm520 enigma2[194]: hdd IDLE!
Jan 22 14:14:59 dm520 enigma2[194]: [IDLE] 119.999996185 300 False
Jan 22 14:14:59 dm520 enigma2[194]: nr_read 248 nr_write 1
Jan 22 14:14:59 dm520 enigma2[194]: sum 249 prev_sum 249
Jan 22 14:14:59 dm520 enigma2[194]: hdd IDLE!
Jan 22 14:14:59 dm520 enigma2[194]: [IDLE] 900.000357866 300 True
----------------------------------------------------------------------------------
root@dm520:/etc/samba# systemctl status samba.service
● samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since So 2017-01-22 14:15:50 CET; 16s ago
Process: 447 ExecStart=/usr/sbin/samba $SAMBAOPTIONS (code=exited, status=203/EXEC)
Main PID: 447 (code=exited, status=203/EXEC)

Jan 22 14:15:50 dm520 systemd[1]: Starting Samba AD Daemon...
Jan 22 14:15:50 dm520 systemd[447]: samba.service: Failed at step EXEC spawning /usr/sbin/samba: No such
Jan 22 14:15:50 dm520 systemd[1]: samba.service: Main process exited, code=exited, status=203/EXEC
Jan 22 14:15:50 dm520 systemd[1]: Failed to start Samba AD Daemon.
Jan 22 14:15:50 dm520 systemd[1]: samba.service: Unit entered failed state.
Jan 22 14:15:50 dm520 systemd[1]: samba.service: Failed with result 'exit-code'.


Danke für die eure Hilfe

wenn ich die Hdd2 wieder aus dem Samba Config herausnehme und die DM neu starte wird das Share auch nicht mehr angezeigt.Irgendwas funktioniert noch nicht so richtig mit smb

Wenn ich mit dem Backup Restore Manager die Netzwerk Einstellungen wiederherstelle und die DM neu starte , dann kann ich wieder auf HDD1 zugreifen

Hi,

also wenn ich im Putty samba stop ausführe kommen einige Meldungen aber Samba ist immer noch aktiv

root@dm520:~# /etc/init.d/samba stop
/etc/init.d/samba: line 15: /usr/bin/ps: No such file or directory
/etc/init.d/samba: line 17: /usr/bin/sed: No such file or directory
/etc/init.d/samba: line 16: /usr/bin/grep: No such file or directory
/etc/init.d/samba: line 15: /usr/bin/ps: No such file or directory
/etc/init.d/samba: line 16: /usr/bin/grep: No such file or directory
/etc/init.d/samba: line 17: /usr/bin/sed: No such file or directory
root@dm520:~#

Hi ,

leider kann ich den link nicht öffnen ,da fehlen mir wohl noch etwas die Berechtigungen :(.... Wie kann ich die erhalten?!?

mecky76