Welcome! Log In Create A New Profile

Advanced

Uboot 2017 - Goflex home won't boot

Posted by as247 
Uboot 2017 - Goflex home won't boot
September 27, 2018 08:55PM
Hello,
I have goflex home and a running lastest version of archlinuxarm here http://os.archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz
But after i installed your uboot - https://forum.doozan.com/read.php?3,12381 it not able to boot to ALARM again.

I also tried to create uInitrd
Quote

cd /media/sdb1/boot
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-linux.img-2018-04-arch -d initramfs-linux.img uInitrd
sync
https://forum.doozan.com/read.php?3,56939,58944

I also tried with Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 but no lucks

Here are bot console logs
For ALARM
Quote

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700)
Seagate GoFlex Home
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
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: Colorful SL300 128GB Firm: R0522A0 Ser#: AA000000000000000467
Type: Hard Disk
Supports 48-bit addressing
Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

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

Part Start Sector Num Sectors UUID Type
1 2048 43511808 2014e27a-01 83
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

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: Colorful SL300 128GB Firm: R0522A0 Ser#: AA000000000000000467
Type: Hard Disk
Supports 48-bit addressing
Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
device ide 0:1
1 bytes read in 6 ms (0 Bytes/s)
Found bootable drive on ide 0
loading uImage ...
4600064 bytes read in 699 ms (6.3 MiB/s)
loading uInitrd ...
5290107 bytes read in 804 ms (6.3 MiB/s)
loading DTB /boot/dtbs/kirkwood-goflexnet.dtb ...
** File not found /boot/dtbs/kirkwood-goflexnet.dtb **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.4.97-1-ARCH
Created: 2017-11-11 4:51:55 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4600000 Bytes = 4.4 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-linux.img-2018-04-arch
Created: 2018-09-28 1:54:49 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5290043 Bytes = 5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK


Starting kernel ...


and for Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

Quote

gcc (Debian 6.3.0-18) 6.3.0 20170516

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700)
Seagate GoFlex Home
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: Colorful SL300 128GB Firm: R0522A0 Ser#: AA000000000000000467
Type: Hard Disk
Supports 48-bit addressing
Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

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

Part Start Sector Num Sectors UUID Type
1 2048 43511808 2014e27a-01 83
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

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: Colorful SL300 128GB Firm: R0522A0 Ser#: AA000000000000000467
Type: Hard Disk
Supports 48-bit addressing
Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
device ide 0:1
1 bytes read in 11 ms (0 Bytes/s)
Found bootable drive on ide 0
loading uImage ...
3821592 bytes read in 585 ms (6.2 MiB/s)
loading uInitrd ...
7245696 bytes read in 1098 ms (6.3 MiB/s)
loading DTB /boot/dtbs/kirkwood-goflexnet.dtb ...
** File not found /boot/dtbs/kirkwood-goflexnet.dtb **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.12.1-kirkwood-tld-1
Created: 2017-07-20 8:11:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3821528 Bytes = 3.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.12.1-kirkwood-tld-1
Created: 2017-07-24 0:18:23 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7245632 Bytes = 6.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK


Starting kernel ...


For ALARM the status LED is stay GREEN at final
For Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 status LED stay orange at final

No IP, no SSH up after Starting kernel...

Please help me to boot into my device again, thank you!
Attachments:
open | download - new_env.txt (2.8 KB)
open | download - old_env.txt (1.6 KB)
Re: Uboot 2017 - Goflex home won't boot
September 27, 2018 10:24PM
as247,

You've set this env to the wrong path for the Debian rootfs:

Quote

dtb_file=/boot/dtbs/kirkwood-goflexnet.dtb

With the Debian rootfs attached. Power up, Interrupt netconsole at countdown.

> Hit any key to stop autoboot:  0

And set it
setenv dtb_file '/boot/dts/kirkwood-goflexhome.dtb'
And then boot
boot

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



Edited 1 time(s). Last edit at 09/27/2018 10:25PM by bodhi.
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 12:23AM
Thank bodhi, it works now.
I set dtb_file to /boot/dtbs/kirkwood-goflexnet.dtb because i want to boot to ALARM, so i kept that old env.

There is another question that, as you can see in above logs .uEnv.txt doesn't load from ide (ssd device)
Quote

loading envs from usb 0 ...
** Bad device usb 0 **
Anyway to tell u-boot to load .uEnv.txt from ide as well if usb is not plugged in?

Thank you so much!
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 12:41AM
as247,

> Anyway to tell u-boot to load .uEnv.txt from ide
> as well if usb is not plugged in?

Somebody has mentioned this is possibly a problem. I have not looked into that yet.

Could you search the forum? I can't find that recent conversation :) I need to record that potential issue in my note for the next u-boot release, if it is indeed a problem.

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



Edited 1 time(s). Last edit at 09/28/2018 12:42AM by bodhi.
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 01:39AM
bodhi,
It's hard to find, there are too many posts
But it should be an issue, it always show "scanning bus 0 for devices... 1 USB Device(s) found " either USB plugged in or not


regards,
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 02:39AM
> But it should be an issue, it always show
> "scanning bus 0 for devices... 1 USB Device(s)
> found
" either USB plugged in or not

Nope. That's the USB hub. It counts as a device. When you plug in a USB drive, it will report as another USB storage device.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 03:18AM
bodhi Wrote:
-------------------------------------------------------
> Nope. That's the USB hub. It counts as a device.
> When you plug in a USB drive, it will report as
> another USB storage device.

But i have no usb hub plugged in, is that internal hub? I have only ssd disk on sata port, nothing else


regards,
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 03:22AM
> hub? I have only ssd disk on sata port, nothing
> else
>
>

There is an internal USB hub.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 09:29AM
Oh I see, does that mean IDE/Sata port is divided from usb 2.0 hub? My SSD is speed limited around 50MB/s seem it matches USB 2.0 max speed :(
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 01:39PM
as247 Wrote:
-------------------------------------------------------
> Oh I see, does that mean IDE/Sata port is divided
> from usb 2.0 hub? My SSD is speed limited around
> 50MB/s seem it matches USB 2.0 max speed :(

No, they are on separate bus.

Please post output of:
dmesg
mount

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 07:38PM
Hi bodhi, pls find in attached files for full dmesg and mount result
mount
Quote

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=54488k,nr_inodes=13622,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=11756k,mode=755)
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=23500k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
dmesg

Quote

[ 7.748571] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 7.964675] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 7.986915] ata1.00: ATA-9: Colorful SL300 128GB, R0522A0, max UDMA/133
[ 7.993568] ata1.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 31/32)
[ 8.046976] ata1.00: configured for UDMA/133
[ 8.065011] scsi 0:0:0:0: Direct-Access ATA Colorful SL300 1 2A0 PQ: 0 ANSI: 5
[ 8.085937] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[ 8.093877] sd 0:0:0:0: [sda] Write Protect is off
[ 8.104689] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 8.104828] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8.126316] sda: sda1
[ 8.135471] sd 0:0:0:0: [sda] Attached SCSI disk
[ 8.918734] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:2e:42:9c
[ 8.927645] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 8.934218] ehci-pci: EHCI PCI platform driver
[ 8.938773] ehci-orion: EHCI orion driver
[ 8.943003] orion-ehci f1050000.ehci: EHCI Host Controller
[ 8.948578] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 8.956456] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 8.984682] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 8.990957] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 8.997812] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 9.005094] usb usb1: Product: EHCI Host Controller
[ 9.009996] usb usb1: Manufacturer: Linux 4.12.1-kirkwood-tld-1 ehci_hcd
[ 9.016748] usb usb1: SerialNumber: f1050000.ehci
[ 9.022186] hub 1-0:1.0: USB hub found
[ 9.026047] hub 1-0:1.0: 1 port detected
[ 9.030578] usbcore: registered new interface driver usb-storage
[ 9.036995] mousedev: PS/2 mouse device common for all mice
[ 9.043158] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 9.050257] i2c /dev entries driver
Attachments:
open | download - dmesg.txt (12.4 KB)
open | download - mount.txt (727 bytes)
Re: Uboot 2017 - Goflex home won't boot
September 28, 2018 08:16PM
as247,

It looks normal to me. So I am not sure about your SSD speed problem. I have an old SATA HHD (Seagate) and my dd write speed test is about 48MB/s.

[    8.077630] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    8.099876] ata1.00: ATA-8: ST2000DL003-9VT166, CC98, max UDMA/133
[    8.106088] ata1.00: 3907029168 sectors, multi 0: LBA48


Re loading uEnv.txt from IDE, I will look into this to see if it is a real problem before the next u-boot release. This is an separate u-boot issue, not related to the SSD or HDD.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Uboot 2017 - Goflex home won't boot
October 03, 2018 08:17AM
Thank you so much Bodhi, I will wait for next U-boot release. And I hope that you can make it boot from first partition without need to set label "rootfs"
Re: Uboot 2017 - Goflex home won't boot
October 03, 2018 01:45PM
as247,

> Thank you so much Bodhi, I will wait for next
> U-boot release. And I hope that you can make it
> boot from first partition without need to set
> label "rootfs"

See the expanation why rootfs label is needed (It is quite easy to set up booting wihtout label rootfs if you choose to do so, but you should not):

https://forum.doozan.com/read.php?3,19093

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Uboot 2017 - Goflex home won't boot
October 03, 2018 09:49PM
Ah, I understood now.
Kernel load is a difference process, it uses boot args for initial and it does't know about OS root location itself, must be set from boot args
By this way we also can separate kernel and rootfs into 2 difference partitions

So boot loader will find kernel and tell kernel how to boot.

There is no standard for kernel name and kernel args, so it's hard to make u-boot to boot any compatible os. uEnv.txt is trying to help that out by customize boot process, unfortunately it's not working with sata now (at least with me)

When i check my old env, i also found why it cannot boot into ALARM
Quote

root=/dev/sd${letter}1 rw rootwait ${mtdparts}
seem ALARM kernel doesn't understand root LABEL, and we must set it using device eg: /dev/sda1

And for Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 I think it can be work fine with multiple partitions as above process. I can have 20GB partition for system and the rest for DATA.
Your guide for Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 confused me that we must have single partition. For USB it's fine, but for 1-3TB disk single partition doesn't make sense
Re: Uboot 2017 - Goflex home won't boot
October 03, 2018 10:14PM
as247,

> Ah, I understood now.
> Kernel load is a difference process, it uses boot
> args for initial and it does't know about OS root
> location itself, must be set from boot args
> By this way we also can separate kernel and rootfs
> into 2 difference partitions
>
> So boot loader will find kernel and tell kernel
> how to boot.

You've got it!

>
> There is no standard for kernel name and kernel
> args, so it's hard to make u-boot to boot any
> compatible os. uEnv.txt is trying to help that out
> by customize boot process, unfortunately it's not
> working with sata now (at least with me)
>
> When i check my old env, i also found why it
> cannot boot into ALARM
>
Quote

root=/dev/sd${letter}1 rw rootwait
> ${mtdparts}
> seem ALARM kernel doesn't understand root LABEL,
> and we must set it using device eg: /dev/sda1
>

ALARM does not use initramfs (i.e. uInitrd) as a default. So you would need to do an extra step with ALARM to create that kernel file. After that, rootfs label will work.

> And for
> Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> I think it can be work fine with multiple
> partitions as above process. I can have 20GB
> partition for system and the rest for DATA.
> Your guide for
> Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> confused me that we must have single partition.
> For USB it's fine, but for 1-3TB disk single
> partition doesn't make sense

Again, you've got the exact reason why I wrote the instruction to require a single Ext3 partition. This will ensure you can boot with any u-boot version since 2009. And then when your configuration is more complicate, you would tailor it to use multiple partitions.

The requirement is your /boot must be on 1st partition, and that partition must be Ext2/Ext3 type. And your rootfs partition must be labeled rootfs. However, because the assumption is that most users are not familiar with embedded Linux, so the instruction is made to be as simple as possible. Any deviation from that instruction, users must know what he/she doing.

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



Edited 1 time(s). Last edit at 10/03/2018 10:16PM by bodhi.
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: