From owner-freebsd-bugs@FreeBSD.ORG Tue May 24 14:40:12 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A28A1065675 for ; Tue, 24 May 2011 14:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 532348FC20 for ; Tue, 24 May 2011 14:40:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4OEeBj5004000 for ; Tue, 24 May 2011 14:40:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4OEeBSf003999; Tue, 24 May 2011 14:40:11 GMT (envelope-from gnats) Resent-Date: Tue, 24 May 2011 14:40:11 GMT Resent-Message-Id: <201105241440.p4OEeBSf003999@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Jonathan Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63E311065678 for ; Tue, 24 May 2011 14:39:49 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 3AD338FC1A for ; Tue, 24 May 2011 14:39:49 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p4OEdn5B095127 for ; Tue, 24 May 2011 14:39:49 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p4OEdnq9095126; Tue, 24 May 2011 14:39:49 GMT (envelope-from nobody) Message-Id: <201105241439.p4OEdnq9095126@red.freebsd.org> Date: Tue, 24 May 2011 14:39:49 GMT From: Jonathan To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: bin/157293: mfiutil/mfi does not allow adding a previously configured drive to be added to a new array X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 14:40:12 -0000 >Number: 157293 >Category: bin >Synopsis: mfiutil/mfi does not allow adding a previously configured drive to be added to a new array >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 24 14:40:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Jonathan >Release: 8.2-STABLE >Organization: >Environment: FreeBSD SERENITY.kc8onw.net 8.2-STABLE FreeBSD 8.2-STABLE #2 r219138: Tue Mar 1 13:42:29 EST 2011 root@SERENITY.kc8onw.net:/usr/obj/usr/src/sys/SERENITY amd64 >Description: My server lost power and the RAID controller did not see the 2TB drive when the system came back up. The tech at the datacenter told the controller to continue booting despite the drive being "missing" and then removed and re-inserted the drive at my request. Now that the system has booted the RAID controller sees the drives as shown below. SERENITY# mfiutil show drives mfi0 Physical Drives: ( 419G) ONLINE SAS enclosure 1, slot 0 ( 419G) ONLINE SAS enclosure 1, slot 1 ( 419G) ONLINE SAS enclosure 1, slot 2 ( 1863G) UNCONFIGURED GOOD SATA enclosure 1, slot 3 If I try to reconfigure the drive as a JBOD or RAID0 I get the error SERENITY# mfiutil create jbod E01:S03 mfiutil: Command failed: Wrong firmware or drive state mfiutil: Failed to add volume: Input/output error SERENITY# mfiutil create raid0 E01:S03 mfiutil: Command failed: Wrong firmware or drive state mfiutil: Failed to add volume: Input/output error Is there anyway to do this with mfiutil or will I have to go onsite (a 3 hour drive one way) and try to reconfigure the drive via the controller BIOS? I also found this report from 9 months ago that had the same problem but I did not see a resolution http://lists.freebsd.org/pipermail/freebsd-scsi/2010-September/004526.html >How-To-Repeat: Temporarily lose a drive on a controller that uses the mfi driver and after telling the RAID control to continue booting anyway try to re-create the array/jbod device with mfiutil. >Fix: >Release-Note: >Audit-Trail: >Unformatted: