🚀 go-pugleaf

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

>handling MD device /dev/md0
>analyzing super-block
>disk 0: /dev/hda1, 24066kB, raid superblock at 24000kB
>mkraid: aborted, see the syslog and /proc/mdstat for potential clues.

>the errors are from mkraid /dev/md0  (you can see in the error - md0)

So, if mkraid tells you to look at the syslog and mdstat, what
messages do they contain?

>> Afterwards you create the file systems on the raid devices.
>after axecuting mkraid???

Yes, afterwards!

>> Basically it is better to use the swap partions separately instead of
>> keeping them within a raid. The RAID-Howto is quite helpful.
>i've tried this... suxxx. cannot get it working... any idea?

Maybe you had an old one. Try
http://unthought.net/Software-RAID.HOWTO/

I did it a bit different then you, since I wanted an automatic
discovery of the raid at boot time. So I enabled persistent-superblock
1 in raidtab and set the partition types to fd.

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