Since 2.0.36 has been out now for a couple weeks I was wondering if
there is a raidtools patch against it, or is it safe to use the
2.0.35 patch against it?
Steve
[...]
> The short-end of it is that you must apply the kernel patches
> that are a companion to the raidtools-0.90 -- stock kernel
> is not compatible with those tools.
Ok, thanks for the help. The raid0145-19981110-2.0.35.gz doesn't apply to
2.0.36. I'd be happy to test anything that might be
Dave Wreski wrote:
>
...# ./mkraid --configfile /etc/raidtab /dev/md0
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hdc1, 425218kB, raid superblock at 425152kB
> disk 1: /dev/hdd1, 425218kB, raid superblock at 425152kB
> mkraid: aborted
I traced that "aborted" down to a fa
I have a 2.0.35 system patched with raid0145-19981110-2.0.35, using
raidtools-19981105-0.90, with drives sda and sdb.
I'd like to add sdc and sdd and build a RAID-5 array from sdb, sdc and sdd;
but not lose the data currently on sdb.
My thought was to build a "degraded" RAID-5 ar
Hi all. Ok, I figured out the message in /pub/linux/daemons/raid points to an
old version of the raidtools, so I got 0.90 to compile on 2.0.36.
However, it appears mdadd is now replaced with mkraid, but it doesn't work for
me:
[root@devel raidtools-0.90]# ./mkraid --configfile /etc/raidtab /de
> I thought for a moment that it might be a hard-to-find
> IDE driver bug, but I see that Andreas managed to get it
> to happen on a SCSI-only RAID0.
Im not sure its MD related either. I've had two 2.1.129 crashes now
where the block devices size table got smashed (ie it died in a hail
of device
Since the stock md/raid0 is now horribly broken in 2.1.12[89],
I decided today to try the latest raid1 stuff:
raid0145-19981110-2.1.127 -- kernel patch
raidtools-19981105-0.90.tar.gz -- raid utilities
After patching the kernel and rebooting, I created /etc/raidtab:
Hi all. I'm having difficulty compiling raidtools-0.50beta3 and 0.42 on 2.0.36.
The 0.50beta3 reports:
gcc -g -O2 -I/usr/src/linux/include -DMD_VERSION=\""raidtools-0.50"\" -c
raidadd.c -o raidadd.o
raidadd.c: In function `do_mdstop':
raidadd.c:126: `STOP_MD_RO' undeclared (first use this fu
On Fri, 20 Nov 1998, Neill Mitchell wrote:
> I can't seem to get my RAID-1 to work under 2.1.129. raidstart /dev/md0
> gives the error - /dev/md0 Invalid argument. I've got the latest raidtools
> and I have tried with mkraid --upgrade which seems to work. mkraid /dev/md0
> says there is an existi
had same config as you with older raid on a 2.0.32 box. autostarted with
an initrd and root raid(what a pain- many thanks to the raid crew!)
i backedup to tape twice and re-installed 5.1 on a blank hd. then made the
new kernel and partitions on scsi disks. got autostart working, and then
made boo
10 matches
Mail list logo
