On Thursday June 15, [EMAIL PROTECTED] wrote:
I am getting the same error as eric did you find a solution to the problem
Apply the following patch to 2.4.0-test1-ac18 or later.
Ingo: could you pease add this to your tree?
The problem occurs if you try to mkraid an array for that some
On Thu, Jun 08, 2000 at 01:14:47PM +1000, Neil Brown wrote:
Hmmm. works for me.
hello, i have a similar problem but a different bug
Linux version 2.4.0-test1-ac12 (root@Moskowskaya) (gcc driver version pgcc-2.95.2
19991024 (release) executing gcc version egcs-2.91.66) #1 Sat Jun 10 20:00:52
with a complaint about a bug in asm/semaphore.h line 185 (magic
number mismatch). If I #undef WAITQUEUE_DEBUG in asm/semaphore.h (which
checks the magic number), mkraid complains: /dev/md0: Invalid argument.
Does MD work on 2.4.0-test1? Am I using the right tools? Is there
someting I am missing
device /dev/sdc1
raid-disk 1
device /dev/sdd1
raid-disk 2
/proc/mdstat:
Personalities : [4 raid5]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
mkraid /dev/md0:
handling MD
185 (magic
number mismatch). If I #undef WAITQUEUE_DEBUG in asm/semaphore.h (which
checks the magic number), mkraid complains: /dev/md0: Invalid argument.
Does MD work on 2.4.0-test1? Am I using the right tools? Is there
someting I am missing?
--
Erik Petersen
[EMAIL PROTECTED]
identical 17Gb
partitions on two disks, each of which is a master on the
ATA66 channels (the disks work fine on their own). The kernel has md
support, as well as all raid levels, built-in.
Here is the output of "mkraid"
----
mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
di
the failure, and
/proc/mdstat looks as it did before "mkraid" was run:
cat /proc/mdstat
Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
-
[...]
--
Philip Edelbrock -- IS Manag
On Tue, 2 May 2000, Jeff Fookson wrote:
I'm having problems configuring a 2-disk RAID-1 array on an i686
machine. The machine has Redhat 6.2 installed
cat /proc/mdstat
Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
read_ahead not set
md0 : inactive
md1 : inactive
ice, /dev/md0.
Here are the steps:
a) ;;specify /dev/hdc8 as failed-disk.
;; make sure both constituent partitions (/dev/hda8
and /dev/hdc8) are not mounted.
mkraid --really-force /dev/md0.
(the message will say /dev/hdc8 is a failed disk)
;; /proc/mdstat should indicate raid1 is run
I am trying to make a software raid5, and it seems no matter what I do
mkraid aborts.
My mkraid output looks like this:
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hde2, 5269320kB, raid superblock at 5269248kB
disk 1: /dev/hdf2, 5269320kB, raid superblock at 5269248kB
disk 2
is smaller than the physical partition. This is why you MUST use
mke2fs on the raid device; you CAN NOT reuse the pre-existing filesystem
from one of the physical partitions for the raid device.
a) ;;specify /dev/hdc8 as failed-disk.
mkraid /dev/md0.
(the message will say /dev/hdc8 is a failed
]
Subject: PLEASE HELP: mkraid aborts!
I am trying to make a software raid5, and it seems no matter what I do
mkraid aborts.
My mkraid output looks like this:
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hde2, 5269320kB, raid superblock at 5269248kB
disk 1: /dev/hdf2
Hi collist guy:
I put some data files in /dev/hda8 and leave /dev/hdc8
empty. After issuing mkraid it doesn't seem to sync
hdc8 to hda8, which is specified as failed-disk.
After mkraid, I am expecting /dev/hdc8 to have the
same data as /dev/hda8. Am I missing any assumption?
Thanks.
Jason
On Mon, 17 Apr 2000, Jason Lin wrote:
Hi collist guy:
I put some data files in /dev/hda8 and leave /dev/hdc8
empty. After issuing mkraid it doesn't seem to sync
hdc8 to hda8, which is specified as failed-disk.
After mkraid, I am expecting /dev/hdc8 to have the
same data as /dev/hda8
-mails back and forth, I believe there
are two ways:(although they are pretty similar)
Assmuming /dev/hda7 contains the needed data and
/dev/hdc8 is 2nd partition. We want to make a raid1
device /dev/md0 on top of /dev/hda8 and /dev/hdc8.
a) ;;specify /dev/hdc8 as failed-disk.
mkraid /dev/md0
-Original Message-
From: Jason Lin [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 17, 2000 12:11 PM
To: The coolest guy you know; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mkraid /dev/md0;; appears to have ext2 filesystem...
Hi everyone:
I think I got a better
I just started the first time to use raidtools, wanted to create a RAID 1
device. The mkraid command aborted with the following message:
machine:~# mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing
-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
device. The mkraid command aborted
mkraid /dev/md0
But I get md2 running instead of md0.
Does anyone know why and how to fix it?
Thanks.
Jason
[root@hostb120 /root]# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hdc6[1] hda6[0] 3028096 blocks
[2/2] [UU]
unused devices: none
[root
/mdstat to make sure that no raids are running. then run
mkraid --really-force /dev/md0
then change the partition types back to fd.
reboot.
good luck.
allan
Jason Lin [EMAIL PROTECTED] said:
mkraid /dev/md0
But I get md2 running instead of md0.
Does anyone know why and how to fix
Hi there:
Appreciate all the replies I got. One more question.
[root@hostb120 /]# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hda7, 514048kB, raid superblock at
513984kB
/dev/hda7 appears to contain an ext2 filesystem -- use
-f to override
mkraid: aborted
Jason Lin wrote:
I don't want to loose the data in /dev/hda7, so
mkraid --really-force /dev/md0 is not a right thing to
do.
What should I do with this problem?
Thanks.
Jason
cat /etc/raidtab
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr
Hey folx,
I'm trying to get mkraid to work on a TurboLinux server. I downloaded, what I think
is the most recent version of the mkraid utils.
raidtools-19990824-0.90.tar.gz
My kernel is
2.2.14-3
I eventually got the stuff to compile and it worked "better" than the shippi
, and if mr cox has
his way, it will finally be in the main kernel.
as such, i feel it is time to rename the --really-force command from mkraid to
--force. to leave as-is, is just great ammunition for those who would slight
the efforts of the developers as incomplete or amaturish.
people know
fprintf(stderr, "cannot determine md version: %s\n", strerror(errno));
- return EXIT_FAILURE;
-}
-
-if (old_force_flag (func == mkraid)) {
- fprintf(stderr,
-
-"--force and the new RAID 0.90 hot-add/hot-remove functionality should be\n"
-" used with extre
[ Wednesday, March 15, 2000 ] root wrote:
mkraid --**-force /dev/md0
/me attempts to get the Stupid Idea Of The Month award
Motivation: trying to keep the Sekret Flag a secret is a failed effort
(the number of linux-raid archives, esp. those that are searchable, make
this a given
How about --force / -f look for $HOME/.md_force_warning_read and
if not exists:
- print huge warning (and beep thousands of times as desired)
- creat()/close() the file
how about an expiration on the timestamp on this file
ie: if the time is longer than 2 weeks make them read it again.
I
Hi,
In my kernel I did only include the module for raid-1. Then, when I try
to create a raid-5 system it doesn't work:
[flobbe@pio flobbe]# mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hdd2, 504000kB, raid superblock at 503936kB
disk 1: /dev/hdd3, 504000kB
[ Friday, March 3, 2000 ] Sander Flobbe wrote:
In my kernel I did only include the module for raid-1. Then, when I try
to create a raid-5 system it doesn't work:
Okay, okay, my fault... but a tiny little cute hint about my mistake
from mkraid would be nice, wouldn't it? :*)
also nice
mkraid would be nice, wouldn't it? :*)
also nice would be your raidtab contents, /proc/mdstat output, syslog
messages, kernel version, patch used, raidtools used, etc, etc, etc
Wow, I *really* needed some sleep *sigh* I can't even blame the
crack since I quit last week. :) really, I did.. I
and looked, everyone seems to have this problem but there
are no answers available
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/hdc1, 1854688kB, raid superblock at 1854592kB
disk 1: /dev/hdc2, 1915200kB, raid superblock at 1915136kB
mkraid: aborted, see the syslog and /proc
? 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 went on and recompiled and bam...no more mkraid
aborted. Many thanks to everybody!!!
--
Alan T. Malek
Systems Programmer,
indiviudally, so I know they're okay. When I issue mkraid,
however, I get the following (I've seen many references to this in the
new groups, but most were in languages I could not understand :-)
# /sbin/mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sda1, 1026599kB, raid
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
[ 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 :)
As a heads
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/mdstat :)
As a heads-up, if your mdstat has
On Mon, Feb 07, 2000 at 03:13:32PM +, Carl L. Roy wrote:
I have just installed Mandrake 6.1 with mkraid version 0.90.0. The
Linux kernel that I am running is version 2.2.13-7mdk. When I attempt
download the kernel update from the mandrake ftp site
L.
--
Luca Berra -- [EMAIL PROTECTED
Hi !
I did install the raid like it is described at
http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ with patch and latest
raid-tools. After editing /etc/raidtab like sample with raid1
I do:
# mkraid /dev/md0
disk 0: /dev/sdb1, 8956209kB, raid superblock at 8956209kB
disk 1: /dev/sdd1
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 07, 2000 11:07 AM
To: [EMAIL PROTECTED]
Subject: mkraid did not work !!
Hi !
I did install the raid like it is described at
http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ with patch
[ Monday, February 7, 2000 ] [EMAIL PROTECTED] wrote:
I did install the raid like it is described at
http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ with patch and latest
raid-tools. After editing /etc/raidtab like sample with raid1
I do:
# mkraid /dev/md0
disk 0: /dev/sdb1
On Mon, 7 Feb 2000 [EMAIL PROTECTED] wrote:
Hi !
I did install the raid like it is described at
http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ with patch and latest
raid-tools. After editing /etc/raidtab like sample with raid1
Hi Peter,
Run dmesg and look for a line like 'autodetecting
-Original Message-
From: James Manning [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 07, 2000 11:21 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mkraid did not work !!
[ Monday, February 7, 2000 ] [EMAIL PROTECTED] wrote:
I did install the raid like
I have just installed Mandrake 6.1 with mkraid version 0.90.0. The
Linux kernel that I am running is version 2.2.13-7mdk. When I attempt
to run mkraid, it aborts without returning any useful information.
How can I get more information on the cause of my problem? Here is
some information about
-Original Message-
From: Carl L. Roy [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 07, 2000 7:14 AM
To: [EMAIL PROTECTED]
Subject: mkraid aborting without any useful information
I have just installed Mandrake 6.1 with mkraid version 0.90.0. The
Linux kernel that I am running
At 03:13 PM 2/7/2000 +, Carl L. Roy wrote:
I have just installed Mandrake 6.1 with mkraid version 0.90.0. The
Linux kernel that I am running is version 2.2.13-7mdk. When I attempt
to run mkraid, it aborts without returning any useful information.
How can I get more information on the cause
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 nothing
32kB, 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 sa
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: aborted, see the syslog and /proc/mdstat for potential clues
I'm running Mandrake 6.1 with a couple of 9GB IBM U2 SCSI Drives off of
an Adaptec 7890 controller. I've been trying for a while now (a couple
of days) to get several of the partitions on the drives to be RAID-1 .
However when I try and run mkraid I get the following
At 12:07 PM 12/30/1999 -0500, you wrote:
I'm running Mandrake 6.1 with a couple of 9GB IBM U2 SCSI Drives off of
an Adaptec 7890 controller. I've been trying for a while now (a couple
of days) to get several of the partitions on the drives to be RAID-1 .
However when I try and run mkraid I get
At 01:54 AM 12/31/1999 +0100, Luca Berra wrote:
You need to patch the kernel for the 0.9x raidtools. I believe Mandrake's
kernels are still at 0.4x and lower for kernel support, with 0.9x
raidtools
included (why they don't pre-patch the kernel source to support the
raidtools they
If you've got existing raid superblocks on at least one of the partitions
(because of your previous unsuccessful mkraid), this may be why mkraid throws up
a warning. Have you tried "mkraid --really-force"?
Cheers,
Bruno Prior [EMAIL PROTECTED]
-Original Message-
Fr
On Fri, 10 Dec 1999, Bruno Prior wrote:
Hi there,
If you've got existing raid superblocks on at least one of the partitions
(because of your previous unsuccessful mkraid), this may be why mkraid throws up
a warning. Have you tried "mkraid --really-force"?
And now to everybody: Sry,
: /dev/hda2, 9888007kB, raid superblock at 9887936kB
disk 1: /dev/hdc2, 9888007kB, raid superblock at 9887936kB
mkraid: aborted, see syslog and /proc/mdstat for potential clues.
---
stay clean
MD device /dev/md0
analyzing super-block
disk 0: /dev/hda2, 5124735kB, raid superblock at 5124608kB
disk 1: /dev/hdc2, 9888007kB, raid superblock at 9887936kB
mkraid: aborted, see syslog and /proc/mdstat for potential clues
I get the following message after doing mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sda1, 24066kB, raid superblock at 24000kB
/dev/sda1 is mounted
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
I am a little confused about how to set up
[mailto:[EMAIL PROTECTED]]On Behalf Of root
Sent: Monday, December 06, 1999 12:04 AM
I am a little confused about how to set up raid1.
I want to mirror /dev/sda to /dev/sdb (two 9 gig SCSI disks)
The example says to have raidtab say /dev/sda1 and /dev/sdb1
Does this mirror the whole disk,
even know why i tried this)
Ive got heaps of memory free but only 1MB of space available on the
local filesystem.
At the stage im trying to run mkraid /dev/md0 the root filesystem is
mounted on a loopback device (or ramdisk?).
Has anyone else experienced segfaults with mkraid ?
cat //p
Oh yea, one other thing.
When i run mkraid /dev/md0 i get the following
handling /dev/md0
analyzing super-block
disk0: /dev/hda3, 387072kB, raid superblock at 387008kB
Segmentation fault
Glenn McGrath wrote:
Hi.
Im trying to modify the debian install disks to be able to setup raid
from
mkraid fails complaining about the device being too small. Here's the details;
Using raidtools-0.50beta3 and 2.0.38 kernel with
/etc/raidtab;
raiddev /dev/md2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 128
device
already has that.
sincerely,
--
Florin Grad
(Technical Support Team)
[EMAIL PROTECTED]
--
From: Bill Carlson[SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, October 27, 1999 4:17 PM
To: [EMAIL PROTECTED]
Subject: mkraid aborts, no info?
Hello,
I'm trying
On Wed, 27 Oct 1999, Fernandez, Richard wrote:
Mandrake doesn't have RAID support built into the kernel AFAIK.
I was trying to do the same thing you're doing using Mandrake 6.0.
Below is an e-mail I received from Mandrake...
dear Richard Fernandez,
you should recompile the kernel with
--
From: Bill Carlson[SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, October 27, 1999 4:30 PM
To: Fernandez, Richard
Cc: [EMAIL PROTECTED]
Subject: RE: mkraid aborts, no info?
On Wed, 27 Oct 1999, Fernandez, Richard wrote:
Mandrake doesn't have RAID
On Wed, Oct 27, 1999 at 03:30:31PM -0500, Bill Carlson wrote:
I'm thinking Florin means the kernel is not compiled with support by
default.
no.
This package includes the tools you need to set up and maintain a software
RAID
device under Linux. It only works with Linux 2.2 kernels and later,
8
device /dev/sdb1
raid-disk 0
device /dev/sdc1
raid-disk 1
When I run mkraid I get the following:
[root@washu /root]# mkraid -c /etc/raidtab.test /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb1, 4192933kB, raid
On Wed, 27 Oct 1999, David A. Cooley wrote:
Hi Bill,
You need to get the latest raid kernel patch (ignore the errors it gives...
one hunk is included in the 2.2.12/2.2.13 kernel) and the latest raidtools
(0.90).
Ah, I see now. I'll try applying the patch to the 2.2.13 now.
Thanks
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
mkraid: aborted
:
raiddev /dev/md0
raid-level
1
nr-raid-disks
2
nr-spare-disks
0
chunk-size
4 persistent-superblock 1
device
/dev/sda5
raid-disk
0
device
/dev/sdb5
raid-disk
1
My question is that when I give the "mkraid
/dev/md0" command why am I getting an error message and aborts my mkra
on a SparcStorage Array 210. I have the /etc/raidtab file setup according to
the docs, and tried using raidtools-.50.
When I run:
mkraid /dev/md0
I get:
sys32_ioctl: Unknown cmd fd(4) cmd(2914) arg(efffd00)
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdn1, 4190400kB, raid
e the /etc/raidtab file setup according to
the docs, and tried using raidtools-.50.
When I run:
mkraid /dev/md0
I get:
sys32_ioctl: Unknown cmd fd(4) cmd(2914) arg(efffd00)
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdn1, 4190400kB, raid superblock at 4190336
Hello,
I'm using the latest version of mkraid and tried to create a RAID1
device from hda1 and hdc1 (trying to set up a RAID1 boot device with
the recently mentioned LILO disk geometry config options).
Both partitions where set to type FD and the raidtab entry is fine, too.
Alas when trying
: inactive
md2 : inactive
md3 : inactive
When running mkraid --bogus /dev/md0 this happens:
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb1, 102384kB, raid superblock at 102272kB
disk 1: /dev/sdd1, 102384kB, raid superblock at 102272kB
mkraid: aborted, see the syslog and /proc/mdstat
: [2 raid0]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive
When running mkraid --bogus /dev/md0 this happens:
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb1, 102384kB, raid superblock at 102272kB
disk 1: /dev/sdd1, 102384kB, raid
and seems to work fine.
[RAID1]
There are two partition equally sized on two different HDs:
sdb6 and sdc6 both with no filesystem on them.
[mkraid]
root@felix:~ mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb6, 128488kB, raid superblock at 128384kB
disk 1: /dev
On Fri, Sep 17, 1999 at 09:32:36AM -0400, David Cooley wrote:
At 12:57 PM 9/17/1999 +0200, you wrote:
Hello,
we are trying to set up RAID1 as described in the Software-RAID-howto.
md-support is compiled into the kernel (not as module) and RAID1 too.
Raid0 ist not compiled in, because the
'
make: *** [vmlinux] Error 1
When I do;
mkraid /dev/md0
I get;
analyzing super-block
disk 0: /dev/hda7, 226768kB, raid superblock at 226688kB
/dev/hda7 is mounted
mkraid: aborted, see the syslog and proc/mdstat for potential clues
Syslog and messages contain no new log messages, and the same
too.
When i try to execute "mkraid -f /dev/md0" i get this message:
..
mkraid: aborted, see the syslog and /proc/mdstat for
potential clues.
My mdstat looks like this:
Personalities : [1 linear] [2 raid0] [3 raid1]
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : in
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
/dev/sdc1
raid-disk 1
First I partitioned two disks using fdisk (RH 6.0).
Then I did: mkraid --really-force /dev/md0
Then: mke2fs -b 4096 -i 16384 /dev/md0
Then: mount /dev/md0 /u
Everything was OK.
I updated my kernel from the stock 2.2.5-15 (RedHat 6.0) to 2.2.11. I
did
When I rebooted I can't mount /dev/md0. Since I got nothing on md0 I
decided to redo it again.
I repeated the above steps and it give theses errors:
[root@rems5a /dev]# mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device
In the past I used the md tools and with my new system, I am trying tu
use the raidtools. I'm experiencing the following problem:
[root@garfield ~]# mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing
I want to use RAID-1 system on Sparcstaion 5, and I install RedHat6.0 for SPARC
and install raidtools using raidtools-19990724-0.90.tar.gz.
When I executed mkraid, I received a following message.
kernel: mkraid[399]: Unimplemented SPARC system call 140
I found the following statement
On Fri, Aug 20, 1999 at 11:03:09AM +0900, Akihiro Okamura wrote:
I want to use RAID-1 system on Sparcstaion 5, and I install RedHat6.0 for SPARC
and install raidtools using raidtools-19990724-0.90.tar.gz.
When I executed mkraid, I received a following message.
kernel: mkraid[399
Having problems getting mkraid to create the /dev/md0
raid device.. here is my info:
System SuSE 6.1 - Clean Install
Kernel - 2.2.10 - with md support for linearr, raid0 and raid1
IDE boot Drive
2 SCSI disks, same size as /dev/sda and /dev/sdb
raidtools-0.90
I did NOT use the patch (raid145
-disks 2
persistent-superblock 1
chunk-size4
device/dev/sda1
raid-disk 0
device/dev/sdb1
raid-disk 1
It is very simple.
But, during mkraid, following message are occured.
DESTROYING the contents of /dev/md0 in 5 seconds
My /etc/raidtab looks like this:
raiddev /dev/md0
raid-level 1
nr-raid-disks 3
nr-spare-disks 0
chunk-size 4
device /dev/sda2
raid-disk 0
device /dev/sdb2
raid-disk 1
raid-level 1 with 3 disks?
You have to use raid-level 5 (or 4).
No you don't. You can have as many mirrors in a RAID-1 mirror set as you want.
The setup described will protect against the simultaneous failure of two disks
(i.e. the failure of a second disk before you are able to replace the
I can't figure out why mkraid is aborting. No messages show up in the
syslog, and I get what looks like a typical response from /proc/mdstat
You are missing persistent-superblocks lines in your raidtab. I thought this
shouldn't matter, as it should default to "persistent-superblo
On Thu, Jul 08, 1999 at 01:00:42PM -0700, Zack Hobson wrote:
Hello RAID hackers,
RedHat 6.0 w/ 2.2.10 kernel (compiled with RAID-1 support)
raidtools 0.90 compiled from distributed source (ie, non-RedHat)
raidtools 0.90 does not work with stock kernels
either you use old raidtools or
Mogens Kjaer wrote:
The Threshold wrote:
...
Redhat 6.0/Kernel 2.2.10/mkraid 0.90.0
...
I made the same mistake; don't upgrade the kernel, stay at
2.2.5-15, then it works.
Mogens
Actually this has been the center of several conversations lately.
There is a patch that works fine
device /dev/sdi1
spare-disk 7
This is the problem. That should be:
device /dev/sdi1
spare-disk 0
Cheers,
Bruno Prior [EMAIL PROTECTED]
/dev/sdb4
raid-disk 1
device /dev/sdc4
raid-disk 2
When I run mkraid --force /de/md0 (because sda2 has a filesystem on it):
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing super-block
disk
The Threshold wrote:
...
Redhat 6.0/Kernel 2.2.10/mkraid 0.90.0
...
I made the same mistake; don't upgrade the kernel, stay at
2.2.5-15, then it works.
Mogens
--
Mogens Kjaer, Carlsberg Laboratory, Dept. of Chemistry
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax
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
sti
raid-disk 1
I have no problems doing a mkraid /dev/md5, but I cannot do 1-4 here is
what I get
[root@dhcp66-239 /root]# mkraid --really-force /dev/md3
DESTROYING the contents of /dev/md3 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md3
analyzing super-block
disk 0: /dev
version from ?
This shows my problem:
mkraid /dev/md0 --really-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
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 read
for the raid.Wel if i set them to fd the
autostart-start , but actually o load the radi from a scsi disk tha i use
to setup the system, and when the kernle load and autostart makes his job i
can stop the array but i'm not more able to destroy and recreate it with
mkraid /dev/md0 (i do not mention really
Well, I know this problem and I'm dealing with it 2... I'm trying to solve it
with help from the others..Just follow the messages with Subject:
mkraid: Aborted.. done patch/0.9/mknod
Actually, Wim, I don't think this is the same problem as yours. I think the clue
is that "Rule"
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 - 100 of 137 matches
Mail list logo
