Welcome! Log In Create A New Profile

Advanced

Recovery Help on Dockstar

Posted by jason 
Recovery Help on Dockstar
June 13, 2016 08:04AM
It seems I've done something incorrectly in updating my Dockstar. I was trying to upgrade to the most current u-boot and rootfs, but it fails to boot. Though I've read through a lot of helpful content here, I haven't figured out how to resolve it myself. I have netconsole access, so I've provided my boot messages and envs

U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21 -0800)
Seagate FreeAgent DockStar
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... 2 USB Device(s) found
   	scanning usb for storage devices... 0 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

no USB devices available
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
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
Unknown command 'ide' - try 'help'
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

arcNumber=2097
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=mw 0x800000 0 1; run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 0x1100000; fi; else if run load_dtb; then bootm 0x800000 - 0x1c00000; else bootm 0x800000; 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-pogo_e02.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.1.99
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; ext2load $bootdev $device 0x1c00000 $dtb_file
load_initrd=echo loading uInitrd ...; ext2load $bootdev $device 0x1100000 /boot/uInitrd
load_uimage=echo loading uImage ...; ext2load $bootdev $device 0x800000 /boot/uImage
machid=0x831
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.1.19
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 ext2load $dev $disknum:1 0x800000 /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
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.1.19
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_import=echo importing envs ...; env import -t 0x810000
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_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /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: 3130/131068 bytes

I think I must have written the wrong u-boot envs for the Dockstar, since it references the dtb for Pogo E02, but I'm not sure how to write the new ones to the device with the access I have.

I also tried to make a USB with 4.4.0 rootfs that would hopefully boot, but when I have that in the device on boot, I get basically the same boot message.

I appreciate any help resolving this.

Thanks,
Jason
Re: Recovery Help on Dockstar
June 13, 2016 01:20PM
jason,

> scanning bus 0 for devices... 2 USB Device(s)
> found
> scanning usb for storage devices... 0 Storage
> Device(s) found

The Dockstar could not find your USB rootfs. Try plug it in the USB port right next to the Ethernet port in the back.

Also, what brand is this USB drive? some is not good for booting.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Recovery Help on Dockstar
October 24, 2016 09:16AM
Hi, Bodhi.

It's been a while, but I recreated the 4.4.0 rootfs and it boots to solid green, however it does not take an IP address. I had netconsole working before, and trying again it doesn't seem to work anymore, though I haven't changed the u-boot envs (intentionally, at least).

The booted unit does not take an IP address, but while booting, it does take the IP address set in the envs.

Any guidance on what I can do to recover this Dockstar?

Thanks!
Re: Recovery Help on Dockstar
October 24, 2016 12:55PM
jason,

> U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21
> -0800)
> Seagate FreeAgent DockStar
> 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... 2 USB Device(s)
> found
> scanning usb for storage devices... 0 Storage
> Device(s) found
> Unknown command 'ide' - try 'help'
> Unknown command 'mmc' - try 'help'
>
> no USB devices available
> Unknown command 'ide' - try 'help'
> Unknown command 'mmc' - try 'help'
> 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
> Unknown command 'ide' - try 'help'
> device ide 0:1
> ** Bad device ide 0 **
> device ide 1:1
> ** Bad device ide 1 **
> device ide 2:1
> ** Bad device ide 2 **
> device ide 3:1
> ** Bad device ide 3 **
> Scan device mmc
> Unknown command 'mmc' - try 'help'
> device mmc 0:1
> ** Bad device mmc 0 **
> device mmc 1:1
> ** Bad device mmc 1 **
> device mmc 2:1
> ** Bad device mmc 2 **
> device mmc 3:1
> ** Bad device mmc 3 **
> loading uImage ...
> ** Bad device usb 0 **
> loading uInitrd ...
> ** Bad device usb 0 **
> loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
> ** Bad device usb 0 **
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!

Try connecting netconsole again like you did above. To see how far you got.

In previous booting, your USB drive was not recognized at all:
scanning usb for storage devices... 0 Storage Device(s) found

So use a different USB drive (use Sandisk brand) and recreate the 4.4 rootfs. Pay attention to all the required steps in the rootfs thread. You must do exactly as stated in the instruction (dont try to replace any command with one you think should work). If you can't do that, post the questions.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Recovery Help on Dockstar
October 25, 2016 07:37PM
Here are the results from the netconsole output of a new rootfs 4.4. The device appear to boot (LED is solid green). However, the device only has an IP address while in uboot. After starting the kernel, the device does not connect to the network (confirmed by router connected device list).

U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21 -0800)
Seagate FreeAgent DockStar
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... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

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

Part    Start Sector    Num Sectors    UUID        Type
  1    2048          31352832      6dde1ad9-01    83
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 242 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3165294 bytes read in 379 ms (8 MiB/s)
loading uInitrd ...
7179935 bytes read in 470 ms (14.6 MiB/s)
loading DTB /boot/dts/kirkwood-dockstar.dtb ...
10398 bytes read in 290 ms (34.2 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-10-26   0:08:41 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3165230 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 ...

Thanks,
Jason
Re: Recovery Help on Dockstar
October 25, 2016 10:02PM
jason Wrote:
-------------------------------------------------------
> Here are the results from the netconsole output of
> a new rootfs 4.4. The device appear to boot (LED
> is solid green). However, the device only has an
> IP address while in uboot. After starting the
> kernel, the device does not connect to the network
> (confirmed by router connected device list).
>
>
> U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21
> -0800)
> Seagate FreeAgent DockStar
> 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... 3 USB Device(s)
> found
>        scanning usb for storage devices... 
> Use USB retry period from the environment: 15
> second(s)
> 1 Storage Device(s) found
> Unknown command 'ide' - try 'help'
> Unknown command 'mmc' - try 'help'
> 
> Partition Map for USB device 0  --   Partition
> Type: DOS
> 
> Part    Start Sector    Num Sectors    UUID       
> Type
>   1    2048          31352832      6dde1ad9-01   
> 83
> loading envs from usb 0 ...
> ** File not found /boot/uEnv.txt **
> Unknown command 'ide' - try 'help'
> Unknown command 'mmc' - try 'help'
> running scan_disk ...
> Scan device usb
> device usb 0:1
> 1 bytes read in 242 ms (0 Bytes/s)
> Found bootable drive on usb 0
> loading uImage ...
> 3165294 bytes read in 379 ms (8 MiB/s)
> loading uInitrd ...
> 7179935 bytes read in 470 ms (14.6 MiB/s)
> loading DTB /boot/dts/kirkwood-dockstar.dtb ...
> 10398 bytes read in 290 ms (34.2 KiB/s)
> ## Booting kernel from Legacy Image at 00800000
> ...
>    Image Name:   Linux-4.4.0-kirkwood-tld-1
>    Created:      2016-10-26   0:08:41 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    3165230 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 ...
> 
>
>
> Thanks,
> Jason

Ok, so it is better! But your roofs might have been created incorrectly.

On another box try to ping this box:

ping debian.local

If it is not online, post what you did to create the rootfs: which OS, USB drive brand, commands executed.... Post the log of the session.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
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: