How to install Pogoplug software on V2 Plug

[pshevrin]

I just installed Arch on my V2 (Pink) pogoplug. Love the distribution but I also wanted to get my Pogo functionality back. I know the senior tech folks at CloudEngines and they helped me a bit. I asked them if I could share the information with this community and they said I could. Please note neither I nor anyone at CloudEngines *** SUPPORTS, ENDORSES, or otherwise stands behind this procedure. You should USE AT YOUR OWN RISK understanding you may DESTROY YOUR DEVICE *******.

Here is what I did, assuming you didn't save your old pogo software and have no pogo software installed/running:

# cd /tmp
# wget http://upgrade.pogoplug.com/svc/upgrade ... 28_upgrade
# chmod +x cloudengines_pogoplug_3_2_6_201203220028_upgrade
#mkdir /usr/local/cloudengines
# cd /usr/local/cloudengines
# /tmp/cloudengines_pogoplug_3_2_6_201203220028_upgrade

You will get a lot of errors when you run the upgrade package as it assumes a different linux setup (init.d) and some kernel modules are not built for this kernel. Ignore all that.

You will need to set some configuration. In /usr/local/cloudengines/bin there is a file called hbplug.conf. You need to edit it. Make sure the line for install dir is:

installdir=/usr/local/cloudengines

and add this:

# Tells hbplug to not attempt to mount anything automatically
nohotplug=1

for each data directory add:

# Tells hbplug to use the specified absolute path as a share point with the name media
# The <d> value is a digit starting with 0 and incrementing by one for each share
# vfsdir<d>=media,/somedir/someotherdir/media
vfsdir0=plugdata,/usr/local/cloudengines/data

Finally, I added the following to rc.local. I added this before the start funciton:

INSTDIR=/usr/local/cloudengines

In the start funciton I added:

echo -n "Starting hbplug: "
ulimit -n 65536
ulimit -c unlimited
nohup $INSTDIR/bin/hbwd $INSTDIR/bin/hbplug > /dev/null 2>&1 &
echo "Success"

and in the stop funciton I added:

echo -n "Shutting down hbplug: "
if pidof hbwd > /dev/null; then
killall hbwd > /dev/null 2>&1
retries=120
while pidof hbwd > /dev/null && [ $retries -gt 0 ]; do
sleep 1;
let retries--
done
if [ $retries -eq 0 ]; then
echo "Failure"
else
echo "Success"
fi
killall -9 ffmpeg
else
echo "Not Running"
fi

You might want to set the hostname for you plug to something other than the default. Once you have done the above and started the pogo process, you'll need to open a browser from a machine on the same network as your plug to http://my.pogoplug.com Login and then use this interface to add the plug. I made sure that there was at least one file/directory in my data directory so that when I added the plug I could see the contents and hence knew all was working.

Hopefully I haven't forgotten anything. Enjoy.

[WarheadsSE]

I am marking this on my todo-try list.

It's possible that with a little cleanup, it could be turned into a clean service. (if it all works)

[WarheadsSE]

I am fiddling, and there are some minor changes to the process By the way, this will create it's own svcid.

The install file will spout gibberish, and then reboot the device. Here is a copy of my results from running the file pastie and the proof it works. image hosted on the device

If you have a Pro/V3/Classic: you might already have this in place, and only need to add the appropriate bits.
** If you converted recently, you're probably golden, if not follow the whole procedure **

1install (see above, and my note) [might reboot]
$this->bbcode_second_pass_code('', '
# cd /tmp
# wget http://upgrade.pogoplug.com/svc/upgrade ... 28_upgrade
# chmod +x cloudengines_pogoplug_3_2_6_201203220028_upgrade
# mkdir -p /usr/local/cloudengines
# cd /usr/local/cloudengines
# /tmp/cloudengines_pogoplug_3_2_6_201203220028_upgrade
')

2 edit the config
$this->bbcode_second_pass_code('', '
nano /usr/local/cloudengines/hbplug.conf
')

3 Add to rc.d
Here you can just make a symlink and watch it barf some jibberish, or make your own.
$this->bbcode_second_pass_code('', '
ln -s /usr/local/cloudengines/bin/hbplug_init /etc/rc.d/pogoplug
')

4 Start
$this->bbcode_second_pass_code('', '
rc.d start pogoplug
')

5 Register your device @ my.pogoplug.com

[moonman]

This is awesome Thanks pshevrin

This thing spits out lots of error before it launches but it does work. Thanks for suggestions WarheadsSE
Also, another note: there's no hbplug.conf untill hbplug is launched at least one time, you can't really create one yourself because service id gets generated automatically by hbplug and it goes into that .conf.
@WarheadsSE hbplug.conf is actually in the bin folder like pshevrin suggested in his guide.

IMHO this needs to be added to the wiki

[tomcheng76]

Thanks for the posting, it really helps if you have a pogoplug.

Can this "howto" eventually ports to other devices like goflex net which has Pogoplug service originally ? Is it possible theoretically ?

[WarheadsSE]

Theoretically, this should be doable for any pogoplug enabled device.

[WarheadsSE]

$this->bbcode_second_pass_quote('moonman', '
')Also, another note: there's no hbplug.conf untill hbplug is launched at least one time, you can't really create one yourself because service id gets generated automatically by hbplug and it goes into that .conf.
@WarheadsSE hbplug.conf is actually in the bin folder like pshevrin suggested in his guide.

[WarheadsSE]

A note:

I seem to be unable to get it to show up in the devices today... I wonder why..

[moonman]

Interesting... I though svcid was the important part to register it so you can't really create it yourself.
Mine looks like this:
$this->bbcode_second_pass_code('', 'vfsdir0=plugdata,/media/2TBDrive/Downloads
installdir=/usr/local/cloudengines
#datadir=.
datadir=.
nohotplug=1
svcid=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
')

[WarheadsSE]

And.. we have observed consequence!

I have taken notice of an odd behavior. My P21 with this on it seemed to be rebooting, randomly (per se). What I found (by watching via serial) was something causing a nasty message about the xce not matching this or that, and causing a reboot.

For the V3 owners in the crowd, I am testing a slightly modified (aka I neutered the ability to reboot) XCE module (the source is open) and I will await it's behavior. I can confirm in the mean time, that other than the mysteriously odd behavior(s), it has been functioning well but has many processes and with ssh & samba in addition, about 40MB of ram are in use. Quite a bit more is spoken for. Also, with my modified XCE, it make use of the actual device id, and does not generate it's own.