Pogo broken on recent update (ssh+samba down)

[kuleszdl]

Hi folks,

I just did an update of my pogo after running nicely for probably one month and it broke the system. Here are its "last words":

$this->bbcode_second_pass_code('', '
(36/56) upgrading util-linux [##############################] 100%
vercmp: error while loading shared libraries: libarchive.so.12: cannot open shared object file: No such file or directory
/tmp/alpm_l51IYc/.INSTALL: line 11: [: : integer expression expected
(37/56) upgrading ntfs-3g [##############################] 100%
(38/56) upgrading openssh [##############################] 100%
(39/56) upgrading pacman-mirrorlist [##############################] 100%
warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
(40/56) upgrading pacman [##############################] 100%
>>> Run `pacman-key --init` to set up your pacman keyring.
Bus errorpgrading perl [###########-------------------] 39%
Connection to mypogo closed by remote host.
')

The machine responds to ping, but I can neither ssh in nor access it via samba anymore. To be honest, if there was debian or ubuntu for the pogoplug pro, I would switch immediately

Btw.: I'm not running this over wifi...

[Geoff]

Yeah, it can be such a hassle when pacman breaks during an upgrade. If you happen to have made a backup, then you can recover fairly easily <--(**hint to all who read this**). Just boot up using the backup, fsck and mount the broken system, and then use the pacman "--root" flag to upgrade it using the intact backup pacman to do the job. To be safe, you could reinstall any packages whose upgrades may have failed. If you don't have a backup, then I guess you would need to make another bootable rootfs from the latest tarball. You could use that to recover the broken system.

[kuleszdl]

I had an old dd-image which I played back on the USB stick (like from 3 months ago), but with this version the update worked without problems. Very strange, but it seems like you really should not attempt to update ALARM without making a backup before...