[RESOLVED] [n00b] V4 ssh woes

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

[RESOLVED] [n00b] V4 ssh woes

Postby skittixch » Tue Jan 17, 2012 7:41 am

I'm trying to install the new software for pogoplug series 4, and I think I've just made a mess of things so far. I went through the installation instructions, and seemingly set everything up as I meant to. Along the way, I received a "tar: short read" message, but I didn't know enough to know this was an error. I kept progressing through, and rebooted my pogoplug. Now when I try to SSH back into my device, I get an "ssh: connect to host ##.#.#.# port ##: Operation timed out".

Potentially making matters worse, I attempted to get the stock pogoplug software back on by reformatting the drive I had plugged in, and making a folder called "revert" (per the directions). Upon this not working, I realized that archlinux would probably have to be installed correctly in order to make this command work.

So here I am with no ssh access to my pogo plug, an empty hard drive, and an infantile level of knowledge about linux. Any suggestions as to where to go from here would be greatly appreciated. I'd be happy just knowing I can start over and take things one step at a time again.
skittixch
 
Posts: 5
Joined: Tue Jan 10, 2012 8:47 pm

Re: [n00b] V4 ssh woes

Postby emkay » Tue Jan 17, 2012 8:10 am

When did this error occur?
During this step (step 9):

$this->bbcode_second_pass_code('', 'tar -xzvf ArchLinuxARM-armv5te-latest.tar.gz # This will take a long time')

?

All other steps went through fine?

What does you LED do while / after booting? Does it turn green/red, does it keep blinking?
emkay
 
Posts: 12
Joined: Wed Nov 30, 2011 10:45 pm

Re: [n00b] V4 ssh woes

Postby kmihelich » Tue Jan 17, 2012 1:22 pm

If you got to the stage of the install where you installed U-Boot by running install-ppv4.sh, then you can revert back to stock by following the instructions. The reversion takes place in U-Boot, and does not need a running Arch install. The instructions are very specific though: use the top USB port with a normal FAT32 formatted drive (not ext2/3). Power on the plug with that drive attached, wait for the blinking to subside and you should get a solid red LED, possibly followed by solid green.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: [n00b] V4 ssh woes

Postby skittixch » Tue Jan 17, 2012 4:12 pm

@emkay yes, that's where the short read error occurred. I actually was a little curious to see that it didn't give me some other sign that it'd completed properly, so I ran the command twice (dumb?) ...both times, it spat out the same "tar:short read" message. I believe uboot installed correctly, but I'll have to wait until later to check it out. thanks so far
skittixch
 
Posts: 5
Joined: Tue Jan 10, 2012 8:47 pm

Re: [n00b] V4 ssh woes

Postby emkay » Tue Jan 17, 2012 4:23 pm

If thats the case, you can just plug that drive into your linux pc (livecd will do) and do the following steps there:

- partition the drive if necessary
- format the rootfs partition with ext3
- download the tarball of the rootfs
- extract the tarball (logged in as root or with ubuntu use sudo su!!) onto the partition
- plug the drive into your PPv4 and let it boot.


If no other problems occurred in your previous install your PPv4 is already modified for alarm and needs no further action. Just prepare a new roots on the drive and enjoy the benefits from alarm!

EmKay
emkay
 
Posts: 12
Joined: Wed Nov 30, 2011 10:45 pm

Re: [n00b] V4 ssh woes

Postby skittixch » Thu Jan 19, 2012 5:34 am

Thank you guys very much. Turns out I needed to plug a thumb drive into the top slots and not a usb hard disk. I restored my pogoplug to stock settings, and started over. I carefully copied the instructions into the terminal, and allowed enough time for processes to finish before I moved on. It seemed successful, but I rebooted the system to find that I'm not able to ssh back in.
$this->bbcode_second_pass_code('', 'macbook:~ Admin$ ssh root@##.#.#.#
ssh: connect to host ##.#.#.# port ##: Operation timed out
')

Any thoughts?

[SOLVED]

I was trying to connect to my old ip address from the DHCP Clients, instead of "Alarm".
skittixch
 
Posts: 5
Joined: Tue Jan 10, 2012 8:47 pm


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 1 guest