Cannot SSH into PogoPlug after installing ArchLinux

[Voidless]

The last step is actually to be done on the computer you ssh from, so basically if you do it with Putty from a windows PC that is not the command you need to run. You actually need to run regedit and delete the keys in HKEY_CURRENT_USER/Software/SimonTatham/PuTTY/SshHostKeys.

But the problem I'm having is past that. I tried to reserve an ip for my pogoplug and ssh into that but that still doesn't work once its booted back on with the orange light I can't ssh in or ping the device anymore... there's places in the FAQ saying that I might just need to change the usb stick I'm using but I just bought this one and I'd like to be sure thats the problem before buying a new one...

[Voidless]

I tried redoing the whole process again with a new usb key (unfortunately it was of the same brand, I have none other available) and I still have to same problem described above... I'll try again tomorrow with a new usb key from another brand if I find one... (anyone got something to suggest)

[moonman]

$this->bbcode_second_pass_quote('Voidless', 'T')he last step is actually to be done on the computer you ssh from, so basically if you do it with Putty from a windows PC that is not the command you need to run. You actually need to run regedit and delete the keys in HKEY_CURRENT_USER/Software/SimonTatham/PuTTY/SshHostKeys.

But the problem I'm having is past that. I tried to reserve an ip for my pogoplug and ssh into that but that still doesn't work once its booted back on with the orange light I can't ssh in or ping the device anymore... there's places in the FAQ saying that I might just need to change the usb stick I'm using but I just bought this one and I'd like to be sure thats the problem before buying a new one...

[KMakato]

Hey all, I've got the same problem going on om my E02 as well.
I've cobbled together a serial link so that I can at least receive the console (no tx yet).
Unfortunately it appears to be a kernel panic stopping everything from booting. Not to sure what to make of it yet, but I'll give you any information that might assist in finding a solution.

So far, I've tried 3 USB flash drives (a new 8GB Sandisk Fit, an old 4GB Crucial, and a new ADATA 16 GB USB 3.0).
Of these, the only one to NOT cause a panic was the ADATA, but it failed Netcfg and after a reboot it went back to kernel panic. I will be trying a platter drive soon just to round things over.

Most recent Console Log:
$this->bbcode_second_pass_code('', '
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.02.27 04:51:13 =~=~=~=~=~=~=~=~=~=~=~=


U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 3  2  1  0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 727
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2869588 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-15-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2869524 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 7.227132] rtc-mv rtc-mv: internal RTC not ticking
[ 7.235903] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 17.248641] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
[ 17.267236] Unable to handle kernel paging request at virtual address 00303030
[ 17.274493] pgd = c0004000
[ 17.277242] [00303030] *pgd=00000000
[ 17.280844] Internal error: Oops: 5 [#1] PREEMPT
[ 17.285480] Modules linked in:
[ 17.288560] CPU: 0 Not tainted (3.1.10-15-ARCH #1)
[ 17.293729] PC is at mount_block_root+0x200/0x280
[ 17.298458] LR is at mount_block_root+0x1e0/0x280
[ 17.303186] pc : [<c052fbfc>] lr : [<c052fbdc>] psr: 40000013
[ 17.303192] sp : cf82bf80 ip : 00000000 fp : 00000000
[ 17.314728] r10: c049f440 r9 : 00000000 r8 : 00008000
[ 17.319979] r7 : c08618fc r6 : c0551e7c r5 : cf812005 r4 : 00303030
[ 17.326536] r3 : cf82beb0 r2 : cf82bf74 r1 : c049f418 r0 : 00000039
[ 17.333094] Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 17.340435] Control: 0005397f Table: 00004000 DAC: 00000017
[ 17.346208] Process swapper (pid: 1, stack limit = 0xcf82a270)
[ 17.352067] Stack: (0xcf82bf80 to 0xcf82c000)
[ 17.356452] bf80: 00000000 00000000 00006180 cf4a2980 00006000 c00d3508 cf8190a0 cf497300
[ 17.364675] bfa0: c049f440 00000001 c0593380 c0551e91 c000945c 00000013 00000000 00000000
[ 17.372897] bfc0: 00000000 c052ff3c fffffffe 00000002 00000000 c0558ee4 c0558ee4 c052f8c8
[ 17.381120] bfe0: 00000000 00000000 00000000 00000000 c052f7ac c000945c ffffeffb edfffffc
[ 17.389352] [<c052fbfc>] (mount_block_root+0x200/0x280) from [<c052ff3c>] (prepare_namespace+0x160/0x1c0)
[ 17.398971] [<c052ff3c>] (prepare_namespace+0x160/0x1c0) from [<c052f8c8>] (kernel_init+0x11c/0x14c)
[ 17.408157] [<c052f8c8>] (kernel_init+0x11c/0x14c) from [<c000945c>] (kernel_thread_exit+0x0/0x8)
[ 17.417073] Code: e1a00004 ebf3b517 e2800001 e0844000 (e5d43000)
[ 17.423353] ---[ end trace ab834c16b0cb6d1f ]---
[ 17.428111] Kernel panic - not syncing: Attempted to kill init!
[ 17.434091] [<c000d290>] (unwind_backtrace+0x0/0xe0) from [<c03cc5d4>] (panic+0x58/0x198)
[ 17.442353] [<c03cc5d4>] (panic+0x58/0x198) from [<c0021a48>] (do_exit+0x88/0x7a0)
[ 17.449992] [<c0021a48>] (do_exit+0x88/0x7a0) from [<c000b8e0>] (die+0x1d4/0x200)
[ 17.457540] [<c000b8e0>] (die+0x1d4/0x200) from [<c03cc4ac>] (__do_kernel_fault.part.2+0x54/0x74)
[ 17.466475] [<c03cc4ac>] (__do_kernel_fault.part.2+0x54/0x74) from [<c03d3c58>] (do_page_fault.part.3+0x274/0x2b0)
[ 17.476953] [<c03d3c58>] (do_page_fault.part.3+0x274/0x2b0) from [<c03d3cc0>] (do_page_fault+0x2c/0x94)
[ 17.486417] [<c03d3cc0>] (do_page_fault+0x2c/0x94) from [<c00083cc>] (do_DataAbort+0x34/0x98)
[ 17.495005] [<c00083cc>] (do_DataAbort+0x34/0x98) from [<c03d2478>] (__dabt_svc+0x38/0x60)
[ 17.503322] Exception stack(0xcf82bf38 to 0xcf82bf80)
[ 17.508415] bf20: 00000039 c049f418
[ 17.516639] bf40: cf82bf74 cf82beb0 00303030 cf812005 c0551e7c c08618fc 00008000 00000000
[ 17.524876] bf60: c049f440 00000000 00000000 cf82bf80 c052fbdc c052fbfc 40000013 ffffffff
[ 17.533120] [<c03d2478>] (__dabt_svc+0x38/0x60) from [<c052fbfc>] (mount_block_root+0x200/0x280)
[ 17.541970] [<c052fbfc>] (mount_block_root+0x200/0x280) from [<c052ff3c>] (prepare_namespace+0x160/0x1c0)
[ 17.551605] [<c052ff3c>] (prepare_namespace+0x160/0x1c0) from [<c052f8c8>] (kernel_init+0x11c/0x14c)
[ 17.560804] [<c052f8c8>] (kernel_init+0x11c/0x14c) from [<c000945c>] (kernel_thread_exit+0x0/0x8)

')
Any help would be much appreciated.

[moonman]

This says it all:

$this->bbcode_second_pass_code('', '(sda1): couldn't mount as ext2 due to feature incompatibilities')

Are you formatting the drives as ext2?

[KMakato]

Negative, unless it says to do so in the installation instructions. From what I understood, "mke2fs -j" would be ext3 (or at least the equivalent).

[KMakato]

And of course by following the same steps I've been following, the installation boots fine from an ancient IDE enclosure, which is less than optimal.
Is it possible that all three flash drives were incompatible, even though one had booted at one point, and all have been booted from on a pc previously? Or could something else have gone wrong?

EDIT: Okay, so after having the POGO booted for awhile, it locked up (dropped ssh, and no response from the console upon inserting a usb drive). After rebooting, I'm getting the kernel panic and the same error as before "couldn't mount as ext2 due to feature incompatibilities" and this is with the HDD, not the flash drive.

[moonman]

I would test for errors on the hdd/flash drive with e2fsck. Convert your drive to ext3. Don't forget to change bootloader variable so that it knows you are using ext3.
$this->bbcode_second_pass_code('', 'fw_setenv usb_rootfstype ext3')

[Voidless]

I'm gonna try that too but how do I use fw_setenv? If I remove the flash drive, reboot, ssh back in the pogoplug (E02) fw_setenv is not a known command, where do I find it? Or install it?

[Voidless]

found where fw_setenv was hiding seems it was not added to path, did a printenv saw that the usb_rootfstype was set to ext2 changed it to ext3 did a reboot I still got the same issue... ill check for error with e2fsck now... see it comes up with something...