Dockstar U-boot problem

I have a dockstar with debian which have been working for 3 years without problem. But now, every time I tried to reboot it, it just hangs there, it can not fall-back to original system either. I tried many different flash drives, they all behave the same (those drives work fine on another dockstar). I also tried updating the U-Boot, but still the same. The message below is from the netconsole, which shows after "starting kernel", there is no more progress. Could anybody help me to find out what is wrong? Thanks a lot.


U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
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... 2 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: 1751
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: 1730
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)
2676840 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-2.6.35.7-dockstar
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2676776 Bytes = 2.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

davidnewton Wrote:
-------------------------------------------------------
> I have a dockstar with debian which have been
> working for 3 years without problem. But now,
> every time I tried to reboot it, it just hangs
> there, it can not fall-back to original system
> either. I tried many different flash drives, they
> all behave the same (those drives work fine on
> another dockstar). I also tried updating the
> U-Boot, but still the same. The message below is
> from the netconsole, which shows after "starting
> kernel", there is no more progress. Could anybody
> help me to find out what is wrong? Thanks a lot.
>
>
> U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
> Seagate FreeAgent DockStar
> arm-none-linux-gnueabi-gcc (Sourcery G++ Lite
> 2009q3-67) 4.4.1
> GNU ld (Sourcery G++ Lite 2009q3-67)
> 2.19.51.20090709
> 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... 2
> 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: 1751
> 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: 1730
> 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)
> 2676840 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-2.6.35.7-dockstar
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 2676776 Bytes = 2.6 MiB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
>
> Starting kernel ...

You're lost your /boot/uInitrd. Check the drive if it's not there, copy it (as root user) from the other dockstar.

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

bodhi Wrote:

>
> You're lost your /boot/uInitrd. Check the drive if
> it's not there, copy it (as root user) from the
> other dockstar.


Thanks a lot for your reply. I don't know if this file should be on the flash drive or on the nand. I checked the drive working fine on another dockstar, they have the same files as below, which does not have /boot/uInitrd file.

root@debian:/boot# ls -l
total 14188
-rw-r--r-- 1 root root 1006188 Feb 16 07:33 System.map-2.6.32-5-kirkwood
-rw-r--r-- 1 root root 84134 Feb 16 07:33 config-2.6.32-5-kirkwood
-rw-r--r-- 1 root root 4535899 Jun 13 10:30 initrd.img-2.6.32-5-kirkwood
-rw-r--r-- 1 root root 4738236 Feb 17 2011 org.uInitrd
-rw-r--r-- 1 root root 2676840 Oct 18 2010 uImage
-rw-r--r-- 1 root root 1437136 Feb 16 07:32 vmlinuz-2.6.32-5-kirkwood

davidnewton Wrote:
-------------------------------------------------------
> -rw-r--r-- 1 root root 4535899 Jun 13 10:30
> initrd.img-2.6.32-5-kirkwood
> -rw-r--r-- 1 root root 4738236 Feb 17 2011
> org.uInitrd
There appears to be two different uinitrd files. You could try using a symbolic link to boot the uInitrd

ln -s boot/uinitrd.img-2.6.32-5-kirkwood boot/uInitrd

or

ln -s boot/org.uInitrd boot/uInitrd

laprjns Wrote:
-------------------------------------------------------

> There appears to be two different uinitrd files.
> You could try using a symbolic link to boot the
> uInitrd
>
> ln -s boot/uinitrd.img-2.6.32-5-kirkwood
> boot/uInitrd
>
> or
>
> ln -s boot/org.uInitrd boot/uInitrd

I tried to do this link, but the result is the same.

I have a goflex net and I have the same problem!
It worked perfectly for first two weeks then it stopped working. Tried also with arch linux image.
Can we join forces?

Thanks,
Mario

Gents,

Did you guys try to upgrade your rootfs to wheezy when this happened? If you can recall the event or have a log, it would be easier to figure out what went wrong.

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

Here is my sequence:

- installed NSA320 boot image on usb
- updated
- installed iscsi initiator for a test
- all ok for one week
- added 1tb 2.5 external hdd
- modified it to 3049 (not remember exact number) to let it see the hdd
- all ok for two days
- come back home ssh/ping the unit no reply at all
- rebooted the unit no reply
- debugged with nc stops at kernel booting (but in another thread people tell me that is it normal that nc output stops here)
- changed usb key with another one with arch linux just installed: no improvement
- steady green light after boot (not orange)

mgiammarco Wrote:
-------------------------------------------------------
> Here is my sequence:
>
> - installed NSA320 boot image on usb
> - updated
> - installed iscsi initiator for a test
> - all ok for one week
> - added 1tb 2.5 external hdd
> - modified it to 3049 (not remember exact number)
> to let it see the hdd

I assumed you've rebooted after changing arcNumber to 3089 ?

> - all ok for two days
> - come back home ssh/ping the unit no reply at
> all

Was there power outage?

> - rebooted the unit no reply
> - debugged with nc stops at kernel booting (but in
> another thread people tell me that is it normal
> that nc output stops here)

Also it would be informative to stop netconsole countdonw and print out the envs with
printenv


> - changed usb key with another one with arch linux
> just installed: no improvement
> - steady green light after boot (not orange)

Did you check Debian rootfs with e2fsck on another box?

How about mount the rootfs on another box and get the output of (assuming it's mounted at /media/sdb1)
ls -l /media/sdb1/boot
Was there any kernel file missing in /media/sdb1/boot ?

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



Edited 1 time(s). Last edit at 07/10/2013 03:59AM by bodhi.

bodhi Wrote:

>
> I assumed you've rebooted after changing arcNumber
> to 3089 ?
>
Yes I rebooted and I was happy to see that it recognized my hdd

> > - all ok for two days
> > - come back home ssh/ping the unit no reply at
> > all
>
> Was there power outage?

Unfortunately no power outage, no reasons to crash.

>
> Also it would be informative to stop netconsole
> countdonw and print out the envs with
> printenv
>
I try to do this now
>

>
> Did you check Debian rootfs with e2fsck on another
> box?
>
Sure I have checked it and then, just to be sure, I have tried with another memory key with another linux distro (arch linux)

> How about mount the rootfs on another box and get
> the output of (assuming it's mounted at
> /media/sdb1)
> ls -l /media/sdb1/boot
> Was there any kernel file missing in
> /media/sdb1/boot ?
drwxr-xr-x 2 root root 4096 giu 13 15:04 3.3.2
-rw-r--r-- 1 root root 107468 apr 24 2012 config-3.3.2-kirkwood-dg
-rw-r--r-- 1 root root 104239 giu 10 11:08 config-3.8.11-kirkwood-tld-2
-rw-r--r-- 1 root root 7004474 apr 25 2012 initrd.img-3.3.2-kirkwood-dg
-rw-r--r-- 1 root root 6283455 giu 29 20:40 initrd.img-3.8.11-kirkwood-tld-2
-rw-r--r-- 1 root root 6283455 giu 29 20:32 initrd.img-3.8.11-kirkwood-tld-2.dpkg-bak
-rw-r--r-- 1 root root 1220456 apr 24 2012 System.map-3.3.2-kirkwood-dg
-rw-r--r-- 1 root root 1279507 giu 10 15:35 System.map-3.8.11-kirkwood-tld-2
-rw-r--r-- 1 root root 2279256 apr 25 2012 uImage
-rw-r--r-- 1 root root 7004538 apr 25 2012 uInitrd
-rw-r--r-- 1 root root 6610550 apr 24 2012 vmlinux-3.3.2-kirkwood-dg
-rw-r--r-- 1 root root 2279192 apr 24 2012 vmlinuz-3.3.2-kirkwood-dg
-rw-r--r-- 1 root root 1805632 giu 10 15:35 vmlinuz-3.8.11-kirkwood-tld-2

David, have you solved the problem?
Can anyone help?
It is incredible that I have bricked a GOFLEX without doing anything.
Why is the green light always on after boot? What does it mean?

Thanks,
Mario

mgiammarco Wrote:
-------------------------------------------------------
> David, have you solved the problem?
> Can anyone help?
> It is incredible that I have bricked a GOFLEX
> without doing anything.
> Why is the green light always on after boot? What
> does it mean?
>
> Thanks,
> Mario

Mario,

The green light means that uBoot has successfully booted, it's done its part. The kernel is loading. It is a good sign, your GoFlex Home is not bricked :) now for some reason, the kernel is not booting.

Mount the stick on another Linux box, and get the output of
ls -lart /boot
ls -l /lib/modules
ls -lart /

Stop netconsole, and get output of
- the netconsole log
- printenv

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



Edited 1 time(s). Last edit at 07/19/2013 03:42PM by bodhi.

bodhi Wrote:
-> :) now for some reason, the kernel is not booting.
Are we sure that the kernel is not booting? Maybe it's not getting an IP. I suggest that they try deleting any persistent net rule in /etc/udev/rules.d/

laprjns Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -> :) now for some reason, the kernel is not
> booting.
> Are we sure that the kernel is not booting?
> Maybe it's not getting an IP. I suggest that they
> try deleting any persistent net rule in
> /etc/udev/rules.d/

Yeah, it could be the problem. Hard to tell what's going on without netconsole output.

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

Thank for all replies.
I have bought some usb keys, tried with several linux flavours and now, incredibly an arch linux has booted.

Now I will never power it down but meanwhile:

1) How can I enable netconsole for all boot duration (and also after boot if possible)?
2) How can I install a boot recovery in its mtd/flash device (it was first thing I tried after unlocking, but tutorial I have found was wrong and so I have not found the right tutorial)
3) Which is the right tutorial to let it reboot correctly even if there is a sata hdd connected?

Thanks a lot for help!

Mario

mgiammarco Wrote:
-------------------------------------------------------
> Thank for all replies.
> I have bought some usb keys, tried with several
> linux flavours and now, incredibly an arch linux
> has booted.
>
> Now I will never power it down but meanwhile:
>
> 1) How can I enable netconsole for all boot
> duration (and also after boot if possible)?
> 2) How can I install a boot recovery in its
> mtd/flash device (it was first thing I tried after
> unlocking, but tutorial I have found was wrong and
> so I have not found the right tutorial)
> 3) Which is the right tutorial to let it reboot
> correctly even if there is a sata hdd connected?
>
> Thanks a lot for help!
>
> Mario

1. See this thread:
http://forum.doozan.com/read.php?3,14

3. See this post:
http://forum.doozan.com/read.php?3,8044,8152#msg-8152

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

Thank you for your prompt reply!

bodhi Wrote:

>
> 1. See this thread:
> http://forum.doozan.com/read.php?3,14
>


> 3. See this post:
> http://forum.doozan.com/read.php?3,8044,8152#msg-8
> 152


I have tried the instructions in this post (fw_setenv....) but now again it does not boot. It boots the kernel but I do not know if it finds the root filesystem.
What can I do?
With netconsole at boot I am able to stop autoboot but then I cannot give any input.

Thanks again,
Mario

Mario,

When you execute these commands,

nc -l -u -p 6666 &
nc -u 192.168.1.100 6666

change the 2nd one to

nc -up 6666 192.168.1.100 6666

Of course, replace 192.168.1.100 with th IP address of your plug (Dockstar or GoFlex,...)

Use the label approach described above for your boot drive, does not matter USB or HDD. If the USB boot drive is labeled rootfs, then the uBoot envs will tell uBoot to find your rootfs always, regardless of whether the HDD is attached or not.

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

bodhi Wrote:
-------------------------------------------------------
> Mario,
>
> When you execute these commands,
>

> nc -l -u -p 6666 &
> nc -u 192.168.1.100 6666
>

>
> change the 2nd one to
>

> nc -up 6666 192.168.1.100 6666
>

>
> Of course, replace 192.168.1.100 with th IP
> address of your plug (Dockstar or GoFlex,...)

Are you sure? If I do:
nc -l -u -p 6666 &
nc -up 6666 10.1.0.10 6666
I get this:
nc: bind failed: Address already in use


Thanks again!
Mario

Sorry, I was using netcat bsd, now I tried again with nc "traditional" and, for the first time, I can print my env, is it correct?:

arcNumber=3089
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:26:6E:ED
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
if_netconsole=ping $serverip
ipaddr=10.1.0.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
ncip=10.1.0.162
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
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_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=10.1.0.162
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
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=usb start; setenv usb_root LABEL=rootfs
usb_root=/dev/sda1
usb_rootdelay=10
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

Looks good to me! so if you still have problem booting with your installed USB stick, then try this rootfs first to make sure you can boot into Debian.
http://forum.doozan.com/read.php?2,12096

And then mount your stick to examine it.

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