Re: intel fakeraid (imsm) linux kernel support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 17, 2010 at 9:19 AM, K. Posern <quickhelp@xxxxxxxxx> wrote:
> Hi all,
>
> I am trying to find out if it is possible to:
>
>        a) Have the linux kernel autodetect / auto-assemble the fakeraid (to
> avoid having an initrd (for speed and KISS))
>
>        b) Boot linux kernel from a fakeraid this: grub2? lilo? ... anything?

Hi, I think I answered these in my other response:

http://marc.info/?l=linux-raid&m=128206374710903&w=2

...but you specifically ask about partition-type-0xfd below:

[..]
> Side-Question:
> To be able to have the kernel auto-assemble / autodetect any [e.g. mdadm]
> linux software RAID-0 you need *partions*, right?

You need partitions and the v0.90 metadata format.

> --> You can't assemble a software raid-0 using two complete drives:

You can, but not if you want to autodetect it.  But just use an initrd
and be happy :-)

>        /dev/sda
>        /dev/sdb
> But you need to create e.g.:
>        /dev/sda1 <<< type set to FD
>        /dev/sdb1 <<< type set to FD
>
>
> It would be great and very kind if someone could clarify these things for me
> (just a link to read the answers somewhere would work too ;).
> Thanks a lot!

One of the biggest differences between the native-md (0.90 and 1.x)
formats and external (imsm and ddf) formats, is that the latter only
use complete drives.  For example if you wanted two raid0 arrays on
the same set of disks using a native-md format you would need to
partition the disks first and then:

mdadm -C /dev/md0 /dev/sd[a-d]1 -n 4 - l 0
mdadm -C /dev/md1 /dev/sd[a-d]2 -n 4 -l 0

...with the external formats you create a container of disks and then
carve multiple volumes out of that set:
mdadm -C /dev/md/imsm /dev/sd[a-d] -n 4 -e imsm # create an imsm container
mdadm -C /dev/md0 /dev/md/imsm -n 4 -l 0 -z $size # create a raid0
array in the container
mdadm -C /dev/md1 /dev/md/imsm -n 4 -l 0 # use the remaining space for
a second raid0 volume

The bios (on an enabled platform) will see /dev/md0 and /dev/md1 as
bootable devices, not the individual component disks (/dev/sd[a-d]).

--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux