LinuxQuestions.org - MD3 MD5 not mountable in mdadm.conf because they need --chunk=64?

(Just realized I posted in software instead of hardware. Could a mod please move this for me?)

I need to dual boot windows, and I'd rather not use fakeraid, so I set up 'Dynamic Disks' (Windows LDM). Since I know I can access Windows Partitions from linux (and not vice versa), I allocated most of my space to Windows. My master plan is to mount certain subdirectories under WinHome, like Videos, Pictures, Documents, etc. in my Linux ~ dir.

Now I'd like to know the best way to have the Windows arrays built and mounted on boot.

My first thought was to define the array in mdadm.conf and mount it in fstab.

In case you've never mounted an LDM array before here's a brief explanation:

I can access LDM arrays using mdadm almost like linux md arrays. Whereas I would manually assemble a normal array like this:

Code:

$ sudo mdadm --assemble /dev/md1 /dev/sda1 /dev/sdb1

... for windows LDM I need to do this:

Code:

$ sudo mdadm --build /dev/md5 --level=0 --raid-devices=2 --chunk=64 /dev/sda5 /dev/sdb5

I think part of the problem is that these arrays are not detected like the other ones...

Code:

$ sudo mdadm --examine --scan

ARRAY /dev/md1 level=raid0 num-devices=2 UUID=8ba27b73:30f46af6:6ecc3f5a:4d5e8e6f

ARRAY /dev/md2 level=raid0 num-devices=2 UUID=8f816ea9:4a2b888e:31083c3d:065e9ccc

ARRAY /dev/md3 level=raid0 num-devices=2 UUID=245f721f:5b6227f1:7fc28c5b:61afe93c

ARRAY /dev/md4 level=raid1 num-devices=2 UUID=936abe86:d6c1079f:5750b10f:c0a9e549

ARRAY /dev/md6 level=raid1 num-devices=2 UUID=8d853f66:7527ccfd:8dcab72e:69517e00

(notice no MD3 or md5)

... and while I can define a level and number of devices in mdadm.comf (as per the manpage), there is no way to define a chunk size.

So I guess mdadm.conf + fstab is not the way to go here. Is it?

What are the alternatives? Should I just stick the "mdadm --build"s and "ntfs-3g"s in a bootscript somewhere, or something along those lines?