Questions from newbie - 2017.07 U-Boot Kirkwood : GoFlex Home (4 replies)

Questions from newbie - 2017.07 U-Boot Kirkwood : GoFlex Home

1) My Experience:
1rst timer on Hacking GoFlex Home. But I been in Linux from some time. Experience in Openwrt with routers. So new to doozan tutorials but I hope to be able to manage the Debian to Goflex Home hack.

2) What I done so far:
I read & follow:
Install Latest Kirkwood Debian rootfs and U-boot from stock OS
https://forum.doozan.com/read.php?2,117079,117084#msg-117084

Linux Kernel 5.15.5 Kirkwood package and Debian rootfs
https://forum.doozan.com/read.php?2,12096

2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug
https://forum.doozan.com/read.php?3,12381,page=1

U-Boot flashing utilities
https://forum.doozan.com/read.php?3,27280

3) Where I am?
I want to be safe as I have not install the serial monitor. I could If needed.

I have my USB prepared with Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2. And I did install Now following 2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome
I did downloaded uboot.2017.07-tld-1.goflexhome.bodhi.tar And I am at A. Flashing Instruction:
I also installed linux-tools-installation-bodhi.tar.gz on device.

4) My results so far:

GoFlex Home version 10.0.x

-bash-3.2$ uname -a
Linux axentraserver.********.seagateshare.com 2.6.22.18 #14 Wed Oct 27 15:41:03 EDT 2010 armv5tejl armv5tejl armv5tejl GNU/Linux
-bash-3.2$ sudo -E -s

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password: 
audit_log_user_command(): Connection refused
-bash-3.2# cat /etc/fw_env.config
cat: /etc/fw_env.config: No such file or directory
-bash-3.2# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00600000 00020000 "uImage"
mtd2: 0f900000 00020000 "root"
bash-3.2# fw_printenv ethaddr
Warning: Bad CRC, using default environment
## Error: "ethaddr" not defined
bash-3.2# dmesg | grep -i 'bad'
Scanning device for bad blocks
UBI: number of bad PEBs:         0
UBI: number of PEBs reserved for bad PEB handling: 38
bash-3.2# dmesg | grep -i ethaddr
bash-3.2# fw_printenv        
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
bash-3.2#

I had install /etc/fw_env.config from U-Boot flashing utilities

But as you see previouly in RED I have discrepancies. Tutorial say I should see

dev: size erasesize name 
mtd0: 00100000 00020000 "u-boot" 
mtd1: 00400000 00020000 "uImage" 
mtd2: 02000000 00020000 "rootfs" 
mtd3: 0db00000 00020000 "data"

And ethaddr is empty

What should I do next to correct discrepancies?

Thanks in advance.
enrique