From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 23 16:16:28 2015 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32F19B87 for ; Fri, 23 Jan 2015 16:16:28 +0000 (UTC) Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B908AC18 for ; Fri, 23 Jan 2015 16:16:27 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id l61so8432791wev.8 for ; Fri, 23 Jan 2015 08:16:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cXI6ESxceLVWZL+1eOs37I5P+/JWMSn/GJPb9QOpiSw=; b=AS5xTW+EKUIrQP0TqA1LeBP1sWoOlI5mDMZ38dlA3L1rUcq8sMfG2Ty+14vILOF0+r RZbGPS2zH+RvhEgRB3u4ahPSm1lzDB9+wUS6msiYsG9cm9X3qArhMXLLfLuQG4IghZwJ qPAPEKlavtQG+IyBkz8M8gvHnMB94V3/MR7Rg/vKy79b+1Px8BT4bLlfz3ZpnrVlg4XN hPC+FHK/vrRMrXarNzZLUmRJ2aNcQjV+vuzpsDQW3gamCJAWAe53o4x6YXIyJIJNT80E 26VJLQeiSQFlkhXIBUZI+c5Ie/RScHo0NAzKk94ibPYvf8Q6V5FAEUpVhpAre5Q74SUG CQtQ== X-Gm-Message-State: ALoCoQmei43QM5CNBgesSNdsVTgrnOmPNKYvBn/ny7Y/zKZo3uGanftrGvj9+trpzowE7whrDf0P X-Received: by 10.194.2.240 with SMTP id 16mr15959178wjx.108.1422029780048; Fri, 23 Jan 2015 08:16:20 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id cy8sm2427724wib.9.2015.01.23.08.16.18 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Jan 2015 08:16:19 -0800 (PST) Message-ID: <54C27442.7040001@multiplay.co.uk> Date: Fri, 23 Jan 2015 16:18:10 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: kpneal@pobox.com Subject: Re: Dell branded storage controller for ZFS file-server | Advice requested References: <5BA9C549-9159-4A85-8C37-C30D700C8E4A@gwynne.id.au> <54C25EA4.1070504@multiplay.co.uk> <20150123151327.GA1526@neutralgood.org> In-Reply-To: <20150123151327.GA1526@neutralgood.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2015 16:16:28 -0000 On 23/01/2015 15:13, kpneal@pobox.com wrote: > On Fri, Jan 23, 2015 at 02:45:56PM +0000, Steven Hartland wrote: >> I believe h330 is a LSI 3008 underneath with 256 QD which is classed my >> mrsas as Invader/Fury 12Gb/s MR controller so you should get decent >> performance from it, as with anything though only testing will answer >> the question categorically ;-) > Just curious: Are jbod disks all bootable? Or does only one show up in the > bios' boot list? This is BIOS dependent, most provide support for a number of boot disks. > If only one, what happens if that drive mostly fails but still shows up > to the bios? How about if it totally fails and doesn't show up? How about > if the boot process starts but fails after control is passed to the boot > code loaded from disk? > > These questions are part of the reason I boot my Dells from the memory > card. > > Personally, I wish Dell would stop screwing around with the firmware used > with LSI chips. Generally we'll use the on-board controller to provide the boot disk pool in a simple mirror then configure a large RAIDZ for data, however that depends on how the physical disks are attached. This avoids the issue where the disk being chosen to boot from in the BIOS is not actually bootable.