Pogoplug eo2 not showing in router

Hello all, I've browsed this forum a few times when I ran into issues with my pogo plug about a year ago, and now I need your help again.

Recently I tried to gain access to my device through the serial port. However, I burnt out my usb converter by using the wires in wrong place on the port itself. Hopefully I didn't damage anything, but my device no longer shows in the router. It powers on, and the ethernet port lights up, but the main LED doesn't come on anymore. It did have arch on it before I lost the usb that contained it, I'm not sure if that helps or not.

Any ideas would be greatly appreciated.

ljm90,


1. Do you have a serial console bootlog when it was last running? It would be important to know what do you have on your system, before we can even start troubleshooting.

2. The USB converter itself usually cannot be damaged. Which wires were connected to which pins? Did you connect the 3.3V to any off the 4 pins?

3. After realizing worng wires were connected, did you reconnect them correctly, and after that do you see anything coming out of serial console?

4. If you disconect the serial wires form the USB serial module converter, and let the system boot. What is the behavior of the main LED?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> ljm90,
>
>
> 1. Do you have a serial console bootlog when it
> was last running? It would be important to know
> what do you have on your system, before we can
> even start troubleshooting.
>
1. I don't have a log, however, I do know that it's running arch Linux if that helps?


> 2. The USB converter itself usually cannot be
> damaged. Which wires were connected to which pins?
> Did you connect the 3.3V to any off the 4 pins?
>
I only say it's damaged because it no longer shows up in my windows device manager, or dmesg in my Debian install. I connected the 3.3v to the power pin on the pogoplug, but I'm not sure where I connected it the first time


> 3. After realizing worng wires were connected, did
> you reconnect them correctly, and after that do
> you see anything coming out of serial console?
>
Yes, but when I tried it I kept getting an error trying to connect to the device.


> 4. If you disconect the serial wires form the USB
> serial module converter, and let the system boot.
> What is the behavior of the main LED?

Nothing. The lights for the Ethernet port light up, but the main led doesn't power at all.

Thanks again for all you do for this Community.

Lenin.

ljm90 Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > ljm90,
> >
> >
> > 1. Do you have a serial console bootlog when it
> > was last running? It would be important to know
> > what do you have on your system, before we can
> > even start troubleshooting.
> >
> 1. I don't have a log, however, I do know that
> it's running arch Linux if that helps?

Sure, do you remember which month and year you installed Arch?

>
> > 2. The USB converter itself usually cannot be
> > damaged. Which wires were connected to which
> pins?
> > Did you connect the 3.3V to any off the 4 pins?
>
> >
> I only say it's damaged because it no longer shows
> up in my windows device manager, or dmesg in my
> Debian install. I connected the 3.3v to the power
> pin on the pogoplug, but I'm not sure where I
> connected it the first time

Not good news. 3.3v should never be connected at all. Unplug power, disconnect it ASAP.

>
> > 3. After realizing worng wires were connected,
> did
> > you reconnect them correctly, and after that do
> > you see anything coming out of serial console?
> >
> Yes, but when I tried it I kept getting an error
> trying to connect to the device.
>

This is good news. Please power up again (after unplug 3.3v like I mentioned above), post the entire serial console log.

>
> > 4. If you disconect the serial wires form the
> USB
> > serial module converter, and let the system
> boot.
> > What is the behavior of the main LED?
>
> Nothing. The lights for the Ethernet port light
> up, but the main led doesn't power at all.
>

Sound like there is still some hope for serial console if we see output.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> > > 1. Do you have a serial console bootlog when
> it
> > > was last running? It would be important to
> know
> > > what do you have on your system, before we
> can
> > > even start troubleshooting.
> > >
> > 1. I don't have a log, however, I do know that
> > it's running arch Linux if that helps?
>
> Sure, do you remember which month and year you
> installed Arch?
>
I don't remember exactly what month, but it was probably around march 2016


> >
> > > 2. The USB converter itself usually cannot be
> > > damaged. Which wires were connected to which
> > pins?
> > > Did you connect the 3.3V to any off the 4
> pins?
> >
> > >
> > I only say it's damaged because it no longer
> shows
> > up in my windows device manager, or dmesg in my
> > Debian install. I connected the 3.3v to the
> power
> > pin on the pogoplug, but I'm not sure where I
> > connected it the first time
>
> Not good news. 3.3v should never be connected at
> all. Unplug power, disconnect it ASAP.
>
I disconnected it almost immediately, as it was getting quite warm. That's when I checked what cables were what and realized my mistake. It hasn't been hookup since.

> >
> > > 3. After realizing worng wires were
> connected,
> > did
> > > you reconnect them correctly, and after that
> do
> > > you see anything coming out of serial
> console?
> > >
> > Yes, but when I tried it I kept getting an
> error
> > trying to connect to the device.
> >
>
> This is good news. Please power up again (after
> unplug 3.3v like I mentioned above), post the
> entire serial console log.
>
That's just it, I can't access the device because my computer isn't seeing the converter.


> >
> > > 4. If you disconect the serial wires form the
> > USB
> > > serial module converter, and let the system
> > boot.
> > > What is the behavior of the main LED?
> >
> > Nothing. The lights for the Ethernet port light
> > up, but the main led doesn't power at all.
> >
>
> Sound like there is still some hope for serial
> console if we see output.

ljm90 Wrote:
-------------------------------------------------------

> >
> > This is good news. Please power up again (after
> > unplug 3.3v like I mentioned above), post the
> > entire serial console log.
> >
> That's just it, I can't access the device because
> my computer isn't seeing the converter.
>
>
I did this once. Do you have another usb port to plug it into or have you rebooted your pc and retried?

I remember it took some time for my pc to be able to use the usb port again. I think it trips a safety fuse to try and save the port. So reboot and see if you can use the port again with anything i.e. usb stick then try another usb port if it still doesn't work.

I have since rebooted my PC and used another USB port to no avail. I took apart the cover of the converter because it looked melted? It looks like where the ground wire hooks up is a little blackened. I'm not sure what that could mean though.

It might have been plugged in too long then and fried the cable.

ljm90,

Quote

> 3. After realizing worng wires were connected, did
> you reconnect them correctly, and after that do
> you see anything coming out of serial console?
>
Yes, but when I tried it I kept getting an error trying to connect to the device.

Quote

That's just it, I can't access the device because my computer isn't seeing the converter.

So you cannot see anything coming out at serial console at all?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/12/2017 08:43AM by bodhi.

bodhi Wrote:
> So you cannot see anything coming out at serial
> console at all?


None. But I don't even get that far. My computer doesn't even show that the converter is being plugged in.

Update: I purchased a new cable because I'm pretty certain that the one I have isn't any good. It'll be here in two days and I'll update again when I get more info