Can't ssh into Pogo after Holidays

by **hilikustue** » Sun Jun 24, 2012 4:35 pm

Hi there,

At June 10th I went into my holidays. The day before I made pacman upgrades I think and then shut it down.
Now when I plug the Plug in, the green LED flashes and then goes off. When I try to ssh into it, I get "Connection refused".
The File System is clean and I am pretty sure it is not the problem with the initscripts, since I already had that here viewtopic.php?f=29&t=2824

Now there is a new sticky marked important having something to do with the kernel but to be honest, I have no clue if this could be the problem and how would I fix this, when I cannot ssh into my Pogo. I could boot it from a VM again I guess but what then?

cheers guys

by **hilikustue** » Mon Jun 25, 2012 5:03 pm

Hi again.

So I thought to myself: "I'll sort this out, no problem" and got the rootfs from the important thread above to a different USB Stick, booted it up and ran the update script that is pinned at the top under the category "important". Went through with no problem.

When i plug in my original rootfs thumb drive, it goes solid green after flashing (hurray) but unfortunately I cannot ping nor ssh into it. My router says the device is offline.

Could I cheat my Pogo to boot up properly with my original thumb drive again?

Thanks

by **Philoo** » Mon Jun 25, 2012 5:30 pm

if you ran the update-oxnas.sh script and you can boot your spare usb key after a pacman -Syu then you are almost there.

boot on your spare. connect the original usb drive (if it was rigged on sata, use a usb enclosure). mount the original rootfs, chroot to it and upgrade your chrooted archlinux.

from there you should be able to boot from the original drive.

Note: you may (or not) need to:
- copy the /lib folder from the spare drive to the original (or rerun the update-oxnas.sh from within the chroot. Since it flashes the backported kernel in NAND, please use that as a last resort)
- mount /proc and /dev to something sensible within the chroot. I had several such situations where pacman could not proceed with the install because it was missing /proc and /dev .

by **hilikustue** » Mon Jun 25, 2012 7:05 pm

Ok, I went through this wiki here https://wiki.archlinux.de/title/Chroot to see what the heck chroot means. I followed the steps via c&p and did pacman -Syu two times to be sure.

It updated many things but I still cannot get my original Stick to boot up. The LED flashes, turns to green but the Plug is still not reachable and doesn't get an IP Address.

there were some warnings during the updates, maybe it has something to do with those?

$this->bbcode_second_pass_code('', 'warning: could not get filesystem information for /media/hd-sdb1: No such file or directory upgrading openssh [##########################################################################] 100%
warning: /etc/ssh/sshd_config installed as /etc/ssh/sshd_config.pacnew
New optional dependencies for openssh
x11-ssh-askpass: input passphrase in X
xorg-xauth: X11 forwarding
')

by **Philoo** » Mon Jun 25, 2012 9:10 pm

Okay, the led goes steady green it means the kernel does not crash (check)

the initial warning in your copy/paste comes from the umounted /proc and /dev . pacman did proceed though so that is not really a concern. (check)

back when it worked did you make changes in your ssh server settings (/etc/ssh/sshd_config) ? the warning about sshd_config.pacnew means that the update of ssh comes with a different default config and that it did not replace the previous one b/c it was changed (presumably you customized it)

from what I see in the package changelog
https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/openssh you need to integrate the new configuration file. I would :
$this->bbcode_second_pass_code('', 'diff /etc/ssh/sshd_conf /etc/ssh/sshd_config.pacnew')

take note of the differences I made in sshd_config that are not in sshd_config.pacnew
add them manually as needed.
then
$this->bbcode_second_pass_code('', 'mv /etc/ssh/sshd_config /etc/sshd_config.old
cp /etc/ssh/sshd_config.pacnew /etc/ssh/ssh_config')

reboot.

Since there ARE changes in the server config file I think it's best not to post the diffs on the public forum.

if you want more instant gratification save the old config file, copy the *.pacnew as sshd_config, reboot and see what breaks (freenx would or some service using ssh as transport for encryption, as well some users account may not be allowed anymore depends on your original setup)

by **hilikustue** » Tue Jun 26, 2012 6:10 am

I just tried your last two lines of code succesfully because I wanted to see if that is the problem.
But unfortunately the LEd still goes to a solid green but it doesn't get an IP Address from my Router and so I still cannot ssh into it.

What else could I check?

Can't ssh into Pogo after Holidays

Can't ssh into Pogo after Holidays

Re: Can't ssh into Pogo after Holidays

Re: Can't ssh into Pogo after Holidays

Re: Can't ssh into Pogo after Holidays

Re: Can't ssh into Pogo after Holidays

Re: Can't ssh into Pogo after Holidays

Who is online