Hi, 

I got no secret and I am using kernel 2.0.36 on a SuSE 6.0 distribution (not the 
SuSE-kernel!!!); but I didn't want to offend you.
There were a lot of question this days starting with "... mkraid doesn't work ..." and 
most of the people forgot to add the force-option.
I set up raid0145-19990309 on a P166 and P200MMX, both are single processor machines 
containing an AHA2940. I patched the kernel, did a menuconfig and enabling the 
raid-options, recompiled it and started the machine again. Building the raidtools 0.90 
was no problem and I set up the raid by using one of the raidtab samples. After all I 
did a mke2fs /dev/md0, but I am not sure, if that is necessary.
The only problem I got is setting up the same raidtools on a SMP machine, both 
processors running (compilation of the kernel fails), but using only one works.
That's all. I hope this helps.

Greetings, Dietmar

>----- Urspr�ngliche Nachricht -----
>Absender: [EMAIL PROTECTED]
>Betreff: Re: Can't get started with raid 1
>Empf�nger: [EMAIL PROTECTED]
>Kopie-Empf�nger: [EMAIL PROTECTED]
>Datum: 13. Apr 1999 15:50
>
> If you got 2.0.35, 36 or 2.2.3 or 2.2.5 of slackware to work (I'm using the
> v36 cdrom for the rest of the system), then please tell me your secret.
> How did you get it set up?  So far as the force switch goes, don't you
> think that if I went to the trouble of running strace, patching mkraid,
> building with serveral kernels, that I didn't trying several forms of
> rebuilding the disks?  Including making structures to force the need of the
> switch?  ;-)
> 
> Yeah, I tried a bunch of stuff -- I'm looking for someone who actually has
> it working and can tell me how to start from one of these kernels and
> really make it start.  But thanks for the thought -- Joe B.
> 
> At 05:35 AM 4/13/99 GMT, [EMAIL PROTECTED] wrote:
> >If your command line really was "mkraid /dev/md0" try "mkraid
> --really-force /dev/md0".
> >A message like "All data on /dev/md0 will be destroyed..." will be given
> and after a few seconds the raid will be initialized.
> >Seems that noone read the manpage of mkraid or the readme of the 0.90
> raidtools.
> >
> >Greetings, Dietmar
> >
> >>----- Urspr�ngliche Nachricht -----
> >>Absender: [EMAIL PROTECTED]
> >>Betreff: Can't get started with raid 1
> >>Empf�nger: [EMAIL PROTECTED]
> >>Datum: 13. Apr 1999 00:45
> >>
> >> I built 2.2.5 (and 2.2.3, and 2.0.35 and 2.0.36) and am having no luck
> >> getting started.  With 2.2.5 (no kernel patches -- can't find any that
> >> apply or can be applied -- in fact all patching of these kernels failed for
> >> me..??)  So, what am I doing wrong?  It must be something simple since I
> >> haven't even started yet, right???  Thanks for all help and suggestions!
> >> 
> >> -- Joe Beauchamp
> >> 
> >> mkraid /dev/md0
> >> 
> >> handling MD device /dev/md0
> >> analyzing super-block
> >> disk 0: /dev/hdb2, 1967962kB, raid superblock at 1967872kB
> >> disk 1: /dev/hdb3, 1911735kB, raid superblock at 1911616kB
> >> mkraid: aborted
> >> -------------------
> >> I keep getting this aborted -- the IOCTL fails...
> >> 
> >> strace shows:  (on slackware)
> >> 
> >> read(5, "/dev/hda1 / ext2 rw 0 0\n/dev/hd"..., 4096) = 75
> >> read(5, "", 4096)                       = 0
> >> close(5)                                = 0
> >> munmap(0x400ca000, 4096)                = 0
> >> _llseek(0x4, 0, 0x400, 0xbfffe730, 0)   = 0
> >> read(4, "\377\377\377\377\377\377\377\377"..., 1024) = 1024
> >> _llseek(0x4, 0, 0x74ad0000, 0xbfffe730, 0) = 0
> >> read(4, "\232\303\f\335\353\32.\356u\10H5"..., 4096) = 4096
> >> close(4)                                = 0
> >> open("/dev/md0", O_RDONLY)              = 4
> >> ioctl(4, 0x40480923, 0x804f758)         = -1 EINVAL (Invalid argument)
> >> write(2, "mkraid: aborted\n", 16mkraid: aborted
> >> )       = 16
> >> close(3)                                = 0
> >> munmap(0x40008000, 4096)                = 0
> >> _exit(1)                                = ?
> >> ---------------------------------------------
> >> /etc/raidtab is:
> >> 
> >> # Sample raid-1 configuration
> >> raiddev                 /dev/md0
> >> raid-level              1
> >> nr-raid-disks           2
> >> nr-spare-disks          0
> >> chunk-size              4
> >> persistent-superblock   1    # set this to 1 if you want autostart,
> >> 
> >> device                  /dev/hdb2
> >> raid-disk               0
> >> 
> >> device                  /dev/hdb3
> >> raid-disk               1
> >> 
> >> 
> >> ___________________________________________________________________
> >>  Joe Beauchamp -- CIO, Interactive Commerce Group -- (610) 768-1444
> >> 
> >
> >
> ___________________________________________________________________
>  Joe Beauchamp -- CIO, Interactive Commerce Group -- (610) 768-1444
> 

Reply via email to