Recovering IOmega ix2-200 NAS after failed upgrade

The following was my solution to fixing a bad NAND flash, after an upgrade failed halfway through. YMMV but you could at least give it a try.

You’ll get access to the bootloader, and be able to upload a new image via TFTP …

I tried the instructions for recovering a bad flash from this page, but it wasn’t working as it should. I saw no access to my USB key, and having tried several different USB keys I was convinced that wasn’t the problem.

You’ll need:

  • RS232 to TLL level shifter 3.3V (I used a PL2303 based clone from Ebay costing about $5,- incl. shipping)
    Philips #2 screwdriver, hobby knife
  • Computer with TFTP server installed, configured at 192.168.1.100
  • Decrypted firmware for the unit – see this page for instructions. You should get the files linked here, or try an upgrade to Cloud Edition with the instructions for generating the upgrade file here (the latter page requires you to run a script from your now-dead-ix2, so you can just do this from a Linux machine).
  • Prepare a USB key as described on the pages linked above (where you got the decrypted upgrade image from). Basically a FAT32 formatted USB key with the upgrade file placed in /emctools/ix2-200d_images/ix2-boot.tgz
  • Place zImage and initrd (from the ix2-boot.tgz file) on your TFTP server.

Procedure:

  • Connect the USB key to any port on your ix2
  • Connect your TTL level shifter to JP1 – see this page for pinout.
  • Connect your ethernet cable from the ix2 to your computer.

At the Marvell>> prompt, do the following:

tftpboot 0x2000000 zImage
tftpboot 0x5400000 initrd
nand write.e 0x2000000 0x100000 0x300000
nand write.e 0x5400000 0x540000 0x300000

That will load the kernel and initrd into memory, and write them to the NAND of the ix2. Now you can either powercycle the unit, or just issue

boot

As I had totally clean drives in my unit the upgrade/wipe happened automatically, just wait 5-10 minutes. Also you can connect to your DHCP enabled network and access the unit (when the procedure completes).

Also you can take a look at Nigels page here, if you want to tinker more and install a full Debian on the unit.

This entry was posted in Tinkering. Bookmark the permalink.

32 Responses to Recovering IOmega ix2-200 NAS after failed upgrade

  1. Martijn Kruiten says:

    There is an ix2-200 sitting next to me that got stuck during an upgrade. I already wiped out the hard drives and tried two methods to recover: methode 1) preparing an hdd and method 2) preparing a usb key. I’ve had no luck so far. Now I want to try your method, but I’m a bit confused about some points.

    -Does it matter which os I run on my pc? I assume this is written for linux. Or is it os independent if you use tftp?
    -How should I connect the PL2303 cable? Cut it, connect the naked wires to the board and the serial/usb connector to my pc?
    -Where do I type tftpboot 0x2000000 etc? I have no idea where I can find the Marvell prompt.

    If you can point me in the right direction, I would be very happy. I do know the basic stuff, like using terminal etc. If you could just say something like: cut and connect the cable like this, use the following os, use this tftp server and open this command window I think I would manage.

  2. Martijn Kruiten says:

    Ok, I think I understand how the cable works. It’s usb on one side and 4 wires on the other. So I imagine it is as straightforward as connecting the usb to your pc and the wires to the board.

    Now what I do not yet understand, is how the communication works. I guess the communication is all done through this cable using tftp? And the utp cable is only connected for configuration when the device is ready? And tftp handles passes the commands through to the device and I can use whatever os I like?

  3. lkarlslund says:

    The USB< ->TLL adapter works as a line level converter for serial communication. That means that one end is USB and the other is TTL-serial.

    When you connect the cable you can use a serial terminal program for your OS.

    If you insist on using Windows (smirk), I can recommend TeraTerm Pro for terminal emulation (http://hp.vector.co.jp/authors/VA002416/teraterm.html) and something like tftpd32 (http://tftpd32.jounin.net/).

    Tera Term is way old, but realiable. HyperTerminal just sucks, so stay away from that.

  4. lkarlslund says:

    I guess that should work.

    My converter has a jumper for 3.3v/5v mode, and I set it at 3.3v just to be safe.

    Look on ebay for “TTL 3.3v” and you can get it for half the price of the item you suggested.

  5. Alkaf says:

    Please, Check the above values, because now I can not boot my ix2-200, offset problem, can you help on this.

    Thank you.

  6. Roel says:

    I have also errors

    reading NAND page at offset 0x100000 failed
    3145728 bytes read: ERROR

  7. lkarlslund says:

    What did you do?

    Please take care about the tftp-part:

    tftpboot 0x2000000 zImage
    tftpboot 0x5400000 initrd

    This loads the kernel and initrd from your tftp-server. Check the logs that the files were transferred to your ix2.

    nand write.e 0x2000000 0x100000 0x300000
    nand write.e 0x5400000 0x540000 0x300000

    This copies the memory locations you loaded the kernel and initrd images into flash, so you can boot them.

    I need more log info to be able to help you.

  8. Roel says:

    This is my log:

    Marvell>> tftpboot 0x2000000 zImage
    Using egiga1 device
    TFTP from server 192.168.1.100; our IP address is 192.168.1.143
    Filename ‘zImage’.
    Load address: 0x2000000
    Loading: T ######################################################done
    Bytes transferred = 2483788 (25e64c hex)
    Marvell>> tftpboot 0x5400000 initrd
    Using egiga1 device
    TFTP from server 192.168.1.100; our IP address is 192.168.1.143
    Filename ‘initrd’.
    Load address: 0x5400000
    Loading: ######################################################done
    Bytes transferred = 2796387 (2aab63 hex)
    Marvell>>
    Marvell>> nand write.e 0x2000000 0x100000 0x300000

    NAND write: device 0 offset 0x100000, size 0x300000

    Writing data at 0x3ffe00 — 100% complete.
    3145728 bytes written: OK
    Marvell>> nand write.e 0x5400000 0x540000 0x300000

    NAND write: device 0 offset 0x540000, size 0x300000

    Writing data at 0x83fe00 — 100% complete.
    3145728 bytes written: OK
    Marvell>> boot

    NAND read: device 0 offset 0x100000, size 0x300000

    reading NAND page at offset 0x100000 failed
    3145728 bytes read: ERROR
    Marvell>>

  9. Roel says:

    By the way :
    The files are from firmware ix2-200-3.2.3.9273.tgz
    (cloud edition)
    My device a non cloud edition upgraded to cloud
    (USB init method )
    Working ok!
    After the latest firmware upgrade 3.2.3 trouble begin (upgraded with HTTP webpage)
    Buttons are missing on the admin webpage.
    After that I was trying the USB init agene with no luck.
    So I follow the instructions on this page.
    After that Uboot is the only thing working.

  10. lkarlslund says:

    I think I forgot:

    nand erase 0x100000 0x300000
    nand erase 0x540000 0x300000

    Do this after tftp transfer, but before the nand write.e commands

    At your own risk 🙂 I no longer have the device to test on.

  11. Roel says:

    Yes that was the problem it booting again
    Thanks for solving the problem.

  12. Nelson says:

    This procedure will work for Iomega ix4-200d?, I upgraded to version cloud and my nas no longer starts, constantly restarts after displaying the logo of Iomega and I could not flash the previous version.
    Thanks

  13. Pingback: Recovering IOmega ix2-200 after failed upgrade

  14. Pingback: IOmega ix2-200'yi Başarısız bir Upgrade'den Sonra Düzeltmek

  15. Ben says:

    Thank you for your instruction.
    I did everything as you said. It was working fine. After the RAID 1 sync, it shutdown itself. Then I turn it back on, it shows the following via ttl and I cannot manage it thru the webpage. Do you know what is going on? Thank you!

    CPU : Marvell Feroceon (Rev 1)

    Streaming disabled
    Write allocate disabled

    Module 0 is RGMII
    Module 1 is TDM

    USB 0: host mode
    PEX 0: interface detected no Link.
    Net: egiga0, egiga1 [PRIME]
    USB: scanning bus for devices… 2 USB Device(s) found
    scanning bus for storage devices… 0 Storage Device(s) found
    Aquiring an IP address using DHCP…
    BOOTP broadcast 1
    *** Unhandled DHCP Option in OFFER/ACK: 28
    *** Unhandled DHCP Option in OFFER/ACK: 28
    DHCP client bound to address 192.168.1.253
    Starting the Recovery process to retreive the file…
    uImage load address 0x02000000
    Warning: Missing environment variable “deviceName”. Assuming default!
    Warning: Missing environment variable “modelNumber”. Assuming default!
    Broadcasting Distress Beacon Packet.
    Warning: Missing environment variable “deviceName”. Assuming default!
    Warning: Missing environment variable “modelNumber”. Assuming default!
    Broadcasting Distress Beacon Packet.
    Warning: Missing environment variable “deviceName”. Assuming default!
    Warning: Missing environment variable “modelNumber”. Assuming default!
    ….

  16. dude says:

    Hi there,
    i have the same issue, i tried to upgeade it then, my iomega is flashing then it will give red light and reboot.
    when i connect the usb ttl cable i don’t get any output.
    Settings: 115200 baud, parity none, flow control xon/xoff, 8 data bits, 1 stop bit.
    then power up the device with the USB.
    then nothing happen
    no data
    any help

  17. lkarlslund says:

    Are you sure your TTL cable is working / connected correctly? I have some ebay cables that did not work at all … if you get zero output from the serial port the bootloader is gone, and I don’t know how to fix that. But I would guess it’s just a cable problem.

  18. lkarlslund says:

    Hmm – seems the unit fails to load the kernel and tries recovery via DHCP / TFTP upload. I don’t have my unit anymore so I really can’t test anything out.

  19. Bill Brazell says:

    In an attempt to get an external USB hard drive to mount writable, I ssh’d to the ix2-200 and edited the fstab file, adding a /dev/sdc1 line. Now it doesn’t boot – just a flashing LED. I’ve ordered a USB-TTL cable since that appears to be the only way to access the unit. Once I get the cable, what method should I use to get in there and edit the fstab file? Do I have to create a USB key to boot from, or use TFTP? Any help is appreciated!

  20. David says:

    Hello
    Great guide
    But I have just one problem…
    I have test the debian squeeze distro on this nas following this installation guide at http://www.cyrius.com/debian/kirkwood/openrd/install.html
    Now I would like to came back to standard version
    The installation of 2 files (zImage ad initrd) as been done, I have format the 2hdd, but when I turn on the nas the power led still blink.
    I would like to install the cloud os version on my non cloud nas.
    Here the serial screen
    Marvell>> boot

    NAND read: device 0 offset 0x100000, size 0x300000

    Reading data from 0x3ffe00 — 100% complete.
    3145728 bytes read: OK

    NAND read: device 0 offset 0x540000, size 0x300000

    Reading data from 0x83fe00 — 100% complete.
    3145728 bytes read: OK
    ## Booting image at 02000000 …
    Image Name: Linux-2.6.31.8
    Created: 2011-07-22 16:54:23 UTC
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2479992 Bytes = 2.4 MB
    Load Address: 00008000
    Entry Point: 00008000
    Verifying Checksum … OK
    OK
    ## Loading Ramdisk Image at 04500000 …
    Image Name:
    Created: 2011-07-29 14:10:23 UTC
    Image Type: ARM Linux RAMDisk Image (gzip compressed)
    Data Size: 2793445 Bytes = 2.7 MB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum … OK

    Starting kernel …

    Uncompressing Linux…………………………………………………………………………………………………………………………………………. done, booting the kernel.
    Please help me 🙂

  21. David says:

    Hi man
    envreset command has solved my problem.

  22. michele says:

    Hi!
    I’m unable to find the file called “ix2-boot.tgz” in the page linked…
    Can someone provide me that file?

  23. michele says:

    Please,can someone take a look at this and tell me what’s wrong?? the linux kernel boots ok, but i cannot get any http interface…
    It’s my bootlog…

    CPU Interface
    ————-
    SDRAM_CS0 ….base 00000000, size 256MB
    SDRAM_CS1 ….disable
    SDRAM_CS2 ….disable
    SDRAM_CS3 ….disable
    PEX0_MEM ….base e8000000, size 128MB
    PEX0_IO ….base f2000000, size 1MB
    INTER_REGS ….base f1000000, size 1MB
    NFLASH_CS ….base fa000000, size 2MB
    SPI_CS ….base f4000000, size 16MB
    BOOT_ROM_CS ….no such
    DEV_BOOTCS ….no such
    CRYPT_ENG ….base f0000000, size 2MB

    Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21)– RD-88F6281A Soc: 88F6281 A0 LE

    Detected Tclk 200000000 and SysClk 333333333
    MV Buttons Device Load
    Marvell USB EHCI Host controller #0: c0672600
    PEX0 interface detected no Link.
    PCI: bus0: Fast back to back transfers enabled
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    NET: Registered protocol family 2
    Time: kw_clocksource clocksource has been installed.
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    TCP reno registered
    checking if image is initramfs…it isn’t (no cpio magic); looks like an initrd
    Freeing initrd memory: 1782K
    RTC registered
    mp_lm63: device lm63 found
    mp_lm63: Alert/tach pin configured for tachometer input
    mp_lm63: PWM clock 1.4 kHz, output frequency 22 Hz
    mp_lm63: PWM output active high, auto mode
    mp_lm63: Module loaded.
    Use the XOR engines (acceleration) for enhancing the following functions:
    o RAID 5 Xor calculation
    o kernel memcpy
    o kenrel memzero
    Number of XOR engines to use: 4
    cesadev_init(c0011ef4)
    mvCesaInit: sessions=640, queue=64, pSram=f0000000
    MV Buttons Driver Load
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    JFFS2 version 2.2. (NAND) é 2001-2006 Red Hat, Inc.
    io scheduler noop registered
    io scheduler anticipatory registered (default)
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
    serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
    RAMDISK driver initialized: 16 RAM disks of 5120K size 1024 blocksize
    loop: module loaded
    Loading Marvell Ethernet Driver:
    o Cached descriptors in DRAM
    o DRAM SW cache-coherency
    o Single RX Queue support – ETH_DEF_RXQ=0
    o Single TX Queue support – ETH_DEF_TXQ=0
    o TCP segmentation offload enabled
    o Receive checksum offload enabled
    o Transmit checksum offload enabled
    o Network Fast Processing (Routing) supported
    o Driver ERROR statistics enabled
    o Driver INFO statistics enabled
    o Proc tool API enabled
    o Rx descripors: q0=128
    o Tx descripors: q0=532
    o Loading network interface(s):
    o eth0, ifindex = 1, GbE port = 0
    o eth1, ifindex = 2, GbE port = 1

    mvFpRuleDb (c07ec000): 2048 entries, 8192 bytes
    Intel(R) PRO/1000 Network Driver – version 7.3.20-k2-NAPI
    Copyright (c) 1999-2006 Intel Corporation.
    e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    Integrated Sata device found
    scsi0 : Marvell SCSI to SATA adapter
    scsi1 : Marvell SCSI to SATA adapter
    scsi 0:0:0:0: Direct-Access Seagate ST500DM002-1BD14 KC45 PQ: 0 ANSI: 5
    sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
    sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI disk
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
    NAND device: Manufacturer ID: 0xad, Chip ID: 0x75 (Hynix NAND 32MiB 3,3V 8-bit)
    Scanning device for bad blocks
    Bad eraseblock 1621 at 0x01954000
    mtd: nand_mtd: partitioning exceeds flash size, truncating
    4 cmdlinepart partitions found on MTD device nand_mtd
    Using command line partition definition
    Creating 4 MTD partitions on “nand_mtd”:
    0x00000000-0x000c0000 : “uboot”
    0x000a0000-0x000c0000 : “env”
    0x00100000-0x00400000 : “zImage”
    0x00540000-0x00840000 : “initrd”
    ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
    ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
    ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
    ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    USB Universal Host Controller Interface driver v3.0
    usb 1-1: new high speed USB device using ehci_marvell and address 2
    usb 1-1: configuration #1 chosen from 1 choice
    hub 1-1:1.0: USB hub found
    hub 1-1:1.0: 4 ports detected
    usb 1-1.2: new high speed USB device using ehci_marvell and address 3
    usb 1-1.2: configuration #1 chosen from 1 choice
    usbcore: registered new interface driver usblp
    drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
    Initializing USB Mass Storage driver…
    scsi2 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    md: linear personality registered for level -1
    md: raid0 personality registered for level 0
    md: raid1 personality registered for level 1
    raid6: int32x1 76 MB/s
    raid6: int32x2 98 MB/s
    raid6: int32x4 108 MB/s
    raid6: int32x8 81 MB/s
    raid6: using algorithm int32x4 (108 MB/s)
    md: raid6 personality registered for level 6
    md: raid5 personality registered for level 5
    md: raid4 personality registered for level 4
    raid5: measuring checksumming speed
    arm4regs : 903.600 MB/sec
    8regs : 670.000 MB/sec
    32regs : 725.600 MB/sec
    raid5: using function: arm4regs (903.600 MB/sec)
    device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
    dm_crypt using the OCF package.
    TCP cubic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    md: Autodetecting RAID arrays.
    md: autorun …
    md: … autorun DONE.
    RAMDISK: Compressed image found at block 0
    EXT2-fs warning: checktime reached, running e2fsck is recommended
    VFS: Mounted root (ext2 filesystem).
    cat: can’t open ‘/sys/block/sdb/removable’: No such file or directory
    mdadm: No devices to examine
    cat: can’t open ‘/sys/block///size’: No such file or directory
    Sys UUID is :
    Valid Disk 1 in md0: /dev/sda1
    Valid Disk 2 in md0:
    USB Device node is /dev/sdb1
    Trying to see the if the reset button is pressed or not
    Started
    /dev/btns file does not exist creating it
    Opened /dev/btns with fd 3
    Reset Key Status: Button Id = 12 Push Count = 1 Release Count = 0
    Reset Button key got pressed
    /mount_images.sh: line 335: lcdimg: not found
    Checking if there is an attached EMC Imager
    scsi 2:0:0:0: Direct-Access Kingston DataTraveler U3 6.50 PQ: 0 ANSI: 0 CCS
    sd 2:0:0:0: [sdb] 1970175 512-byte hardware sectors (1009 MB)
    sd 2:0:0:0: [sdb] Write Protect is off
    sd 2:0:0:0: [sdb] Assuming drive cache: write through
    sd 2:0:0:0: [sdb] 1970175 512-byte hardware sectors (1009 MB)
    sd 2:0:0:0: [sdb] Write Protect is off
    sd 2:0:0:0: [sdb] Assuming drive cache: write through
    sdb: sdb1
    sd 2:0:0:0: [sdb] Attached SCSI removable disk
    sd 2:0:0:0: Attached scsi generic sg1 type 0
    FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
    Checking for pre-image script… none.
    Image tar file found
    tar: invalid gzip magic
    apps Not found in /usb_drive/emctools/ix2-200d_images/*.tgz tar file
    Going in to Network Imaging Mode
    umount: cannot umount /dev/md0: Invalid argument
    eth0: started
    udhcpc (v1.9.2) started
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    Sending discover…
    No lease, failing
    eth1: link down
    eth1: started
    udhcpc (v1.9.2) started
    Sending discover…
    Sending discover…
    eth1: link up, full duplex, speed 1 Gbps
    Sending select for 192.168.2.27…
    Lease of 192.168.2.27 obtained, lease time 86400
    deleting routers
    route: ioctl 0x890c failed: No such process
    adding dns 85.37.17.55
    adding dns 85.38.28.93
    Device Model- ix2-200d
    Device: Socket Listening on: 2081
    Mac address = 00:50:43:64:20:13
    Device: Sent a broadcast packet

    Device: Waiting for Hello Response…
    No response received
    Device: Going to send a broadcast again

    Mac address = 00:50:43:64:20:13
    Device: Sent a broadcast packet

    Device: Waiting for Hello Response…
    No response received
    Device: Going to send a broadcast again

    Mac address = 00:50:43:64:20:13
    Device: Sent a broadcast packet

    Device: Waiting for Hello Response…

  24. Yiourkas says:

    Thanks for the guide.

    I have a question though. I have an old pc with a RS232 port on it. Can I just use this one, or do I have to use a USB to serial chip like the one you describe?

    cheers,
    Y

  25. JC Astruc says:

    Hello,
    Thank you for your guide, you saved my ix2.
    After trying to upgrade a non cloud ix2-200 it got stuck with an infinite blinking.
    Once connected to the serial port i noticed that the checksum was faulty and stopped the boot process. I applied your tutorial and now it’s all right.
    Some commands found while playing around :
    usb start -> scan all usb ports, usb storage -> list usb disks, ide reset -> spin up hard drives

  26. Simone says:

    HI,
    i’m a beginner.. my problem is that i can only ping NAS IP and nothing else..
    i’m a windows user.
    i tried to follow your steps but i can’t undestand how you connect the ix2-200 to the PC.
    i created the USB Flash with the firmware and plugged in the lower back usb port
    i connected the serial cable (i hope correctly) from NAS to usb PC and windows recognize the device but it didn’t show in the device manager.
    (i had to connect the nas power cable too?)
    i have only one disk in the nas in bay 1.
    how i can connect from my pc to the NAS?
    can someone tell my a stupid step-by-step guide like
    1 open program xxxx
    2 set this
    3 go to..
    4 type..
    5 etc..
    i can’t realy undestand how to proceed

    TKS

  27. ilker says:

    I am having trouble with my ix-2 200 cloud.
    I can reach files in nas from win 8 pc and all media files can be seen from all media player in network (including hi-fi receivers, ios device, etc…)

    But i can not reach admin pages of Nas. http://nas-ip/manage.html or http://nas-ip/diagnostics.html

    Has anyone faced the same problem? or any advice to solve this problem?

  28. Didier says:

    Thank you, you save my ix-200! I tried for a year to put another linux distribution on it, and I’m afraid I couldnt get back to anything working after numerous tests.
    But flashing the zImage and initrd from official firmware was enough to restart the machine with good will :-), and the usual firmware flash from iomega on a usb stick did the whole initialisation of the machine in 5 minutes!!!

  29. Hector Campos says:

    After powercycle my ix2-200:
    front leds off
    RJ45 led blinking but not IP
    HD Spin.
    UART : no output (blank screen)

    Bricked my U-boot?

  30. Pingback: iomega StorCenter ix2–200 – mikrom

  31. Patrick says:

    please Help my ix2-200 is down
    the white LED light
    the update ist failed

Leave a Reply

Your email address will not be published. Required fields are marked *

*