Re: Debian on SS400-E
chris wilkinson wrote on 20110325:
> H <hans <at> lambermont.dyndns.org> writes:
> > I've installed Debian on my NAS and I'm very happy with it. The device
> > is now finally functioning as it should have from the beginning, feature
> > wise that is, as others have noted performance is sad but that's no real
> > issue to me.
>
> Sounds like you suceeded to do what I'd like to do, i.e. install Debian
> alongside, without destroying the NAS functions.
>
> Would you be able to summarize the steps you followed?
Sure;
First build yourself a serial cable, you need this for the redboot
prompt part : http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable
Test that it is working.
Then i basically followed
http://d-i.alioth.debian.org/manual/en.armel/ch05s01.html#boot-firmware-ss4000e
I used a kernel from
http://people.debian.org/~joeyh/d-i/armel/images/20101212-11:26/iop32x/network-console/ss4000e/
but that link is unavailable now.
The ss4000e/ directory seems gone from
http://people.debian.org/~joeyh/d-i/armel/images/daily/iop32x/network-console/
anyone ?
I used the minicom telix port instead of cu to upload the kernel, but that's details.
My disks are 3x 1TB and 1x 2TB, I used this layout :
20101224_142707 root@stor:/etc/init.d/ fdisk /dev/sda
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000053b1
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 19531775 9764864 83 Linux
/dev/sda2 19531776 21485567 976896 82 Linux swap / Solaris
/dev/sda3 21485568 1953520064 966017248+ 83 Linux
with an extra slice for the 2TB disk.
Note that Debian is installed only on /dev/sda1 , so that disk is
required for the system to boot. I'd like to use a quad-mirror here but
have not found a way to make this work.
After installation i used this :
RedBoot> fconfig boot_script_data
boot_script_data:
.. load ramdisk.gz
.. load zImage
.. exec
Enter script, terminate with empty line
>> fis load -b 0x0180000 ramdisk.gz
fis load -b 0x0100800 zImage
exec -c "console=ttyS0,115200 rw root=/dev/md0 mem=256M@0xa0000000" -r 0x01800000
(empty line)
to no longer need the serial link and redboot commands to boot.
Now i could use badblocks (ipstor did not have that) and more
importantly: smartmontools which ipstor also did not have (absurd).
I used mdadm to set up a raid5 over 3 1TB disks and 1 2TB disk (that
disk has another TB available).
mdadm --create /dev/md0 --chunk=512 --metadata=1.2 --level=5 --raid-devices=4 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
This gives 2.7TB available space.
-- Hans
Reply to: