> someone out there correct me if i am wrong, but from looking at my
boxes:
[big snip]
> allan
Ok, now it's clear.
I need to patch my kernel. =)
I fount a patch here: http://people.redhat.com/mingo/raid-patch
But, another question, so theresn't any problem running a
raid on the same d
Perhaps it would help to put some version information in the proc
file? A raid-md version or something? It seems that most people's
troubles are related to not being able to confirm if they really were
able to patch, build, and install the kernel properly.
Just my $.02.
Phil
On Thu, Mar 23,
At 04:25 PM 3/23/2000, James Manning wrote:
>[flag]
> > And if I get the same msg when I try to build a raid 0? (my kernel
> > is RAID patched: 2.2.14)
> >
> > [flag@Luxor flag]$ cat /proc/mdstat
> > Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
> > read_ahead not set
> > md0 : inactive
[flag]
> And if I get the same msg when I try to build a raid 0? (my kernel
> is RAID patched: 2.2.14)
>
> [flag@Luxor flag]$ cat /proc/mdstat
> Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
alla
someone out there correct me if i am wrong, but from looking at my boxes:
raid 0.4x (which comes stock in the 2.2.x series of kernels)
has a /proc/mdstat that looks like this:
[root@finch root]$ cat /proc/mdstat
Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
read_ahead not set
md0 : in
I got the same errors until I increased my chunk size to 32K
At 01:32 PM 3/23/2000, you wrote:
>On Thu, 23 Mar 2000, m. allan noah wrote:
>
> > > mkraid: aborted, see the syslog and /proc/mdstat for potential clues
>
>And if I get the same msg when I try to build a raid 0? (my kernel
>is RAID p
On Thu, 23 Mar 2000, m. allan noah wrote:
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues
And if I get the same msg when I try to build a raid 0? (my kernel
is RAID patched: 2.2.14)
[flag@Luxor flag]$ cat /proc/mdstat
Personalities : [1 linear] [2 raid0] [3 raid1] [4 r
"m.allan noah" wrote:
>
> instead, then you are running a patched kernel, and your problem must lie
> elsewhere (try recompiling the raid tools from source)
... and check if you installed the raidtools.rpm and not the
mdutils.rpm.
Marc
--
Marc Mutz <[EMAIL PROTECTED]>http://marc.mut
probably, you are not REALLY running a patched kernel.
if you
cat /proc/mdstat
and see stuff about /dev/md0 being 'inactive'
then you are running an unpatched kernel, need to check lilo and make sure the
new kernel is there. also check your patch for rejects and your config to have
raid built
Hello,
since two days (and nights) I try to get software RAID 0.90 running on
SuSE-Linux with a standard kernel 2.2.14 with an raid patch found at
.../mingus running.
I can try what I want, every time the following error appears:
mkraid: aborted, see the syslog and /proc/mdstat for potential cl
10 matches
Mail list logo
