🚀 go-pugleaf

"alex" <ntnewsNOSPAM@hrz3.hrz.tu-darmstadt.de> writes:

>> So, if mkraid tells you to look at the syslog and mdstat, what
>> messages do they contain?
>nothing :-((( i've done a cat /proc/mdstat - nothing inside...

Uh oh. Do you have built your own kernel? I see currently the
following possible reasons for your failure:
- You have either not compiled-in raid 1 support into the kernel or you
  have not loaded the module. If you are working with modules, try
  "modprobe raid1" to load the module.
- You have already mounted the partition you want to add to the
  raid. This does not work!

>> >> Afterwards you create the file systems on the raid devices.
>> >after axecuting mkraid???
>> Yes, afterwards!
>hm. you mean teh filesystem on md0 or? not hdb1 and so on? sorry but i'm a
>newbie in linux...

On md0 and the others. When your raid is running (mdstat must tell you
so), then you run "mke2fs /dev/md0" or any other filesystem you want
to use.

The partition type fd for raid is set via fdisk. E.g. fdisk /dev/hda
and then change the type their. This is only necessary, if you want to
boot from the raid or simply want to have it started automatically at
boot. Again, this either requires compiled raid 1 support or the
module being loaded upon boot.

Andreas
-- 
Fraunhofer FOKUS        \  mailto:zisowsky@fokus.fhg.de (AOL banned)
Andreas Zisowsky         \ mailto:zisi@cs.tu-berlin.de
Kaiserin-Augusta-Allee 31 \ phone: +49-30-3463-7262  fax: -8262
10589 Berlin, Germany      \ http://www.fokus.fhg.de/usr/zisowsky