> -Original Message-
> From: Werner Reisberger [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 15, 2000 8:47 AM
> To: [EMAIL PROTECTED]
> Subject: mkraid aborted - no clue
>
>
> I just started the first time to use raidtools, wanted to
> create a RAID 1
&
super-block
disk 0: /dev/sdb13, 2056288kB, raid superblock at 2056192kB
disk 1: /dev/sdc13, 2056288kB, raid superblock at 2056192kB
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
I didn't find any clues in syslog or other log files and this is in
/proc/m
lude/linux/raid/ is now detected
> > and that this message is okay and can be ignored? Thanks.
>
> Very safe to ignore :) patches just don't have a very effective
> way of getting across the concept of "delete this file" :)
>
> James
Roger that. Thanks. I
[ Thursday, February 10, 2000 ] Alan T. Malek wrote:
> I grabbed the patch and applied which seemed to go okay. Now when I
> compile I get this message.
>
> /usr/src/linux-2.2.14/include/asm/md.h is empty
> /usr/src/linux-2.2.14/include/linux/md.h is empty
> /usr/src/linux-2.2.14/include/linux/r
I grabbed the patch and applied which seemed to go okay. Now when I
compile I get this message.
# make dep
make[1]: Entering directory `/usr/src/linux-2.2.14/arch/i386/boot'
make[1]: Nothing to be done for `dep'.
make[1]: Leaving directory `/usr/src/linux-2.2.14/arch/i386/boot'
scripts/mkdep ini
Gregory Leblanc wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > -Original Message-
> > From: Alan T. Malek [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, February 09, 2000 10:34 AM
> > To: Gregory Leblanc
> > Subject: Re: mk
James Manning wrote:
>
> [ Wednesday, February 9, 2000 ] Alan T. Malek wrote:
> > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
> >
> > Any suggestions?
>
> Yeah, send us anything that showed up in syslog and the contents
> of /proc/mdst
[ Wednesday, February 9, 2000 ] Alan T. Malek wrote:
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> Any suggestions?
Yeah, send us anything that showed up in syslog and the contents
of /proc/mdstat
You'll need to patch your kernel to include support for the 0.90 series raid
code. RedHat 6.0 ships with raidtools-0.90.
Greg
1026599kB, raid superblock at 1026496kB
/dev/sda1 appears to be already part of a raid array -- use -f to
force the destruction of the old superblock
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
# /sbin/mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in
ollowing error
>ocures:
>
>DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
>handling MD device /dev/md0
>analyzing super-block
>disk 0: /dev/hda4, 8032kB, raid superblock at 7936kB
>disk 1: /dev/hdd2, 8032kB, raid superblock at 7936kB
>mkraid: aborte
lock at 7936kB
> disk 1: /dev/hdd2, 8032kB, raid superblock at 7936kB
> mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
>
> my /proc/mdstat looks like:
> Personalities : [3 raid1]
> read_ahead not set
> md0 : inactive
> md1 : inactive
>
raid superblock at 7936kB
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
my /proc/mdstat looks like:
Personalities : [3 raid1]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
and /var/log/syslog says no
(0kB)
mkraid aborted
Please note I have good reasons to use this combination of kernel and tools and
that using exactly the same procedure, md0 and md1 were created with no
problems.
Any suggestions???
TIA
Alex
, Fax/Data: +49 6257 83037
> SWB - The Software Brewery - | http://www.swb.de/ | Anime no Otaku
Hope this helps.
Cheers,
Bruno Prior [EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Matt Shirel
> Sent:
almost 500 miles back home, server2 is giving the following error when we try to
mkraid on the root partition (the last remaining partition standing between us
and a suscessful build):
DESTROYING the contents of /dev/md1 in 5 seconds, Ctrl-C if unsure!
/dev/md1: active -- run raidstop
mkrai
I have two 9GB SCSI drives on one controller on a
Red Hat 6.0 server.
My partition table is the following:
sda1 boot Primary
ext2 size of
partitionsda5 Logical
ext2sda6 Logical swapDisc
#2sdb1 Logical
ext2 size of
partitionsdb5 Logical
ext2sdb6 Logical sw
On Fri, Aug 27, 1999 at 05:52:22PM -0400, esl wrote:
> I updated my kernel from the stock 2.2.5-15 (RedHat 6.0) to 2.2.11. I
> did not use modules for raid etc.
sotck and redhat are a contaddiction in terms
the redhat kernel is heavily patched
it also happens to include raid pathches that are not
f unsure!
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/sdb1, 8886256kB, raid superblock at 8886144kB
> disk 1: /dev/sdc1, 8891376kB, raid superblock at 8891264kB
> mkraid: aborted
When I've seen, this, I've *typically* seen some helpful kernel output.
nsure!
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb1, 8886256kB, raid superblock at 8886144kB
disk 1: /dev/sdc1, 8891376kB, raid superblock at 8891264kB
mkraid: aborted
Thanks for any assistance.
E. L.
yzing super-block
disk 0: /dev/sdb6, 411547kB, raid superblock at 411456kB
disk 1: /dev/sdc8, 408586kB, raid superblock at 408512kB
mkraid: aborted
[root@garfield ~]#
My /etc/raidtab is the following:
[root@garfield ~]# cat /etc/raidtab
raiddev /dev/md0
raid-level
Hi all,
I'm running Red Hat 6.0 + updates and "2.3.3ac3+efs1.0b" = 2.3.3 with
Alan Cox's patch #3, and efs 1.0b (so I can read SGI CDs in my CD
drive). I was having problems that mkraid from the Red Hat 6.0
raidtools-0.90-3.i386.rpm that even with the right force arg, mkraid
still aborted.
Afte
On 11 Jun 1999, Osma Ahvenlampi wrote:
>
> You have to patch 2.2 to get full raidtools 0.90 level
> functionality. However, Red Hat 6.0 kernels have the correct patch
> applied by default. If you stick with Red Hat's kernel (or build your
> kernel from Red Hat's kernel-source RPM), you'll be fin
Gerben Welter <[EMAIL PROTECTED]> writes:
> On Fri, 11 Jun 1999, Mark Beck wrote:
> > Im having problems setting up RAID 0 on my box. Its running Redhat 6 with
> > latest kernel.
Latest Linux kernel, or latest Red Hat distributed kernel?
> But i'm also confused about another thing since i've re
eally-force
> > DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/hda1, 24989076kB, raid superblock at 24988992kB
> > disk 1: /dev/hdb1, 24989076kB, raid superblock at 24988992kB
B
> disk 1: /dev/hdb1, 24989076kB, raid superblock at 24988992kB
> mkraid: aborted
That's my exact problem. Someone else suggested to take a look in the
logs, but i can't find find anything there either :(
But i'm also confused about another thing since i've read cont
ock at 24988992kB
mkraid: aborted
No information can be found in the System logs.
mkraid version 0.90.0
Linux lisc0002.rrds.co.uk 2.2.9 #5 Wed Jun 9 15:48:15 BST 1999 i686 unknown
Any help appreciated.
Mark Beck
Well I got 2 messages from people with same question:
did ya make /dev/md0?
Well.. I did 8-(
#ls -l /dev/md0
crw-rw 1 root disk 9, 0 Jul 21 1998 /dev/md0
#lsmod
Module SizeUsed By
raid1 63040 (unused)
#uname -a
Linux ha1 2.2.6 #1 Tue Jun 1 10:53:09 CEST 1
>
> What setup ?
> How big are the partitions ?
>
Raid level 1, partitions of 710Meg
further more I hacked trough the code and came to the conclusion that it
crashed on (yes, it's true) -->>> /dev/md0: Invalid Argument
And again: modules are loaded, patch is loaded, using 0.90 and 2.2.6
GreeT
OK, Now I really go mad:
I've got the descructive problem of mkraid going to abort without leaving any
hints in syslog / mdstat..
I'm working with the linux 2.2.6 kernel AND did the patch
raid0145-19990421-2.2.6 AND have raid-0.90-19990421-2.2.6 installed
I couldn't find any other hints in the
/sdc5, 8883882kB, raid superblock at 8883776kB
disk 1: /dev/sda5, 8883882kB, raid superblock at 8883776kB
disk 2: /dev/sdb5, 8883882kB, raid superblock at 8883776kB
mkraid: aborted
There isnt any error reported in syslog.
Any help would be appreciated
Hi
Some suggestions/questions:
- Did you patch the kernel?
- If yes, try mkraid --really-force /dev/mdX
- Are you using the right raidtools (0.90)?
Greetings, Dietmar
>- Ursprüngliche Nachricht -
>Absender: [EMAIL PROTECTED]
>Betreff: mkraid: aborted
>Empfänger: [EMA
I am trying to do raid linear. I have a Sparc IPX running
RedHat Linux 2.2.5 (RedHat 6.0)
I have two 4 gig disks, with raidtab :
raiddev
/dev/md0
raid-level
linear
nr-raid-disks
2
persistent-superblock
1
device
/dev/sdj1
r
lt;[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 2. toukokuuta 1999 21:00
Subject: Re: mkraid: aborted???
>
>
>"so don't tell us it can't be done, putting down what you don't know.
>money isn't our god, integrity will free ou
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
On Sun, 2 May 1999, Anders Lindh wrote:
> mkraid: aborted
look in var/log/messages, also run dmesg
>
> The contents
disk 0: /dev/hda3, 7582680kB, raid superblock at 7582592kB
disk 1: /dev/hdc1, 9903568kB, raid superblock at 9903488kB
mkraid: aborted
The contents of /proc/mdstat remains the same after mkraid is done. I've
compiled my kernel (2.2.7 on a RedHat 6.0 box) with raid support (left
raid 1 support out
I'm all for a more informative error message than "mkraid aborted".
Other thoughts:
1) In the kernel "make menuconfig" help, point out that this code if for an
earlier/specific version of raidtools.
2) In the Raidtools ReadMe's, make it clearer that the 2.2.x
e who like the older tools?
I understood the current alpha code is scheduled for integration into
the base kernel soon. However, if the error diagnostics of the
raidtools were a bit better, we wouldn't have this question pop up all
the time. "mkraid aborted" doesn't tell any
Jason Speckman wrote:
> I have kernel 2.2.5 with raid 1 compiled in, raidtools 0.90. I
and Paul Witting wrote:
> both Dell 2300's with RedHat 5.2 installed. I have upgraded the kernel of
> this machine to 2.2.5, including RAID 0 and RAID1 support in that kernel. I
Sounds like both these guys we
ent: Tuesday, April 20, 1999 2:17 PM
> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: Raid 0 - mkraid aborted...
> >
> >
> > Have you done a "mkraid --really-force /dev/mdX" or just a "mkraid
> > /dev/mdX"?
> > Try the force
> both Dell 2300's with RedHat 5.2 installed. I have upgraded the kernel of
> this machine to 2.2.5, including RAID 0 and RAID1 support in that kernel. I
> downloaded the 3/7/99 version of Raidtools .90 and installed them.
Have you applied the "raid145" patch to the kernel ?
> When I try to mkra
id superblock at 36081856kB
> disk 2: /dev/sde1, 36081958kB, raid superblock at 36081856kB
> disk 3: /dev/sdf1, 36081958kB, raid superblock at 36081856kB
> disk 4: /dev/sdg1, 36081958kB, raid superblock at 36081856kB
> disk 5: /dev/sdh1, 36081958kB, raid superblock at 36081856kB
kB
disk 2: /dev/sde1, 36081958kB, raid superblock at 36081856kB
disk 3: /dev/sdf1, 36081958kB, raid superblock at 36081856kB
disk 4: /dev/sdg1, 36081958kB, raid superblock at 36081856kB
disk 5: /dev/sdh1, 36081958kB, raid superblock at 36081856kB
mkraid: aborted
[root@visitors raidtools-0.9
0
device /dev/sdc2
raid-disk 1
# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb2, 64260kB, raid superblock at 64192kB
disk 1: /dev/sdc2, 64260kB, raid superblock at 64192kB
mkraid: aborted
What's going on in
v/sdb1, 4441941kB, raid superblock at 4441856kB
> disk 1: /dec/sdc1, 8883913kB, raid superblock at 8883840kB
> mkraid: aborted
Is the raid01445-19990309-2.2.3.gz patch applied?
- Anyway, the HOWTO in raidtools-19990309-0.90.tar.gz is the most
uptodate - I think so.
Bye,
Robert
On Thu, 11 Feb 1999, Luca Berra wrote:
> the latest raid patch raid0145-19990128-2.2.0 is not included in kernel
> 2.2.1 the patch should apply to 2.2.1 with only one reject, which, i
> believe, can be safely ignored.
yep that reject is in mmap.c, which can be ignored. (the RAID patch simply
h
On Wed, Feb 10, 1999 at 07:10:56PM -0500, Stephen Hurrell wrote:
> I am using a linux 2.2.1 "stock" kernel from ftp.ca.kernel.org. I tried applying
> the latest raid0145 patch but it failed in many places so I assumed that it was
> already "rolled into 2.2.1". Is this correct? FYI: I tried the
no,
t; handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/sda3, 6417967kB, raid superblock at 6417856kB
> > disk 1: /dev/sdb4, 6417967kB, raid superblock at 6417856kB
> > disk 2: /dev/sdc4, 6417967kB, raid superblock at 6417856kB
> > mkraid: abor
17967kB, raid superblock at 6417856kB
> disk 2: /dev/sdc4, 6417967kB, raid superblock at 6417856kB
> mkraid: aborted
Is your kernel patched with a relevant raid0145-* patch? I've seen the "mkraid:
aborted" message when (by a mistake) rebooted to a stock kernel, su
6417856kB
mkraid: aborted
org04:~#cat /etc/raidtab
raiddev /dev/md0
raid-level 0# it's not obvious but this *must* be
# right after raiddev
persistent-superblock 1# set this to 1 if you want auto
I'm using the 0.50 tools and RAID works but the 2.0.38 kernel was never
patched. The tools did not contain any info that specifically stated that a
patch was needed and for the most part, the tools work and I can get raid
running. However I am starting to see some strange behaviour such as ckrai
, 8924144kB, raid superblock at 8924032kB
mkraid: aborted
If anyone can give advice, I would appreciate it.
TNX,
Godfrey N Nix C.Eng MBCS B.ScTech(Hons) Dip Ed.
Network Operations Manager
East Midlands Network Ltd (emnet)
phone 0115 956 8260
visit http://www.emnet.co.uk
52 matches
Mail list logo
