Server :: Can't Write To Seagate Blackarmor NAS Through CIFS Mount
Jun 25, 2010
I've got a Seagate Blackarmor NAS which I can mount with CIFS to my Centos 5 server fine but only root can read and write to it. All other users can only read. I've tried several different mount options but results are always the same.
Specific issue: I'm trying to connect the the NAS so Bacula, a backup app, can write backups to it. "bacula" is set up as a user on the NAS. BTW, I'm pretty sure the OS on the NAS is Linux, and I can connect through windows and write fine.
I'm trying to talk the studio I work at into switching one of the departments to linux. (likely kubuntu). So I'm trialling it, but having issues mounting windows shares.It's working great; all except that only Root can write to the mount. I've tried a few different things with fstab, no go.Below is my fstab so far, and you can see the mountpoints.
Code: # /etc/fstab: static file system information. #
I have one NAS device and using samba share one folder without password, how can I use command mount -t cifs to mount this share folder? I tried the below command, but always popup password checking?How should I do mount this folder without password checking?
I am trying to image about 30 laptops with WinXP, and I am using Clonezilla and DRBL for the task. We will start migration to Win7 starting Q4, so for now we are still using XP. I used a Clonezilla live USB to capture a standardized image to a CIFS/SAMBA share on the enterprise file server. The file server does not support NFS. To deploy the image, I used Virtualbox to build a VM with Centos 5.5 and then later Ubuntu 10.10. I mounted the CIFS share to /home/partimag but I found that I cannot share this CIFS mount out as NFS so I was unable to deploy the image with the image still residing on the CIFS; I had to copy the image to the VM's local drive.
Now using the DRBL live distribution, which is Debian based, I was able to obtain the image from a CIFS share and then share it out to the clients to be imaged as NFS (I think). I was able to use the DRBL live for some older computers, but since that hasn't been updated in nearly 2 years, I think it's missing some device drivers for my newer machines so it doesn't work on them -- this is why I looked at using CentOS and Ubuntu. To mount the CIFS shares, I'm using the following command:
mount -t cifs -o user@domain //share_ip_addr/share_name/folder /home/mount_point
Do I need to do something different to enable the mounted CIFS share to be shared out as a NFS share so that the clients to be imaged can see the contents from the CIFS share as a NFS share? The below image depicts my setup. The workstation has two NICs. The 10 network is the enterprise network and the 192 network is for DRBL imaging only. DRBL/Clonezilla does PXE boot and leases DHCP for the laptops. The laptops are shielded from the enterprise LAN; I am not doing any kind of NAT on on the server. The Linux VM is built with dual NICs and are set to bridged mode so they appear to be a separate NIC from the VM host on the network even though they going into the same port on the wall. [URL]
Using Fedore 12 I am trying to mount on a server with the following command: # mount -t cifs //samba-pool-suse/pool-suse /mnt -o user=xxxx I was waiting that the system askme the user password and thats all, but the answer is: mount: wrong fs type, bad option, bad superblock on //samba-pool-suse/pool-suse, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program) In some cases useful info is found in syslog - try dmesg | tail or so using:# dmesg | tail returs: CIFS VFS: cifs_mount failed w/return code = -22
I've been trying for a while mounting a EMC NAS share on linux. As far as I know the NAS share behaves just like a regular windows share, so the mount process should be very similar. On the NAS server, the disc "Disc1" is shared, and I need to mount a sub-subfolder of that share. This is my line in /etc/fstab:
We have a homegrown process that runs on a windows box and produces a csv file. We mount the directory these are output to using autofs/cifs and then process them using a program on our linux database servers.
Is there a way from linux, looking at the cifs share, to tell if the target file is currently in use by a process on the windows box? We are having issues where an incomplete file is being processed occasionally.
I've mounted a kind of proxy to map some cifs folders, 150 aprox. It umounts and mounts everything each hour, to check on changes on a configfile managed by a secretary, she just edits a file with names and I prepared a cron to notice the new mountpoints. It's a debian, no desktop , no nothing else. Just mount.cifs and apache2 to let the master webpage access to some files on each user samba home. The server has 4 cores and 2Gb of RAM. It's brand new, but it goes very slow.
Does anyone have an idea why is that working so slow? The apache is working well, it's the shell which is working extremelly slow.
The mount appears to complete cleanly, however when I browse the directory /winfiles it is always empty.The smbclient command works properly using the same credentials.The /root/credentials file looks something like this
Linux box info: root@mytestbox:~# uname -a Linux mytestbox 2.6.32-30-generic-pae #59-Ubuntu SMP Tue Mar 1 23:01:33 UTC 2011 i686 GNU/Linux
Windows box info: Windows Server 2008 SP2 Enterprise I've verified via --verbose output that mount.cifs is indeed processing the passed on options.
root@mytestbox:~# mount -t cifs //10.1.1.10/Test /root/testwin --verbose -o credentials=/root/testcreds,rw,nocase,noperm,noacl,nounix,noserverin o,iocharset=utf8,file_mode=0777,dir_mode=0777
Yet, when I type mount all it reports is (rw,mand). The share works just fine, and I can see the masking (all files are showing as rwxrwxrwx as expected etc) but mount is not listing the options?!
Is this normal expected behavior? Is there a bug report on this? I've google'd to the best of my capabilities and could not locate any such information which is why I decided to hit the forums prior to filing a bug.
I plugged in a seagate expansion drive 1Tb into my linux server for backup purposes but it is unable to mount it. I can see the expansion drive in My computer but when I click on it, it says unable to mount, device already mounted or busy. Windows can read the hard disk with no problems. It is ntfs formatted. I installed ntfs kernel and fuse. Ntfs is displayed when I run cat /proc/filesystems. However it just can't mount the expansion drive.
it says cant mount volume and wont recognize my seagate expansion drive after I had the seagate plugged in to a windows pc! It says something about using command line to fix it but I'm new to Linux and don't know what to do!
I purchased a Seagate Goflex 500GB external hard drive yesterday and tried to connect it with my Fedora machine. Unfortunately my machine could not mount the drive. I have never had such problems earlier with other USB drives.PLease, how to use this ext disk on the fedora machine.
I'm having some trouble in trying to make a clean solution and tougher time searching to not get the basic mounting pages/posts. So I thought I'd throw this out hereFor Oracle, we have an app server that runs /sharedapps and is an NFS mount for all other app/db nodes. What I'm working on now is that on this app server that hosts/exports /sharedapps file system has a sub folder with a CIFS mount (/sharedapps/data/appmount). e thing is that the remote nodes with the NFS mount to /sharedapps don't see the remote data in /sharedapps/data/appmount, only the main app server that has the CIFS connection. Realistically it makes sense why, but I'm trying to research if there is a way to have it do so. This is where I'm struggling. We are working on this in a dev instance right now but soon to be in production. In production, there are many DB nodes that could process a request which is why it would be best to have the NFS connection follow the remote CIFS connection
I have a Windows 2003 server with fiber attached volumes (NTFS) that I would like to mount readonly on a linux system to back it up to tape. The fiber device will allow me to present the volume R/W to one host and R/O to another, however, the R/O system doesn't see any of the changes made by the R/W server. In other words, how can I make a readonly volume refresh, scan for changes, or update without un/re-mounting it?
Is the "mount -o --bind" option what I want? From the MAN is doesn't seem right... the option "sync" seems slightly more promising but I think I'm just grasping at straws here. The best I have come up with is a cron job to unmount then mount the volume periodically.
So after having spent the past half year preparing to abandon Windows and come over to Debian I finally made the switch last night only to realize I forgot one important thing... I didn't figure out how to map the network drive on my Windows server (currently learning to replace this with Debian as well) to my Debian system.
I have read about 15 links but keep getting the following error: Mount Error (6): No such device or address
Here is what I'm trying to enter into my terminal (with important bits removed for security of course)
mount -t cifs //xxx.xxx.xxx.xxx/Network_Storage/ -o username=xxx,password=xxx /mnt/cifs
I used command as followings. nothing special. mount -t cifs //192.168.55.53/windows$/Home /mnt/ -o user=username%password It works well after mounted. But mounting itself takes 1-2 minutes terribly. After mounted successfully, file transfer speed looks to be normal.
This appears to mount correctly, however there are some filenames on the server with the bullet character() in their name, and by mounting via fstab, the bullet shows as a question mark, but mounting from nautilus shows the bullet.
Anyway I can mount with fstab, and have all characters show properly in the filename?
I have 2 USB drives connected to an XP machine that I rotate twice a month for backups. On my CentOS box, I have that drive mounted at /home/backup using cifs.
Because the drive is mounted on the Linux box, Windows XP complains when I try to "Safely Remove Hardware". As a result, I have to "umount /home/backup", then "Safely Remove Hardware". After connecting the new drive, I then have to "mount /home/backup" in order to use it again on the Linux box.
Now, this question may be a Windows XP question, but I was wondering if there is anything I can do on the Linux box first. Is there anything that can be done on either end, so that I won't have to "umount /home/backup" first?
I'm using Debian 8.2 from a very recent download of the latest NetInst (less than 2 weeks). I'm sort of new to Linux - More accurately, I've used Unix and Linux extensively in the past, so most of my knowledge is dated. In particular, the whole systemd / systemctl paradigm is completely new to me.
Problem: I've added an entry to /etc/fstab to mount a NAS drive as CIFS. When I do a system shutdown or reboot, the system hangs for 90 seconds trying to unmount the NAS. If I manually umount the NAS prior to shutdown / reboot everything works fine.
I've done a fair amount of investigation and web searches, but haven't found a fix yet. Apparently several people were encountering similar problems about a year back, and it seems pretty clear that the root cause what ordering of steps in the shutdown process, e.g., WLAN being turned off before unmounting filesystems. This seems to have been resolved for most users (no one is discussing it any more), but I'm now running into the same issue. Ugh.
I tried to add a shell script to /etc/rc0.d to umount the NAS first in the shutdown process. This had no effect. I assume this is because the new systemd / systemctl paradigm supplants the old /etc/rc model of runlevel control, though it is rather baffling (to me, at least) as to why /etc/rc* still exists if the system is no longer using it...?
Here's some things I'd like to try, but how to proceed:
1. In the new systemd / systemctl paradigm, how do I examine and change the ordering of steps in the shutdown process? I've seen a lot of documentation on systemd, but nothing tells me how to do what I used to be able to do with /etc/rc with a simple rename of a symlink. If I knew how to look at the order of shutdown and change that ordering, I'm fairly certain I could identify and resolve this issue.
2. Is there some other way to mount my CIFS NAS other than editing /etc/fstab? Is it possible that my manual edit to /etc/fstab is the cause of this issue? My research into systemd indicates that it IS supposed to be compatible with /etc/fstab. I have not yet found documentation describing how to mount a filesystem at boot WITHOUT editing /etc/fstab ...
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
I have a bootable utility toolset that I put together with Fedora 14, one of its primary functions is to map a user designated share via script and access information from it. The command that I used, that functioned perfectly, in Fedora 14 was:
Code: sudo mount -t cifs -o user=provided.account.name //file-server.mydomain.com/share/images /mnt/source
We recently moved to a new home and I am trying to get my home file/print server set up again. Thanks to swerdna's excellent website, I got my server box (just upgraded from 11.0 to 11.2) running Samba and serving my shares over the network, and my "client" machines can access them without a problem.However, I'm not having much luck setting up CIFS mounts on my Linux desktop. I have my all-purpose user added to the Samba auth list (via smbpasswd), and configured my client as swerdna's howto's specify, and I can access the files just find. However, when I try to mount the shares with this command:
Code: mount -t cifs -o username=klein,password=klein //192.168.1.70/sharedmedia /home/zak/SharedMedia/ I get the following error:
Code: //192.168.0.242/websites /mnt/supercube cifs rw,user=XXX,pass=XXX,iocharset=utf8,file_mode=0777,file_mode=0777,dir_mode=0777,uid=XXX 0 0 But it doesn't auto mount with everything and disconnects whenever I suspend my computer. The only way to get it to mount is with Code: sudo mount -a and it mounts fine with no error.
Did lucid change the way it uses fstab or something? Obviously writing mount -a isn't a huge concern, but it kind of destroys the point of putting it in my fstab.