[ARMedslack] ARMEDSlack on the ix2-200

[debeus]

Hello fellow ARMEDSlackers,

I've been installing on the ix2-200 Cloud Edition, a low cost NAS with
two SATA drives, a wired gigabit ethernet port and a few usb ports.

Everything's working but the LEDs, the buttons and a little odd problem
with the RAID setup.  See below for details.

First thing I did was plug in a serial/TTL ftdi cable to access the
serial console.  The instructions/pin-outs can be found on
http://iomega.nas-central.org/wiki/Category:Ix2-200

but are 
Pin 1 	VCC (3.3V)
Pin 2 	TxD
Pin 3 	GND
Pin 4 	RxD 

Pretty much you can follow directions for the Marvell kirkwood series; I
also found this:  http://blog.nobiscuit.com/
tremendously helpful.  There's a patch for controlling the LEDs and
buttons, which successfully applies to 3.2.6 (-current). I've compiled
it, but haven't run it yet because I'm trying to figure out my RAID
problem first.


Installation in a nutshell: (nearly identical to the above source and
the ARMEDSlackware Marvell-kirkwood instructions)

For the ix2-200 systems:
Marvell>>   setenv arcNumber 1682
Marvell>>   setenv ethaddr AA:00:00:00:00:01
Marvell>>   setenv mainlineLinux yes
Marvell>>   saveenv
Marvell>>   reset

I decided to install to the built in ide, but you can use an external
usb drive as well. Just be aware that the usb drive will reorder the
names of the ide drives. ie sda becomes sdc, etc.  I also had a conflict
between the usb drives and a usb printer on boot (making the drives not
recognized by uboot), but it may just be that particular printer.

You have to use eth1 not eth0. After install you also need to modify
rc.inet1.conf to replace eth0 with eth1 (change the DHCP="yes" to "" and
vice versa)

Marvell>> ide reset
Marvell>> tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img
Marvell>> tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood
Marvell>> setenv bootargs console=ttyS0,115200 kbd=us nic=auto:eth1:dhcp
root=/dev/ram rw;bootm 0x00800000 0x01100000

After install to disk:

setenv bootargs_console 'console=ttyS0,115200 kbd=us nic=auto:eth1:dhcp
mtdparts=orion_nand:0x300000 at 0x100000(uImage),0x1000000 at 0x540000(uInitrd)'
setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4'
setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root);
run bootcmd_slk ; reset'
setenv bootcmd_slk 'ide reset;ext2load ide 0:1
0x01100000 /uinitrd-kirkwood;ext2load ide 0:1
0x00800000 /uImage-kirkwood;bootm 0x00800000 0x01100000'

saveenv
reset

Note that I setup the mtdparts for flashing the NAND with the kernel and
initrd, but I haven't done that part ..yet.

I'm running -current on it. There are a few curiosities. I reformatted
the disks, because they were GPT and uBoot doesn't do GPT.  Clearly, the
modified debian kernel and initrd in flash mounted the RAID on GPT, but
that seemed entirely too precarious to mess with for a first
installation.  I followed the suggestions on the ARMEDSlackware
installation, with the exception that I made a fourth partition setup as
RAID-1 for storing data. 

The slackware installer recognizes and starts my RAID drives, but the
installed kernel and initrd do not, and give the following error:

from dmesg

[   27.885568] mdadm: sending ioctl 1261 to a partition!
[   27.891016] mdadm: sending ioctl 1261 to a partition!
[   27.896092] mdadm: sending ioctl 1261 to a partition!
[   27.968245] md: md0 stopped.
[   27.981895] md: bind<sdb4>
[   27.999198] md: bind<sda4>
[   28.056769] bio: create slab <bio-1> at 1
[   28.079794] md: personality for level 1 is not loaded!

from mdadm -D /dev/md0 
State : active, Not Started

whereas the installer dmesg states:

[   25.321046] mdadm: sending ioctl 1261 to a partition!
[   25.321065] mdadm: sending ioctl 1261 to a partition!
[   25.324330] mdadm: sending ioctl 1261 to a partition!
[   25.324348] mdadm: sending ioctl 1261 to a partition!
[   25.778956] md: bind<sda4>
[   25.813034] md: bind<sdb4>
[   25.830783] md: raid1 personality registered for level 1
[   25.831386] bio: create slab <bio-1> at 1
[   25.831633] md/raid1:md127: active with 2 out of 2 mirrors
[   25.831768] md127: detected capacity change from 0 to 977827812352
[   25.851975]  md127: unknown partition table
[   26.155539] md127: detected capacity change from 977827812352 to 0
[   26.155562] md: md127 stopped.
[   26.155582] md: unbind<sdb4>
[   26.155638] md: export_rdev(sdb4)
[   26.155795] md: unbind<sda4>
[   26.156905] md: export_rdev(sda4)
[   26.251771] md: md0 stopped.
[   26.267501] md: bind<sdb4>
[   26.272242] md: bind<sda4>
[   26.298228] bio: create slab <bio-1> at 1
[   26.298693] md/raid1:md0: active with 2 out of 2 mirrors
[   26.298828] md0: detected capacity change from 0 to 977827812352
[   26.306706]  md0: unknown partition table

and the mdadm -D /dev/md0 
State : clean

Any suggestions as to why the raid1 personality is missing from the
installed kernel would be greatly appreciated.  

Anyone else here have one of these things?