Welcome! Log In Create A New Profile

Advanced

Problem to Connect to Dockstar

Posted by jerry 
jerry
Problem to Connect to Dockstar
May 17, 2020 07:07PM
Hello,

I have a Dockstar and I have used it for 7 years, the current OS is Debian8 (thx for your great job)

Now, I tried to upgrade my system. So I installed on other USB-Stick Debian10.
The problem is, that I can't connect to Dockstar via SSH. Ping doesn't answer me too.
When I start the new system, so I get this messages:


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:        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)
4963680 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
9713936 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4963616 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

What can I do? Is it possible to get more messages (change the Debugg-Level)?

Thanks
your sincerely
Jerry
Re: Problem to Connect to Dockstar
May 17, 2020 08:21PM
Hi,

Your uboot is very old, looks original / stock to me. While you can probably get it to work upgrading the uboot will make it much easier to run newer rootfs and kernel.

Check out; 2017 Uboot for Kirkwood

Oh, and if you'd like tips on getting it booting, I'd suggest checking that the dts was correctly appended to the kernel as stock uboots require.



Edited 1 time(s). Last edit at 05/17/2020 08:25PM by jdwl101.
Re: Problem to Connect to Dockstar
May 17, 2020 09:33PM
Jerry ,

Make sure that you do Step 4b. Even though U-Boot 2011.12 is not stock u-boot, it is old, and does not support booting with separate DTB.


4b. Boot with DTB file embedded in the kernel image (no U-Boot envs changes are needed if your system already booting on USB or HDD). Again, this step 4b is for stock U-Boot only. 

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box. 

Generate the uImage and uInitrd (the kernel files vmlinuz-5.6.5-kirkwood-tld-1 and initrd.img-5.6.5-kirkwood-tld-1 were generated by dpkg in Step 3): 
cd /boot
mv uImage uImage.orig
mv uInitrd uInitrd.orig
cp -a zImage-5.6.5-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-goflexnet.dtb  >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n 5.6.5-kirkwood-tld-1 -d zImage.fdt  uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.6.5-kirkwood-tld-1 -d initrd.img-5.6.5-kirkwood-tld-1 uInitrd

And use the Dockstar DTB in the above Step 4b:

cat dts/kirkwood-dockstar.dtb  >> zImage.fdt

With netconsole, this is all you'll get with the boot log.

Starting kernel ...

Chance is that it already booted. Check if there is a new IP in your network, or ping the host name of this rootfs:

ping debian.local

-bodhi
===========================
Forum Wiki
bodhi's corner
Jerry
Re: Problem to Connect to Dockstar
May 19, 2020 03:28PM
Hello,

jdwl101, I used this script to install the new uBoot:

http://projects.doozan.com/uboot/

I will try your version.

by
Jerry
Jerry
Re: Problem to Connect to Dockstar
May 19, 2020 03:42PM
bodhi Wrote:
-------------------------------------------------------

> Chance is that it already booted. Check if there
> is a new IP in your network, or ping the host name
> of this rootfs:
>
>
> ping debian.local
>

Hello bodhi,

I try it. There is no new IP-address and the ping of debian.local is not successful.

I already tried your hint with 4b. But I will try it again. If not successful, so I will try to update my uBoot.

Thx
Jerry
jerry
Re: Problem to Connect to Dockstar
May 19, 2020 06:24PM
Hello,

I tried the way of bodhi, but it wasn't successful.
So I begun with the installation of new current version of uBoot.
In point 4 I found this line:

Quote
4. Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M (8 blocks), don't flash u-boot, because you will almost certainly brick your box. Please post your question here (there is a work around for it).

When I run this, I receive this message:

Pogoplug:/tmp$ dmesg | grep -i 'bad'
[    1.050000] Scanning device for bad blocks
[    1.060000] Bad eraseblock 108 at 0x00d80000

You write:

Quote
This bad block is the 4th block which resides within mtd0 (block 0 to block 7). So u-boot should not be flashed.

What can I do?

bye
jerry
jerry
Re: Problem to Connect to Dockstar
May 19, 2020 07:11PM
OK. I did it :-)

Now the system boote from USB-Stick and I connect to it with SSH.
But I receive this messages:

U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700)
Seagate FreeAgent DockStar
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
Initializing devices...
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'
Loading envs from usb 0...
** File not found /boot/uEnv.txt **
Loading envs from usb 1...
** Bad device usb 1 **
Loading envs from usb 2...
** Bad device usb 2 **
Loading envs from usb 3...
** Bad device usb 3 **
Loading envs from ide 0...
** Bad device ide 0 **
Loading envs from ide 1...
** Bad device ide 1 **
Loading envs from ide 2...
** Bad device ide 2 **
Loading envs from ide 3...
** Bad device ide 3 **
Loading envs from mmc 0...
** Bad device mmc 0 **
Loading envs from mmc 1...
** Bad device mmc 1 **
Loading envs from mmc 2...
** Bad device mmc 2 **
Loading envs from mmc 3...
** Bad device mmc 3 **
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 508 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
4973738 bytes read in 1002 ms (4.7 MiB/s)
loading uInitrd ...
9713936 bytes read in 1330 ms (7 MiB/s)
loading DTB ...
** No boot file defined **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-05-19  21:46:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973674 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2020-05-19  21:49:34 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

Is it OK?
Re: Problem to Connect to Dockstar
May 19, 2020 08:46PM
jerry Wrote:
-------------------------------------------------------
> OK. I did it :-)
>
> Now the system boote from USB-Stick and I connect
> to it with SSH.
> But I receive this messages:
>
>
> U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36
> -0700)
> Seagate FreeAgent DockStar
> gcc (Debian 6.3.0-18) 6.3.0 20170516
> GNU ld (GNU Binutils for Debian) 2.28
> Hit any key to stop autoboot:  0 
> Initializing devices...
> 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'
> Loading envs from usb 0...
> ** File not found /boot/uEnv.txt **
> Loading envs from usb 1...
> ** Bad device usb 1 **
> Loading envs from usb 2...
> ** Bad device usb 2 **
> Loading envs from usb 3...
> ** Bad device usb 3 **
> Loading envs from ide 0...
> ** Bad device ide 0 **
> Loading envs from ide 1...
> ** Bad device ide 1 **
> Loading envs from ide 2...
> ** Bad device ide 2 **
> Loading envs from ide 3...
> ** Bad device ide 3 **
> Loading envs from mmc 0...
> ** Bad device mmc 0 **
> Loading envs from mmc 1...
> ** Bad device mmc 1 **
> Loading envs from mmc 2...
> ** Bad device mmc 2 **
> Loading envs from mmc 3...
> ** Bad device mmc 3 **
> running scan_disk ...
> Scan device usb
> device usb 0:1
> 1 bytes read in 508 ms (0 Bytes/s)
> Found bootable drive on usb 0
> loading uImage ...
> 4973738 bytes read in 1002 ms (4.7 MiB/s)
> loading uInitrd ...
> 9713936 bytes read in 1330 ms (7 MiB/s)
> loading DTB ...
> ** No boot file defined **
> ## Booting kernel from Legacy Image at 00800000
> ...
>    Image Name:   Linux-5.2.9-kirkwood-tld-1
>    Created:      2020-05-19  21:46:59 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    4973674 Bytes = 4.7 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
>    Image Name:   initramfs-5.2.9-kirkwood-tld-1
>    Created:      2020-05-19  21:49:34 UTC
>    Image Type:   ARM Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    9713872 Bytes = 9.3 MiB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
> 
> 
> Starting kernel ...
>
>
> Is it OK?

It is OK. It already booted. Try SSH in.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

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: