Cannot access Mint 14 SSD RAID 1 Drive [SOLVED]

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read this

Cannot access Mint 14 SSD RAID 1 Drive [SOLVED]

Postby jackmason on Wed Jan 30, 2013 5:30 pm

Mint 14 has mdadm SSD RAID1 NTFS drive(s) mounted and usable from Mint. Using Mint and accessing network drives on Windows 7, files can be dragged from Windows 7 to the Mint RAID drive.

On Mint, the RAID drive has been shared and is visible from Windows 7 but cannot be accessed. We want the Mint RAID drive to be mounted on 8 Windows 7 computers simultaneously and used by them for read/write, create directories, etc. and do not want these systems to have to use a username or password to mount the drive, which is what we now do with the existing Windows 7 Pro RAID drive.

How do we make Mint do what we need or do we just need to continue using Windows? After reading a couple of articles on how to set this drive up, here is what we have so far for /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.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

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

[global]

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
server string = %h server (Samba, LinuxMint)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### 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

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

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


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

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 ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if '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

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ 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

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

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

# Maximum number of usershare. 0 (default) 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 director as \\server\username
;[homes]
comment = Home Directories
browseable = yes

# 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 = no

# 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 = 0775

# 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 = 0775

# 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
# The following parameter makes sure that only "username" can connect
#
# 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 = no

# 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

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
Last edited by jackmason on Thu Jan 31, 2013 5:20 pm, edited 1 time in total.
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Linux Mint is funded by ads and donations.
 

Re: Cannot access Mint 14 SSD RAID 1 Drive

Postby TheForumTroll on Wed Jan 30, 2013 9:05 pm

I cannot seem to find where you have shared the drive ("the RAID drive has been shared and is visible from Windows 7"). All I see is shared /home's and that would be pointless with no logins I would think.

I was expecting to see something like this...

[diskName]
comment = disk
path = /disk
valid users = someone
public = yes
writable = yes
printable = no
create mask = 0700

I'm sorry if I missed it and need to go clean my glasses or get some sleep. It's late here :lol:
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Cannot access Mint 14 SSD RAID 1 Drive

Postby jackmason on Thu Jan 31, 2013 2:36 pm

I added this to /etc/samba/smb.conf:

[bfl_mint]
comment = disk
path = /media/bfl
public = yes
writable = yes
printable = no
create mask = 0775

I want everyone to have access to the drive and did not know what to put for users. The mount point is /media/bfl, so I used that. Should it be something else? It does not work as is.

Thanks
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Unable to mount location

Postby jackmason on Thu Jan 31, 2013 3:45 pm

After making changes to /etc/smb.conf provided via other posts, I can no longer access Windows shared drives from Mint 14. The message is:

Unable to mount location
Failed to retrieve share list from server.

Prior to the changes, things did work. Is there a way to return to the default smb.conf file and start over?

Here is the file as it is now:

#
# 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.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

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

[global]

## Browsing/Identification ###
netbios name = mint14

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

# server string is the equivalent of the NT Description field
server string = %h server (Samba, LinuxMint)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
name resolve order = lmhosts host wins bcast

#### 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

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

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


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

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 ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if '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

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ 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

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

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

# Maximum number of usershare. 0 (default) 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 director as \\server\username
;[homes]
comment = Home Directories
browseable = yes

# 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 = no

# 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 = 0775

# 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 = 0775

# 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
# The following parameter makes sure that only "username" can connect
#
# 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 = no

# 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

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[bfl_mint]
comment = disk
path = /media/bfl
public = yes
writable = yes
printable = no
create mask = 0775
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Re: Unable to mount location

Postby altair4 on Thu Jan 31, 2013 4:01 pm

If this is a normal home lan you have this line almost reversed:
name resolve order = lmhosts host wins bcast

Put bcast first:
Code: Select all
name resolve order = bcast lmhosts host wins


By the way you have some errors in your smb.conf that's making the command "testparm -s" output funny results so you might want to clean it up a bit:

** Remove the ";" in front of [homes]:
;[homes]

** Put ";" in front of each line not just the first 2:
;[netlogon]
; comment = Network Logon Service
path = /home/samba/netlogon
guest ok = yes
read only = no

Then restart samba:
Code: Select all
sudo service smbd restart
sudo service nmbd restart
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6028
Joined: Tue Feb 03, 2009 10:27 am

How to set up shared drives

Postby jackmason on Thu Jan 31, 2013 4:02 pm

We have set up Mint 14 with a static IP address, which pings fine. We have set up two SSD drives as RAID1 under Mint and mounted them as in /etc/fstab as /dev/md127 on /media/bfl as ntfs and rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush.

That all seems to work. We are trying to replace a Windows 7 Pro Firebird server with Mint and have installed Firebird 2.5. That seems to work and has been accessible from Windows systems. We have defined the workgroup in /etc/samba/smb.conf as TIGER, and that seems to work.

However, we have been given conflicting advice from the network posts and the Internet on how to make Mint talk to Windows, and vice versa. We believe our /etc/samba/smb.conf file has some problems so we are willing to begin again and reinstall Mint from scratch. At one point, we could get over TIGER and see the Windows drives and even copy files to our RAID drive.

The problem we have not been able to surmount is how to let Windows access our RAID drive. It will be mounted on at least 6 Windows computers as a standard Windows drive for programs, files, and email storage. The best we have been able to do so far is to have Windows see the drive as a mounted drive (bfl_mint) but not be able to access it because of permissions.

We want all Windows computers on our network to be able to access the drive so it can be mounted without having to have a username and password. How do we do that?

Thanks
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Re: How to set up shared drives

Postby altair4 on Thu Jan 31, 2013 4:08 pm

We want all Windows computers on our network to be able to access the drive so it can be mounted without having to have a username and password.

It's not going to happen with this mount:
We have set up two SSD drives as RAID1 under Mint and mounted them as in /etc/fstab as /dev/md127 on /media/bfl as ntfs and rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush.

I don't do raid but this is what umask=077 does: It creates a mount point with these permissions:
drwx------

A samba guest comes across as a Linux "other" so umask has to be set at umask=000.

EDIT: OR, you can keep it the way it is and force the smb guest to become whoever the user is represented by "uid=1000". For example:
[bfl_mint]
comment = disk
path = /media/bfl
public = yes
writable = yes
printable = no
force user = altair
create mask = 0775

Change altair to whoever "uid=1000" is.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6028
Joined: Tue Feb 03, 2009 10:27 am

Re: Unable to mount location

Postby jackmason on Thu Jan 31, 2013 4:24 pm

Thank you very much!!!! We can now get to the Windows drives again.

A new drive showed up from Windows (homes, Share) but it, like our RAID 1 drive (bfl_mint) are still permission denied. If you can fix the problem with us not being able to mount bfl_mint, we would be most happy to send you a free book of your choice (we are a bookstore).

Thanks
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Re: Unable to mount location

Postby altair4 on Thu Jan 31, 2013 4:26 pm

You have 3 topics opened up on basically the same subject. See my answer on the other one.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6028
Joined: Tue Feb 03, 2009 10:27 am

Re: Unable to mount location

Postby altair4 on Thu Jan 31, 2013 4:46 pm

A new drive showed up from Windows (homes, Share)

It's because you made it browseable. A "homes" share should not be made browseable and besides it won't do you much good without real samba users so edit smb.conf again and comment out the line with a # sign:
[homes]
comment = Home Directories
#browseable = yes
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6028
Joined: Tue Feb 03, 2009 10:27 am

Re: Unable to mount location [SOLVED]

Postby jackmason on Thu Jan 31, 2013 5:02 pm

I had to do

; [homes]
; comment = Home Directories
# browseable = yes

to get rid of the homes drive showing up.

Hope that is okay.
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Re: Unable to mount location

Postby altair4 on Thu Jan 31, 2013 5:12 pm

Your "testparm -s" will look funny again but you basically only have one big share so it doesn't matter much. Did this work for you: viewtopic.php?f=90&t=124410
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6028
Joined: Tue Feb 03, 2009 10:27 am

Re: How to set up shared drives

Postby jackmason on Thu Jan 31, 2013 5:17 pm

I changed the /etc/fstab entry to be:

/dev/md127 /media/bfl ntfs rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=000,nounix,flush 0 2

Looking at one of your other posts, you indicated:

//192.168.0.200/Daten /media/Daten cifs user=rudi,password=geheim,rw,iocharset=utf8,codepage=850,uid=1000,nounix 0 0

should I change mine to be cifs as well? Is that a better way to mount a Windows drive?

The force user = bfl and changing umask did it. I can now get to the drive from windows.

You do not know how much this helps!!!!

Send me an email (jack@mybfl.com) with your shipping address and some book titles you would like to have and I will get them shipped out to you. You have saved me several days of work!!

I will mark all three posts (did not realize I had three) as solved as soon as I figure out how to edit them.
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Re: Cannot access Mint 14 SSD RAID 1 Drive [SOLVED]

Postby TheForumTroll on Thu Feb 07, 2013 11:48 am

Sorry I'm a bit late to the party, but two things:

First off, the one line you write is for mounting a remote share (I.E. on a remote linux client) and the other is for mounting a local drive (on the server where the disk is physically at):

Local: /dev/md127 /media/bfl ntfs rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=000,nounix,flush 0 2
Remote: //192.168.0.200/Daten /media/Daten cifs user=rudi,password=geheim,rw,iocharset=utf8,codepage=850,uid=1000,nounix 0 0

Local should use the type of filesystem (NTFS) and remote the network protocol (CIFS) as a remote client don't care what filesystem it is (so you can mount a Linux filesystem like ext4 on a Windows client for example). So no, you should not use CIFS for mounting a local NTFS disk :)


Secondly, /etc/fstab is publicly readable, meaning a non-root user can read it (otherwise how could they mount anything?):
Code: Select all
ls -l /etc/fstab
-rw-r--r-- 1 root root 1686 Dec 23 02:01 /etc/fstab

Try it out yourself with "less /etc/fstab".

Your password, though it might not be needed to be kept safe, would be better off in another file. Of course since this is using Windows networking it is sent over the network in clear text as per the Windows specifications, but still. I would do something like this (change to whatever user you are using):

Code: Select all
//192.168.0.200/Daten /media/Daten cifs rw,credentials=/home/rudi/.smbcredentials,uid=1000,gid=1000,file_mode=0755,dir_mode=0755,iocharset=utf8 0 0


...and then create the file with username and password:
Code: Select all
sudo nano /home/rudi/.smbcredentials


Enter it like this:
Code: Select all
username=rudi
password=geheim


Lock down the file, save and remount with something like this:
Code: Select all
sudo chmod 0400 /home/rudi/.smbcredentials
sudo umount /media/Daten
sudo mount /media/Daten


Remember, anyone can read the password if they can access the network with the share (sorry, nothing to do about that unless Microsoft change it) so better not use a login from the server itself or anything else, just in case.
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Cannot access Mint 14 SSD RAID 1 Drive [SOLVED]

Postby altair4 on Thu Feb 07, 2013 1:16 pm

@jackmason

On the off chance you come back to this [SOLVED] topic there is no need to do any of what TheForumTroll posted above.

This is a long thread and is actually a merging of 2 separate threads so the original issue may have gotten lost in the flow. You have a server with one share that allows guest access from your clients. You wouldn't have anything in fstab that references cifs.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
altair4
Level 16
Level 16
 
Posts: 6028
Joined: Tue Feb 03, 2009 10:27 am

Re: Cannot access Mint 14 SSD RAID 1 Drive [SOLVED]

Postby TheForumTroll on Thu Feb 07, 2013 6:57 pm

Well, what a mess :lol:
PC: Intel I5-2500K || ASUS Sabertooth P67 || 4GB Corsair XMS3 || Gainward GTX 460 GS-GLH || OCZ Vertex 3 || Noctua NH-D14 || Corsair HX 750W || NZXT PanzerBox || Zalman ZM-MFC1+ || ASUS VW246H || Microsoft SideWinder X6 || Logitech G9 Lazer
TheForumTroll
Level 2
Level 2
 
Posts: 58
Joined: Tue Aug 21, 2012 3:47 am

Re: Cannot access Mint 14 SSD RAID 1 Drive [SOLVED]

Postby jackmason on Wed Feb 13, 2013 8:35 pm

It works now, so everything is good. No usernames or passwords in /etc/fstab. Thanks to both of you!
jackmason
Level 2
Level 2
 
Posts: 61
Joined: Fri Jan 25, 2013 6:00 pm

Linux Mint is funded by ads and donations.
 

Return to Newbie Questions

Who is online

Users browsing this forum: Bing [Bot], Kugelsicher and 15 guests