Reinstalling Arch on Pogo v2

[forbajato]

I have been having some trouble with my Pogo v2 with it crashing a lot, several times a week. I assumed it was due to the old hard drive I had used to put the Arch root filesystem on. Today it finally gave up and when I went to look the hard drive had no partition on it (in gparted). When it gives up it boots to the regular Pogo software (I assume since the front light is now green instead of the orange that it used to be).

I started the re-install from scratch but got this error:
$this->bbcode_second_pass_code('', '## Unknown uBoot detected on mtd0: 0eb4684426a96efd12574c1ea9b52b6f
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.
rm: cannot remove '/tmp/valid-uboot.md5': No such file or directory')

Is there a solution to this? I love using my ArchPogo and would like to get it going again.

thomas

[xenoxaos]

You don't need to rerun the installer again. All you need to do is extract the rootfs (as root) to an ext2 formatted drive and reboot.

[forbajato]

OK, a follow up question - when I extract the rootfs to an ext2 formated drive as in step 7 of the tutorial, then sync and reboot. Everything seems to go fine. When I try to SSH back to the box I get a $this->bbcode_second_pass_code('', 'port 22: Connection Refused') error. Does that mean the SSH server isn't running by default on the plug? How can this be fixed?

[pepedog]

sash runs by default.
Maybe ip address changed?

[forbajato]

I checked the IP with nmap. I unplugged the drive with arch on it and rebooted the plug, was able to ssh into the plug's stock OS. At the risk of doing the same thing over and over again expecting a different result, would reinstalling (again) help?

thomas

[forbajato]

That is odd ... I tried re-booting several times, log in after reboot always failed. On the last attempt I ended up leaving the thing on, when I got back from lunch - it is working. I guess I was trying to log in too quickly, before sshd had started up properly.

Thanks to everyone for the help!

thomas