some questions/suggestions for you:
1. as regards speed, what format is your drive? we have found the best speed with ext3 or hfsplus (non-journaled). ntfs is somewhat slower owing to linux driver support, and fat is limited. we are working to improve filesystem speed.
2. what sort of windows errors are you getting on p:? i agree, we do need to improve pogoplug execute-on-login intelligence.
3. as regards the corruption issue, what likely happened is your drive wasn't cleanly unmounted due to the power cycle. this will cause it to become read-only to pogoplug, until you plug it into a pc and run chkdsk (or if it's a mac, just plugging it in should fix it). were you able to browse it at all in read-only mode? we are working to improve unclean unmounts.
4. hibernating and/or switching networks shouldn't be an issue, pogoplug should pick up the network changes and update itself. however there is a bit of a delay in there (up to 5 minutes), so give it a few minutes after switching networks and it should reflect any changes. reload performs a forcible reload, but letting the app refresh itself is the "desired" method.
I'm having a few problems using the pogoplug drive application for Windows. I am trying to migrate to Pogoplug from a first generation Buffalo Linkstation NAS device. I was hoping that pogoplug would work as well (or even better) than my NAS device, but allow me to use it over the WAN as well as the LAN. It seems to be designed that way, but I'm having trouble getting it to live up to that. Here are some of my issues:
1. The speed of the drive isn't as fast as my old linkstation was. It ranges from significantly slower to just about the same, but not quite as fast. Clicking "Reload" on the pogoplug icon in the tray window seems to help it get faster, but it still doesn't quite match up. On my linkstation I could watch an AVI file smoothly. From the pogoplug, it skips. Is there anything I can do to improve the speed?
2. I'm also a bit disappointed in the software for the windows drive. I actually prefer my linkstation that mounted as a network drive, because Windows knows what to do when network drives come online and go offline. Windows seems to have a harder time when drives that appear to be local do that. For one thing, when I start up my computer, it takes a minute for the wireless hardware to load and for me to connected to my network. But pogoplug immediately tries to reconnect the drive and I always get an error because it has tried to reconnect before I'm fully authenticated on the network. Plus, it just seems that I'm getting more windows errors about the P: drive than I should be.
3. This shouldn't happen often, but I ended up encountering some kind of corruption issue. The power to my pogoplug cycled while I had a file open in the windows drive. This caused the comptuer accessing that file to crash, along with making the drive unreadable to pogoplug. I was instructed to run chkdsk on the drive because it appeared to be corrupted. What I ended up doing was renaming the .cedata directory and a file that I think was called ".ceid". This enabled pogoplug to access the drive again.
Out of curiosity, what is the .cedata directory and the other stuff that is created on the drive? I'm not familiar with that.
4. In realizing the way that the windows drive works, I see that I'm going to have another problem. I frequently hibernate my computer between work and home. But since I'm changing networks, that means I'll have to "reload" my pogoplug drive whenever I do that. That seems pretty irritating to me. I use Dropbox as well and it seems to be able to adapt and reconnect by itself whenever my network configuration changes. Why can't the pogo drive do that also?
I was really excited about pogoplug, but now I'm wondering if I should have just upgraded to a newer Linkstation NAS. I really wanted to be able to mount a drive from the WAN, but now I'm not sure if that is going to work really well. Thoughts? Suggestions?
1. I'm using NTFS. I'd like to keep with that because I'm using a portable drive that I want to be able to use with my Windows machines without having to install ext3 support.
2. I think the errors usually have to do with login. I was having trouble in Picasa editing a photo and then saving it, but I'm not sure that has to do with Pogoplug or Picasa. I was able to edit files in other programs.
3. This is kind of an irritating issue. Does this mean that I have to go to the web site and eject every time I pull the drive off? That's a bit inconvenient, especially since I want to be able to carry this drive with me at times, and use it on Pogoplug at times.
4. OK - I'll try this a few times and see how it goes.
Is there any information available about the development priority of the windows drive software piece? The speed issues make me wonder if this is really going to be a good solution for accessing pictures through Picasa or using files over the drive connection.
we are indeed working to improve ntfs speed at present. unfortunately the web app is the only place to eject your pogoplug drives right now. we are working to improve this to make it easier and more convenient, but safely ejecting drives requires user intervention on any platform. the windows drive software is under active development, and speed is certainly an important point. do you see the same slowdowns when uploading via the web app?
It looks like the .ce files are a part of Pogoplug's mounting and network stuff - a feature of the OS.
I run NTFS as well and it is nowhere near as fast as my Buffalo NAS. I cannot download an archived audiobook over the net at all. Small files seem to come through over the net. It takes forever just to load directory names, much less download a file! I have a directory with 9000 files and I might as well go get a sandwich when I try to open it. About as quirky as an old 1200 baud modem!
What is - .cedata - ? Is this something that my iPhone put on the drive I have on the Pogoplug? Having being able to get to my files on the drive that I have on the Pogoplug my iPhone is a nice touch.
I have an external drive formated for mac (journaled), its a 2tb drive loaded with about 900gb of movies I've encoded from my DVD collection via handbreak. Most of the files are around 1gb in size. My issue is, its spent the last 29 hours (full-transcoding) processing a single file and only completing 48% of it. At that speed it will take approximately 2.5 years to convert my drive to use. What do I need to do to speed this up, its ridiculous how long its taking. Any ideas!?
My issue is the same as the above poster's--I've altered my media settings to "auto-generate full transcode" with the remaining options set to "as soon as possible". I've been monitoring the process and it is moving extremely slow. I've searched the knowledge base as well without any luck. My drive is a Hitachi 1TB, though I'm not sure that's important. Thanks in advance for any advice you can give.
Hello dear fellow Pogo enthousiasts...
I recently got my Pogoplug Pro en installed it the same day.
It works, but thats about it.
Im using a 1.5Tb external HDD formatted with NTFS. It holds my video as well as my mp3 collections.
Furthermore im using different media database/players like iTunes, Mediaplayer and Mediamonkey.
just loading the database for these players (approx 65.000 files) takes days and days and days......
I read the replies Keith from cloud services gave to all former thread entries, so i can safely say im having the same issues, which actually make me think if the Pogoplug was the best solution for my needs.....
Some other info that might be relevant:
Windows 7 premiun 64 bits with the appropriate Pogoplug 64bit app loaded
A maximally optimized Wifi network on G standard (i know N standard will get me better performance)
As for now i used the old DOS "subst" command to actually attach my harddrive cabled, load the libraries and the after pogo is up and running, making the old path of the cabled hdd available as a drive using "subst"
I would greatly appreciate any tips or news on improvements.
Also im offering to (beta) test new solutions from cloud systems that might be under construction.
Hello all!
I managed to tune the networkperformance of the wireless option by tweaking the TCPIP stack.
Adding registry entries for TCPAckDelay and some other tweaks improved my speed by over 200%.
Source documentantion on these tweaks can be found @ www.speedguide.net
Hope other people manage the same improvements!

RSS


