Welcome! Log In Create A New Profile

Advanced

Pogoplug v4 not starting

Posted by vaidyasr 
Pogoplug v4 not starting
August 16, 2019 10:37PM
I haven't used my pogoplug with Debian for almost an year. I have tried to switch on today and found the green light glowing, but can't find in network. I found the below log from netcat. The OS stalled at 'Starting kernel...' for long time. Any clue how to fix it?
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

MMC rescan: current device # 0 initialized OK

no USB devices available

no IDE devices available

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            15517696        00013210-01     83
loading envs from mmc 0 ...
98 bytes read in 948 ms (0 Bytes/s)
importing envs ...
running scan_disk ...
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 515 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
3232368 bytes read in 875 ms (3.5 MiB/s)
loading uInitrd ...
6838053 bytes read in 1413 ms (4.6 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10266 bytes read in 4532 ms (2 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.8.3-kirkwood-tld-1
   Created:      2016-12-07  15:25:08 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3232304 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.8.3-kirkwood-tld-1
   Created:      2016-12-07  15:25:48 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6837989 Bytes = 6.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...

Re: Pogoplug v4 not starting
August 16, 2019 10:59PM
vaidyasr,

It looks normal.

> Starting kernel ...

netconsole only display this much. Unless you've also done this to display dmesg on netconsole:

https://forum.doozan.com/read.php?2,9522

So, chance is that the kernel has booted and you should try to find the box. On another Linux box, if the hostname is debian, then ping it:

ping debian.local
or see if a new IP address was on the router list.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Pogoplug v4 not starting
August 16, 2019 11:09PM
Thank you bodhi. I can able to see the pogoplug in my router list, but can't ping it. Waited for about 1/2 hour and can't ping.
Re: Pogoplug v4 not starting
August 17, 2019 05:25AM
vaidyasr ,

> Thank you bodhi. I can able to see the pogoplug in
> my router list, but can't ping it. Waited for
> about 1/2 hour and can't ping.

Without serial console, we cannot see the problem for sure. But it seems likely that your roofs has error and got stuck during boot.

Try bringing it to another Linux box and check and fix errors. Assuming it is mounted at /media/sdb1 (was assigned device letter /dev/sdb1):

umount /media/sdb1
e2fsck /dev/sdb1
sync
And bring it back to the box, power up, see if the LED flash and then turn green.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Pogoplug v4 not starting
August 17, 2019 08:27AM
I did previously fsck to clean the disk. I have done again now and the machine came online for 2 pings and then it went unreachable.
64 bytes from 192.168.1.104: icmp_seq=1 ttl=64 time=8.22 ms
64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=4.16 ms
From 192.168.1.114 icmp_seq=9 Destination Host Unreachable
From 192.168.1.114 icmp_seq=10 Destination Host Unreachable
From 192.168.1.114 icmp_seq=11 Destination Host Unreachable
From 192.168.1.114 icmp_seq=12 Destination Host Unreachable
Re: Pogoplug v4 not starting
August 17, 2019 01:34PM
Well, in my experience, flash drive is not so good after 1 -2 years as system drive.

I once saw my dockstar had some errors (Kingston 1gb, after about 1 year) in dmesg, so I shut
it down and FSCKed it on another system, then it could not boot again. :P

Formatted the flash drive and re-made the system, it worked again.

After that, I just use hard drive or NFS as the root file system.
Re: Pogoplug v4 not starting
August 17, 2019 03:37PM
@david

> so I shut
> it down and FSCKed it on another system, then it
> could not boot again. :P

:) that happened to me years ago too, with a Patriot brand USB.


@vaidyasr

Try create a new rootfs with another USB drive (I prefer Sandisk), using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the released thread and boot with it. That way we can eliminate u-boot booting phase as a problem.

If you can boot with the new rootfs as replacement, then we know what the next step should be.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Pogoplug v4 not starting
August 17, 2019 11:14PM
Tried with a new micro-sd with adapter and formatted with ext3 and done the steps mentioned on the link. The below is the nc log. Still same behavior. No ping after few response.
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

MMC rescan: current device # 0 initialized OK

no USB devices available

no IDE devices available

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            15661056        61872a2a-01     83
loading envs from mmc 0 ...
** File not found /boot/uEnv.txt **
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: ide_preinit failed
device ide 0:1
** Bad device size - ide 0 **
device ide 1:1
** Bad device size - ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 885 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
3821592 bytes read in 1455 ms (2.5 MiB/s)
loading uInitrd ...
7245696 bytes read in 1642 ms (4.2 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10284 bytes read in 2346 ms (3.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...

.
Re: Pogoplug v4 not starting
August 17, 2019 11:15PM
Trying a USB pen drive will make the difference?
Re: Pogoplug v4 not starting
August 18, 2019 03:29AM
vaidyasr,

Make sure you followed the instruction very closely (the rootfs must be prepared while you are being root user, with a single partition Ext3, labeled it rootfs).

With the new rootfs. Power up, interrupt netconsole at countdown, and

printenv
boot

And post the entire netconsole log here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Pogoplug v4 not starting
August 18, 2019 07:55AM
How do you interrupt?. when it is saying 'Hit any key to stop autoboot:' do I need to type enter? Tried and the screen simply freezes.
Re: Pogoplug v4 not starting
August 18, 2019 09:35AM
output of printenv
printenv
arcNumber=3960
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.1.104
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
nc_ready=1
ncip=192.168.1.108
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.1.108
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3059/131068 bytes
Re: Pogoplug v4 not starting
August 18, 2019 04:36PM
vaidyasr,

Your env looks OK. So try creating a new USB rootfs and boot with it.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Pogoplug v4 not starting
August 18, 2019 05:14PM
Also, your pogoplug might have different IP addresses during the u-boot period and debian / linux period.

If you got a steady green led at last, maybe it booted successfully.
Re: Pogoplug v4 not starting
August 18, 2019 06:30PM
> If you got a steady green led at last, maybe it
> booted successfully.

Right!

Try ping its host name:

ping debian.local

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Pogoplug v4 not starting
August 18, 2019 08:53PM
daviddyer Wrote:
-------------------------------------------------------
> Also, your pogoplug might have different IP
> addresses during the u-boot period and debian /
> linux period.
>
> If you got a steady green led at last, maybe it
> booted successfully.
Thank you for tip. Yes, the IP is different and now found I can ping.
Re: Pogoplug v4 not starting
August 18, 2019 08:55PM
bodhi Wrote:
-------------------------------------------------------
> > If you got a steady green led at last, maybe it
> > booted successfully.
>
> Right!
>
> Try ping its host name:
>
>
> ping debian.local
>
It seems the SD card reader may have a fault. when I tried using the existing SD card as well as new SD with the boot/rootfs you have mentioned, it simply stalls at 'Starting kernel'. When I use the USB drive the plug works fine.Thanks for your time.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: