But there was a db directory, so I moved that and db.info into a backup directory, and re-started Twonky. Si I installed PuTTY, shut down Twonky, enabled SSH access, logged in to the Linux as root, and found that there was no twonky.db as suggested. Now, coincidentally to the upgrade, or the power cycle, the Twonky server started playing up, reporting an error 400162.Īfter trying the usual suspects of shutting Twonky down, re-building, re-scanning, re-starting, etc, to no avail, I found this suggestion: It was okay, but I spotted a pending firmware upgrade, so I installed that and let it re-boot again. On re-booting, the NAS took a while, so I used the Dashboard to see what was going on. I foolishly unplugged my 4TB M圜loud last night, in order to sort out power leads etc. 4: I think I’ve finally figured out how to get Twonky working in a stable fashion, so I’ve written up my findings in a
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |