12.3 wont install cant handle a raid0 array

12.3 installer is messing up the raid0 definitions from 12.2
it gives different part sizes and when you start installing it gives

" formatting device mapper volume / dev/mapper/nvidia_part1 (164.73) with etx4
system error code was -3030"

And then the raid array is no longer usable

12,2 installing from scatch with a new array defined is just installing and all is working
this message comes from 12.2

So goodby 12.3 there is nothing new on that dvd

A complete up todate 12.2 works better allso on my 12.3 laptop

so 12.3 is a very big disappointment

Aren’t you a bit too quick to deny this? I was not able to install a raid for 12.2 either and I asked questions but unfortunately nobody was able to help me install it. So I don’t see a change from that point of view from 12.2 to 12.3. I will attempt again on a different partition to install it, with and without raid. I think that lots of work was put into having 12.3 today, so let’s settle a bit and try to soak in multiple experiences from multiple users until we are judging the outcome. We, as people, are inclined to judge even though we don’t always have the reason/rights/etc to do it looking through our own experiences and not taking in consideration the experience of the others as a group. So let’s judge it in 3 weeks from now based on the problems encountered the number of defects and the number of questions in here.

So did you report the error in detail to bugzilla? No reporty no fixy

susegebr wrote:

> 12.3 installer is messing up the raid0 definitions from 12.2
> it gives different part sizes and when you start installing it gives
>
> " formatting device mapper volume / dev/mapper/nvidia_part1 (164.73)
> with etx4
> system error code was -3030"

I get the same error in a vaio laptop that had many previous versions of
opensuse all working fine (currently it is 12.2, but I can’t install 12.3).
Can’t format the /boot or the / partitions.

In addition it complains that it cannot get the sizes for the /windows/C
partition.

There is a previous question asked if I want to let handle the raid disks
and I always have replied “no” for all opensuse installations in this
computer (and they always worked fine).
Should I answer “yes”? It is a double boot computer with WinXP in another
partition and I would not like to lose the XP partition.

Should I delete the those unformattable partitions and create them again?
I am a bit concerned that if I do so I’ll end up with a brick and can’t go
back to 12.2 (as the error above does leave the system usable in 12.2
because the installation does not continue).
Thanks

-G-

No working installer ? then the otherway arround

installed 12.2 upgraded the kernel kde4 printing

Then changed the software repositories from 12.2 to 12.3

updated the system so bypassing the faulty installer on the 12.3 dvd

now i have a perfect working 12.3 on a raid array formatted in 12.2 rotfl!

during updating put the 12.3 dvd in the drive !!!

Please report the problem o bugzilla

please tell me where and how to report and where is bugzilla ???

If i can find it and format a report with the data i have i will put it on bugzilla

https://en.opensuse.org/Bugzilla

Why are you going through all that hassle of partitioning and worrying about RAID not working?

Put your whole Linux system into a virtual machine and leave XP right where it is. Problem solved.

susegebr wrote:

>
> No working installer ? then the otherway arround
>
> installed 12.2 upgraded the kernel kde4 printing

Can you plese give more details? What repo did you use to upgrade the
kernel?, etc.

> Then changed the software repositories from 12.2 to 12.3
>
> updated the system so bypassing the faulty installer on the 12.3
> dvd
>
> now i have a perfect working 12.3 on a raid array formatted in 12.2
> rotfl!

I wondered also if upgrading rather than making a new install would work. I
have not tried this yet.
Thanks.
-G-

tuyennguyen wrote:
> Why are you going through all that hassle of partitioning and worrying
> about RAID not working?

Hi, because it should be possible to do it? :slight_smile:

> Put your whole Linux system into a virtual machine and leave XP right
> where it is. Problem solved.

Thanks, that is an idea that I will keep in mind, but I would need to move
the existing home partition into a virtual machine install (I would not know
how to do it) and resize the XP partition again, and possibly screw it all
up in the process.
I thought that installing 12.3 should be possible like all the previous
versions.

Cheers, -G-

I too have expirienced the issue with raid 0 config. i have two vertex 3’s on a raid config via my uefi asus mobo. i did get 12.3 x64 working on my raid. i happened to have a 3rd drive in my arsenal with some free space(unpartitioned). without utilizing my third Sata for boot and swap i was getting the same errors. -3303 and -4000. when i setup a boot and swap on the third and let the installer make only a dm for the raid for root and home install went fine. I also had to delete all other installer made instances of the raid besides the one covering the entire span of my raid drive(111GB in my case). then told the installer to use a primary partition (self made) for boot, and swap on the third. this worked flawlessly. i am actually making this post from my linux installed on the raid 0. so this brought to mind (not tested yet) that the eufi bios creates a pseudo partition accessable by OS for further partitioning. so what i plan on doing for my next test is to leave some unused space on my setup via the bios set raid configuration aside from what i plan on using for home, and root. with it unused. maybe the installer will then be able to use it to install boot, and swap. so, in short i think it just cant set an active primary inside what is being set as an extension. I know i’m probably not wording that right, but I am somewhat new to custom partition creation inside a uefi environment. let alone a raid configuration at that. just thinking that if raid config via mobo can set the two drives to act as one, it must be somewhat “partitioned” at this point. hope this info helps others trying to install this awesome OS (openSuSE 12.3 x86_64). with it up and running on my raid config. it SCREAMS. I like it so much better than windows 8/7/vista/xp.

Update to my previous post. nevermind the idea of leaving open area via the uefi mobo config. I finally got it too boot, swap, and home/root the raid completely. not sure if its the right way, but it is going smoother than my previous invention/workaround using a separate drive which was ide for boot/swap. although raid/ide, it was still creating a bottleneck. so, what i did, was strange. cuz i did not have this problem on 12.2 install. After creating the raid definitions in the suse installer partition section, i wanted to see if there would be a difference loading my eufi iommu with mode for 32->64 bit enabled. it did end up getting rid of the cannot get firmware error during installer load, but then returned amd-vi error no southbridge detected on *****(didnt right down the name lol). so, i proceeded anyway. getting the usual errors along the way -3303. when that failed, i rebooted, and decided to try a different way. when the installer this time loaded up some DM’s for me on top of my previously mentioned DM RAID definitions. after setting the boot/swap/home/root to these new DM’s the install went off without a hitch. I am now booted into 12.3 x86_64bit completely on the raid 0 config set by my eufi mobo config. so, i guess i would next time, let the installer find the raid, then in expert mode, enable device mappers, and set my partitions there. again I haven’t run benchmarks on it yet, but it seems alot smoother. Hope this helps anyone else having this problem or the devs find a solution. I have the newest mobo firmware allowable, and not sure why my firmware has those bugs, but w/e… t;-p its working rotfl!

Same error here but on AMD 970 mobo (promise controller):
formatting device mapper volume /dev/mapper/pdc_aabbccdd_part1 (363.10) with etx4 system error code was -3030"

Workaround:

  • Create RAID0 array in BIOS
  • Download gparted (USB or ISO)
  • Boot gparted
  • Partition/format the RAID array to desired configuration
  • Boot with openSUSE 12.3 DVD and start install
  • Select Custom Partitioning
  • Observe 2 sets of partitions on the target RAID array. One set on the bottom of the page has a dash in the name and has the labels assigned by gparted (example: /dev/mapper/pdc_aabbccdd-part1 BOOT) - use this (mount by device name). Do not use the set with no label and no dash (ex: /dev/mapper/pdc_aabbccdd_part1). These 2 sets show slightly different partition sizes and I believe one is wrong.
  • Install using partitions selected above (it is safe to reformat, but don’t resize).

It looks like this was reported years ago (10.3, 11.3) and called fixed a couple of times:

https://bugzilla.novell.com/show_bug.cgi?id=293728
https://bugzilla.novell.com/show_bug.cgi?id=604255

On 2013-03-14 19:56, gogalthorp wrote:
>
> Please report the problem o bugzilla

It is a known problem, it has already been reported, with the bypass of
installing 12.2 then upgrading.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

On 2013-07-30 00:03, Carlos E. R. wrote:
> On 2013-03-14 19:56, gogalthorp wrote:
>>
>> Please report the problem o bugzilla
>
> It is a known problem, it has already been reported, with the bypass of
> installing 12.2 then upgrading.

Oops, sorry. I posted without noticing the date of your post :frowning:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)