Cannot SSH to pogoplug after updating pacman

[ccatccaatt]

I tried this method on linux system for brand new usb disk. I tried to format new usb to ex2 and ex3 both as /dev/sdd2. To reinstall I only repeat step 7 and 8. And it doesn't work, now the pogoplug is always blinking. I cannot even see it on my router's device list.

I tried to repeat starting from step 6, but ./mke2fs doesn't run on my linux. The error shows: "wrong format. different architecture".

I also tried to use pogoplug to install. But I cannot see it on my router with no usb disk pluging in it. So cannot ssh it.

So now my old usb is the only one that could start the system on arch linux, but I cannot ssh. So I don't want to change my old usb drive.

What should I do now?

Thanks

Tried several approaches people suggested and did not work.

I finally did re-install and everything worked again.

Made a copy of files on the old flash disc and saved some time in configurations.

To reinstall, just following the directions on this webpage for POGO-E02 and POGO-E02G
http://archlinuxarm.org/platforms/armv5 ... s-ui-tabs2

Make sure unplug all the usb discs before turning on the power.

[WarheadsSE]

First, stop trying to download that ARM binary and run it on x86. Use the OS's built-in mke2fs.

[theviper06]

I made my system new, right now.
Now the Update appears again. What to do, that this failure does not appear again?

Code: Select all

[root@alarm ~]# pacman -Syu
:: Synchronizing package databases...
 core                      37.9 KiB   456K/s 00:00 [######################] 100%
 extra                    420.4 KiB   935K/s 00:00 [######################] 100%
 community                384.5 KiB  1149K/s 00:00 [######################] 100%
 alarm                   1989.0   B  10.3M/s 00:00 [######################] 100%
 aur                        9.3 KiB   384K/s 00:00 [######################] 100%
:: Starting full system upgrade...
:: Replace gnupg2 with core/gnupg? [Y/n]


[WarheadsSE]

I suggest running multiple -Syu's to ensure everything is up to date, prior to rebooting.

If you're horridly concerned, prior to reboot, pacman -Sy openssl to be certain it's there, installed and has it's dependencies.

[hansarsch]

Idid the reinstall, didn't take that long, since I could copy over the configuration from the old drive.

Im experiencing the same issues as you guys. I have a tar of my working system. Since I'm somewhat of a noob I dont know how to restore my settings though without ending up in this unresponsive state again. Which folders/config files are safe to copy over a fresh install?

I suppose its naive of me to think that I can simply extract my old system-backup minus some ssh-relevant files to get back to my old setup?