Dockstar after debian boot not reachable

Hello,

after using Debian for quite a while i decided for a clean new install on an 8GB stick (Supertalent).
However, Debian does not work?!? Booting ends after an orange light with a weak green light, but it is not accessable.
I don't think it is an usb stick issue, since I installed archlinux successfully on it. I also got Debian running once, but after some configuration, it did not boot anymore. Also switching to an Trancend Jetflash, which works for my pogoplug did not help. Now, also my old 2GB stick, which I was using for years, does not start anymore?!? Same end, weak green light, no access.

I have configured netcat, this is what I get:

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... 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:        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)
1435408 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4529953 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1435344 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4529889 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

So far, it does look good, doesn't it?
Has anybody an idea, what is going wrong?
I would be very grateful!

Regards, Dieter

@Dieter,

If it does not boot, try the recommendation for a similar problem here (use another USB stick to do this):
http://forum.doozan.com/read.php?2,10912,10914#msg-10914

After you got it booting, while running in that rootfs, you can setup netconsole to see kernel messages for your kernel on your 1st USB stick, following this:
http://forum.doozan.com/read.php?2,9522

Hello,

thanks for your reply. I might have fixed my problem:
I am using a fritz.box router and I have configured it to alway assign the same ip to the according MAC adress and the name "dockstar".
If course, for a clean install, this did not fit (called debian), and therefore, I might ended up with this problems.

However, deleting the assignment in the fritz box completely works at the moment fine!

Regards, Dieter