NetBSD Problem Report #39329

From www@NetBSD.org  Sun Aug 10 04:31:27 2008
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 11E7563BC30
	for <gnats-bugs@gnats.netbsd.org>; Sun, 10 Aug 2008 04:31:27 +0000 (UTC)
Message-Id: <20080810043126.95C5863BB81@narn.NetBSD.org>
Date: Sun, 10 Aug 2008 04:31:26 +0000 (UTC)
From: randolf+netbsd.org@inter-corporate.com
Reply-To: randolf+netbsd.org@inter-corporate.com
To: gnats-bugs@NetBSD.org
Subject: Intel S3000AH server motherboard with on-board LSI controller not supported by mfi
X-Send-Pr-Version: www-1.0

>Number:         39329
>Category:       install
>Synopsis:       Intel S3000AH server motherboard with on-board LSI controller not supported by mfi
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Aug 10 04:35:00 +0000 2008
>Last-Modified:  Sun Aug 10 11:10:02 +0000 2008
>Originator:     Randolf Richardson
>Release:        NetBSD v4.99.70
>Organization:
Inter-Corporate Computer & Network Services, Inc.
>Environment:
Not applicable because OS not installed.
>Description:
Intel S3000AH server motherboards are very common in North America in the corporate world, and have been available for years.  These motherboards include an on-board LSI Logic RAID-1 controller (which can be switched in the BIOS to an Intel Matrix Storage RAID-1 controller, but this might be a "fakeraid" which depends on drivers to make the mirroring actually work).

NetBSD's sysinst from the i386 ISO fails to detect any hard disks in the system when either the LSI Logic or Intel Matrix Storage controllers are used.

This is a request to improve mfi so that these LSI Logic controllers may be supported.

Here's a link to the technical detail page on Intel's web site for this particular motherboard:  http://www.intel.com/support/motherboards/server/s3000ah/

>How-To-Repeat:

>Fix:
For now I'm using a solution that's not so ideal (because RAIDframe sometimes leaves me with an unmountable file system after a coredump of any application, so this isn't a suitable solution) is to manually duplicate wd0 to wd1 using a utility called "g4u" (copies Unix partitions), and then rely on a cron job to "rsync" the data from wd0 to wd1 every night.

Obviously this solution can't provide as much reliability as a hardware RAID solution, and my hope is that NetBSD will have better support for SATA and SAS hardware RAID controllers before NetBSD 5 is released.

Thanks in advance.

>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: install-manager@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: install/39329: Intel S3000AH server motherboard with on-board LSI controller not supported by mfi
Date: Sun, 10 Aug 2008 13:05:08 +0200

 On Sun, Aug 10, 2008 at 04:35:00AM +0000, randolf+netbsd.org@inter-corporate.com wrote:
 > >How-To-Repeat:
 > 
 > >Fix:
 > For now I'm using a solution that's not so ideal (because RAIDframe sometimes leaves me with an unmountable file system after a coredump of any application, so this isn't a suitable solution) is to manually duplicate wd0 to wd1 using a utility called "g4u" (copies Unix partitions), and then rely on a cron job to "rsync" the data from wd0 to wd1 every night.

 It's also be usefull to find why raidframe behaves this way. I've a lot
 of systems using raidframe, and none show this behavior.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

Home	PR Database Search