Welcome! Log In Create A New Profile

Advanced

Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB

Posted by cpe 
cpe
Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 01, 2013 04:16PM
Hi all,

I have dockstars which in some point in time didn't get back up again.
Using a Nokia USB-cable with some test hooks, tftp'ed mtd0, 1, 2 and installed rescue from USB stick.
Unfortunately, they don't boot the USB stick which installed without error messages (wheezy-script)

I attached my environment.
uname -a
Linux pogo02-rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux

Please help me making the devices work again.

#update#
######start boot-log ########

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
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-0x000010000000 : "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: 219 MiB
UBI: number of good PEBs: 1752
UBI: number of bad PEBs: 0
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: 1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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)
1606576 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6883383 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: kernel 3.2.0-4-kirkwood
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1606512 Bytes = 1.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: ramdisk 3.2.0-4-kirkwood
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6883319 Bytes = 6.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

######## end bootlog ###########

Thanks in advance and greetings
CP



Edited 1 time(s). Last edit at 05/02/2013 11:36AM by cpe.
Attachments:
open | download - pogo02-env-20130428.txt (2.9 KB)
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 02, 2013 12:03AM
Do you have a boot log? that would be much easier to tell than just looking at the envs.
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 02, 2013 11:37AM
thanks for supporting.
thought the Environment would be the biggest Thing.
just added the boot log.

thanks and greets
CP
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 12:11AM
That is strange. Your rescue kernel is showing pogo e02, and you installed this on a Dockstar.

Linux pogo02-rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux

How did you install the rescue 2.8.2?

Perhaps Davygravy can comment on this. Does the hostname always show pogo02-rescue?
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 12:48AM
Hi
Installed it from USB Stick which I installier from the Image.
changing the Hostname is no rocket Science.
Changing the fs TP readwrite neither.
IfM this should be the issue it would be easiest but I cannot believe it.

Tranks ans greets from Germany
Cp
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 01:37AM
Ok. I don't know why your rescue rootfs says Pogo E02.

Any how your best bet would be using Davy's NSA320 rootfs, so download that and put it on a USB stick and boot with it:
http://forum.doozan.com/read.php?2,7806
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 03:04AM
Hi,
does this fit also for the Seagate Dockstar?
It says it runs with zyXel ... in this article.

Thanks
CP
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 03:11AM
It will boot your Dockstar OK. Since you have arcNumber set to 2097, it should boot (2097 is the reference board arcNumber, not a Dockstar). Once you're booted OK, then worry about arcNumber.
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 04:21AM
Hi,

tried it like this (see http://forum.doozan.com/read.php?4,3896,3896) but with the img out of your tarball (http://dl.dropbox.com/u/1015928/Kirkwood/rootfs_images/NSA320quickstart.tar.gz):

rescue:/ttt# flash_eraseall /dev/mtd2
Erasing 128 Kibyte @ 2000000 -- 100 % complete.
rescue:/ttt# ubiformat /dev/mtd2 -s 512 -f kirkwood-debian_rootfs.img -y
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: error!: file "kirkwood-debian_rootfs.img" is too large (335544320 bytes)
error 0 (Success)

so I had to bring the original rescue back in place (which surely will bring back the "recue" hostname and nothing like pogo02):

rescue:/ttt# ubiformat /dev/mtd2 -s 512 -f rootfs-mtd2.img -y
ubiformat: mtd2 (nand), size 33554432 bytes (32.0 MiB), 256 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 255 -- 100 % complete
ubiformat: 256 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 218 -- 100 % complete
ubiformat: formatting eraseblock 255 -- 100 % complete

rescue:~# uname -a
Linux rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux

Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
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-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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)
1606576 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6883383 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1606512 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   ramdisk 3.2.0-4-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6883319 Bytes = 6.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

without USB-stick:
U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

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

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


         Doozan Forum
Kirkwood/*Plug* Recovery System
     V2.8.2 : Oct 29 2012

rescue login:

greets
CP



Edited 3 time(s). Last edit at 05/03/2013 04:56AM by cpe.
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 03, 2013 11:01PM
CP,

The rootfs is for USB stick! put that on a USB stick and boot with USB.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 09, 2013 02:48AM
Hi Bodhi,
sorry this may Sound crazy but .. I can boot the rescue USB stick without any Problems. But NOT the wheezy or Lenny or whatever "usual" USB stick also the one made with this dockstar using the actual wheezy-install-script.
Will it help making another rescue System?

Sorry but ...
Greets
CP
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 09, 2013 11:44PM
CP,

Sorry, I don't know much about rescue system! I don't really use it at all, other than installing one on Pogo E02 long ago to try it out. But never booted back into it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 25, 2013 04:56AM
Hi Bodhi,
just booted from what you proposed.

88E1116 Initialized on egiga0
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... EHCI timed out on TD - token=0x80008c80
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-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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)
2279256 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7004538 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2279192 Bytes = 2.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.3.2-kirkwood-dg
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7004474 Bytes = 6.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

and that's it

shit



Edited 1 time(s). Last edit at 05/25/2013 01:31PM by cpe.
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 25, 2013 05:10AM
Hi

the HOSTNAME that I gave the device was pogo02
I don't see anything that the device would be a pogo E 02 but I am no specialist.

Hope you can help me getting the dockstar back to work.

booting the rescue (in NAND):
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


         Doozan Forum
Kirkwood/*Plug* Recovery System
     V2.8.2 : Oct 29 2012

rescue login:

the environment:
rescue:~# fw_printenv
arcNumber=2097
baudrate=115200
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=18
cesvcid=YZM3SBMTWU5WFEXCD2MYLJY84W
console=console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:1A:CA:44
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ipaddr=172.16.1.28
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtddevname=rootfs
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=172.16.1.35
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=/dev/sda1
usb_rootdelay=20
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
bootcmd_usb=run set_bootargs_usb; run usb_init; ext2load usb $usb_device 0x800000 /boot/uImage; ext2load usb $usb_device 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000
hostname=dockstar02
rescue:~#



Thanks and greetings
CP



Edited 1 time(s). Last edit at 05/25/2013 01:36PM by cpe.
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 04:40AM
Since so your situation is you can log in to the rescue system, and you have problem with Davy NSA320 rootfs, you should rerun the installation to install Debian Squeeze , and then upgrade to Wheezy.

- Log in to the rescue system.
- Use an empty USB thumb drive (it will be erased during installation).
- Follow the installation instruction: http://projects.doozan.com/debian (use this script http://projects.doozan.com/debian/dockstar.debian-squeeze.sh)
- Don't change arcNumber, keep it as 2097
- After you got it booting into Squeeze, upgrade it to Wheezy.

Make sure to get it working first, and then to control the LED properly, you will need to upgrade to a kernel that can support Pogo E02 arcNumber:
http://forum.doozan.com/read.php?2,12096

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 06:21AM
hi ..
after some minor issues (perl, ...) I managed to get squeeze on the stick
but still it does not boot:
88E1116 Initialized on egiga0
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-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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)
1437200 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4536056 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel 2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1437136 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   Debian ramdisk 2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4535992 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 08:47AM
1. What is your envs looks like? from serial console uBoot prompt:
printenv

2. Mount the Squeeze USB on another Linux box, and run (assuming the USB drive is mounted as /media/sda1)
ls -l /media/sda1/boot/

What is the output of this ls -l command? do you see uImage and uInitrd ? if not, you will need to boot back to rescue system and generate them. If you've saved the installation log, we can verify that whether they were generated or not.
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 08:54AM
env:
rescue:~# fw_printenv
arcNumber=2097
baudrate=115200
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=18
cesvcid=YZM3SBMTWU5WFEXCD2MYLJY84W
console=console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:1A:CA:44
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ipaddr=172.16.1.28
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtddevname=rootfs
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=172.16.1.35
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=/dev/sda1
usb_rootdelay=20
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
bootcmd_usb=run set_bootargs_usb; run usb_init; ext2load usb $usb_device 0x800000 /boot/uImage; ext2load usb $usb_device 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000
hostname=dockstar02

cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 08:58AM
mounted under /mnt

both are there

root@sheeva01:/mnt# ls -la boot/
total 12788
drwxr-xr-x  2 root root    4096 May 26 13:05 .
drwxr-xr-x 21 root root    4096 May 26 13:05 ..
-rw-r--r--  1 root root 1006188 Feb 16 14:33 System.map-2.6.32-5-kirkwood
-rw-r--r--  1 root root   84134 Feb 16 14:33 config-2.6.32-5-kirkwood
-rw-r--r--  1 root root 4535992 May 26 13:05 initrd.img-2.6.32-5-kirkwood
-rw-r--r--  1 root root 1437200 May 26 13:05 uImage
-rw-r--r--  1 root root 4536056 May 26 13:05 uInitrd
-rw-r--r--  1 root root 1437136 Feb 16 14:32 vmlinuz-2.6.32-5-kirkwood

Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 09:14AM
Every thing looks normal. Another possible reason could be the USB brand, what brand the stick is? and can you try the intallation on another stick?
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 09:16AM
hi Bodhi,
the dockstar ran without Problems until i upgraded to wheezy
then I also upgraded uBoot etc.
and also the sticks that ran don't do it any more.
So USB stick is unlikely as reason :(

But I try it
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 09:47AM
Quite a few people has problem with the rescue systems lately. I'm not sure why. I don't use it because I don't have a need for it, so I can't really have a good feel for the problem.

If you can't make it work then I would suggest abandoning it for now. Just rerun the complete installation, and force a uBoot update and uBoot envs reset so you can get back to a booting Squeeze system.
cpe
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 26, 2013 10:17AM
how will I get the "complete uBoot Environment which is running"

here the env and the /boot
root@sheeva01:~# screen /dev/ttyUSB0 115200
-rw-r--r--    1 root     root       1437136 Feb 16 13:32 vmlinuz-2.6.32-5-kirkwood
-rw-r--r--    1 root     root         84134 Feb 16 13:33 config-2.6.32-5-kirkwood
-rw-r--r--    1 root     root       1006188 Feb 16 13:33 System.map-2.6.32-5-kirkwood
-rw-r--r--    1 root     root       4535991 May 26 15:10 initrd.img-2.6.32-5-kirkwood
-rw-r--r--    1 root     root       1437200 May 26 15:10 uImage
-rw-r--r--    1 root     root       4536055 May 26 15:11 uInitrd
drwxr-xr-x    2 root     root          4096 May 26 15:11 .
drwxr-xr-x   21 root     root          4096 May 26 15:11 ..
rescue:/mnt/boot# fw_printenv
arcNumber=2097
baudrate=115200
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=18
cesvcid=YZM3SBMTWU5WFEXCD2MYLJY84W
console=console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:1A:CA:44
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ipaddr=172.16.1.28
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtddevname=rootfs
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=172.16.1.35
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=/dev/sda1
usb_rootdelay=20
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
bootcmd_usb=run set_bootargs_usb; run usb_init; ext2load usb $usb_device 0x800000 /boot/uImage; ext2load usb $usb_device 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000
hostname=dockstar02
rescue:/mnt/boot#

88E1116 Initialized on egiga0
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-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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)
1437200 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4536055 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel 2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1437136 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   Debian ramdisk 2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4535991 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


unfortunately didn't find any log files

also a second stick that worked for a year didn't boot .. just the same result:
88E1116 Initialized on egiga0
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-0x000010000000 : "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:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
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:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
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)
1437200 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4536254 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel 2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1437136 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   Debian ramdisk 2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4536190 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.



Edited 2 time(s). Last edit at 05/26/2013 01:23PM by cpe.
Re: Dockstar actual UBoot, Rescue 2.8.2 in NAND doesn't boot Debian from USB
May 30, 2013 10:31PM
@cpe,

I meant you can always rerun uBoot installation as described here:
http://projects.doozan.com/uboot/
When prompted for restore environment, say yes to get the envs reset to the normal Debian setup, and then try to boot with Debian Squeeze stick.

This way at least you can run Debian and worry about rescue system later.

-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: