RaspberryPi + Deluge reboot -> All files downloading again

[Milorad]

Greetings
This morning I had to reboot my Pi that has Deluge 1.3.12 installed on it. Here is what I did.
1) sudo pkill deluged
2) sudo pkill deluge-web
3) sudo umount /xxxx/xxxxx/xxx/HD with the folders for Deluge
4) sudo reboot (the pi)

At some point the Pi got stuck while rebooting. So I unplugged the power. And put it back on.
The Pi started nicely, once started I ssh to it from my Mac and reloaded Deluge
1) deluged
2) deluge-web --fork
3) connected to the daemon from my Mac. Deluge instead of seeding all the files (76), was reloading them . What happened I need help on this

Thank you.

[Exor]

I don't know if I have exactly same problem as your but I think I have similar problem as your.

There was power outage in my area twice in last month, in Deluge's webui shows all of them error when they were seeding. I tried to resume them but they show downloading. I decided to restart RPI and then still showing downloading. I had to force recheck which take about an hour EACH torrent. This is ridiculous. I think there should be at least a way to get around of having to recheck every time I restart RPI due to power outage or internet outage.

Is there a way? Many other bittorrent clients don't do this. They just show error then I resume them, they find files and continue seeding since there's no change in path. The torrents in the list were never deleted.

Thank you in advance!


EDIT: After researching more in this forum. I think the cause of "downloading" is that it reads the "download" path not "moved" path after resuming. But after you force recheck, it will check the "moved" path. I think there should be the feature to make it automatically connect to "moved" path instead of checking "download" path. I am not exactly sure if this has been discussed. If there is no feature request for this, I might make a ticket for this if there isn't one yet.

[Cas]

Latest version 1.3.13 should mitigate this type of issue

[Exor]

Latest version 1.3.13 should mitigate this type of issue

Before I do it, I want to know is there a way to update from 1.3.12 to 1.3.13 in command? If so, can you point me to right direction? If not, do I have to remove it and then reinstall from apt-get?