[RESOLVED] New batch of pogoplug P22 E02 not working

[caldersm]

I have the same issue.....weird how several people are having this issue.

This time I got a 16gb flash drive and did everything by the book....including the eth0 and the profile....same issue. Boots fine with no key, but isnt ping-able with the key. Also....I noticed that there is a lot of activity on the key, up to point and then it stops flashing....and doesnt do it again. Am going to try netconsole tonight....question about that....

They talk about setting up IP address 10.10.10.x for netconsole....but my home network is 192.168.0.xx.....Do I need to adjust those IP addy's...or use 10.10.10.x...?

[fgina]

Problem is if the network doesn't start up how would it post information to a net console server?

[caldersm]

ahhh....like that commercial....."Slow turtle"...!!

very true.....well....I am stumped.....hope someone comes up with something.....I was looking forward to my samba server....

[yazyazoo]

I think I was helping someone else who had the same problems. Can you try this and see if it works? After installing and reboot let it boot for 5 minutes. Then actually physically remove the power and plug it back in. Wait 5 minutes and see if you can SSH in.

Let me know how that works.

[fgina]

yaz, yes tried that already. and many other tricks found all over internet. some may even be outdated and not for this e02 device. such as,

- cold/soft boots with x minutes wait.
- e2fsck and partition usb key on different archlinux box
- set static ip using profile
- add fstab for partition info manually
- set static ip in rc.conf
- debian wheezy install script errors out, last error in log "kernel too old"
- debian debian squeeze script completes without error but restart still boots to pogo's OS
- something about preup wait 15 seconds in some config file

none worked so far.

I'm a geek. so looking forward to find the right fix for this 15 bucks thingy. and sure a lot of other people will benefit from the troubleshooting. so, what else are there to try?

[anoddspoon]

I had what appears to be the same problem when I installed arch on my Pogoplug E02. I wish I could remember the article that showed me the process on these boards, but here is what solved it for me:

-reboot the pogoplug without the usb drive; ssh in
-plug in the usb drive and manually mount it
-edit /etc/network.d/wired-eth0 to tell the system your Pogoplug has a static ip address (yes, mine is behind a dhcp router but lying to it made it work)
-save the file and reboot the Pogoplug with the usb drive plugged in.

[yazyazoo]

fgina,

try this. I forgot to add this to the last instructions. Re install from scratch and stop and the 'sync' section. Add this extra line to the install instructions. /usr/sbin/fw_setenv usb_rootfstype 'ext3'. Actually just cut and paste what I have below. The last three sections should look like this:



wget http://archlinuxarm.org/os/ArchLi...est.tar.gz
tar -xzvf ArchLinuxARM-armv5te-*.tar.gz # This will take a long time
rm ArchLinuxARM-armv5te-*.tar.gz
sync # Takes a while when using a flash drive

/usr/sbin/fw_setenv usb_rootfstype 'ext3'

cd ..
umount /tmp/usb
/sbin/reboot


After the reboot. Wait 5 minutes and see if you can SSH in. If not then unplug the power and replug in power and wait 5 minutes and see if you can SSH in.

[fgina]

yaz, it's not the file system's problem. I know boot strap sees the usb partition and starts to boot. because my dhcp server does record a dhcp client request and registers a host named "alarm". don't know if the client got the assigned ip or not, or something else after that craps out. if arch does boot up to some point, I think the file system is ok or it should stop the bootloader stage. this problem is highly suspicious related to networking.

regarding the post two above, the latest build now uses /etc/netctl to store its profiles. there's no longer a /etc/network.d. according to doc, https://wiki.archlinux.org/index.php/Netctl.
$this->bbcode_second_pass_code('', '# cp /etc/netctl/examples/ethernet-static /etc/netctl/profile
then,
# netctl start profile
')
Since I'm not booted in arch, in pogo's ssh session, how do I manually edit files to perform netctl start profile?

[fgina]

oh damn. don't know why. the thing suddently started working. alarm fully boots! ssh in as root pw root. I didn't change anything, what's the deal? I'm going to shut it down install again with another flash drive to find out what the heck made it work suddently.

btw, what should be the front led color status while booted in alarm?

[fgina]

ok I'm lost. just finished another fresh install on a different flash drive. it worked right after the first reboot. don't know why. I spend total of 30 hours to get it work. only the last 30 minutes mattered and there were nothing changed. still I think alarm's dhcp imlementation may be a bit shaky. there are people with this or similar problems all over the internet