Problem booting Pogo V4

Box: Pogoplug V4

Just flashed the 2016.05 U-Boot and the default envs.
and make a Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi rootfs on sdcard according to the 20-Feb-2016 tutorial.

The green LED blinked for a while longer than normal. And when the LED blink stopped, I could't find the box on the local LAN.

Could you give me some advice? Thanks

the netconsole:

$ nc -l -u -p 6666

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          62331904      00000000-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 887 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
3154896 bytes read in 1360 ms (2.2 MiB/s)
loading uInitrd ...
7179935 bytes read in 1626 ms (4.2 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10246 bytes read in 2216 ms (3.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   5:55:25 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3154832 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 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 ...

Edited 3 time(s). Last edit at 10/03/2016 02:52PM by bodhi.

This is the problem with mounting rootfs.

Go back to when you create the rootfs. Did you change any of the steps? those steps must be done exactly, don't try to replace any with something you think equivalent.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,
Very appreciated for your help.
I tried 5 times today, repeated the steps of making a new rootfs, but each time I failed to boot into the system.
I even tried to use a new SD card, but got the same result.
Is there any way to log the booting process?
Thanks again.


I made the rootfs in an old Pogoplug box with the uboot.2014.07.

root@Pogoplug:~# mkfs -t ext3 /dev/mmcblk0p1
mke2fs 1.42.12 (29-Aug-2014)
/dev/mmcblk0p1 contains a ext3 file system
        last mounted on Mon Oct  3 23:54:13 2016
Proceed anyway? (y,n) y
Creating filesystem with 7791742 4k blocks and 1949696 inodes
Filesystem UUID: 08fef5e6-4261-4296-b602-633489422c74
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@Pogoplug:~# mkdir -p /tmp/rootfs
root@Pogoplug:~# mount /dev/mmcblk0p1 /tmp/rootfs/
root@Pogoplug:~# cd /tmp/rootfs/
root@Pogoplug:/tmp/rootfs# md5sum /home/silicat/temp/downloads.temp/Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
9f957e1dc5a36f90a285ab4615cb02fd  /home/silicat/temp/downloads.temp/Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@Pogoplug:/tmp/rootfs# tar -xjf /home/silicat/temp/downloads.temp/Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@Pogoplug:/tmp/rootfs# vi etc/fstab
root@Pogoplug:/tmp/rootfs# cat etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/root      /               ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0
root@Pogoplug:/tmp/rootfs# sync
root@Pogoplug:/tmp/rootfs# cd
root@Pogoplug:~# umount /tmp/rootfs/

Edited 2 time(s). Last edit at 10/04/2016 12:18AM by SiliCAT.

SiliCAT,

It seems you have missed a step: label the rootfs.

root@Pogoplug:~# mkfs -t ext3 /dev/mmcblk0p1
mke2fs 1.42.12 (29-Aug-2014)
/dev/mmcblk0p1 contains a ext3 file system
        last mounted on Mon Oct  3 23:54:13 2016
Proceed anyway? (y,n) y
Creating filesystem with 7791742 4k blocks and 1949696 inodes
Filesystem UUID: 08fef5e6-4261-4296-b602-633489422c74
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

Right here.

tune2fs -L rootfs /dev/mmcblk0p1

Or you could have labeled it while formatting:

mkfs -t ext3 -L rootfs /dev/mmcblk0p1

If it still did not work after labeling it then interrupt u-boot console, and get listing of u-boot envs and post here.

printenv

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,
You are right.
I labeled the file system as "rootfs", and it worked. Now I have a box running with the latest uBoot and the recent Debian.


Just one thing maybe I need to mention.
After the first "apt-get update && apt-get upgrade" perhaps we have to reboot the box.
My Debian got messed up when I executed "apt-get update && apt-get upgrade" followed by "apt-get install sudo", and could never boot into the system again. This would not be a problem if a reboot is taken after "apt-get upgrade".



Edited 1 time(s). Last edit at 10/04/2016 06:51PM by SiliCAT.