My setup:

unRAID 4.4.2 Basic

 

Protected array:

(disk0) parity 1.5 TB Seagate

disk1 1.5 TB WD Green (really full)

disk2 1.5 TB Seagate (really empty)

 

Unprotected disk (flash drive as well):

disk5 80gb Hitachi

 

disk5 is mounted in my go script with:

mkdir /mnt/disk5

mount -t reiserfs -o acl,user_xattr,noatime,nodiratime /dev/disk/by-id/scsi-SATA_HDS728080PLA380_PFDBU0EJS265WX-part1 /mnt/disk5

 

1 simple question before I get to my real headscratcher:  how do i share /mnt/disk5 at \\tower\disk5 - exporting the Disk shares (SMB) only works for the disks in the array.

 

Now the real issue. 

 

My initial setup was parity + disk1 array with new disks.  Moved lots of data to disk1 through a couple of user shares.  This emptied off my existing disk2 which was in a windows box.  I moved disk2 into the unraid box.  precleared.  added to array.  All went well with littlie drama.

 

Now I want to spread out my data a bit in order to avoid unnecessary spinup.

 

I have a user share called "backup" which used to include disk 1.  I changed it to include disk 2 (although I did not excluce disk1)

 

in /mnt/disk1/backup i had two folders one called jack and one called jill (names changed to protect the innocent) that covers my wife and my laptops respectively.

 

jill contained about 3gb of data (docs).

jack contained about 230gb of data (ghost images).

 

I executed:

root@silo:/mnt/disk1/backup# mv jill ../../disk2/backup/

Went off without a hitch (note I didn't know about nohup or "&" tips yet and did this from a screen session from another unix box.  I know for next time.)

 

I then executed:

root@silo:/mnt/disk1/backup# mv scott ../../disk2/backup/

 

But now I see files showing up in /mnt/disk5/backup.

 

My two user shares are backup and media.

 

I also want to spread out my "media" user share between the two disks as well with some manual copying to /mnt/disk2. 

 

How do I stop this from happening?  What am I doing wrong?  Do you need to see any config files?  Did I need to reload samba after making changes to user shares?  Should I mount disk5 as something other then "diskN"?

 

Thanks,

 

--dimes

 

Don't use /mnt/diskN as a personal mount point of an unprotected drive...  Use something elsewhere. I'll bet you are getting the user-shares very confused.

 

Try something like /tmp/disk5 as the mount point for your unprotected disk.

 

Joe L.

 

I usually use /mnt/partitionname

 

so if there is a /dev/sdj1

 

I do

 

mkdir /mnt/sdj1

mount /dev/sdj1 /mnt/sdj1

 

By adding an entry to /etc/samba/smb-shares.conf like

 

root@Atlas /etc/samba #tail /etc/samba/smb-shares.conf 
        read only = No
[sdj1]
        path = /mnt/sdj1
        read only = no (or yes)

 

then doing a

 

smbcontrol smbd reload-config

 

will make the partition accessible over samba.

 

Keep in mind you will not be able to umount it if samba has files open.

Don't use /mnt/diskN as a personal mount point of an unprotected drive...  Use something elsewhere. I'll bet you are getting the user-shares very confused.

 

Try something like /tmp/disk5 as the mount point for your unprotected disk.

 

Joe L.

 

 

I had a feeling this was it but have to wait for this mv to finish before testing.  Will do.  Thanks.

 

I usually use /mnt/partitionname

 

so if there is a /dev/sdj1

 

I do

 

mkdir /mnt/sdj1

mount /dev/sdj1 /mnt/sdj1

 

By adding an entry to /etc/samba/smb-shares.conf like

 

root@Atlas /etc/samba #tail /etc/samba/smb-shares.conf 
        read only = No
[sdj1]
        path = /mnt/sdj1
        read only = no (or yes)

 

then doing a

 

smbcontrol smbd reload-config

 

will make the partition accessible over samba.

 

Keep in mind you will not be able to umount it if samba has files open.

 

Thanks.

 

I definitely want to only use code that won't break if I reorder my disks or swap out hardware.  Hence my use of only /by-id.  I'll probably just mount it as /dev/hit80 or something similar.

 

So editing smb-shares.conf is the general way to add smb shares but what is the "unraid" way.  Won't smb-shares.conf overwrite when I reboot? 

 

Should I, at the very top of my go script, mount to /mnt/hit80 and then i echo >> into smb.shares?  This way my changes won't be overwritten on reboot and future unRAID upgrades will be simpler becasue I haven't modified the bz files.  Am I understanding this correctly?  I'm about two weeks into serious unRAIDing.

 

Thanks again,

 

--dimes

I usually use /mnt/partitionname

 

so if there is a /dev/sdj1

 

I do

 

mkdir /mnt/sdj1

mount /dev/sdj1 /mnt/sdj1

 

By adding an entry to /etc/samba/smb-shares.conf like

 

root@Atlas /etc/samba #tail /etc/samba/smb-shares.conf 
        read only = No
[sdj1]
        path = /mnt/sdj1
        read only = no (or yes)

 

then doing a

 

smbcontrol smbd reload-config

 

will make the partition accessible over samba.

 

Keep in mind you will not be able to umount it if samba has files open.

 

Thanks.

 

I definitely want to only use code that won't break if I reorder my disks or swap out hardware.  Hence my use of only /by-id.  I'll probably just mount it as /dev/hit80 or something similar.

 

So editing smb-shares.conf is the general way to add smb shares but what is the "unraid" way.  Won't smb-shares.conf overwrite when I reboot? 

 

Should I, at the very top of my go script, mount to /mnt/hit80 and then i echo >> into smb.shares?  This way my changes won't be overwritten on reboot and future unRAID upgrades will be simpler becasue I haven't modified the bz files.  Am I understanding this correctly?  I'm about two weeks into serious unRAIDing.

 

Thanks again,

 

--dimes

If you are using the latest version or two, you can put your smb commands in

config/smb-extra.conf

 

They are automatically included in the samba config even if you reboot.

 

Also, if you put lines at the top of your "go" script, unRAID will not have started the array... so put your extras at the end... and put a sleep 30 in between.

 

# At the end of the "go" script

sleep 30

mkdir /mnt/sdj1

mount ..... /mnt/sdj1

 

It is not the most sophisticated, but it will work.

If you are using the latest version or two, you can put your smb commands in

config/smb-extra.conf

 

They are automatically included in the samba config even if you reboot.

 

Ahh.. did not know about this one...

Will have to use it now! Thanks Joe!

If you are using the latest version or two, you can put your smb commands in

config/smb-extra.conf

 

They are automatically included in the samba config even if you reboot.

 

Ahh.. did not know about this one...

Will have to use it now! Thanks Joe!

First introduced in 4.5beta2... slightly changed in 4.5beta3 onward

(name of included file changed from 'boot/config/smb.extra' to 'boot/config/smb-extra.conf' )

 

Mentioned in the release notes... with a lot of other nice features.

Thanks.

 

In the meantime for the 4.4.2 users like me:

 

cat /boot/config/smb-extra.conf >> /etc/samba/smb.shares
smbcontrol smbd reload-config

 

...gets it done when you upgrade to >4.5.x just delete the lines and the system will do it if you named the smb-extra.conf file appropriately.

 

Thanks for the help.  I'm doing my best not to edit bzroot and bzimage and have been successful thus far.

Thanks.

 

In the meantime for the 4.4.2 users like me:

 

cat /boot/config/smb-extra.conf >> /etc/samba/smb.shares
smbcontrol smbd reload-config

 

...gets it done when you upgrade to >4.5.x just delete the lines and the system will do it if you named the smb-extra.conf file appropriately.

 

Thanks for the help.  I'm doing my best not to edit bzroot and bzimage and have been successful thus far.

You are more efficient than you might realize...

 

The samba config file name in /etc/samba also changed in 4.5.3... your line described above will simply create a small un-used file in /etc/samba.

It will not append to the existing file samba config file, because the config file used in 4.5.3 is /etc/samba/smb-shares.conf

 

So... the two lines work now...when you append the file in config to the one in /etc, and will also work when you upgrade, when it includes the file in config on its own...  Nice work.

 

I've not had to edit bzroot or bzimage either... and I'm certain I've had more unusual customizations than most unRAID users in my server.

 

Joe L.