Cannot SSH into PogoPlug after installing ArchLinux

[KMakato]

Okay, I seem to have gotten my E02 to boot fully into Arch after way too many attempts.
The drives WERE formatted as ext3, but were not syncing properly, or something, and thus getting corrupt regardless.
I used an Arch Linux "live cd" in VMware for making the filesystem and for running e2fsck.

In VMware, I partitioned my flash drive, made the filesystem, then ran e2fsck before installing anything onto the drive, just to be on the safe side. I made sure to safely shut down the live cd before pulling out the flash drive, then inserted it into the pogo.

Once in the pogo, I just ran through the normal installation (starting at "mkdir usb" under /tmp), but instead of "reboot" I did "poweroff", waited for everything to stop, and unplugged the pogo.

Before even trying to boot off of it, I put the flash drive back into the VMware instance and ran e2fsck again. Oddly enough, it did find issues (something about indexes or trees, should have written it down), even though everything had been unmounted and disconnected safely. Told it to fix everything, then ran it again just to be on the safe side. Not sure if it did anything, but I ran "sync" before disconnecting the drive (safely).

I put the flash drive back into the pogo, opened the console, and powered on the pogo. Amazingly, it booted, no issues. Was able to ssh in and run "pacman -Syu" without it locking up or anything. Ran "sync" and "poweroff", power cycled, and it booted back up again fine!

I'm probably rambling, but I'm just glad that it finally booted properly.

And just in case someone needs the syntax for e2fsck:
$this->bbcode_second_pass_code('', 'e2fsck -f /dev/sdX1')
Just replace X with what corresponds to your device, and if it asks if you want to remove damaged indexes/trees (I'll correct that later) just say yes.

[ThinkFast]

Having the same basic problem. Except after I executed step 9 "ssh-keygen -R 10.0.0.191", I tried to SSH back in and got a message "The authenticity of host '10.0.0.191 (10.0.0.191)' can't be established.\RSA key fingerprint is 86:2e:...\".
I thought it would help to restart the Pogo. So I made the mistake of pulling the power and restarting!
After that when I SSH there was no response and the command time out.

After reading this thread, I tried removing the USB key and powered up. Then SSH to it, but I'm getting the same message "The authenticity of host '10.0.0.191 (10.0.0.191)' can't be established.\RSA key fingerprint is 86:2e:...\".
The terminal session buffer ran over but here's the end of it:
./var/spool/mail/
./var/games/
-bash-3.2# rm ArchLinuxARM-armv5te-*.tar.gz
-bash-3.2# sync
-bash-3.2# cd ..
-bash-3.2# umount usb
-bash-3.2# /sbin/reboot
-bash-3.2# Connection to 10.0.0.191 closed by remote host.
Connection to 10.0.0.191 closed.
speedyg:~ speedyg$ ssh-keygen -R 10.0.0.191
/Users/speedyg/.ssh/known_hosts updated.
Original contents retained as /Users/speedyg/.ssh/known_hosts.old
speedyg:~ speedyg$ ssh root@10.0.0.191
The authenticity of host '10.0.0.191 (10.0.0.191)' can't be established.
RSA key fingerprint is 86:2e:5c:1f:c6:05:61:ef:75:bd:c4:de:46:62:a2:da.
Are you sure you want to continue connecting (yes/no)? n
Please type 'yes' or 'no': no
Host key verification failed.
speedyg:~ speedyg$
[* Removed power to Pogoplug, waited 10s and reconnected. *]
speedyg:~ speedyg$ ssh root@10.0.0.191
ssh: connect to host 10.0.0.191 port 22: Operation timed out
speedyg:~ speedyg$

Not sure how to proceed now. Maybe reboot the router to flush the DNS data.
Any ideas?

[Socaltom]

if putty is giving you the warning just accept it and move on. What happens is that when you are connected using the pogo OS, Putty creates a "key" that identifies that its not someone spoofing that ip. When you reconnect to the same ip, it detects a different "key" and it warns you. But since we know it should be different its ok to ignore the warning.
Tom

[KMakato]

Usually when I ssh in, putty pops up a dialog with the options "Yes" "No" "Cancel" (meaning YES add ssh key to reg and connect, NO don't add key to reg and connect, CANCEL connection). I always choose NO. It'll pop up every time, but it's worth not having to bother with removing keys if the old one changes.

Oh, and you'll definitely have to remove your drive and run e2fsck on it on another computer/live cd after unplugging it like that.

[ThinkFast]

Thanks for responding!
I ignored the warnings and got in. I then started the process over and ran fdisk on the drive. I finished the rest of the process and was successful. Then I changed my password and executed "/sbin/poweroff".
Thanks for your help everyone!

[huntusa]

Have u tried using default password root/root after installing Archlinux? Pogoplug SSH password will not work once Archlinux is intalled.You will have to do

ssh root@<IP>
password: root

This will get you in your Archlinux installation.