Iomega ix2-200 bad flash recovery and HDD replacement 

Introduction
The Iomega StorCenter ix2-200 (Pricewatch) is a cheap stand-alone NAS which runs a combination of an unknown internal OS on its mainboard and Linux from the HDDs. The only thing the internal OS does is boot Linux from the first partition (which is a little over 2 GB and always in RAID1) of both disks. After Linux is started, you can configure the second partition (which uses the rest of the disk space) of both disks in JBOD or RAID1 for Shared Storage, iSCSI, etc. by using a web interface.A flaw of the ix2-200 is that Linux is loaded from the HDDs. If something happens to both disks, the internal OS cannot boot Linux and there is no way to recover the OS on a fresh pair of disks. Symptoms of not being able to boot Linux are that after boot up the disks will spin up, but will never be read. The power light will just keep blinking and nothing will happen.
Unfortunately, the firmware which Iomega offers for download seems to be encrypted. Fortunately, by using the data from the original disks and some trial-and-error, I extracted the Linux OS and put it on a new single disk which can be used to boot the ix2-200 and rebuild a new RAID1-set. Know that the new disk has to be prepared in Linux for RAID1 usage, otherwise the internal OS of the ix2-200 won't accept it. I decided to put what I learned in this guide (including the extracted Linux OS from the currently available firmware: version 2.1.25.229), since a lot of people seem to have trouble with this NAS.
This guide was made using a desktop PC, Knoppix Linux V6.2 and a SATA-to-USB adapter to prepare the first disk for the ix2-200. You can also directly use the SATA controller on your motherboard if it is supported by Knoppix. If you are going to try this, make sure that no other disks (PATA, SATA or USB) are connected. This will make sure that the right disk is prepared and that not one of your system's disks is wiped by accident.
Note that I cannot provide the GPL licensed code for the files I provide here, since Iomega doesn't provide it either. The only thing I'm doing is providing the same binaries that Iomega is offering, although mine are in a usable format. I'm still trying to get the sources from them.
Warning: This guide is made for the ix2-200, not the ix2! As far as I know, these are two completely different machines. The instructions could work for your ix2 if you would have the original Linux OS files for it and use ~1 GB of space for the first partition. However, this was not tested.
Final warning: Of course, you do everything at your own risk. Also, according to Iomega you will void your warranty. I wonder how they are ever going to check this when someone would put the original disks back before starting an RMA...
The guide
- Download ix2-200-2.1.25.229-files.7z.001 and ix2-200-2.1.25.229-files.7z.002 to /tmp. In Knoppix, you can use the web browser to do this.
- Open the Terminal Emulator and use the following commands:code:
1 2 3 4 5
su root cd /tmp 7z x ix2-200-2.1.25.229-files.7z.001 tar xvvf ix2-200-2.1.25.229-files.tar rm -f ix2-200-2.1.25.229-files*
The needed files are now decompressed and ready to be put on disk. - The next step is to prepare the disk. If you are using a USB-to-SATA adapter, you can connect it to the computer after the disk is powered on. Use the command 'dmesg' to find out which device-ID it gets. For this guide, we will assume the disk gets device-ID 'sda'.
In the console which is still open, start 'fdisk /dev/sda'. - Use the 'p<enter>' command to check if the disk has any partitions. If it does, remove the partition table with 'o<enter>'.
- Use the 'n<enter>' command to create a new partition. Make it a 'p'rimary partition, number '1', starting at cylinder '1' and make sure the last cylinder is '254'. Check the configuration of the new partition with the 'p<enter>' command. If the Device Id isn't 83, use the 't<enter>' command to make it hex code '83'.
- Use 'w<enter>' to write the changes to disk and exit fdisk.
- The partition should first be prepared for RAID-usage. Use the following command to make it part of a (broken) RAID1-set:code:
1
mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda1 missing
Just continue ('y<enter>') if you get any warnings about a current file system or that the partition was part of a previous raid array. Knoppix should report that array /dev/md0 has started after mdadm is done. - Format the new partition with the ext2 filesystem using:code:
1
mkfs.ext2 /dev/md0
- Now the only thing left to do in Knoppix is to copy the previously unpacked data to the disk. Use the following commands:code:
1 2 3 4
mount /dev/md0 /mnt/ cp -rf /tmp/ix2-200-2.1.25.229-files/* /mnt/ sync umount /mnt/
- You are now done with the first disk. Before moving on, make sure that the partition table of your second disk for the ix2-200 is empty. You can do this by connecting it to your computer and by repeating steps 3, 4 and 6 of this guide (if you restarted Knoppix, make sure you use 'su root' before running fdisk).
- You can now boot your computer back into your regular OS. Make sure you have a web browser ready, because we're going to reconfigure the Iomega StorCenter ix2-200.
- Install only the first disk into the ix2-200 and power it on. Make sure that the network cable is connected to your network and wait for it to boot up. You know when it's done when the LED with the exclamation mark (!) next to it is starting to blink red after a minute or two.
- The ix2-200 will have requested a DHCP address from your router. Look in your router's DHCP configuration/log which device requested the last address by looking at the most recent timestamp and/or the MAC address, which should begin with "00:D0:B8".
- This guide assumes the IP is '192.168.1.11'. Use a web browser to go to http://192.168.1.11 . The Setup wizard will start. Walk through the wizard.
- After you have finished the wizard, go to the Dashboard. The StorCenter will show a red circle with a white cross and the error message "The Iomega StorCenter device failed and some data loss may have occurred". This is the reason for the blinking red LED at the front. Don't worry, this is normal in this scenario.
- Shut down the ix2-200, install the second disk and turn it on again. It will get the same IP again after the white LED next to the exclamation mark is on.
- Go to the Dashboard in your web browser again. If the Status only reads 'Data Protection is being reconstructed', then the IX2-200 will have made the second partition and you are done. Enjoy your (new disks inside your) ix2-200. However, read the following step if the Status also reports that two disks with existing data have been found and if this message does not disappear after a minute.
- If you get the message that two disks have been found with existing data with a blue circle with a white 'i' in it next to the message, do not click the message to initialize the disks. If you would do this, the ix2-200 would erase the two disks entirely, including the first partition of which the internal OS starts Linux. This would effectively brick the ix2-200 and force you to start over with this guide.
Instead of initializing the disks, go to Settings -> Disks -> Manage Disks -> Erase Disks. Enable the check box at the top, select Quick Erase and click Apply. The ix2-200 will reboot after 30 seconds and show the Setup wizard again after 3-4 minutes. Finish the wizard again. After returning to the dashboard, the only Status message will be 'Data Protection is being reconstructed'. The IX2-200 just made the second partition. You are done.
Tweaker tip!
If you want SSH access to the Linux OS, go to http://ip-of-ix2-200/support.html and snoop around. The username is 'root'. The password is 'soho' + the password you use for the web-interface. If no password is needed for the web-interface, the password of root is 'soho'. If the password of the web-interface would be 'abc123' the password of root would be 'sohoabc123'.
--
Anonymous comments are not allowed. If you want to talk about the ix2-200 and this guide and you are not a member of Tweakers.net, you can always start a discussion in the NAS support forum of Iomega.
03-'10 Ziggo Digitale TV op de PC met cardsharing
02-'10 Verbeterde Apple Magic Mouse drivers voor Windows
Comments
"The only thing the internal OS does is starting Linux from the first partition" -> start
"before starting an RMA..." -> a
"Look into your router's DHCP configuration/log" -> in
Wrong. "Something is booting Linux" or "Something is boot Linux"?
"before starting an RMA..." -> a
Wrong. 'ar ahm ee' starts with a vowel.
"Look into your router's DHCP configuration/log" -> in
Correct. Fixed.
New comments written in Dutch will be removed. This guide is not just made for Tweakers.net, but for everyone who has problems with the ix2-200.
[Comment edited on donderdag 11 februari 2010 12:41]
how hard 'read expensive' can it be to add about 4gb of flash memory on a so called dom disk. - look for example to the price of the cheapest 4gb usb-stick and remember that those are RETAIL prices.
note that in some-cases it could still be worth some to initiallise swap space on the hdd's ...
but embedded linux in its bascics can perfectly run on just ram.
minus 10 points for iomega in my count
ow ant btw, another 1k pennalty for not releasing the sourcecode
*this all in a scale of 1 - 100
Wrong. "Something is booting Linux" or "Something is boot Linux"?
WRONG, "Something is booting Linux" or "(what) Something does is boot Linux"?
The "does" in the sentence is what makes the diffence between start or starting.
"before starting an RMA..." -> a
Wrong. 'ar ahm ee' starts with a vowel.
Well that depends on how you read it, indeed phonetic RMA starts with an but usually I read the entire meaning if i see an acronym (making it a).
So that's okay either way.
But the first really is "start" and not "starting".

I'm looking to get a NAS, this particular NAS is one which got my attention, not only is it fast, it's affordable, good basic hardware and tweak-able, but how tweak-able, I just can't find any answer to my questions, maybe you do have the answer...;)
Questions:
1: with root access, is it possible to install an NZB download program like getnzb or sabnzbd+?
2: after changing disks like you describe, is it possible to use two different sized disks, OS partition is RAID1, rest of the space is configured as JBOD, or a second secured RAID1 with the free unassigned space as JBOD?
If this is possible then this NAS is really the sweet spot..

Eventually: yes. However, some changes should be made to the OS to make it more customizable (extra drivers would REALLY help) and acceptable to other software. First of all, it should be possible to recreate the used kernel so extra drivers can be added (not that this is needed for a normal program). Secondly, the most logical way to install programs on this machine would be using Debian's APT repositories. However, I haven't tested whether the ix2-200 accepts 'regular' ARM-compiled programs. This would make an interesting MP3 player, though.Questions:
1: with root access, is it possible to install an NZB download program like getnzb or sabnzbd+?

It is possible to put the second partition of each disk in JBOD, but I only tested this with two similar disks. I also tested two different sized disks in RAID1 and the second partition would be as big as the smallest disk would allow (which makes sense).2: after changing disks like you describe, is it possible to use two different sized disks, OS partition is RAID1, rest of the space is configured as JBOD, or a second secured RAID1 with the free unassigned space as JBOD?
The first partition is always RAID1 (otherwise, the ix2-200 will not boot). You cannot split the second partition for different uses (one part RAID1, another part JBOD).
[Comment edited on donderdag 11 februari 2010 14:07]
This could be figured out when you get the source files...

As you described in your tutorial this specific OS partition is needed and spanning the raid 1 over these two disks is essential when one of the drive's is failing.
But what about the rest of the disk space, I want a part of the disk to be RAID 1 for documents/foto's and the rest as JBOD for movies and so on, beside the OS partition.
besides what you described in your tutorial, Is it possible to copy the OS partition to a new larger disk and so on replace the original disk delivered with the NAS, after the disk is recognised by the iomega NAS, add a second disk which will then get the RAID-1 OS copy?
This would mean having a third partition: something which is not manageable with the original firmware. The management interface isn't prepared for that. Technically, it would be possible to create and manage this with a custom firmware. But wouldn't it be easier to just use the second partition in RAID1 and add extra USB drives for non-redundant storage? The ix2-200 supports this out-of-the-box. It wouldn't be JBOD, but at least you can use extra disk space with just one NAS.But what about the rest of the disk space, I want a part of the disk to be RAID 1 for documents/foto's and the rest as JBOD for movies and so on, beside the OS partition
That's possible. You can prepare one larger disk using my tutorial and add the second disk after the first boot and shut down. I haven't tested this, but it should be possible to buy the 1TB version (2x500GB) and replace the disks with 2x1TB or 2x2TB.besides what you described in your tutorial, Is it possible to copy the OS partition to a new larger disk and so on replace the original disk delivered with the NAS, after the disk is recognised by the iomega NAS, add a second disk which will then get the RAID-1 OS copy?
[Comment edited on donderdag 11 februari 2010 14:46]
Not sure which web interface password do you refer to. I have created 3 users, including user admin, with each their own password that can access the NAS via the web.
I have tried user root with my "soho" plus my web interface password, concatenated, but no luck.
Any help please?
If I'm correct, it should be the password of the admin-account. If the admin password would be 'abc123', the password for root should be 'sohoabc123'.Not sure which web interface password do you refer to. I have created 3 users, including user admin, with each their own password that can access the NAS via the web.
Any help please?
I haven't tested this thoroughly and used the information about SSH access from this site for the ix2. If it still doesn't work, could you change the passwords of your users temporarily to something you can tell me and get me the 'root'-line from the file '/etc/shadow' from the first ext2 partition?
[Comment edited on donderdag 11 februari 2010 15:52]
If you delete the 'admin' user password so that the admin user does not have a password, the combination of user 'root' with password 'soho' works for SSH access.
Still this box is rather new, now root access is possible, maybe someone will release a custom firmware with all new features, like customizable RAID1 sizes and JBOD support and my needed NZB support...

For the price tag of 250 euro at redcoon this is one of my favorites..., but still searching for other possibilities.
The nice people of Iomega provided this link for the ix2 GPL software: https://iomega-na-en.cust...std_adp.php?p_faqid=20778Note that I cannot provide the GPL licensed code for the files I provide here, since Iomega doesn't provide it either.
Network settings are checked, cabling is ok. the switch is a fritz.box 7170. Had made dump files which are send to iomega but i am not impressed by this product. There are many, many erros in the log.
I am not expecting a solution from Iomega soon.
I followed your directions and made it through step 15 without any problems. However, when I started the unit with new drive it just sat there with the blinking light of death. Just for completeness, I repeated the steps with the second drive and it worked! I got the flashing red light above a solid white one. Great! I checked my router, found the DHCP lease for the appropriate MAC address, and entered it in my browser. Again, success. I even got two emails from the device with subjects
Problems with 'ix2-NAS' device (100)
Problems with 'ix2-NAS' device (101)
So I did not just imagine things.
Next, I shut the device down from the web interface, installed the second drive (with the matching Linux partition) and went to bed expecting the array to be rebuilt when I checked in in the morning. Unfortunately, that wasn't the case. It was just sitting there with the blinking light of death again.
I've tried every permutation I can think of to get back to at least one drive working, but so far without luck. I do see the device requesting a DHCP lease, though I cannot browse or SSH to the address. I don't believe both drives are bad, since I can repartition and use them on other systems. Do I need some sort of good luck charm or secret incantation to get this to work?
I had taken the Seagate drives from the ix2-200 and swapped them with a pair of drives from an external SimpleTech duo pro drive - the Hitachi 7,200 rpm drives. So I took one of the original Seagate drives and, following the instructions above, replaced the Linux partition and files. And it worked perfectly.
At that point, I thought maybe I could insert a Hitachi drive, let the mirror rebuild, and then swap the other Hitachi for the original Seagate leaving me with mirrored 7,200 rpm drives. Wrong. When I inserted the Hitachi, it didn't show up. I rebooted. It still didn't show up. I thought maybe one SATA channel had gone bad, so I inserted the second Seagate drive. It showed up.
Bottom line: not all drives have firmware that will work with the ix2-200. So I'm back to the original, factory-equivalent unit.
Live and learn, I guess.
Thanks again Zep Man for unbricking my unit.
I am having a problem with the ix2-2oo unit - it does not power down. Without any help from the Iomega Support, who are completely clueless and useless, I have managed to isolate the problem to the following:
If I disable all the services and functions AND I unplug the network cable, the unit does power down. This implies it has something to do with network services. I suspect it is the Windows CIFS Sharing Service (Samba Service) as you can not disable this service.
Using SSH access to the unit, I have tried to play around and shut down the Windows Sharing Service, but i don't know enough about Linux and Debian. I know I need to shut down the smbd and nmbd services, but somehow they are re-started of I don't succeed in killing them.
Can anybody with some Linux / Debian experience help?
... I bought today an ix2-200. And I fell over your wonderful instruction by accident as I searched for infos about partitioning.
1st I was little bit shocked, as you write about Linux etc. ... I never used Linux (Rec.: Undoubtfuly its an excellent open source) as I use since 20 years Microsoft (with all the suffering of system crashes ;-) ). Actually I have a Vista system and already XP professional and same Windows NT 4.0 have been very stable systems. So I wanted to avoid learning something new like Linux.
I bought this ix2-200 because it was a good prize for a home office solution, same with the idea, that I wanted exchange one of the 1 TB hard discs into a 2 TB big one. It was told to me from the technical staff of the computer shop that this should be not any problem to do this switch even the warantee would not be lost (maybe a typical German law situation). Now here I am...
... with following question and little bit unsafe about what to do:
Can I exchange one of the internal 1 TB of ix2-200 with the 2 TB Western Digital (WD Caviar Green SATA) ? - I want the big one only as backup storage. Nothing more... just mirroring all existing datas from my mashines and different existing internal and external hard discs...
The smaller internal 1 TB I want use for regular storage of two mashines (Vista Laptop, XP Computer)... and connect another 1 TB mobile HD with the ix2-200 USB so the internal big 2TB would do only automated data backupping of 2x 1TB (one ix2-200 internal + 1 external mobile).
But now I hesitate. It looks much more difficult to do this step, or ? - What do you think about ?
So fare, hope hearing soon as actually I have no backupping and its little bit scary without such a safeteness... Warm regards from Hamburg/North Germany - SM2010
+++
Unfortunatelly, I could not manage to bring up the iX2-200 to normal operation, due to the message "2 new drives with existing data found". After running settings --> disk --> quick erase as you described and restarting the mirroring of the Data Volume gets started again. It finishes up after some hours, lookup SSH ( cat /proc/mdstat ) tells about success operations
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[1] sda2[0]
974722192 blocks super 1.0 [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[2]
2040215 blocks super 1.1 [2/2] [UU]
unused devices: <none>
root@storage-2:/#
but the errormessage because of two new disks with different data is displayed though and remirroring is started over and over again on each reboot.
Hope for a hint. And I am ashaming for my bad english language skills.
Is it possible to use 1 disk or do you have to use 2 disks ?
I have a white led of death ix2-200, with a lifetime of photos on it and then the more important stuff too. Just noticed it now, I think it went down a while ago. Not being a Linux user, Im not even sure I understand the instructions, but first of all, Im fuzzy on whether this procedure can save the data on the 2nd partitions of the discs. I don care much about the HDDs, just need to grab all the data.
In step 3 you say "The next step is to prepare the disk. " - is it one of the ix's disks?
I assume it is and, Im sure it is lame to ask, but when you say to remove parttions tables of both disks, this makes all the data lost, right? But then, there information on how long data reconstruction would take... and Im lost.
Ill appreciate any help on that, TIA!
So I have followed all your steps and have got down to #18 - "2 new drives with existing data have been found". I have tried the "Erase Disk" option a number of times (the Quick erase restarts the interface but the Secure Erase just sits and sits - even left it overnite). So now am stuck with two drives that I cannot use in the NAS until it gets past the problem. I have enabled SSH access but am stuck as to what I should look for, or what I should do to try and solve the problem.
FYI - before the machine dropped I had upgraded it to the latest firmware as well - could there be a conflict between the flash component and what is on the HD?
ANY and ALL responses would be appreciated ...
Thanks ... Dave
Thanks and hope this helps the next "Iomega" crash victim.
Dave
The key to success is to add the --metadata=1 option to the first drive as dewynn has indicated. This prevents the duplicate data scenario and having to quick erase the drives. Thanks you for writing this guide...it works is all I have to say!!
Inserting the second drive did not change anything to the situation, neither trying to delete/erase the drives. The NAS reboots again and again, or shows the "white light of death" (+ the red one) until I plug out the AC power cord and plug it in again, and then the NAS reboots and show me the start-up wizard again ... and always the error/failure message.
I must say (but i think it's irrelevant) that my disks are 2 Samsung Spinpoint 1T0 and i'm working on my Mac in a virtualized Ubuntu distibution.
So, i got the idea to check the differences (in structure : partition table, etc.) btw the new hard disk (before insertion in the NAS) and the one of the original drives.
I noticed that on the original disk there's a second partition (tagged as "raid") after the 2,1 Go one that holds the firmware. On the new disk, the extra space (998Go) is "unallocated".
So i decided to create a second partition (as i suspect the NAS to fail doing this job itself)
My complete sequence in the terminal was the following (from a blank disk ... that is refered as "sdb" in the disk utility software of ubuntu) :
fdisk /dev/sdb
n
p
1
1
254
w
n
p
2
254
'enter the last number possible to cover the entire space of the disk'
w
mdadm --create --verbose --metadata=1 /dev/md0 --level=1 --raid-devices=2 /dev/sdb1 missing
mdadm --create --verbose --metadata=1 /dev/md1 --level=1 --raid-devices=2 /dev/sdb2 missing
mkfs.ext2 /dev/md0
mkfs.ext2 /dev/md1 (i takes some time since it's 998 Go)
(then i copy the 2 archive files downloaded to the /tmp (using ubuntu file browser))
cd /tmp
7z x ix2-200-2.1.25.229-files.7z.001
tar xvvf ix2-200-2.1.25.229-files.tar
rm -f ix2-200-2.1.25.229-files* (in my case, i have an error telling me it's a folder)
mount /dev/md0 /mnt/
cp -rf /tmp/ix2-200-2.1.25.229-files/* /mnt/
sync
umount /mnt/
[Comment edited on vrijdag 31 december 2010 11:34]
The process described here above worked fine with one disk (the second partition (dedicated for storage) was accessible and writable on my Mac) ... But every time I have introduced the second (blank disk), the NAS failed to reconstruct itself the raid arrays.
So, i bought a second SATA-USB adapter... plugged the 2 drives at the same time on my MacBook Pro, mounted the adapter in the virtual machine running ubuntu...
And, the the terminal, created /dev/sdb1 et /dev/sdb2 (on the first drive) and /dev/sdc1 et /dev/sdc2 (on the second) (following the tutorial of The Zep Man)
then typed in the terminal :
mdadm --create --verbose --metadata=1 /dev/md0 --level=1 --raid-devices=2 /dev/sdb1 /dev/sdc1
mdadm --create --verbose --metadata=1 /dev/md1 --level=1 --raid-devices=2 /dev/sdb2 /dev/sdc2
mkfs.ext2 /dev/md0
mkfs.ext2 /dev/md1
cd /tmp (where i copied the 2 archive files downloaded to the /tmp (using ubuntu file browser))
7z x ix2-200-2.1.25.229-files.7z.001
tar xvvf ix2-200-2.1.25.229-files.tar
rm -f ix2-200-2.1.25.229-files* (in my case, i have an error telling me it's a folder)
mount /dev/md0 /mnt/
cp -rf /tmp/ix2-200-2.1.25.229-files/* /mnt/
sync
umount /mnt/
(shut down my computer (before syncing process was over), put the 2 drives in the NAS, start it up .... GOTCHA, the NAS began automatically the reconstruction of the second array )
Thank you anyway for the help.
[Comment edited on vrijdag 31 december 2010 16:40]
Thanks for this wonderful post though!

I have replaced the seagate drives and re-used them for something else, I have installed 2 off 2TB WD Black caviar drives and am pulling my hair out.
Every time I try to install as per the post, I get the error message and can see from the ssh that the device is creating the MD1, for which it takes 6 to 8 hours so I wait till that is completed, but the error remains. I have tried deleting the disks from with the webapp and by writing them to zero with dd /dev/zero dd/dev/sda when connecting them to a linux machine.
Any more thoughts or things to try would be much appreciated.
I also tried this http://iomega.nas-central.org/wiki/Category:Ix2-200-usb-init
but it does absolutely nothing. Is there a set sequence I have to follow to get the usb to boot and re-initialise........
Thanks in anticipation.
Graham
Is there an easy way to convert the raid from the SSH shell rather than the webpage.
I had same new drive error, tried to zero out them and even wrote zero-superblock with no go, then started again from disk 1 (like in this guide) and instead blanking the disk 2 , i made the first primary partition on it with start at cylinder 1 and made it bigger than the disk 1 with last cylinder being 500 then made it raid1 and mkfs.ext2 /dev/md0, then stopped md0 and fdisk removed the partition so disk2 was "empty". then booted from d1 and shutdown put disk2 in booted again and it allowed me finally to change protection mode to jbod without sayin raid101 error then did the quick erase and then changed it back to raid1 protection mode.
[Comment edited on vrijdag 15 juli 2011 05:15]
OMG! F1nally! That USB init method worked. But I did not use Cloud FW, because my device is vanilla ix-200.joakimlaine wrote on Sunday 14 August 2011 @ 20:55:
Has anybody tried with http://iomega.nas-central.org/wiki/Category:Ix2-200-usb-init using the cloud edition firmware downloaded from iomega support site into non cloud ix2-200 if it works?? will it erase the drives or keep old data?? This would also add os x lion compatibility. I'd test it but dont have extra drives to try with.
Guys, I will create you a guide the will be uber-n00b-friendly. Now I have to sleep because I have spent my last 3 days with this problem....
Has anybody tried with http://iomega.nas-central.org/wiki/Category:Ix2-200-usb-init using the cloud edition firmware downloaded from iomega support site into non cloud ix2-200 if it works?? will it erase the drives or keep old data?? This would also add os x lion compatibility. I'd test it but dont have extra drives to try with.
--
Yes, I did this yesterday and can confirm that it does work. I moved from ix2-200 firmware 2.1.38.xxxxx to the very latest firmware for the ix2-200 Cloud edition, 3.1.12.47838.
One caveat that I didn't see listed: backup all of your data before you perform this. I tested on both drives in a few different methods. One drive i cleared all data and started fresh. The other I tried to update this on the fly. I lost all data on the drive I tried to do it on the fly with.
To make it real easy: CopyJobs, backup all of drive to a external drive. Update drive firmware, let device rebuild it's redundancy and then CopyJobs from external drive back to the nas. It'll take a while, but is super easy to do.
Access the SSH with:
https://<ix2-200 ip>/diagnostics.html
Have fun.
Enjoy!
http://www.technopat.net/...oud-edition.html?langid=1


In an attempt to get an external 3TB drive mounted as read/write, I edited the /etc/fstab file. Rebooted and got the white flashing LED of death. Took the drives out and attached them to my PC and booted from a Linux rescue CD. Got the partitions mounted and looked through them. Found a 4gb and a 16gb on md0. I could not find the /etc directory anywhere. Is it somehow hidden or part of an image? All I need to do is edit one file, but I can't locate it. Do any of you gurus know how I can get to the fstab file to edit it?
Thanks!
My father in law crashed his Iomega ix2-200.
and then tried to fix it himself.
Now I'm left with two completely blank (he retrieved the disks of the NAS and formatted them in a pc, removing the partitions in the progress..)
SO I'm trying to use this guide to reset the NAS Os on the disks.
But I'm stuck on step 5:
Use the 'n<enter>' command to create a new partition. Make it a 'p'rimary partition, number '1', starting at cylinder '1' and make sure the last cylinder is '254'. Check the configuration of the new partition with the 'p<enter>' command. If the Device Id isn't 83, use the 't<enter>' command to make it hex code '83'.
When using Knoppix 7.2 fdisk /dev/sda, units are in sectors and not in cylinders.
I can also not set the starting point to 1, since the default (and minimum value) for the sector is 2048.
Can someone please help me fix this?
There is an option in FDISK 'u' that enables the partition to be declred as cylinders. Iswitches between the two.
Hope this is helpful.
However I still haven't fixed my ix2!!
http://tweakimg.net/g/s/confused.gif
Comments are closed