Pogoplug V2 (pink) no light no SSH [Resolved]

[bodhi]

$this->bbcode_second_pass_quote('loafy', 'I') have been having the same problem - using the Pink instructions based on the exchange in viewtopic.php?f=29&t=2133&p=11454#p11455 but I have yet to get the unit to reboot with the flash drive in place with the system installed on it.

I've tried various types of flash drives with the latest one being a SanDisk Cruzer Fit 8GB as suggested in http://forum.doozan.com/read.php?2,1915,6235#msg-6235

the only way to get the unit to come back is to remove the flash drive and reboot it.

I'm ready to throw in the towel so any help would be greatly appreciated!

thanks

[loafy]

bodhi

good suggestions and something I should have tried before posting - I guess my frustrations were getting the better of me...

I did an fsck on the flash drive on another system and indeed found a number of issues (see below) . I let fsck make the changes and correct the file system then re-inserted the drive back into the pogo unit and rebooted but am seeing the same thing - solid yellow and no network access.

My next step is to re-format the stick under the mint unix system I have then re-install archlinux via the instructions.

will try the netcat option if I'm not successful with the above.

thanks again for the help

$this->bbcode_second_pass_code('', '
(oo)\_______
(__)\ )\/\
||----w |
|| ||
mint@mint ~ $ whoami
mint
mint@mint ~ $ sudo fsck /dev/sdb1
fsck from util-linux-ng 2.17.2
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sdb1
mint@mint ~ $ mount
aufs on / type aufs (rw)
none on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
/dev/sr0 on /cdrom type iso9660 (ro,noatime)
/dev/loop0 on /rofs type squashfs (ro,noatime)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/mint/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=mint)
/dev/sdc1 on /media/ad4ef509-3401-45cf-99bf-b4a05054a7f2 type ext2 (rw,nosuid,nodev,uhelper=udisks)
mint@mint ~ $ df -h
Filesystem Size Used Avail Use% Mounted on
aufs 1.5G 65M 1.5G 5% /
none 1.5G 292K 1.5G 1% /dev
/dev/sr0 832M 832M 0 100% /cdrom
/dev/loop0 815M 815M 0 100% /rofs
none 1.5G 100K 1.5G 1% /dev/shm
tmpfs 1.5G 20K 1.5G 1% /tmp
none 1.5G 340K 1.5G 1% /var/run
none 1.5G 0 1.5G 0% /var/lock
/dev/sdc1 7.4G 548M 6.5G 8% /media/ad4ef509-3401-45cf-99bf-b4a05054a7f2
mint@mint ~ $ sudo fsck /dev/sdc1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/sdc1 is mounted.

WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Do you really want to continue (y/n)? no

check aborted.
mint@mint ~ $ umount /media
umount: /media is not mounted (according to mtab)
mint@mint ~ $ umount /media/ad4ef509-3401-45cf-99bf-b4a05054a7f2
mint@mint ~ $ sudo fsck /dev/sdc1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/sdc1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 122162, i_blocks is 64, should be 32. Fix<y>? yes

Inode 122164, i_blocks is 64, should be 16. Fix<y>? yes

Inode 130483, i_blocks is 24, should be 8. Fix<y>? yes

Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes

Inode 130531 was part of the orphaned inode list. FIXED.
Inode 130541 was part of the orphaned inode list. FIXED.
Inode 448466 was part of the orphaned inode list. FIXED.
Inode 448467 was part of the orphaned inode list. FIXED.
Inode 448468 was part of the orphaned inode list. FIXED.
Inode 448350, i_size is 3657053, should be 3661824. Fix<y>? yes

Inode 448350, i_blocks is 7136, should be 7160. Fix<y>? yes

Inode 448349, i_size is 3648034, should be 3653632. Fix<y>? yes

Inode 448349, i_blocks is 7128, should be 7144. Fix<y>? yes

Inode 448354, i_size is 2534077, should be 2539520. Fix<y>? yes

Inode 448354, i_blocks is 4960, should be 4968. Fix<y>? yes

Pass 2: Checking directory structure
Entry 'cedb-journal' in /??? (122161) has deleted/unused inode 122163. Clear<y>? yes

Pass 3: Checking directory connectivity
Unconnected directory inode 122161 (/???)
Connect to /lost+found<y>? yes

Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Inode 2 ref count is 21, should be 22. Fix<y>? yes

Inode 122161 ref count is 3, should be 2. Fix<y>? yes

Unattached inode 122164
Connect to /lost+found<y>? yes

Inode 122164 ref count is 2, should be 1. Fix<y>? yes

Pass 5: Checking group summary information
Block bitmap differences: +492031 +(492040--492043) +(501760--501761) -526336 -530432 -544768 +552960
Fix<y>? yes

Free blocks count wrong for group #15 (32257, counted=32250).
Fix<y>? yes

Free blocks count wrong for group #16 (31732, counted=31734).
Fix<y>? yes

Free blocks count wrong (1783195, counted=1783190).
Fix<y>? yes

Inode bitmap differences: +(122161--122162) +122164
Fix<y>? yes

Free inodes count wrong for group #15 (8144, counted=8141).
Fix<y>? yes

Directories count wrong for group #15 (0, counted=1).
Fix<y>? yes

Free inodes count wrong (457384, counted=457381).
Fix<y>? yes


/dev/sdc1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdc1: 31259/488640 files (0.1% non-contiguous), 170896/1954086 blocks
mint@mint ~ $ sudo fsck /dev/sdc1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/dev/sdc1: clean, 31259/488640 files, 170896/1954086 blocks
mint@mint ~ $

')

[loafy]

update - I did the re-install after the fsck corrections from the external Linux machine but no luck in getting the unit to boot using archlinux.

will try the other suggestions - thanks

[loafy]

bodhi,

I rebuilt the flash drive on a linux system and loaded archlinux on it then set up nc and set all the variables on the pogo unit with fw_setenv and got the console details below.

I'm still unable to get past the solid yellow light and can not ssh into the box. a consistent ping shows a few packets are returned but the majority dropped.

this looks something is messed up with /boot/uInitrd? not sure where to go next....

thanks

$this->bbcode_second_pass_code('', '
mint@mint /tmp $ nc -l -u 6666 &
[1] 3732
mint@mint /tmp $ nc -u 192.168.1.120 6666

U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
Marvell-PinkPogo by Jeff Doozan
Hit any key to stop autoboot: 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)
2821160 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.4-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2821096 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
')

[WarheadsSE]

loafy, please at least wrap your bootlogs in a code tag.

[bodhi]

$this->bbcode_second_pass_quote('loafy', 'b')odhi,

I rebuilt the flash drive on a linux system and loaded archlinux on it then set up nc and set all the variables on the pogo unit with fw_setenv and got the console details below.

I'm still unable to get past the solid yellow light and can not ssh into the box. a consistent ping shows a few packets are returned but the majority dropped.

this looks something is messed up with /boot/uInitrd? not sure where to go next....

thanks

$this->bbcode_second_pass_code('', '
mint@mint /tmp $ nc -l -u 6666 &
[1] 3732
mint@mint /tmp $ nc -u 192.168.1.120 6666

U-Boot 2010.09 (Oct 23 2010 - 11:51:16)
Marvell-PinkPogo by Jeff Doozan
Hit any key to stop autoboot: 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)
2821160 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.4-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2821096 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
')

[loafy]

Guess I can re-do step 7 but I have done this a number of times with no change.

7. Download and install Arch Linux ARM:
cd usb
wget http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz
tar -xzvf ArchLinuxARM-armv5te-*.tar.gz # This will take a long time
rm ArchLinuxARM-armv5te-*.tar.gz
sync # Takes a while when using a flash drive

from what I see in the tar ball the only file in ./boot is uImage. There is no uInitrd file anywhere in the package.

should this get created somehow?

thanks

[WarheadsSE]

.. just because it is checking if a uInitrd exists... then it should exist?

[loafy]

$this->bbcode_second_pass_quote('WarheadsSE', '.'). just because it is checking if a uInitrd exists... then it should exist?

[WarheadsSE]

I think it's time you considered the possibility that your u-boot may not be passing the right arguments to the kernel.

It's reading the kernel right, and attempting to boot it, then going "nowhere."