Lenovo Iomega EZ Media & Backup Center

Hi, I need to know if it is possible to install LEDE or OpenWRT on
Lenovo Iomega EZ Media & Backup Center, and, if it is not possible, I want at least be able to install Debian on it
EDIT: So far I was able to install Debian, see here: Lenovo Iomega EZ Media & Backup Center

I read on some sites that has the same CPU of Seagate GoFlexNet and Zyzel NSA-310: Feroceon 88FR131
Someone knows how to do it?

This one:
https://img1.r10.io/PIC/56363964/0/1/450/56363964.jpg
https://content.hwigroup.net/images/products_xl/156729/8/iomega-ez-media--backup-center-1tb.jpg

Some info Here:

http://iomega.nas-central.org/wiki/Category:EZ_Media
http://iomega.nas-central.org/wiki/Stock_Configuration_(EZ_Media)
http://iomega.nas-central.org/wiki/Some_information_from_a_running_system_(EZ_Media)
http://iomega.nas-central.org/wiki/Install_firmware_on_a_fresh_disk_(EZ_Media_%26_ix2-ng)

Seagate GoFlexNet:

https://wiki.openwrt.org/toh/seagate/goflexnet

Zyzel NSA-310:

http://zyxel.nas-central.org/wiki/Some_information_from_slash_proc_(NSA-310)

What could I try to do? I have several HD's around to do tests on it.

Currently have a 3TB empty HD, WD Black with stock firmware but it is EXTREMELY slow, about 2 or 3Mb/s even with gigabit switch and cable... when I installed that disk it was faster, around 30Mb/s or little more...
I want to be able to test it with other firmware, if it works, I will buy another cheap 2 or 3 WD green/red harddrive (since black runs much hotter and noisier than this one) and plan to use it... but if I am stuck with original stock firmware I just will sell it as is, I just don't want it, it is just too slow.

[quote="braian87b, post:1, topic:5031"]
Lenovo Iomega EZ Media & Backup Center
[/quote]From specs and the site it seems this device does not have enough flash for its own firmware (it seems to have only 1 MB), so you install its "firmware" on the hard drive.

Lede would need to be installed on the drive too.

It's definitely possible to support it, as it is currently already supported by bodhi's Debian Kirkwood project so I would just need to copy his stuff (again).
See here http://forum.doozan.com/read.php?2,35331

You can try out his Debian, it should be better than stock firmware, although installation requires some manual work as you see in the thread, like opening the case and connecting a TTL-USB dongle to have serial console access to the board so you can communicate with the bootloader and configure it to boot Debian.

There are also some caveats or workarounds, but it should work fine. In the sense that should be able to share files at around 30 MB/s at least.

If you are interested in that, I'll recommend you to open a new thread on that forum for questions related to installing Debian in that device, post a link here and I'll be there too.

Damn, lets do this! I will be pleased to do some experiment, I opened some time ago, I can do that again, I have solder iron and TTL-USB too... just need instructions from someone with more practice on the steps, like someone that already done at least on similar hardware and understand about boot process on this ( I do not understand very well).

Can you ? :wink:

[quote="braian87b, post:3, topic:5031, full:true"]Can you ? ;)[/quote]I'll have a more through look at this in the weekend.

I can't promise anything though, and it will probably take a few weeks.

1 Like

So, I had a look.
I added partial support, but I don't know how to make LEDE images to be flashed on disk so yeah, that's a problem.

Currently the only thing that should work is the LEDE "run-from-RAM" image, which is mainly for testing purposes as it can't save any change you make (on reboot it loses all changes).
Without further help from people that know more about how to make disk images I'm probably not going further than this.

Which is this file here https://www.dropbox.com/s/fb92zvq12akll5r/lede-kirkwood-ix1-spi-initramfs-uImage?dl=0

If you want to test this, write it on an unpartitioned disk with dd as instructed in the "install firmware on a fresh disk",
dd if=/path/to/my-file of=/dev/sdx seek=2048

Then if you place it in the NAS it should be able to boot it and you should be able to reach it with ssh. Having serial console is better because in case it does not boot at least you can post the error messages to me.

I've uploaded the changes on my github's fork of LEDE https://github.com/bobafetthotmail/source/tree/iomega-ez-nas

I can still help you installing Debian in it though (if you post in the doozan forum as linked above).

I had also a WD MyBook Live Single, I know that it support LEDE.
Some user pointed me that just a dd command is needed:


and this is the commit: https://git.lede-project.org/?p=source.git;a=commit;h=dc7efaefb53d4671893add07934839eb8d44934d
There is a shell script and makefile, but I don't know how to modify to make it work with your file.

I will try to do the dd today, thanks!!!

Dropbox filename: lede-kirkwood-ix1-spi-initramfs-uImage

I sent you an instruction on which I did not know others:

Connected a blank disk to the computer on linux system (live cd
linux) downloaded the

firmware and put it in the home directory opened the terminal and entered

the command "dd if ="you name firmware" of = / dev / sdX" where the X-letter
of your disk needs to be opened gparted and viewed

see after installation go to disk in the folder /etc/config/network Open
the file "network" with a text editor from the administrator node and fix
the "static" option on "dhcp".

Then you can disconnect the disk from the computer to connect the
management card and try to go to the address that will be assigned
mybooklive.

There is still it but only in Russian language

Hi, yes, In this thread we are trying to do the same with an Iomega EZ Media & Backup Center, I had both devices, this one and the WD MybookLive Single I want to have LEDE on both. Edit: I have installed LEDE on WD MBL Single without problems.

I will try to install on both and let you know results, Thanks!

Thanks, I use Google Translator, so far is mostly clear: https://gist.github.com/braian87b/0d90b053f9603e3cc22127e3a6caf906

I ensure that drive is without data, even MBR or GPT...
I used dd to write the file using seek=2048 too.. (is that ok?)

It does not boot, I do not know where is serial-ttl on the board, I will disassemble and scan/photo and test some pins that I saw next week to try to get error messages.

Should I give up and install Debian? there is an easy to follow link somewhere to do that?

[quote]It does not boot[/quote]The bootloader tries to load both the kernel and initramfs from sector 2048 and sector 8192. Don't know what the bootloader does when it fails to load the initramfs. Maybe it just panics.

A serial connection could tell. You can find information about the serial port here. That's the ix2-ng. AFAIK it has the same mobo, except for the 2nd sata connector.

You can also try to put the original initrd on 8192. Alhough I don't know what the LEDE kernel will do with it.

Here I shoot some pictures of my Board. I think it is the same as you said,


I added on other site too: http://iomega.nas-central.org/wiki/Category:EZ_Media

On 3rd image there is a populated 4-pin connector labeled "CN4" that is seria-ttl, it is at bottom left.

The pins are from left to right tx gnd rx, the 4th one is not needed.

I had some time now to test Debian, it is difficult to install it ?

[quote]On 2nd and 3rd image there is an un populated 4-pin connector labeled "CN7" near the SATA connector, I think that is seria-ttl.[/quote]No, it isn't. That is power for the disk. Do not connect your TTL device to it. You'll fry it. (Edit: CN7 is probably not sata power. I was mistaken with CN5. Don't know what CN7 is)

The serial port is CN4.

[quote]I had some time now to test Debian, it is difficult to install it ?[/quote]Depends on your skills. Basically you have put a kernel and a root filesystem on the disk, and change the u-boot parameters to load&use it. More info on the doozan forum.

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

It seems the EZ is still in beta. Don't know what that means.

Ok, I used the initrd and zimage from files.tgz that comes inside ./emctools/hm3_images/ that I downloaded from http://downloads.iomega.nas-central.org/Users/Mijzelf/EZMedia/EZMedia-recovery-4.0.2.9960.zip as I see on the URL the file was uploaded by you @Mijzelf...
And later on top of that I put the @bobafetthotmail downloaded from https://www.dropbox.com/s/fb92zvq12akll5r/lede-kirkwood-ix1-spi-initramfs-uImage?dl=0 in order to try if it boots, (below is the boot log using serial-ttl)

dd if=zImage of=/dev/sdb bs=512 seek=2048
dd if=initrd of=/dev/sdb bs=512 seek=8192
dd if=lede-kirkwood-ix1-spi-initramfs-uImage of=/dev/sdb bs=512 seek=8192 
Serial TTL boot log(click here) __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** ix1-spi ** ** uboot_ver:0.0.8 **
 ** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Oct 28 2011 - 15:17:21) Marvell version: 3.6.1 - EMC

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

Soc: 88F6282 A1 CPU running @ 1200Mhz L2 running @ 600Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 6 tRP = 6 tRAS = 15 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[1024kB@f8000000] Flash:  1 MB

Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: WDC WD60PURX-64T0ZY1                     Firm: 80.00A80 Ser#:      WD-WX11D3778ZFD
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1528862.5 MB = 1493.0 GB (-1163856720 x 512)


CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: WDC WD60PURX-64T0ZY1                     Firm: 80.00A80 Ser#:      WD-WX11D3778ZFD
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1528862.5 MB = 1493.0 GB (-1163856720 x 512)


IDE read: device 0 block # 2048, count 6144 ... 6144 blocks read: OK

IDE read: device 0 block # 8192, count 8192 ... 8192 blocks read: OK
## Booting image at 00040000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2013-03-12  22:02:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2831076 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00900000 ...
Bad Magic Number

Am I doing right? Please let me know how I must continue these tests, I really want to have working LEDE on this...
meanwhile I will read on doozan's forum how to put Debian on this.

There is a way to boot to usb? it will be great that...

lede-kirkwood-ix1-spi-initramfs-uImage should be written on 2048, and initrd on 8192. I think the LEDE kernel will simply ignore the initrd, because it already has an initramfs, but the bootloader clearly doesn't, as it refuses to boot with an invalid ramdisk:[quote]## Loading Ramdisk Image at 00900000 ... Bad Magic Number (silence) [/quote]

Great, ok, I do:

dd if=lede-kirkwood-ix1-spi-initramfs-uImage of=/dev/sdb bs=512 seek=2048
dd if=initrd of=/dev/sdb bs=512 seek=8192

I'm using the initrd from files.tgz inside http://downloads.iomega.nas-central.org/Users/Mijzelf/EZMedia/EZMedia-recovery-4.0.2.9960.zip

Here is the output:

Serial TTL boot log(click here)
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** ix1-spi ** ** uboot_ver:0.0.8 **

 ** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Oct 28 2011 - 15:17:21) Marvell version: 3.6.1 - EMC

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

Soc: 88F6282 A1 CPU running @ 1200Mhz L2 running @ 600Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 6 tRP = 6 tRAS = 15 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[1024kB@f8000000] Flash:  1 MB

Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: WDC WD60PURX-64T0ZY1                     Firm: 80.00A80 Ser#:      WD-WX11D3778ZFD
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1528862.5 MB = 1493.0 GB (-1163856720 x 512)


CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: WDC WD60PURX-64T0ZY1                     Firm: 80.00A80 Ser#:      WD-WX11D3778ZFD
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1528862.5 MB = 1493.0 GB (-1163856720 x 512)


IDE read: device 0 block # 2048, count 6144 ... 6144 blocks read: OK

IDE read: device 0 block # 8192, count 8192 ... 8192 blocks read: OK
## Booting image at 00040000 ...
Bad Magic Number

IDE device 1: not available

IDE read: device 0 block # 2048, count 6144 ... 6144 blocks read: OK

IDE read: device 0 block # 8192, count 8192 ... 8192 blocks read: OK
## Booting image at 00040000 ...
Bad Magic Number
Marvell>>

Hmm. That lede-...-uImage is not a uImage. It's a plain kernel:~$ file lede-kirkwood-ix1-spi-initramfs-uImage lede-kirkwood-ix1-spi-initramfs-uImage: Linux kernel ARM boot executable zImage (little-endian)
You'll have to package it using mkimage (I guess load address and execution pointer are both 0x8000), or use the bootloader to load it at 0x8000 and then boot 0x8000. Not bootm, as it expects a uImage.

I don't know how to do that, can you tell me how?

Sorry but I do not understand very well how it works all the uboot, kernel, root, image etc things...
I know some about Debian and LEDE/OpenWRT but I never do anything with kernel upgrades, kernel images, etc.