openBSD 4.2 and LSI raid
Hi All, I am trying to mirror an openBSD4.2 install on a Sun v20z box. That box has LSI 1030 internal raid controller. According to the LSI manual, I reboot the box into the LSI tool by pressing Ctrl-C while booting. When I try to mark the primary disk, it says "Can't keep data. Incompatible partition". So, it could not mirror a disk with already installed openBSD4.2 partitions. 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. So, has anyone run into that problem? If so, how did you succeed mirroring an openBSD4.2 disk on such a hardware platform? Thanks, Rami Sik
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
Re: openBSD 4.2 and LSI raid
Have a look at the following doc from Sun (section D.1.5):
http://docs.sun.com/source/817-5248-20/appd.html
I know what you mean. It sounded strange in the first place, but life is
full of surprises!
Rami Sik
-Original Message-
From: NetOne - Doichin Dokov [mailto:[EMAIL PROTECTED]
Sent: January 29, 2008 1:57 PM
To: Rami Sik
Cc: J.C. Roberts; misc@openbsd.org
Subject: Re: openBSD 4.2 and LSI raid
Rami Sik ??:
> 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?
> -Original Message-
> From: J.C. Roberts [mailto:[EMAIL PROTECTED]
> 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
Re: openBSD 4.2 and LSI raid
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
-Original Message-
From: J.C. Roberts [mailto:[EMAIL PROTECTED]
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
Re: openBSD 4.2 and LSI raid
Rami Sik ??:
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?
-Original Message-
From: J.C. Roberts [mailto:[EMAIL PROTECTED]
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
Re: openBSD 4.2 and LSI raid
On 2008/01/29 23:57, NetOne - Doichin Dokov wrote: >> 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. I *think* you should probably set the new disk as a hotspare. But who knows what this crazy firmware is doing. A timely reminder of the requirement to test what happens when things break, since I am building a box with mirrored disks at the moment :-) > 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? http://docs.sun.com/source/817-5248-20/appd.html Note that there are many different devices known as "LSI raid". At least: mpi(4) (formerly mpt), ami(4), mfi(4).
Re: openBSD 4.2 and LSI raid
On Tuesday 29 January 2008, Stuart Henderson wrote: > On 2008/01/29 23:57, NetOne - Doichin Dokov wrote: > >> 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. > > I *think* you should probably set the new disk as a hotspare. > But who knows what this crazy firmware is doing. It seems the "crazy firmware" is checking the partition type read from the disk against some kind of whitelist... highly annoying. It's moments like this when I wonder why I don't use softraid *alot* more often. Rami, sorry I misunderstood your first post. The partition type hacking you mentioned in your follow up seems like your only choice short term but long term, the best answer is to replace the controller or use softraid. kind regards, JCR
