Rami Sik ??????:

quoted text
> Yes, I first started by setting up the raid and installing openBSD on

> top of it. All was fine until one of the disks failed. Then, I replaced

> the failed disk, and try to re-initiate the raid (mirroring) where I got

> stuck since the raid controller did not like the partitioning.

>

> However, I advanced one step further now: If you use fdisk to assign a

> different id to the openBSD partition (like 83 as suggested by Sun for

> the Linux installs), raid controller seems to start mirroring your disk

> to the second one. However, when you change your partition id from the

> default value of A6 to 83, openBSD could not boot. So, I am planning to

> play with the partition id so that I could set up the mirroring through

> LSI raid controller. Once it is done, I will revert the partition id

> back to its default value of A6. Then I will see if mirroring still

> works, and boots off of the second disk!

>

>

> Rami Sik

>

The RAID controller *should not* care about partitions at all - WTF?!

It's job is to duplicate the data and present the disks as one logical

unit to the OS, and nothing more. You sure that is your problem?

quoted text
> -----Original Message-----

> From: J.C. Roberts [mailto:jcroberts@designtools.org]

> Sent: January 29, 2008 1:13 PM

> To: Rami Sik

> Cc: misc@openbsd.org

> Subject: Re: openBSD 4.2 and LSI raid

>

> On Monday 28 January 2008, Rami Sik wrote:

>

>> I did a research and found the similar problem already reported for

>> Linux installations, and Sun released a workaround for it. However, I

>> cannot find anything about openBSD installations.

>>

>

> At present, I've got two LSI RAID controllers here running OpenBSD

> ("MegaRAID 150-6 SATA" and "MegaRAID i4" PATA).

>

> Though I don't know about your specific controler (1030), the normal

> answer is to create your logical drive in the controler setup and

> *THEN* install the operating system.

>

> From your description, it seems you're doing things backwards, namely

> installing the OS on one drive and then trying to create a miror.

>

> -jcr