Welcome! Log In Create A New Profile

Advanced

Help reviving my old Iomega IX4-200d

Posted by AmitMa 
Help reviving my old Iomega IX4-200d
September 07, 2022 09:48AM
Hi.
My old Iomega IX4-200d is dead and I'm trying to revive it.
I understand that the first step is installing u-boot, but I didn't find a guide for this.
Can someone please point me to the right guide?
I'm already connected to the device using serial.

Thanks!
Re: Help reviving my old Iomega IX4-200d
September 07, 2022 03:15PM
AmitMa,

> My old Iomega IX4-200d is dead and I'm trying to
> revive it.

How dead? ie. does the LEDs flash during power up?

> I understand that the first step is installing
> u-boot, but I didn't find a guide for this.
> Can someone please point me to the right guide?

> I'm already connected to the device using serial.

Does the serial console output anything when you power up? if it does then capture the log and post here.

============

It serial console is silent then see this example how to run kwboot to load and run u-boot image:

https://forum.doozan.com/read.php?3,51739,51919#msg-51919

The ix4-200d stock u-boot image:

https://forum.doozan.com/read.php?2,22623,25690#msg-25690

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Help reviving my old Iomega IX4-200d
September 08, 2022 02:57AM
The LED screen is working.
It indicates that the NAS is trying to boot from a USB or network.


         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** uboot_ver:v1.1.0 **

 ** MARVELL BOARD: IX4-110 LE

U-Boot 1.1.4 (Oct 15 2009 - 17:28:22) Marvell version: 3.4.18

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF600

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Found 0x20 i2c device
Toggle power status
Set Power State as Always On
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:32 MB
Found ADT7473, program LED ...(led_volt=90)  OK
Found ADT7473, program thermal/Fan ...(pwm_min=0) (pwm_max=130) (therm=67) (temp_min=60)  OK

Marvell Serial ATA Adapter
Integrated Sata device found


CPU : Marvell Feroceon (Rev 1)
Found initrd at 0x2d4000

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is RGMII

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
SCSI:  AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode
flags: 64bit ncq stag led pmp slum part
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: WDC WD6400AAKS-2 Rev: 01.0
            Type: Hard Disk
            Capacity: 610479.3 MB = 596.1 GB (1250261615 x 512)
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0xb0000, size 0x224000

Reading data from 0x2d3e00 -- 100% complete.
 2244608 bytes read: OK

NAND read: device 0 offset 0x2d4000, size 0x2f0000

Reading data from 0x301000 --   6% complete.reading NAND page at offset 0x304000 failed
 3080192 bytes read: ERROR
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2012-01-05  18:29:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1910204 Bytes =  1.8 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 12000000 ...
   Image Name:
   Created:      2012-05-02  20:38:45 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1831340 Bytes =  1.7 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRCâ–’

and looping...
Re: Help reviving my old Iomega IX4-200d
September 08, 2022 04:15PM
Take a look at the instructions and files I have linked in this post:
https://forum.doozan.com/read.php?3,25120,132700#msg-132700

There if full recovery steps and firmware to recover your box. It is an older firmware to get the recovery done but once up and running, you can still download the latest stock image from Lenovo and get you back to normal state.
Re: Help reviving my old Iomega IX4-200d
September 08, 2022 05:34PM
AmitMa ,

> Take a look at the instructions and files I have
> linked in this post:
> https://forum.doozan.com/read.php?3,25120,132700#msg-132700
>
> There if full recovery steps and firmware to
> recover your box. It is an older firmware to get
> the recovery done but once up and running, you can
> still download the latest stock image from Lenovo
> and get you back to normal state.

Yes, the stock FW is corrupted. So it is semi-bricked. Recovery procedure CodeJACK posted should get this box back to stock condition. And then from there, you can consider install Debian (on USB rootfs).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Help reviving my old Iomega IX4-200d
September 09, 2022 01:25AM
OK. I recovered the box to the stock (Thanks a lot)!
What is the next step for installing debian?
There is a step-by-step guide like CodeJACK sent?
Thanks again!
Re: Help reviving my old Iomega IX4-200d
September 09, 2022 04:22AM
There is no specific instruction for the ix4-200d box but following bodhi's process in this thread will get you running:
https://forum.doozan.com/read.php?2,12096


Check the Wiki page for instructions on how to move your working USB install to the local disk for better performance and install of OMV is thats what you want.
Re: Help reviving my old Iomega IX4-200d
September 09, 2022 03:27PM
AmitMa,

Create Debian USB rootfs using Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread:

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

Scroll down to section

Quote

Updated 26 Sept 2021:

Basic Debian bullseye Kirkwood rootfs for most Kirwood plugs:

Since you will be running stock u-boot, you will need to set up u-boot envs as instructed in Step 5:

Quote

5. Done.

If you are installing on a Kirkwood box that runs stock u-boot (it is not on the new u-boot support list) then see
Boot Kirkwood rootfs with stock u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Help reviving my old Iomega IX4-200d
September 18, 2022 02:08AM
Thanks. I succeed in booting into Debian.
How can I make this permanent?
After restart, the stock is booted.
Re: Help reviving my old Iomega IX4-200d
September 18, 2022 11:27PM
Save the envs before booting.

Quote

Boot Kirkwood rootfs with stock u-boot

Note: I've updated this instruction to make it more robust (to take into consideration the limitation of much older stock u-boots)

Assuming you have created a USB rootfs following the instruction in the release thread.

Power up, interrupt u-boot count down, and then.

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset'

And then,

printenv
saveenv
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Help reviving my old Iomega IX4-200d
September 19, 2022 01:37PM
Thanks! What a great forum!
What if I want to install OMV?

Can I follow this guide?
https://forum.doozan.com/read.php?2,94014

If yes, do I need to update uBoot?
Currently, I booted from USB into Debian.
root@debian:~# uname -a
Linux debian 5.13.6-kirkwood-tld-1 #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 armv5tel GNU/Linux

I tried to follow the steps without updating uBoot, and when I tried to use "fdisk", I noticed it isn't installed so I stopped to figure out if I'm doing somformattedrong.

#UPDATE
I formated the HDD and created partitioned as the guide described, but after the first reboot, I booted into the stock firmware.
I didn't "saveenv", but I'm assume that it doesn't matter because the whole purpose is to boot from the HDD. Am I right?



Edited 2 time(s). Last edit at 09/20/2022 11:01AM by AmitMa.
Re: Help reviving my old Iomega IX4-200d
September 20, 2022 11:12PM
This is the current working thread for this box. You can read from begining to see what can be done to boot HDD rootfs on this box.

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

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



Edited 1 time(s). Last edit at 09/20/2022 11:26PM by bodhi.
Re: Help reviving my old Iomega IX4-200d
September 21, 2022 02:32AM
This is a really long thread.
I will appreciate if you can point me to the specific guide.
Re: Help reviving my old Iomega IX4-200d
September 22, 2022 02:45AM
AmitMa Wrote:
-------------------------------------------------------
> This is a really long thread.
> I will appreciate if you can point me to the
> specific guide.

I am quite busy, so cannot discuss the alternatives. Post in that thread and hopefully CodeJack can help explaining what s/he did. And where we are.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
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: