If you want a share to use in windows, forget NFS, go to samba...
NFS can work in windows, but every time i tried i had problems with it (with external tools, with MS Windows Services for UNIX or with more recent windows server 2012). All are really just hacks to windows, not even MS gave me enough support when a NFS start failing on a server after 1 year ...
I love the Pi, but I have to tell you it doesn't hold the fastest IO in the market.
According to this article on the USB performance there is a empiric limit of 30MB/s transfer rate on the USB port. And all the USB ports use the same IO interface. As that, the limit of all combined USB should be capped on that 30MB/s limit.
If you take a look at some HD ...
I was missing leading /
vers=1.0 may have helped
Drive had two logical names. S-Drive wasn't working. Seagate was.
sudo mount --verbose -o username=John,password=********,vers=1.0 //192.168.1.1/Seagate /home/pi/SEAGATE/share/
You can also use the scp command to copy files from the remote location to your local computer. So you could do
scp email@example.com:~/acc.c ~/
If this also does not work check if you are the owner of both the local and remote directory and that you have read/write permissions.
NFS uses IP/Hostname based security so that means you should give permission on NFS server to clients. Permissions should be defined at /etc/exports file. Example /etc/exports file:
# Path Client IP (options)
Owncloud provides the "dropbox" clone without using btsync, but if you want to add secure transfer - I understand that may be a valid addition to the mix.
That being said, your permissions for the file system will need to be enabled for the user running the OwnCloud server and also btsync. Typically this will be www-data on a Debian Apache server and ...
In my case it turned out to be the file /var/cache/minidlna/files.db that was owned by root instead of the user minidlna. I removed the files after stopping minidlna, restarted with a force rescan and that file was rebuilt from the media directory with the correct permissions (owner minidnla), since then no problem!
If you can browse from the Pi, then you should already have internet access from the terminal. The trouble is that you are using the wrong binary to test it. The firewall on a Mac blocks ping for security reasons. Most firewall do the same, or at least, should do. So ping is not a good binary to use to test network connectivity, in a secure environment. From ...
I do not understand why VSFTPD, ProFTPD, PureFTPD should not work. They all are available from the default Raspbian repository. You should be able to just install one of them, configure and run it.
But anyway, if you use default Raspbian Stretch then there is no need to install any FTP server. ssh has a sftp server module that is installed by default:
Try Seafile running on RPi. Owncloud is more popular, but less secure. Plus parts of Seafile are written in Python, official language for RPi.
You can download RPi version from Seafile official website:
Then you can use very detailed tutorial on how to setup Seafile on RPi:
Just had the same issue with some files missing. Turned out to be a permission problem. minidlna runs under a dedicated user account minidlna. It will not list files that it cannot read.
chmod -R o+rX on your media files. Then rescan your library (sudo service minidlna force-restart or sudo -u minidlna minidlna -R). Worked for me.
I had similar issue. I fixed it by allowing user minidlna accessing media files.
In my case files are on external UBS drive where media folder is owner by www-data user and www-data group.
www-data is owner since files are also available via ownclound (apache)
usermod -a -G www-data minidlna
sudo systemctl restart minidlna
To me it looks more like a bug. Not all folders were shown. After renaming the missing folders on the harddisk just by adding '1' at the end of the folders name hthey appeared. And they stay visible also after renaming the folder back to the orignal name ('1' removed again).
I found, that only 10 folders show up in the 'Folders' folder and not more. ...
When I had the same problem, which wasn't resolved with the -R option, I solved it by changing name of one of the folders in my video share. (/Share/Video/Horror -> /Share/Video/Horror_t), then running -R.
All of the files in that folder showed up immediately. So I went through and renames all the folders with _t (standing for test) on the end of their name ...
Eventually I have solved my problem with two steps:
updating my pi's firmware by
putting sec=ntlm in the options of call to mount
So the final command that I use is:
sudo mount -t cifs //192.168.0.1/torrent /home/NAS -o uid=1000,iocharset=utf8,username="YOURUSERNAME",password="YOURPASSWORD",sec=ntlm
To use the /etc/fstab to ...
TLDR: both sites you mention support uploading files through an API (using code instead of a web browser).
TrainingPeaks has an upload-via-SOAP API. They also have a much easier non-soap method. It's less secure but it means you could test it without writing proper code (simply using curl). It appears they only accept PWX files, which are a Timex format.
By default, samba will create a share for the user you log in as corresponding to that user's home directory. Since you're logging in as user pi, that's the "extra" share you're seeing. If you want to disable this behavior, look for a [homes] section in your /etc/samba/smb.conf and comment that entire section out by prefacing each line with '#', or just ...
Create a folder in /media or /mnt called windows7. Make sure your raspberry Pi and Windows 7 can talk to each other. In this scenario lets pretend Windows 7 has the IP address 192.168.0.1 while our Raspberry Pi has the address 192.168.0.2. use ping to make sure both machines can reach one another.
Share a folder in Windows 7, perhaps C:\User\MyName\Videos.
You have followed an old SysV guide, and probably messed something up. See https://raspberrypi.stackexchange.com/a/39665/8697 - all you should NEED to do is install netatalk. You could then customise /etc/netatalk/AppleVolumes.default, but this is NOT necessary to get home.
I use netatalk all the time, and often cannot connect, after my Mac has been ...
Here is what you could try (expanding on the comment by Seamus):
Connect Raspberry Pi and Windows PC by Ethernet cable
Find out IP-address of Ethernet interface of the Raspberry Pi.
Normally this will be a self-assigned link-local IP-address
in the range of 169.254.1.0 to 169.254.254.255.
You can find the IP-address of the RPi via ifconfig eth0 (...
Yes - Samba is a good choice for what you want to do.
There are many good resources for setting up Samba, here's one I created
The main alternative for Samba is NFS. Each has its pros and cons. I use Samba because I'm more familiar with it. You can research the tradeoffs by doing a search like this one.
There's a fair amount of effort ...
The Raspberry Pi Zero does not have a wired port to connect it direct to your network, so you always have to use an additional device with an USB port and a wired network port. As you noted you will connect the Pi Zero with an USB cable to the additional device and use OTG ethernet gadget mode to emulate an ethernet connection. On the other side you connect ...
What do I need to change to enable me to move a file from my hard drive to my usb drive?
GNU/Linux, of which openELEC is a form, attaches external storage as subdirectories of the root filesystem -- usually in /mnt, although they can go anywhere.
I'm actually not a openELEC user so I cannot provide you with specifics, but if you browse through the /mnt ...
As short answer, what I can say from my experience is, as long as you do not use samba (free implementation of SMB/CIFS) or NTFS for the NAS part, that should be fine. Those two features are known to be CPU intensive and could be a bottleneck for the RPi.
XBMC can run quite smoothly on a Pi. transmission-daemon (the daemon client for the popular BitTorrent ...
Hmm, I got much faster reads from 4x USB drives as a raid than a single.
I currently have a raid 0 of old HDD's running MySQL server at the moment, and it moves through data pretty quickly. For some reason writes seem a bit slower than I expected. But reads are PDQ.
I haven't done any side by side tests though.