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:
... 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?
Hi, I'm trying to accomplish the same thing : automatically mount a Windows raid volume (dynamic disk) at boot-up. The mdadm command you suggested works fine, but I haven't found any way to configure mdadm.conf.
Did you end up creating a bootscript?
|All times are GMT -5. The time now is 12:01 AM.|