Goflex upgrade uboot auto-script fail!

Dear friends,

While I'm upgrading u-boot on Goflex Home I get error

"
HTTP request sent, awaiting response... 404 Not Found
10:11:07 ERROR 404: Not Found.
"

See log file attached for detail. I think there is a problem with uboot file location on server.

Please help me to correct this issue.

Many thanks.

Hi khongpt,

You are running an old script from Jeff to update u-boot. I have is a new procedure to update to the latest u-boot:
http://forum.doozan.com/read.php?3,12381

If you are comfortable with flashing u-boot manually using this new procedure, you can do it from stock OS command line.

Jeff has not been updating the script that you ran, or regression testing it for a while. So it is expected that the script might not work.

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

Hi bodhi,

After flashing U-Boot 2016.05-tld-1 with manual proceduce, I'm do booting with HDD Linux-4.4.0-kirkwood-tld-1 rootfs, but getting error below:

[ 2.277926] Waiting 10 sec before mounting root device...
[ 12.290723] VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6
[ 12.298064] Please append a correct "root=" boot option; here are the available partitions:
[ 12.306512] 1f00 262144 mtdblock0 (driver?)
[ 12.311638] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I'd attached boot log and printenv uboot log, kindly help me to solve this issue.

Rgrds

khongpt

khongpt,

When you created the 4.4 rootfs, note step 4:

Quote

4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

You should not do step 4, since you are installing new uboot at the same time. So reverse step 4:

Mount the HHD on another Linux box, assuming it is mounted as sdb1:

cd /media/sdb1/boot
mv uImage.orig uImage
sync

Then put it back to the GFHome and power up.

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

bodhi ,

When I skipped step 4 (that's mean non DTB embedded for booting), the box can't boot to the kernel.

## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.4.0-kirkwood-tld-1
Created: 2016-02-19 7:33:04 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7179871 Bytes = 6.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000
Loading Kernel Image ... OK
Loading Ramdisk to 07439000, end 07b11e5f ... OK
Loading Device Tree to 07433000, end 0743896c ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


So, Don't I need to upgrade kernel to 4.9.0 ?

khongpt

khongpt Wrote:

> So, Don't I need to upgrade kernel to 4.9.0 ?

No, kernel 4.4 in the rootfs is fine. No need to upgrade the kernel until after you have booted into Debian.

Try creating the rootfs again without step 4. Make sure you are root user when you create the rootfs, and the ext3 partition is labeled as rootfs. Every steps in the installation must be followed exactly, if you have to tweak anything, then it will not work.

Your boot log in the last boot in this post: http://forum.doozan.com/read.php?3,32604,32611#msg-32611
indicated that the DTB was embbedded inside uImage. And the separated DTB loaded by u-boot never took effect.

So review your steps in your installation log (should keep the log while you doing this), you will find something was not done properly.

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

Hi bodhi,

I've just tried TFTPboot, and It's imazing!

I copy the uImage and uInitrd from /boot to the tftproot (DTB was embbedded inside uImage)

setenv ipaddr 192.168.0.3
setenv serverip 192.168.0.2
setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
tftpboot 0x800000 uImage
tftpboot 0x1100000 uInitrd
bootm 0x800000 0x1100000

And box now boot successfully. I'm root# now.

khongpt,

> And box now boot successfully. I'm root# now.

Great!

However, you're booting the box as if it is with the old u-boot (one that does not support FDT so you have to append the DTB to uImage).

The setup is not correct if you have to boot with tftp. So If you want to complete the setup to the way it should be, then in Debian, get the output of the following commands and post here.

dmesg
fw_printenv
mount
e2label sda1
ls -lart /
ls -lart /boot

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

Oh, Sorry!

After get root#, I used your uboot tool and flashed old uboot to my box. Now It work nomally as before upgrading.

I'll try to upgrading new U-Boot 2016.05-tld-1 with manual proceduce again. I think there was something miss when I upgraded my box to new uboot, and I'll do it again carefully. I hope everything will fine. See my good news.

Thanks.

-khongpt.