On 5/8/07, Orlando Andico <[EMAIL PROTECTED]> wrote:
putting /boot on a raid partition is difficult.
because the kernel is loaded from the /boot partition. but the raid
driver code is inside the kernel. so how can you load the kernel if
you can't read the raid volume?
that said there are ways around it. but they are not straightforward.
the easiest scheme is to use hardware raid. that's what all the
business-critical folks do anyway. very few people use software raid
for mission-critical applications.
create a small hardware raid partition for boot. 500 mb is fine. thats
what i do. but make sure your kernel has hardware raid support
builtin. or else you have to boot with initramfs
i dont use hardware raid because it is much slower than software raid.
and it willingly replicates filesystem blocks with errors. since the
boot partition is mostly read only thats fine.
On 5/8/07, Hazel Lopez <[EMAIL PROTECTED]> wrote:
> That would mean, I would leave a /boot partition on any of the disks?
> But that wouldn't it undermine the purpose of having raid1 at all? My
> machine ought to run via any one of the disks that have the filesystem on,
> right?
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
--
the thing i like with my linux pc is that i can sum up my complaints in 5 items
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
