Centos 7 Linux server smba share folder issue
Hi Experts
I have a customer that has Centos 7 samba file server installed.
The exciting storage is LVM volume consists of 3 hard disks (1TB x 3), configured RAID5(centos level), formatted in XFS file system.
My scope is to upgrade the storage of the server using additional 2TB x 4 hard disks.
I just simply created additional RAID5 volume using Utilities-Disk and formatted the new volume in EXT4 file system, created a new shared folder there.
The problem is the shared folder created in new volume I created cannot be accessed by Windows 7 users, get error message" contact network administrator" etc. But it can be accessed from Windows XP machine.
After some Googling, found some suggestion about changing setting for "Network security: LAN Manager authentication level" for windows 7 but it doesn't work.
The confusing here is why it simply doesn't work while it is just the new volume, in the same server ?
The only difference with exciting old shared folder volume is file system. Any idea why it's shared folder can't be accessed ?
Question:
1.
Can I simply extend exciting LVM volume with additional 2TB x 4 (raid5) ? Can I add new HDD to exciting Volume group ?
If yes, please advise the step? If I do that, would that fix the issue?
Please note that the old volume is 1TB x 3 RAID5 volume, new hard disks are 2TBx4 hard disks.
I need to carefully do this not to affect exciting shared folder and volume.
2.
If I delete new RAID5 array (2TBx 4) partition and create new Volume group/ new Logical volume using VGCREATE, LVCREATE, format the new volume in XFS file system/ create shared folder there, would that fix the issue ?
Please advise.
Thanks
I have a customer that has Centos 7 samba file server installed.
The exciting storage is LVM volume consists of 3 hard disks (1TB x 3), configured RAID5(centos level), formatted in XFS file system.
My scope is to upgrade the storage of the server using additional 2TB x 4 hard disks.
I just simply created additional RAID5 volume using Utilities-Disk and formatted the new volume in EXT4 file system, created a new shared folder there.
The problem is the shared folder created in new volume I created cannot be accessed by Windows 7 users, get error message" contact network administrator" etc. But it can be accessed from Windows XP machine.
After some Googling, found some suggestion about changing setting for "Network security: LAN Manager authentication level" for windows 7 but it doesn't work.
The confusing here is why it simply doesn't work while it is just the new volume, in the same server ?
The only difference with exciting old shared folder volume is file system. Any idea why it's shared folder can't be accessed ?
Question:
1.
Can I simply extend exciting LVM volume with additional 2TB x 4 (raid5) ? Can I add new HDD to exciting Volume group ?
If yes, please advise the step? If I do that, would that fix the issue?
Please note that the old volume is 1TB x 3 RAID5 volume, new hard disks are 2TBx4 hard disks.
I need to carefully do this not to affect exciting shared folder and volume.
2.
If I delete new RAID5 array (2TBx 4) partition and create new Volume group/ new Logical volume using VGCREATE, LVCREATE, format the new volume in XFS file system/ create shared folder there, would that fix the issue ?
Please advise.
Thanks
ASKER
Hi
"Since the other was xfs, why use ext4 in this one?"
I use GUI from Utilities- Disk to format new RAID5 volume for new array, there is no XFS option to choose as file system, only fat32, ntfs, ext4 hence I choose ext4.
When I go through online articles, I realize I can use XFS from CLI.
Selinux is disabled, verified. Now I don't have access to server, just testing in LAB.
What could be causing the new shared not accessible by Windows 7 ?
What do you suggest for my scenario that would work ? Format to XFS would fix ? Extend the volume would fix ? Could you please provide step/how to verify to extend the volume group ?
Thanks
"Since the other was xfs, why use ext4 in this one?"
I use GUI from Utilities- Disk to format new RAID5 volume for new array, there is no XFS option to choose as file system, only fat32, ntfs, ext4 hence I choose ext4.
When I go through online articles, I realize I can use XFS from CLI.
Selinux is disabled, verified. Now I don't have access to server, just testing in LAB.
What could be causing the new shared not accessible by Windows 7 ?
What do you suggest for my scenario that would work ? Format to XFS would fix ? Extend the volume would fix ? Could you please provide step/how to verify to extend the volume group ?
Thanks
I do not know what is preventing your windows 7, did you lower the security threshold from 128 to 40 bits in the file sharing
Where you are testing, do you have access to both, on the server you need to look at the share settings.....
Your 6TB raid5 how are you partitioning it ? do you have a single 6TB logicalvolume?
Where you are testing, do you have access to both, on the server you need to look at the share settings.....
Your 6TB raid5 how are you partitioning it ? do you have a single 6TB logicalvolume?
ASKER
Hi Arnold
I only created 6TB RAID5 volume. haven't created volume. Would I be able to do as below:
1. Created 6TB volume as logical disk.
2. Can add 6TB volume to exciting volume group(2TB volume) ? How to add without affecting exciting 2TB volume ?
How can I add and extend exciting volume ?
Thanks
I only created 6TB RAID5 volume. haven't created volume. Would I be able to do as below:
1. Created 6TB volume as logical disk.
2. Can add 6TB volume to exciting volume group(2TB volume) ? How to add without affecting exciting 2TB volume ?
How can I add and extend exciting volume ?
Thanks
Pvcreate the new /dev/md<letter/number for the 6TB raid5 disk>
To see it fdisk -l will list your disks and their partitions
cat /proc/mdstat
To see your raided volumes
The 6TB volume filesystem type needs to be lvm.
Vgextend VolGroup /dev/mdx
Lvresize will be the way to expand the logical volume..
If you are in a lab, test expanding the existing raid5 volume by adding additional drives.
To see it fdisk -l will list your disks and their partitions
cat /proc/mdstat
To see your raided volumes
The 6TB volume filesystem type needs to be lvm.
Vgextend VolGroup /dev/mdx
Lvresize will be the way to expand the logical volume..
If you are in a lab, test expanding the existing raid5 volume by adding additional drives.
ASKER
I think extending Vgroup would not extend lv.
Would I need to extend lv as well after extending vgroup ?
Would I need to extend lv as well after extending vgroup ?
ASKER
btw, how can I check the log why win7 machine unable to access shared folder ? SMB log ?
If you are familiar with Webmin, can I see smb log from Webmin ?
Thanks
If you are familiar with Webmin, can I see smb log from Webmin ?
Thanks
you have to look at the linux box to see whether it indicates why the attempt from windows 7 fails.
check sharing and reduce the encryption to 40 bits. and see.
the username with which you are logged in might not allow or match the .......
The process is
pvcreate to define the new volume
vgextend to extend the VolumeGroup
Lvresize to use the new space in the VolumeGroup to increase the size of the logical volume.
i.e. until you make a container larger, the items within are limited to the size of the container.
I've heard of webmin, but have not used it.
When approaching anything, look around, the naming of logs, etc. should be there if accessible from that interface.
check sharing and reduce the encryption to 40 bits. and see.
the username with which you are logged in might not allow or match the .......
The process is
pvcreate to define the new volume
vgextend to extend the VolumeGroup
Lvresize to use the new space in the VolumeGroup to increase the size of the logical volume.
i.e. until you make a container larger, the items within are limited to the size of the container.
I've heard of webmin, but have not used it.
When approaching anything, look around, the naming of logs, etc. should be there if accessible from that interface.
ASKER
The one you mentioned, "check sharing and reduce the encryption to 40 bits. and see"
Where to set it ? In linux folder permission ? How to set ?
If you are referring to Win7 GPEDIT setting, I don't think that is the cause as Win7 machine can access other old shared folder of old volume.
Please advise.
Thanks
Where to set it ? In linux folder permission ? How to set ?
If you are referring to Win7 GPEDIT setting, I don't think that is the cause as Win7 machine can access other old shared folder of old volume.
Please advise.
Thanks
on the windows 7, right click on the network connection indicator, open network and sharing settings/center...
once at the display of network informaiton,,,
open advanced sharing settings
If not mistaken, at the bottom of this page there are the options for the security 128 bit is default
Compare your smb.conf setting on the working server with the smb.conf on the new.......
When using windows 7 to access the share on the new, do you get prompted for a login?
open a command window and try
net use X: \\newlabserver\sambashare /user:username
enter the password for username, do you get access to the share or do you get a system error? what system error?
If you get access to the share, the user with which you are loged into this windows 7 system does not match the samba security and it does not seem to prompt you for login access ......
once at the display of network informaiton,,,
open advanced sharing settings
If not mistaken, at the bottom of this page there are the options for the security 128 bit is default
Compare your smb.conf setting on the working server with the smb.conf on the new.......
When using windows 7 to access the share on the new, do you get prompted for a login?
open a command window and try
net use X: \\newlabserver\sambashare /user:username
enter the password for username, do you get access to the share or do you get a system error? what system error?
If you get access to the share, the user with which you are loged into this windows 7 system does not match the samba security and it does not seem to prompt you for login access ......
ASKER
Hi Arnold
Thanks for your quick respond.
Plz not that it is the same server, only different volume. Old exciting one and the new one I created.
Win7 machine can access shared folder shared from old volume.
Win7 only cannot access shared folder of the new volume.
Since it is same server, there is only single smb.conf file I believe.
Which option u referring to change from 128bit in Win7?? I can't find it.
But I think this won't be solution since Win7 can access shared folder of old volume. Any suggestion ?
Thanks
Thanks for your quick respond.
Plz not that it is the same server, only different volume. Old exciting one and the new one I created.
Win7 machine can access shared folder shared from old volume.
Win7 only cannot access shared folder of the new volume.
Since it is same server, there is only single smb.conf file I believe.
Which option u referring to change from 128bit in Win7?? I can't find it.
But I think this won't be solution since Win7 can access shared folder of old volume. Any suggestion ?
Thanks
does the new volume actually exist?
if you only add an entry in /etc/smb.conf it does not make the volume functional.
for a share to be functional, the logicavolume/partition has to be mounted and reflected in df -k where the entry you added in /etc/smb.conf points to.
Thus far all I can rely on is the information in two of your questions that I am participating, this one and the other.
(in the combination of information from both, it does not seem that your new RAID5 of 6TB is a valid mounted partition to which smb.conf could point and access)
/dev/mdx is not a valid smb.conf entry
please post
fdisk -l #list of physical disks
cat /proc/mdstat # list of software raided volumes
lvmdiskscan #list of devices visible to LVM
pvdisplay #list of physical volumes and their info
vgdisplay #list of volumegroups and their info
lvdisplay #list of logical volumes and their info
df -k #list of mounted partitions
if you only add an entry in /etc/smb.conf it does not make the volume functional.
for a share to be functional, the logicavolume/partition has to be mounted and reflected in df -k where the entry you added in /etc/smb.conf points to.
Thus far all I can rely on is the information in two of your questions that I am participating, this one and the other.
(in the combination of information from both, it does not seem that your new RAID5 of 6TB is a valid mounted partition to which smb.conf could point and access)
/dev/mdx is not a valid smb.conf entry
please post
fdisk -l #list of physical disks
cat /proc/mdstat # list of software raided volumes
lvmdiskscan #list of devices visible to LVM
pvdisplay #list of physical volumes and their info
vgdisplay #list of volumegroups and their info
lvdisplay #list of logical volumes and their info
df -k #list of mounted partitions
Here is a web in user creation/deletion and includes an export option..
http://doxfer.webmin.com/Webmin/Users_and_Groups
http://doxfer.webmin.com/Webmin/Users_and_Groups
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Yes you can run pvcreate in the new volume, then vgextend the VOlumegroup with the new volume, and then lvresize to increase the ......
Not sure you you did not use mdadm to expand the existing raid5 volume.
Though raid5 with such large disks .......
You have to decide the route you want to take, understand the consequences including the backup of the data.
Look at mdadm to expand the existing..
Since the other was xfs, why use ext4 in this one?
Xfs might have been chosen because of the type of files being placed there.
Note there are Selinux settings that you might.. Or sone setting when setting up this share in the smb.conf omitted a reference/entry that exists in the other.