Home > Tech > Iomega StorCenter Pro 200rl root access

Iomega StorCenter Pro 200rl root access

March 13th, 2009

So we got one of these NAS boxes at work and like all self respecting sysadmins we wanted root access on the box ideally with SSH, unfortunately the NAS server doesn’t support this. However it is trivial to obtain root access by using an Ubuntu live CD as follows.

Firstly boot off the live CD and once you have your live CD desktop open up a terminal window, we now need access to the system drive on the NAS box which we can acquire as follows:-

$ sudo apt-get install mdadm
$ sudo mdadm --assemble --scan
$ sudo mount /dev/md3 /mnt

Next we need to make sure we’re working on the NAS system drive for all our commands so let’s chroot into it:-

$ sudo chroot /mnt

To reset the root password we need to run:-

 # passwd

To enable SSH (which is already installed) on startup we need to run:-

# update-rc.d ssh defaults 16

Finally we cleanup and reboot the NAS server:-

# exit
$ sudo umount /mnt
$ sudo reboot

Don’t forget to remove/eject the CD when the Ubuntu live CD prompts you to.

Now once the NAS reboots into its native OS (which happens to be Debian) you’ll find you’ll be able to login to the box as root with all the power that comes with it.

Tech ,

  1. raupe
    | #1

    Thanks for that great article. For me the –scan didn’t work (I used the system rescue cd, since it comes with the mdadm tool – http://www.sysresccd.org), so I had to specify the disks manually. The command would then read ‘mdadm –assemble /dev/md3 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1’

    Also, the chroot had to be appanded with /bin/sh, like: chroot /mnt/backup /bin/sh

    Hope that helps.

  2. Travis
    | #2

    I have the 200rl with root access and one of the drives temporarily failed. When the raid 5 md0 array rebuilt itself all my data disappeared and it looks like it may have been cause by the chunk size being reconfigured. Can anyone run “mdadm –misc -detail /dev/md0” and let me know what the chunk size should be?


  3. | #3

    Sorry for the delay, hope it helps…

    NAS01:~# mdadm –misc –detail /dev/md0
    Version : 00.90.03
    Creation Time : Fri Mar 13 20:44:00 2009
    Raid Level : raid5
    Array Size : 2917941888 (2782.77 GiB 2987.97 GB)
    Device Size : 972647296 (927.59 GiB 995.99 GB)
    Raid Devices : 4
    Total Devices : 4
    Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Dec 17 15:44:08 2009
    State : active
    Active Devices : 4
    Working Devices : 4
    Failed Devices : 0
    Spare Devices : 0

    Layout : left-symmetric
    Chunk Size : 64K

    UUID : a7db5e45:ea5f2030:8467a421:84d4f733 (local to host NAS01)
    Events : 0.147437

    Number Major Minor RaidDevice State
    0 8 2 0 active sync /dev/sda2
    1 8 18 1 active sync /dev/sdb2
    2 8 34 2 active sync /dev/sdc2
    3 8 50 3 active sync /dev/sdd2

  4. Brecht
    | #4

    We have an 200rL that had to rebuild his raid5 because something other than the disks failed (don’t know what that something can be?). Now after the rebuild al the data is gone. The webinterface shows 0GB used. Is the data really gone? Does anybody have an idea? According to the webinterface the shares still exist but they are inaccessible.

  5. Lukasz
    | #5

    Anyone even thinking about using this device – don’t. This is one big piece of garbage. Device cannot detect faulty disks correctly and it won’t notify about that fact. More over, it’ll re-create array on faulty disks – of course erasing old content.

    The only solution is to install your own Linux distribution, configure via ssh by hand and take care on your own about monitoring.

    I’ve got two devices like this and they both are going under the knife now.
    IOmega support was, well, less than interested in helping us. They have sent us heavily used replacement unit with disks more than a year old – and with the same software issues.

    So, forget about IOmega 200rl.

  6. elish
    | #6

    The root password is “soho”

  7. JMR
    | #7

    Once you can access as root. You can change users passwords via ‘passwd’ command, BUT it doesn’t works with the user network folder for wich connection you need the password specified before via web admin.
    So you end up having two passwords for each user, the one you specified via web admin and the one you changed via ssh.
    Any idea to have only one valid password preferably the one changed via ssh?

  1. No trackbacks yet.