IX2 200 no boot log

Hi, I have 2 Lenovo Iomega ix2 200 and they both don't work. One of them blinks only the white LED, the other one blinks white and red LED.
I use a FT232 USB to connect - JP1 = 1st empty, 2nd txd, 3rd gnd, 4th rxd.

I tried to connect via gtkterm using the correct settings but no luck with both, no response
I tried using Lenovo Imager tool in order to build a USB to reinstall the system but no luck (used different usb 2.0 and 3.0 on the 3 ports)
Followed this video https://www.youtube.com/watch?v=72Re1-JaHgQ but didn't install from USB
Followed this guide https://github.com/vanaware/openwrt/releases/tag/v17.01.4-iomega_ix2_200-v1 but got stuck at setenv bootcmd 'setenv bootargs console=ttyS0,115200n8 root=/dev/sda1; usb start; ext2load usb 0:1 0x00800000 /uImage; bootm 0x00800000'
run bootcmd - the termail reporterd that couldn't start "run" command
Followed this guide https://github.com/artizirk/ix2-200 but at step 5 got stuck because of no response of gtkterm
Changed 2032 battery

Is there any way I could restore my NASs?

Thanks in advance and forgive me for my poor english writing

ZaTTG,

Unfortunately we don't have a lot of experience restoring stock FW for this box.

But if you don't care about keeping stock FW, you could install and run the latest Linux kernel and Debian on this box (that's what this forum is about).

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

Thank you for your answer, I don't care keeping the stock firmware, I just want them to work. How can I proceed? I'm new to this kind of stuff.

ZaTTG,

Serial console is required for installation on Kirkwood box like this one (running with stock u-boot, since I don't have a new u-boot for it like other Kirkwood boxes).

1. Create the new Debian rootfs on USB using Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Scroll down to 26 Sept 2021 section.

https://forum.doozan.com/read.php?2,12096

2. Connect serial console. Plug in the new USB Debian rootfs. Power up.

Interrupt serial console at countdown and follow the instruction in this post to enter the envs and boot the box:

https://forum.doozan.com/read.php?2,102054,105374#msg-10537

=====

The installation approach above is non-destructive. As long as you don't save the envs then everything will be back to the original state before when you turn of power and unplug the USB rootfs. So at serial console prompt, avoid executing commands such as saveenv and resetenv, and any other commands that you are not sure what it does.

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

Hi bodhi, I tried what you suggested, it seems to get stuck when after the command boot. Can you help me further?
Edit : I noticed that when i paste something, it's like double-paste even if the command is correct when I press enter



Edited 1 time(s). Last edit at 11/02/2021 08:45AM by ZaTTG.

ZaTTG,

> Edit : I noticed that when i paste something, it's
> like double-paste even if the command is correct
> when I press enter

Probably your serial console, but it seems to take the other commands, so let's not worrying about that right now.

[18933.13h.34m.04s.899] usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
[18933.13h.34m.04s.947] load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
[18933.13h.34m.04s.947] load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd
[18933.13h.34m.04s.947] usb_boot=mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000
[18933.13h.34m.04s.947] usb_bootcmd=run usb_set_bootargs; run usb_boot
[18933.13h.34m.04s.947] bootcmd=usb reset; run usb_bootcmd; usb stop; reset
[18933.13h.34m.04s.947] 
[18933.13h.34m.04s.947] Environment size: 2275/16380 bytes
[18933.13h.34m.04s.947] Marvell>> bootboot
[18933.13h.34m.47s.307] Unknown command 'boot' - try 'help'

At this point, instead of using boot command, which you cannot (it seems to be removed by this stock u-boot).

Do:

run bootcmd

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

Hi bodhi, the command you suggested worked, it boots into Debian, the network isn't working, its because by default it brings up eth0 which is not the one that works, the correct one is eth1 from what I understand (issue of ix2 200).

How can I swap eth0 to eth1? Should I change /etc/network/interfaces? Or there is a command like setenv ipaddr <ipaddr> ?
How to permanently install Debian then?

Thanks

ZaTTG,

> Hi bodhi, the command you suggested worked, it
> boots into Debian, the network isn't working

Cool. Ethernet problem is because you've use the wrong DTB!

[18936.09h.26m.32s.489] [    0.000000][    T0] Booting Linux on physical CPU 0x0
[18936.09h.26m.32s.489] [    0.000000][    T0] Linux version 5.13.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021
[18936.09h.26m.32s.489] [    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[18936.09h.26m.32s.489] [    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[18936.09h.26m.32s.489] [    0.000000][    T0] OF: fdt: Machine model: Seagate GoFlex Net

Since you can log in with serial console, you can correct this directly on the rootfs.

cd /boot
cp -a zImage-5.13.6-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-iomega_ix2_200.dtb  >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.13.6-kirkwood-tld-1 -d zImage.fdt  uImage
sync

And then reboot.

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

Hi bodhi, i did a "clean install" from USB, using this command

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

now I can't get an IP address from my PfSense even tho DHCP is enabled

ZaTTG,

> now I can't get an IP address from my PfSense even
> tho DHCP is enabled

Looks like there is some problem with hardware.

[18939.07h.55m.29s.703] [   34.475874][  T918] mv643xx_eth: no PHY
[18939.07h.55m.29s.703] [   34.475925][    C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[18939.07h.55m.29s.703] [   34.491508][  T105] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Check your ethernet cable connection.

Also try while the system is running, unplug the ethernet cabe and plug it back in. Or use a different cable.

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