Iomega IX4-200d - Boot Loop

[gracie27]

Hi begreat,

Here.

[IoMegaMan]

Brilliant, that worked! Thank you so much.

For those reading this in 2017 and beyond - I've expanded the instructions, added all of the required programs, and uploaded it here: https://goo.gl/b003hu (this links to Dropbox).

All credit goes to begreat.

[LOU198]

Excellent post!

So i've a little problem after copy and paste "reset" on step i:

I've looked what's happen on Marvell when i follow the nine steps:

a. setenv initrd_size 0x2f0000 ok
b. saveenv ok
c. tftpboot 0x2000000 zImage ok
d. tftpboot 0x12000000 initrd ok
e. nand erase 0x2d4000 0x2f000 ok
f. nand erase 0xb0000 0x224000 ok
g. nand write.e 0x12000000 0x2d4000 0x2f0000 ok
h. nand write.e 0x2000000 0x0b0000 0x224000 ok
i. reset ok and problem come

So by step, Marvell can:

b: SAVE

c & d:LOAD

e & f: ERASE

g & h: WRITE

And after step "i:reset (or boot)", Marvell try to read. We can see on the picture i post before:

"Reading data from 0x2fd800-- 5% complete.reading NAND page at offsett 0x304000 failed

3080192 bytes read : ERROR"

And at the end of page we can see : "

"Loading Ramdisk Image at 12000000 ...

Bad Magic Number "

Then, Marvell restart and restart and repeat same thing.

So Marvell can save, load, erase, write but.....can't read!?!

I'll like to know on the step "reading", where Marvell is reading, to find where's the problem?

It read on USB? TFTPD64.exe? NAS hdd Iomega?Is there mistake in prog "image"? problem whith "TTL to USB" ?

So what?

Now, it's impossible to turn off Iomega. After close all on PC, i must disconect power and remove 3V bat for several minutes. If no removed bat, iomega power on immediatly when put power supply...

Thanks a lot to help me, i think it's not a big problem but i'm stuck...

---

[Aladoine]

Google Traduction :
Hello, thank you for this recap with all the instructions.
But what if we are like Gracie27 without the pins?

Bonjour, merci pour ce recapitulatif avec toutes les instructions.
Mais comment faire, si nous sommes comme Gracie27, sans les broches ?

[asholino]

Hello :

i tried but doesn't risolve ad i think the hardware is not the same also the firmware

[HeadHunter94]

Yess, i have exactly the same problem. If you've found a solution please share it with me.

Thank in advance

I was refering to the bad magic number problem at the end of the instructions

[MoSo1]

Hello,

Found the solution from a thread on NAS-Central through the TimeMachine.

The Bad Magic Number is basically the result of a misallocation of memory addresses.

Here goes the solution that worked for me:

Replace where applicable.

resetenv
tftpboot 0x2000000 zImage
tftpboot 0x12000000 initrd
nand erase 0x2d8000 0x2e4047
nand erase 0xb0000 0x1fb1d8
nand write.e 0x12000000 0x2d8000 0x2e4047
nand write.e 0x2000000 0x0b0000 0x1fb1d8
reset

Reference:

https://web.archive.org/web/20150922043423/http://forum.nas-central.org/viewtopic.php?f=251&t=17277

Please spread the fix! 

Cheers!

[MoSo1]

I wish to thank Paul for his excellent work in providing the whole package (documentation, files,...)

Like many others, I had managed to get my machine half-way form the dead unitl It reached the "Bad Magic Number"!

This final step got it to boot properly.

Paul, you may wish to integrate it in a ver2.1 instructions file and provide updated links to the whole package (DropBox plus an alternate location maybe)

The whole archive from NAS Central has lots of info(http://forum.nas-central.org/viewforum.php?f=251&sid=46dc8dd4e8b873da2e212938c08c6524) and apparently you can even convert you plain vanilla ix4-200d to an ix4-200d Cloud Edition!

Please spread the fix! 

Thanks again.

[HeadHunter94]

For those where this fix didn't work either!!

My fix which worked for me:

Take a picture of what is written on putty where the NAND or something (i guess) is loading (please excuse i'm no computer scientist)

It should visible: NAND read: device 0 offset (a), size (b) 

The NAND "phrase" should be written 2 times. Those numbers in this sentence are very important! 

So now write down those in total 4 numbers (a,b,c,d)

then write in putty

setenv initrd_size (number d) in my case it was the 0x2e4047 like in the fix of MoSo1

saveenv

tftpboot 0x2000000 zImage

tftpboot 0x12000000 initrd

nand erase (number c, in my case it was the same then in the first fix ) (number d)

nand erase (number a, in my case same then in the original and MoSo1 fix) (number b, in my case it was the same then in the first fix)

nand write.e 0x12000000 (number c) (number d)

nand write.e 0x2000000 (number a , here in both fixes (original and MoSo1) the additional 0 between x and b was the problem (don't know how it got there)) (number b)

reset

than it should work

of course only if you follow thoroughly the original fix 

and i hope that the numbers/phrase arent inverted in your case. i would recommend to play around with those numbers in the case that my fix doesnt work.

once again thank you all for your effort and please excuse my noobish jargon

[ArturG]

Thanks begreat! That worked for me. Got the recovery image installed.

Now I have different issue - it cannot obtain an IP address.. DHCP is working fine on my newtwork, tried static to no avail?

Anybody had simillar issue?

On the front panel it's saying " Network Unavalible"

Thats the ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:50:43:de:39:2c
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2911 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2507 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:191299 (186.8 KiB)  TX bytes:105294 (102.8 KiB)
          Interrupt:11

eth1      Link encap:Ethernet  HWaddr 00:50:43:de:39:2d
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:15

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6722 (6.5 KiB)  TX bytes:6722 (6.5 KiB)

Thanks,

Artur