I know others have experienced this problem.  I am feeling the need to present it as a new thread in hopes others having this problem will take a look and contact technical support so that a resolution can be obtained quickly.

I have three plugs that are affected.  Two are pink and there is one BIZ.

I am wondering when a problem is submitted with prior, related, tickets/requests identified why the prior events seem to be ignored.  I would think that they should be reviewed.  In my eyes, they are all a part of the problem with the three (3) pogoplugs I have that mysteriously go brainDead (off line, drives not attached, ssl not available, etc.). 

One ticket that was submitted had a 9mb file that consisted of PDF file attached (36 pages of screen prints) of a complete case/history of a "brain dead" experience that was caught as it happened.  The frustrating part of this submission was that I was asked, later, to provide the symptoms that were being experienced.  So, I am certain that the screen prints were ignored.

Distilling what has happened over this period of time (since Sept 11, 2010), it seems the only solution is to remove power, disconnect everything from the device and let is just sit there for at least several hours (maybe 3-4 at a minimum).

I have three (3) Plugs that heal using this unconventional method, when "no drives are attached" is reported as well as some other ailments.  If you read the exploits of others (www.pogoplugged.com) that have pogoplugs that also go offLine mysteriously, they, too, have also found that the healing that most often works is to leave the pogoplug without power and totally disconnected.

This Smacks of something like, as best as I can describe, a logical connect whose condition is only released after some given period of time.  It is like a device that is attached via a USB port.  When an attempt is made to "Safely Remove" the device an error appears (maybe like the pogoplug's "no drives attached") that says it cannot be removed because something is using it.  The easy fix is to close/dismiss windows explorer; QB, etc. that had touched the device or a file residing on the device.  The difficult fix, that sometimes requires a reboot, is when there are currently no "visibally" open files or devices.  This is what I sense is happening with the plugs that exhibit the "brain dead" attributes.  If one totally removes the pogoplug from the internet (power down, disconnect RJ45/wireless) and then goes to the internet at URL my.pogoplug.com and enters the appropriate eMail and P/W for the pogoplug in question the presentation that appears in the window is much like a "brain dead" pogoplug device whose hard/flash/etc. drives do not get discovered.  So, there is some logical state/connection that is left behind and may be the cause?

Gordon, and others (to me or on pogoplugged) have suggested similar actions (eject and powerDown over a short period of time) to force the "logical" disconnect to get the pogoplug functioning again.  Unfortunately, I do not find this "short" period of time to be sufficient to execute the logical disconnect to heal the pogoplug's malady.  This problem is happening to me far to often (see tickets/requests) and at times when I am traveling where I can not give the pogoplug the attention it needs (visit pogoplugged.com for other people with the problem).

Now, to this morning ... 20110617,

At 1250 central time on June 17, 2011, another pogoplug (a pink this time) went brain dead in what seemed like a series of steps.  During the earlier parts of the morning, the plug had been accessed.  Then I noticed that the flash drive was missing.  Next, I noticed that several partitions of an attached hard drive were missing.  Finally, when I looked again, there were no drives attached.  SSL, this time was there.  Shared files, from my other pogoplugs, were accessible.  Web access got me to the point where I could see this but no drives.

Tried the eject and reattachment for discovery.  Nope, no discovery.  Tried removing power from the pogoplug.  No discovery of the flash or hard drives.

Finally, I reverted to the process that worked in the past instances where the pogoplug (either of the pinks or the Biz) went brain dead.  I removed power for several hours.  Let it be known that just a short time does not work.  It must be several hours.  (NO, it is not a heat problem ... .)

In the mean time, I tested both the hard disk drives and the flash drive on another computer.  I used chkdsk /f.  Nothing was found and the report was "healthy!"

At about 1550 I applied power again with the hopes I had removed the pogoplug from the Cloud for a sufficient amount of time.  It was, the Flash drive was again recognized.

Then I decided to attach the printer.  Maybe I would have better luck?  The printer (HP 1320 from the "list") was connected.  It was discovered.

On a side note, I am still amazed how quickly the pogoplug can discover a network attached printer that won't work faster than it can find and use a printer on the "list" that is attached by the required USB cable.

I have checked "Settings" and all entries look good.  The HP 1320 is the printer of choice and is recognized as a pogoplug enabled device.  Ya kinda wonder what this means since the Samsung printer is also recognized the same way and is unsupported.

Picked a text file.  Printed it to the HP.  The blueBar appeared saying the job was queued.  The PrintersTAB shows the status to be "Completed Successfully."  Nothing at the printer - no lights no paper no anything.  So, the pogoplug/printer is broken (tickets have been submitted on this problem, too).  No change with the printer.  So much for spending the money for a printer that was on the "list" and getting these results.

1715 I connected both of the other harddrives.  One of the harddrives looks okay.  The other only shows three partitions.  Maybe I am confused so I will eject the drive and check the number of partitions on the harddrive on a computer.

Here is something to ponder.  When ejecting the drive with partitions, two(2) of the partitions were called drives.  The third partion, when ejected, was called a PRINTER!  I have attached a screen print for your edification.  Belay that attachment.  Seems I did a Ctrl-C on some text and clobbered it.  Let's see if I can recreate it?  Nope, this time it was a drive for the first of the eject alert message windows that appear.  Sorry about that!

So the Pink plug has self-Healed by being in an offLine-powerOff state for several hours without me doing anything to make it revive.

This scenario has happened before to me on all three of the plugs; and, has repeated itself.  The very first time it happened, Sept 11, 2010 ticket, I did not understand.  Now that there have been several instances, I am beginning to get a better handle on the problem and as I wrote earlier in this note the problem has a moniker of a logical connection that has not disconnected that takes hours for the server to release the condition.

I like this product and I like the concept.  Right now, the pogoplugs are no more than toys that take a lot of attention to keep them working and documenting issues for input to technical support for their action.

I would like to have this issue resolved so that I can take the pogoplug as a serious and reliable business tool that I can use with our customers/clients and be confident in its operation when I am close to the pogo's and when I am traveling far away from the pogo's.  I have taken the time again to present the problem/issue in hopes that it will be given the consideration that I think it is due and not be closed.