What I have not tested is the LTS kernel with a gpt partition table. I installed linux-lts kernel, 3.14.45-1-lts, created a 1 partiton MBR drive, formatted this with ext4, and I've been rsync'ing for 12 hours now happily. I was able to write lots of data to it with no issue.Īs this was a fuse module and not in the Kernel I then suspected the Kernel. I mounted up the NTFS partiton with NTFS-3g and this was fine. I put the drive back in the original box. This was about 300GB of data and it would normally die long before this. I copied over a further 2 times and this was fine. I formatted it with NTFS and copied over my Steamapps directory and this was fine. I tried Seatools for Windows, this was fine also. Seatools for DOS was fine, but I didn't expect any errors. I couldn't get this to work on this box so I tried with a windows box I have. I contacted seagate and they suggested to try seatools. I disabled NCQ and the drive also died, but with a different failed command as we'd expect. I limited the link speed to sata2 3Gbps and sata1 1.5Gbps and the same thing happened. I tried to format it with vfat just to see, and the same thing happened. I could dd TB's of zeros to the /dev device, but once I started dd'ing to a file on a FS the drive would die within a few minutes. Which is the NCQ commands not getting through.Īt this point, the drive needs a cold start to get going again. ata1.00: failed command: WRITE FPDMA QUEUED Folders and files can be created, but they can not be edited.Ata1.00: exception Emask 0x0 SAct 0x7ffdffff SErr 0x0 action 0圆 frozen Without this, you will be able to mount the share but will not be able to write to it. Most of everything is the same, except the syntax you use to actually mount the share. The -e stands for "exports" or a list of shares exported by NFS on the BA. Use the showmount command to see what is exported by the BlackArmor: The share name (for example /DataVolume/Public) is not shared.įor instance, trying 192.168.10.204:/Public (note no volume name) will cause an "access is denied" error. The client (Linux computer) is not on the allowed list of IP addresses. "Access is denied" during the mount may indicate some of the following: Sudo mount -t nfs 192.168.10.204:/DataVolume/Public /mnt/Public Mount errors Normally this will be in Computer, under Filesystem and then mnt. You will have to browse to the location of the folder. Note: This will not create a shortcut on your desktop, nor will it show up in Computer.Remember that it is the folder that you already created. /mnt/ : The location to which you want your share to be mounted.: The Share within the Volume of the hard drive that you want to mount./ : Volume Name of the actual hard drive that you want to mount.:/ : IP address of the drive you are trying to mount.nfs : Tells the type of share you are trying to mount.You use this when you do not have the drive information located in /etc/fstab -t : Is used to tell the system that this is just an ordinary mount command.Now, once that is created, you can mount the share. To mount an NFS, you first have to create the folder to which you want it to mount. Otherwise, consult your system documentation or package manger for more info. Make sure you have the nfs-common package installed. When adding them, do it one at a time, clicking Add each time. Make sure to enter the IP Addresses of your Linux computers. Under NFS Service, ensure that it is set to Enable. Go to the Network section and then to Services. If it is not, check on the modify and make sure to check the NFS box. If NFS is enabled for a particular share, there will be a green checkmark on it. Go to the Network section and then to Shares. Ensure the share you want to access is setup for NFS. Get the IP address from the LCD of your BlackArmor.Ģ.Access the management page of the BlackArmor. Please check for package manager for it or equivalent.ġ. NOTE: The nfs-common package may need to be installed on Linux to get support for NFS clients. NOTE: The easiest way to access the shares and files is to use Windows sharing (CIFS) via a file manager. NOTE: Please see this Knowledge Base article for more information on Linux support for the Seagate BlackArmor NAS 440. Familiarity with Linux, the command line, and security privileges (becoming root or the sudo command) is recommended. This article provides some advanced tips on using NFS and CIFS with Linux, but please consult your system documentation for more information. The BlackArmor NAS supports the NFS (Network File System) and CIFS protocols which can be used on Linux and other operating systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |