> I have a difficult RAID problem.
No you don't. It's quite straightforward.
> Anyway, I switched over to RH6.0 and I can't get the RAID disks t
> work. I upgraded the kernel to 2.1.15 and compiled in the RAID stuff.
> And a cat on /proc/mdstat show md0 to md4 are there.
RH6.0 comes with kernel 2.2.5, so how can you "upgrade" to 2.1.15? RH6.0's
kernel also includes a number of patches including the raid-patch to support the
new raidtools (0.50 - 0.90). A stock 2.1.15 kernel does not include this patch,
and therefore only supports the old (0.42 or earlier) raidtools/mdtools. So an
unpatched kernel with old RAID support compiled in will be able to see the md
devices (hence /proc/mdstat), but it will not be able to start or stop them with
the new raidtools.
> When I was using debian the raid commands used mdcreate, mdadd, mdrun,
> etc. Under RH the comands consist of raidstart, raidstop, etc.
Exactly. That is because debian used old-style RAID and RH uses new-style RAID
by default.
You have 2 options. Get raidtools-0.42 and carry on using old-style RAID, in
which case your arrays will not need upgrading, but performance and features
will be restricted. Or get a kernel with support for raidtools-0.90. The stock
RH6.* kernels come with this support as a module, or get a vanilla kernel source
tarball and patch it with the appropriate raid patch. You need to match up your
kernel, raid-patch and raidtools. You can get patch and tools from
ftp.kernel.org in the /pub/linux/daemons/raid/alpha directory.
If you go for new-style RAID, you will need to upgrade your array
("mkraid --upgrade"), as you tried to do. There have not been many success
stories about this, so make sure you have a good, recent backup. If necessary,
you will have to recreate the arrays and then restore the data.
> I have also downloaded the recommended vesion of the raittools 0.50
> beta3 and I can't compile then for some reason.
Recommended by whom? This is well out of date. Get raidtools-0.90 if you want
new raidtools or raidtools-0.42 if you want old raidtools.
Cheers,
Bruno Prior [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Simon Haddon
> Sent: 02 November 1999 23:49
> To: Multiple recipients of list; [EMAIL PROTECTED]
> Subject: Problems moving from debian to RH with RAID
>
>
> Hi,
>
> I have a difficult RAID problem.
>
> I was building a system with debian 2.1 using RAID 1 on hdb and hdc
> (leaving hda for boot). I managed to get the raid working just fine
> but was having to many problems with Oracle and ColdFusion, so I
> decided to switch over to RH 6.0 as both products are verified against
> those releases.
>
> Anyway, I switched over to RH6.0 and I can't get the RAID disks t
> work. I upgraded the kernel to 2.1.15 and compiled in the RAID stuff.
> And a cat on /proc/mdstat show md0 to md4 are there.
>
> When I was using debian the raid commands used mdcreate, mdadd, mdrun,
> etc. Under RH the comands consist of raidstart, raidstop, etc.
>
> Following is what I have done and tried.
>
> Created a /etc/raidtab with the following ( I use md0 to md4)
>
> # /u01
> # NB chunksize and persistent-superblock added for new raid tools
> raiddev /dev/md0
> raid-level 1
> nr-raid-disks 2
> nr-spare-disks 0
> chunk-size 4
> persistent-superblock 1
> device /dev/hdb3
> raid-disk 0
> device /dev/hdc3
> raid-disk 1
>
> # /u02 etc...
>
>
> Ran: raidstart -a
> Got: /dev/md0: Invalid argument
>
> Ran: mkraid -u /dev/md0
> Got: handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hdb3, 2097648kB, raid superblock at 2097536kB
> array needs no upgrade
> mkraid: aborted
>
> Ran: mkraid --really-force /dev/md0
> Get: DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if
> unsure!
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/hdb3, 2097648kB, raid superblock at 2097536kB
> disk 1: /dev/hdc3, 2097648kB, raid superblock at 2097536kB
> mkraid: aborted
>
>
> I have also downloaded the recommended vesion of the raittools 0.50
> beta3 and I can't compile then for some reason.
>
> Could someone help please.
>
>
> PS.
> The only problem was having with Oracle was that su under debian was
> not working properly. Ie: "su - oracle -c dbstart" didn't work as su
> was not giving me oracle's environment. ColdFusion was the real
> problem as it wanted versions of libraries that I coldn't find on the
> debian release an the installation process wouldn't work wih all typed
> of errors.
>
>
>
>
>
>
