DSM-G600, DNS-3xx and NSA-220 Hack Forum

ok.. here is what I did:

started with this:
ch3snas v1.04RC5 with
ffp 0.5, cleanboot 2.0.5 and bash (and some other stuff) installed.
raid1 is configured and synced after yet another "md: kicking non-fresh sdb2 from array!" issue.
"EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended" lines where present for:
sdb4, sda2 and sdb2.

I followed the instructions here:
http://www.inreto.de/dns323/fsck/

fscked sda4,sdb4 and md0

rebooted, and everything was ok:

Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1.  Priority:-2 extents:1
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
ext3: No journal on filesystem on sda2
ext3: No journal on filesystem on sdb2
md: md0 stopped.
md: md1 stopped.
192.168.5.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 192.168.5.255 on egiga0
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md0 active with 2 out of 2 mirrors
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4

(it makes me courious why sd[ab]4 are mounted twice and sd[ab]2 is mounted even if they are a raid1 devices. as far as I understand, linux software raid1 devices can be used as stand alone devices and so be mounted. but mounting them RW will destroy the raid1)

then I did some configuring, mean: creating some directories for actual storage purposes.

after the specified amount of time, the disks went to sleep as expected.

I used the open ssh session to enter the 'halt' command in order to turn the device off with cleanboot.
as soon as I hit enter both drives spun up (I saw the corresponding enties in /var/log/messages).
seconds later the ssh connection died.
it took quite a vew seconds until the powerled flashed and the device went off.
interesting detail: there where about 10 seconds of left hdd-led (sdb) flashing (right/sda-led was on) between the 'halt' command and the power-led flashing.

after I turned the device on again I had errors again:

Adding 530104k swap on /dev/sda1.  Priority:-1 extents:1
Adding 530104k swap on /dev/sdb1.  Priority:-2 extents:1
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
ext3: No journal on filesystem on sda2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
ext3: No journal on filesystem on sdb2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
md: md0 stopped.
md: md1 stopped.
md: md0 stopped.
md: bind<sdb2>
md: bind<sda2>
md: kicking non-fresh sdb2 from array!
md: unbind<sdb2>
md: export_rdev(sdb2)
raid1: raid set md0 active with 1 out of 2 mirrors
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
ext3: No journal on filesystem on sda4
ext3: No journal on filesystem on sdb4
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

and this is where I am now.. without an idea what to do (expect: never turn the device off)
syncing the array takes about 3 hours (1TB disks), so experimenting is rather time expensive.

cleanboot 2.0.5 downloaded from:
http://dns323.kood.org/forum/p18200-200 … tml#p18200

every bit of help would be appreciated