I don't understand how the installer of 11.3 deals with my INTEL ICH10R fake RAID0 !

Hi,

I have two 150GB WD Raptors stripped in an INTEL ICH10R RAID0 array. Windows 7 is installed on it in a 100GB partition, there is a 150GB secondary partition, a 100MB system reserved partition created by Windows 7 and there is about 25GB unallocated space to install a linux distribution.
My problem is the fake ICH10R RAID which does work only at the moment for me with Fedora Core 13 : Ubuntu 10.04 breaks it but i do not like FC13 very much. So i Googled and Googled for installation problems on this fakeraid and dmraid is involved there is a bug in it at least in Ubuntu 10.04 and openSUSE 11.2, with 11.3 my RAID is detected -> i have a MD RAID popup.

My question is : How to install properly 11.3 on the space left on my fake RAID array without breaking anything although i have a full backup of my system. I don’t understand anything of the partitioning part of openSUSE in general. Do i must activate MD RAID, i tried once and my NTFS partitions were not displayed but RAID was detected with the correct size. I am totally lost with this installer !!!

Any help would be appreciated,

Thanks.

Arf ! RAID is a pain…

You really need it? Really difficult with oS too. :confused:

Hello,

Please see https://bugzilla.novell.com/show_bug.cgi?id=619566.

Urg! I am really disappointed that the SuSE folks released with udev foobared. I’d call it a show-stopper bug! FC13 is really solid :).

oxala wrote:

>
> Hello,
>
> Please see https://bugzilla.novell.com/show_bug.cgi?id=619566.
>
> Urg! I am really disappointed that the SuSE folks released with udev
> foobared. I’d call it a show-stopper bug! FC13 is really solid :).

It’s not as bad as that - udev works quite well for most situations, but
maybe the dmraid context wasn’t considered serious enough to warrant
being a show-stopper? Anyway, an immediate work around is to use
software raid instead (mdraid).


Per Jessen, Zürich (21.2°C)
http://en.opensuse.org/User:Pjessen

Hello,

I know this is the wrong place for this discussion, … but I can’t resist.

Udev was updated to an upstream version just prior to the RC2 release … less than 24 hours … NO WAY it could have been properly tested. This was to fix a problem with udev deleting nodes needed for lvm to work.

I had other issues with udev in RC1 and RC2. I have not even started my own testing in the final release, but I expect to encounter the same issues … such as devices for raid members not being hidden from nautilus, custom udev rules that worked in 11.2 being unusable in 11.3, etc.

The udev subsystem is awesome … big improvement over the old fixed device node UNIX model, but it is a part of the system that MUST be rock solid.

oxala wrote:

> Hello,
>
> I know this is the wrong place for this discussion, … but I can’t
> resist.
>
> Udev was updated to an upstream version just prior to the RC2 release
> … less than 24 hours … NO WAY it could have been properly
> tested. This was to fix a problem with udev deleting nodes needed for
> lvm to work.

Yes, I have been tracking the bugreport
(https://bugzilla.novell.com/show_bug.cgi?id=598193) for a while - a
non-working LVM would definitely have been a show-stopper.

> The udev subsystem is awesome … big improvement over the old fixed
> device node UNIX model, but it is a part of the system that MUST be
> rock solid.

I agree - I guess the decision was whether to postpone 11.3 for
three-four weeks, try to roll back to <whatever the situation was
before udev broke) or fix the most immediate problems and carry on as
planned.

I am surprised that this dmraid issue turns up after 11.3 has gone GM -
the udev problem has been around since April - I guess no-one has been
testing much on systems with dmraid. (I don’t, I don’t have any).


Per Jessen, Zürich (29.6°C)
http://en.opensuse.org/User:Pjessen

According to the device mapper “This should has been fixed with the latest update to device-mapper.” … if you updated and if it has not been fixed for you, it would likely be good if you reported this in the bug report.

Something else that may help in such cases in the bug report, if you did determine that such a function/application works in another distribution (and not in openSUSE), politely note that in the bug report, and if you can add details of the functioning distribution (ie kernel version, specific application versions, and if you know how (to find out) note which patches were applied (that may not yet be upstream)) in that other Linux distribution version which enabled the specific functionality that is missing in openSUSE.

Hi all,

  • Firstly : is there any difference beetween dmraid and mdraid ?
  • Secondly : What is the correct procedure to get the updated device mapper ? Running a full update with a live CD or get it directly from a NET install ?

Thank you for your answers.

schicode2009 wrote:

>
> oldcpu;2190241 Wrote:
>> According to the device mapper “This should has been fixed with the
>> latest update to device-mapper.” … if you updated and if it has not
>> been fixed for you, it would likely be good if you reported this in
>> the bug report.
>
> Hi all,
>
> - Firstly : is there any difference beetween dmraid and mdraid ?

Yes. Apart from ‘dm’ vs ‘md’, they’re also completely different.


Per Jessen, Zürich (21.2°C)
http://en.opensuse.org/User:Pjessen