After install kernel 2.6.17 some /dev/md- appear

[Dan]

Joao Batista Gomes de Freitas wrote:
>> Message: 9
>> Date: Sun, 25 Jun 2006 21:08:34 +0200
>> From: Thomas Widhalm <widhalmt at unix.sbg.ac.at>
>> Subject: Re: After install kernel 2.6.17 some /dev/md- appear
>> To: For users of Fedora Core releases <fedora-list at redhat.com>
>> Message-ID: <449EDF32.6060808 at unix.sbg.ac.at>
>> Content-Type: text/plain; charset=ISO-8859-15
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi!
>>
>> I write this as an answer because my problems appeared after updating
>> the kernel, too. I do not use the X_64 kernel.
>>
>> I have an IDE and a SATA hdd within my box. On the SATA disk there are
>> only some old ntfs partitions. It is connected to the onboard raid-
>> conrtoller, set up as 1+0 raid. (I had to do that because my OSs didn't
>> recognise the disk otherwise)
>>
>> Fedora 5 wouldn't go on booting after this message:
>> "Jun 25 20:46:06 snoopy kernel: device-mapper: 4.5.0-ioctl (2005-10-04)
>> initialised: dm-devel at redhat.com"
>>
>> Any hint what might be wrong?
>>
>> Regards,
>> Thomas
>> - --
>> *****************************************************************
>> * Thomas Widhalm                             Unix Administrator *
>> * University of Salzburg                       ITServices (ITS) *
>> * Systems Management                               Unix Systems *
>> * Hellbrunnerstr. 34                     5020 Salzburg, Austria *
>> * widhalmt at unix.sbg.ac.at                     +43/662/8044-6774 *
>> * gpg: 6265BAE6 	    http://www.users.sbg.ac.at/~widhalmt *
>> *****************************************************************
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.3 (GNU/Linux)
>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>>
>> iD8DBQFEnt8ykbjs3GJluuYRApmpAJ9zoNLC1YjAZRBkRZoWm6HdmEP0AACfWcHe
>> myTW79KX9adwVcvO4PV9wKc=
>> =1toY
>> -----END PGP SIGNATURE-----
>>
>>
>>     
>
>
> I am in a similar situation. This is what I am running:
>
> AMD 64 300+ 
> ASUS A8N-E motherboard with nvidia sata controller.
> The RAID BIOS support is enabled
> I am using LVM and hardware RAID 0 with 2 sata HDs
> FC5 686 
>
> After yuming to kernel 2.6.17 I get stuck at the same point and message.
>
>
>
>   
Just a bit of semantics...nvidia RAID is not hardware RAID, it is 
software RAID implemented on the motherboard; usually referred to as 
"fakeraid". dmraid has handled fakeraid rather well recently, however 
kernel updates to 2.6.16 and now 2.6.17 each seem to have broken it in 
their own way. To update to 2.6.16, I installed the dmraid from 
development, dmraid -an and dmraid -ay (while booted on a fakeraid 
partition), and _then_ installed the new kernel. Had to manually add a 
GRUB entry, other than that it works fine.
Haven't tried 2.6.17 on fakeraid yet since from this thread and the 
bugzilla on dmraid (search for dm-striped) it appears to have more issues.
-Dan