I posted this on the clonezilla forum but i think it is a permission issue with samba on my
ubuntu 20.04 server
I’m trying to use clonezilla to save the image of a pc directly to the samba share on my server.
I get as far as mounting the share and get the error “access denied directory does not exist”
on the windows pc the share is /data/shares
on the ubuntu server the smb.conf the data path is /mnt/raid ( which is on sdb)
this is the first time I’m trying to clone to the samba share,
I’ve tried using the the super user and root user id’s
I’m not sure what permission are need to have clonezilla use the share
copy and paste your smb.conf within the box created by using the </>
It has been a while since I’ve played with samba shares, I pretty much stick to NFS protocols . Coupled with I don’t use Clonzilla . But I’ll attempt a assist with my limited knowledge.
But it sounds like a write permission error on the samba server share side as a stab in the dark is my first thought. but without a understanding of how your shares are configured limits many in assisting you
P.S.
I’m assuming that you have written to the shares prior to this attempt? Yes /No?
Boot into Clonezilla Live: Start your computer from the Clonezilla bootable media.
Select “device-image” mode: Choose the option to create a disk image.
Configure network settings: Navigate to the network settings within Clonezilla and provide the details of your Samba server, including IP address, share name, username, and password.
Choose the destination path: When selecting where to save the image, specify the network path to your Samba share, for example, smb://server_ip/share_name.
I’ll see about getting the conf posted as soon as i can.
I’ve have written to the share
the link to “windows backup to samba” , that is is the one I tried following and can not get past step 9 in " Backup Image to SAMBA Server" (mounting the image )
#
# 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
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
#### 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 = primary
# classic domain controller', 'server role = 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 =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[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.
# Un-comment the following parameter to make 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
[DATA]
path = /mnt/raid
valid users = @www-data
browsable = yes
writable = yes
read only = no
sgt-mike, Looks like the issue was the user, It appears that the User I use to logon to the server and run maintenance does not have permission to the samba share. I thought that this account should have had permission to all the drives (remotely) is guess not.
I tried using the user account from my windows as the user clonezilla wanted and it was able to mount the drive. ( this account is one that I use to access the shares on the server from the pc)
Thanks of looking at my post and trying to assist me in fixing the issue.
Unless something has changed you can’t just save it wherever. You can assign a clone file name but not the location. It’s only valid location to my knowledge is /home/partimag. Since one has to live boot it to run it it’s just as easy to just live boot a debian live environent, install clonezilla then just using sshfs you can mount right where it needs to go. No messing about with Windows samba shares.
@tross9
I posted to your other thread asking for assistance on the failing hard drive. Sorry I did not put two and two together and that you had posted on UF then here. As well as the details.
I think that the actual solution will be going forth with your other post. Hopefully that will get you to be able to limp along before the drive fails and then you can reconfigure to a easier system.
for your sanity I would look into
a. cockpit
b. webmin
As a start they are web browser based and may be easier for you. A lot of users use one those two just look at them and see if they fit your needs. In my opinion it would make it easier for you as it would afford a GUI to manage a headless CLI server.
Personally when I upload from my windows machine I use webmin to copy to my headless NFS Linux server.
I gave up on Samba years ago, and went in a different direction (not speaking ill of Samba) just changed my methods and usage.
But do stick with linux / or a flavor of as it is really a robust system if configured correctly.
On RAID I’d suggest further evaluation on your end if it’s needed or even simply just desired either way is fine. Just understand it is honestly planning for a drive failure and redundancy. While I have used mdadm and now ZFS I have no issues with either and I do like ZFS a little better after it being suggested by a user on the UF forum. I could go on and on but truth is most of the RAID solutions have pros and cons it’s honestly just picking out the one solution most agreeable for your needs.
I don’t know your machine (box) capability ie number of sata ports or case make up etc.
But I would place my OS on a 64gb drive (no LVM on the install) and then place multiple drives into a RAID or LVM if I desired that. Or simply mount them into munt points if I didn’t need them in a RAID. In my minds eye that is way easier to manage. One other thing keep a cold spare on hand in the event of a drive failing once it is used order another one. Drives will fail.
To prove my point currently I have something like 6 SATA drives (scrub drive /some contain backup data), 2 4TB SAS drives (cold spares), and 2 (128gb) Nvme drives right now waiting on something to fail. And sometime this week another 11 4TB SAS drives are due in for adding another vdev into a existing RAIDZ2 pool. Next month or the month after I’ll look into maybe another 20 4TB SAS drive to start a different zpool.
Just my 2 cents for your thoughts / consideration.
Wish you well with your learning and endeavors.
jmgibson81,
“It’s only valid location to my knowledge is /home/partimag.”
– that is correct, but this was not the problem, it turned out that the account i was using ( which I thought had read/write permission to all drives and folder did not) and when clonzilla tried to mount /home/partimag , it could not.
I finally tried the account that did work , it was the account ( my pc windows account) that i did not think would work, but it did.