Raspberry Pi Torrent Server – From Scratch

As requested, this is a guide to taking a Raspberry Pi and turning it into an always on Torrent box, complete and self-sufficient with its own mass storage meaning it needs no help from other computers. Also, as the Pi consumes such little power compared to a full desktop PC, money can be saved by using the Pi for overnight transfers while other computers can remain off.

piserver1

For this project I recommend a RPi 2, as its powerful enough to perform the transfers up to its maximum 100Mbps network speed, and is a cheaper choice since the RPi 3 superseded it last year. To get started, you need the following hardware:

  • Raspberry Pi 2 board.
  • Micro USB wall adaptor – Needs to be capable of 2Amp output.
  • Micro SD card – Minimum of 8GB, class 6 or above, plus SD adaptor for connecting to a PC.
  • USB Portable Hard drive – USB powered is preferred, I use a Toshiba Canvio Basics 1TB.
  • Ethernet Cable – And spare port on the modem/router for internet connection.
  • A PC – On the same network as the Pi for connection and configuring.

The Pi was designed to as low cost as possible to the user, so apart from the Pi board you may already have everything to run a Pi, and if not these are cheap and easily available online.

With a RPi 2 at hand, let’s get started…

Continue reading “Raspberry Pi Torrent Server – From Scratch”

Adding Kodi Sources Manually

During my migration from Windows Server 2003 to Server 2012, I encountered an issue with Kodi on Raspberry Pi and how it connects to the Win 2012 file share. When accessing the server with a Samba file share instead of a prompt for credentials the error message “Operation not permitted” is displayed.

Kodi Operation Not Permitted

Kodi allows the manual adding of network locations but does not support adding the credentials that are needed to access the location.

Therefore a bit of tweaking is needed to get access to Windows 2012 shares on Kodi.

Continue reading “Adding Kodi Sources Manually”

Connecting to a Headless Raspberry Pi

A great feature of the Raspberry Pi is that it can be fully used as a headless unit, meaning it does not need a monitor, keyboard or any other input device connected. This is great when running it as a server or for automated processes that require the unit to be tucked away.

What is annoying is that setting up the Pi for the first time may need those input devices to be able to configure the network and install applications. Thankfully there is a way to connect to a headless Pi from the start, with it only needing power and Ethernet connection.

Continue reading “Connecting to a Headless Raspberry Pi”

OSMC on Pi with PPTP VPN

The arrival of the Raspberry Pi 2 meant the B+ previously used as a server was now ready for a new purpose. These little machines make great media players and is easy to setup so this would be its new role.

However, this Pi would be in my parents’ home, and miles away from where my videos are stored. I didn’t want to add a hard drive locally as syncing the library would be an issue. But thanks to the fibre internet connection on the server side I could upload at 10Mbps, enough to stream media across the net.

Therefore, the plan is to use an install of OSMC and add a VPN connection to my home server that starts when the Pi starts to make the operation seamless.

Continue reading “OSMC on Pi with PPTP VPN”

Raspberry Pi 2

The Raspberry Pi Foundation has brought a new model of the Pi to the table, so with the same low price it was easy to add to my Pi family.

Raspberry Pi 2

For those not yet familiar with the RPi 2, it keeps the small and simple form factor of its predecessors, but gives performance upgrades in the form of an 800mhz quad core processor, with overclocking options still available, and combined it with a whole Gigabyte of RAM. These upgrades, on paper at least sound that it could make the Pi into a useable desktop machine, with less freezing during full CPU load that was easy to achieve previously.

Continue reading “Raspberry Pi 2”

Net Killing RPi – SOLVED!!

With my troubleshooting exhausted, I turned to the Raspberry Pi forums in hope of some new ideas on how to fix it.

I was not disappointed. I quickly got answers pointing towards RF issues around the HDMI cable or grounding of the Pi/TV.

Ferrite clips along the HDMI and power cables failed, and initially grounding failed due to the fact I was using the whole 10 metres of cable I purchased to ground the Pi. Thinking this may be causing a lot of resistance for the low current used, I shortened it to around 50cm and…

Hooorah!

 

DIY solution to ground the RPi.
DIY solution to ground the RPi.

The Raspberry Pi and my internet working in close proximity and perfect harmony. The solution is to attach one end of a short wire to the HDMI port of the Pi, and the other end is attached to the ground pin of a standard socket plug.

This has been an expensive problem for me, 2 HDMI cables, a shielded RJ11 cable for the ADSL connection and a bunch of ferrite clips/rings when all I needed was a £2.39 piece of wire from Maplin. At least one benefit of this expense is the increased broadband speed, provided by the shielded RJ11 cable, taking my connection from 2.5Mbps to 3.2Mbps.

Its all working now, taking its place tucked behind the TV and providing me with a great media player solution, the abilility to control XBMC with my Bravia TV remote is an excellent feature.

My forum thread on the RPi forums can be found here.

Net killing RPi – Getting Somewhere…

In my last post I was a confussled mess, failing to get my head around how a network device (The Raspberry Pi) could cripple an exclusive function of my router.

I decided to troubleshoot the issue further, I set up a basic ping to help me pinpoint when the internet was going down

Ping results before Pi was switched on.
Ping results before Pi was switched on.

After performing some basic troubleshooting, it transpired that the fault was happening whenever the HDMI cable was connected to the Pi and my Television (Sony Bravia EX4-32).

Ping results after HDMI cable connected.
Ping results after HDMI cable connected.

Thinking it was a bad HDMI cable, I bought another, but to no avail. My next brainwave was that the Pi was emitting EMI (or RFI) which drove me to buy a 10 metre HDMI cable to get the Pi as far away from my router and other networking equipment, alas this didn’t work either.

Troubleshooting further, it turned out that the HDMI cable didn’t need to be properly connected, mealy touching the Pi on any metallic part will cause the internet to cease.

All it takes to knock me offline.
All it takes to knock me offline.

So in essence I am still no closer to solving my Pi/Internet mystery, if you can help me please comment!

All other HDMI works fine as I am now using the 10m HDMI cable as a screen extender on my laptop.

Bootnote:

In my previous post I signed off by stating that that the Pi and my internet were working in harmony. However it turned out that my modem had dialled back my downstream internet speed to 1.5Mbps instead of the usual 3Mbps, normally a result of the modem trying to obtain a more stable internet connection due to, lets say, interference on the line!

RPi kills my internet

It was all going so well, got my Raspberry Pi and after the initial fiddle with Debian Squeeze I got another SD card and put Raspbmc on it, things were great!

Only niggle in my head was that the card I put Raspbmc on was 8GB, and that bigger card would be put to better use in my camera that was using a 4GB card. I thought it would be no problem to reformat cards and swap them over?

Wrong!

The 8GB in the camera was fine, and I used the Raspbmc installer as before to load it on the new SD card. The trouble was that when first booted up the Pi, it seemed to freeze on the

Sending HTTP request to server

No problem I thought, hop on my laptop and find out if other users experienced the same. But low and behold the internet on my laptop ceased to to work, with strange requests for proxy passwords to sites like Facebook and even the Weather gadget on Win 7!

First thoughts were that I cooked my router, as I been downloading a lot and on a warm day to (yes there was a warm day … I think!). But after it was off for as long as I could stand, powered it back on and normal service was resumed.

After rebooting all network equipment it finally dawned that the internet would go down for everything connected to my network when the Pi was powered up! I had never experienced this before and could not for the life of me fathom it out. I thought that it had a defect in the Pi meant that some sort of power surge was knocking out the system? This was quickly dismissed as local traffic was unaffected, meaning the network hardware was operating normally.

A quick glance at my Sky broadband supplied Sagem F@ST 2504 modem showed the internet connection had failed, with the internet indicator glowing orange with a red pulse every second. Stranger still, upon unplugging the Raspberry Pi, connection to the net restored within  seconds!

Drawing4

So how can a network device have the ability to target and destroy an internet connection? Its my understanding that a Pi has no ability to retain settings other than whats stored on a SD card, but this issue continued when using two different memory cards.

Drilling down to an extreme form of troubleshooting, all network devices, including my second switch/access point was disconnected from the Sagem router. leaving just the Pi connected. Then from Midori on Debian Squeeze (remembering that the internal network was unaffected) rebooted the router using the web interface.

Suddenly the Pi could connect, attaching my whole network back together I found that everything was back to normal,

Laptop, Pi, iPhone, everything!

And this is the worst thing, I don’t know what caused this, and what I specifically did in the reboot process that solved it?

So I would love to hear if this has happened to you, and if there was something you can pinpoint as the issue? This one has got me completely stumped!

Its Alive!

Finally, 4 days after delivery I finally get my Raspberry Pi powered up and functioning!

P1000684

First off, Debian Squeeze was installed, Samba added and worked out what is could, or could not do. Then it was about deciding what to do with it, first thoughts were a web server to host this Blog, but that was quickly solved by my other purchase of 4GB RAM for my Server.

The second choice was a media server, initially this looked dubious considering its performance when running Debian. But a bit of research yielded a program called xbmc, which in essence is a Linux version of Windows Media Centre. Further searching revelled a new project called Raspbmc, I thought I’d share this:

P1000745
Xbmc running on a Raspberry Pi

Raspbmc is built on a custom Linux platform that boots straight into xbmc and so acts as a purpose media player exclusively for the Raspberry Pi, and is tailored to new users not up to scratch with *nix. So much so it installs to a SD card via a single click of a program running in Windows or Mac OS X.

So far it is in Beta stage but stable, it is clear that the xbmc software on which it is based is designed for more powerful hardware than a RPi, the menus can slow and seem jerky if requesting menus in quick succession, but video playback is unaffected and is just as smooth as my Intel Core i7 laptop.

For now it suits me fine, the Pi as a media player is excellent for my needs. The fact that a quick swap of the SD card changes it from media player to desktop means I still explore Linux through Debian without messing with my current setup.