Samba Shares and CPU Temp

Still not working: Samba shares not working at all, cant share anything with windows and CPU Temp not working correct it show -1 celsius on Kodi 19.3 on DietPi v8.1.2 on Raspberry Pi 4 Model B 8GB (aarch64)

I’ve send it a bug report : 86ef7574-4cba-44d5-8de7-0ea990863f4a

For the SMB problem please paste the output of cat /etc/samba/smb.conf
And what exactly is not working? You can’t connect to your share? You can’t write to it? Pls a little bit more info.

indeed some more information would be needed. Otherwise we are not able to help. Pls describe more in detail what is not working and where you are struggle for SAMBA

I’m With Windows 11 Pro and when trying to connect to dietpi over samba i can’t access it and it gives its error on Windows 0x80004005

cat /etc/samba/smb.conf
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes
\
\
\
#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
\
\
####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<<kahan@informatik.tu-muenchen.de>> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
#   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
comment = Home Directories
browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

But this is not the configuration file how DietPi is creating it.

Question: how did you install samba?

I’ve install samba on dietpi-software has normal.

try to install SAMBA as your configuration file is the one from the original SAMBA package and not the one provided by DietPi

dietpi-software reinstall 96
cat /etc/samba/smb.conf
1 Like

I have the same problem, I reinstalled samba through the command you passed and it didn’t work, could you help me. same message applying. cat /etc/samba/smb.conf.

System odroid c4

can you try to remove the configuration first

rm /etc/samba/smb.conf
dietpi-software reinstall 96
1 Like

thanks, as soon as i get home i’ll test this solution.

 workgroup = WORKGROUP
         server string = %h server
         dns proxy = no
         log file = /var/log/samba/log.%m
         max log size = 1000
         syslog only = no
         syslog = 0
 
         panic action = /usr/share/samba/panic-action %d
 
         security = user
         encrypt passwords = true
         passdb backend = tdbsam
         obey pam restrictions = yes
         unix password sync = yes
 
         passwd program = /usr/bin/passwd %u
         passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
         pam password change = yes
         map to guest = bad user
 
         load printers = no
         printcap name = /dev/null
         disable spoolss = yes
 
 [dietpi]
         comment = DietPi Share
         path = /mnt/dietpi_userdata
         browseable = yes
         create mask = 0664
         directory mask = 0775
         valid users = dietpi
         writeable = yes
 max connections = 8

any problem in the configuration? I reinstalled samba, I would like to view the mnt/HD folder

on our default configuration, external USB disk are not shared automatically. This is something you would need to configure manually, following our online docs SAMBA - Destination directory

1 Like

thank you, I solved it. I would like to leave it without a password, can you help me?
on windows I was able to enter the password and it is working, but on Kodi I can’t see the smb network.

edit: it was working on windows but it stopped working out of nowhere

what exactly is not working? Did you reboot your system? Does the smb service is still running? Did you checked smb logs?

1 Like
root@DietPi:~# systemctl status smbd nmbd
● smbd.service - Samba SMB Daemon
     Loaded: loaded (/lib/systemd/system/smbd.service; disabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-07-18 01:25:14 BST; 7h ago
       Docs: man:smbd(8)
             man:samba(7)
             man:smb.conf(5)
    Process: 1882 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
   Main PID: 1886 (smbd)
     Status: "smbd: ready to serve connections..."
      Tasks: 3 (limit: 3446)
     Memory: 17.1M
        CPU: 1.351s
     CGroup: /system.slice/smbd.service
             ├─1886 /usr/sbin/smbd --foreground --no-process-group
             ├─1888 /usr/sbin/smbd --foreground --no-process-group
             └─1889 /usr/sbin/smbd --foreground --no-process-group

Jul 18 01:25:14 DietPi systemd[1]: Starting Samba SMB Daemon...
Jul 18 01:25:14 DietPi systemd[1]: Started Samba SMB Daemon.
Jul 18 01:28:24 DietPi smbd[2262]: pam_unix(samba:session): session closed for user nobody
Jul 18 01:28:53 DietPi smbd[2361]: pam_unix(samba:session): session closed for user nobody
Jul 18 01:34:20 DietPi smbd[2430]: pam_unix(samba:session): session closed for user nobody
Jul 18 01:37:05 DietPi smbd[2435]: pam_unix(samba:session): session closed for user nobody
Jul 18 01:37:20 DietPi smbd[2439]: pam_unix(samba:session): session closed for user nobody
Jul 18 08:47:08 DietPi smbd[2878]: pam_unix(samba:session): session closed for user nobody
● nmbd.service - Samba NMB Daemon
     Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-07-18 01:25:14 BST; 7h ago
       Docs: man:nmbd(8)
             man:samba(7)
             man:smb.conf(5)
   Main PID: 1866 (nmbd)
     Status: "nmbd: ready to serve connections..."
      Tasks: 1 (limit: 3446)
     Memory: 19.2M
        CPU: 997ms
     CGroup: /system.slice/nmbd.service
             └─1866 /usr/sbin/nmbd --foreground --no-process-group

Jul 18 01:25:13 DietPi systemd[1]: Starting Samba NMB Daemon...
Jul 18 01:25:14 DietPi systemd[1]: Started Samba NMB Daemon.

SAMBA is running and working. Still the question, what is the exact issue now?

1 Like

my smb network is not visible either on windows that I access from the notebook or on Kodi through the nvidia shield, on windows it worked for a period and then it was not visible again, I’m new to the system, that’s why my difficulty, thank you very much in advance.I’m running dietpi on the latest version for odroid c4 installed on a micro sd sandisk

are you able to access the SAMBA share if you enter the IP address directly within the Windows explorer?

You would need to install Web Service Discovery host daemon, to allow Windows to find the share automatically.

1 Like

Not yet, I’m kind of lost on this install, anyway, thanks a lot for the help so far. I’m at work, as soon as I arrive I’ll test it

could you help me with the installation? what command do i use?