From owner-freebsd-questions@freebsd.org Tue Mar 13 12:25:59 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6862F4955A; Tue, 13 Mar 2018 12:25:58 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (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 52F2A7A499; Tue, 13 Mar 2018 12:25:58 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: by mail-ua0-x231.google.com with SMTP id c40so9044186uae.2; Tue, 13 Mar 2018 05:25:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=SeGlG3ooT8T8szI81EK2LLLSBaO8vVI8uYji8Z3GIks=; b=K/Q9Q7PfeToYHrjjIVjbkw6jtkWoZuDcOOazBJMKWm3N76t0wJM2cl23DsOyaCRs5X 8Mw9DcPvZCKc8kXV5iX/VehHPUc65WiuX09Nmve2qTZKNDEewhSlH2QGH4C6pcIAyEDF EBWsgzH3DyweVo3zmh3Hhu7iYq7MJvPr97Q5wxPtHBFYezIP3BsApDMnhZVN4GKe3fFN HDN3DA6UMYFOsKXoIsXQYpHmXE0XdKQReiPEeXBte/ItJcJ2Fa11nCkyX94wtEN0FtsE P2DJVaif8vxKbwpAuc9MUzcFTntQmESfC0kJR33Q5sQBLm9P5c6Wtj4jqT2B90SH47qC 7rrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=SeGlG3ooT8T8szI81EK2LLLSBaO8vVI8uYji8Z3GIks=; b=YNd5CAL0GSArR+Ew8bsn2zkIbUZwaxBrLRwBWg18g2Ks8SYxf7+Gdz0QRcpBeLJPNr 1McxD8OSfvg6Xt8kqLfrG6YC5dITYuclBGKn1JUacO6ddStv6U5LbEr9QXfiQulRrAQv pgIHH0WMTR2nWJ3tQwXjjYmEbdwpS+GBsP6aZiHqqIqt4DL774vv7pQmCe78TeKkX25O YaIFIviW8JXLs5kE+SJVeKyk9Iz65+KmNBYLEUDJa2NXX6dQh589E0XsADqVmiNJOLvG UPwq659zcD/A2YIsNMdcVBAflKgMA07zZ+Y7UYLW6Fjzz1CL61OJSQ8jQMpCEYzkoAc7 ZBzQ== X-Gm-Message-State: AElRT7GM1++IJBU5mv8u1BPnkmix770/5WRopLd3vnPRV366KwZi400B lUhd+mkn6BI9+MWdphN+HFQcYTLlNTi2dhredYk= X-Google-Smtp-Source: AG47ELsDNRXeYk1DogHGU4C2re+CaWYTrAdwg2CUQLkQr02QVgGluokGahHlCZGmT2qJw1Y1o74ZG3d39s4hzRLnaE0= X-Received: by 10.159.60.89 with SMTP id w25mr273819uah.59.1520943957657; Tue, 13 Mar 2018 05:25:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Rick Miller Date: Tue, 13 Mar 2018 12:25:47 +0000 Message-ID: Subject: Re: FreeBSD 11.x fails to boot w/ SAS3 4Kn HDD and LSISAS3008 on SuperMicro X10DRH-iT To: FreeBSD Questions , freebsd-geom@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2018 12:25:59 -0000 As it turns out, it seems EFI must be specified as the boot environment as opposed to legacy or BIOS+EFI. Setting the boot environment to EFI only resulted in successful system boot. Thanks for the replies. The answer came from Allan Jude on Twitter. On Mon, Mar 12, 2018 at 6:18 PM Rick Miller wrote: > Hi all, > > Thanks in advance to anyone that might be able to help. I subscribed to > freebsd-geom@ so that the list did not need to "reply-all". Having > trouble getting FreeBSD 11-STABLE @ r329011 to boot from SAS3 4Kn HDDs via > LSISAS 3008 HBA on a SuperMicro X10DRH-iT motherboard after an apparent > installation. All internal media (including all other disks attached to the > HBA) were removed to eliminate other storage being the reason the system > won't boot. This occurs specifically in CSM mode, but the preference is to > boot via UEFI mode instead. > > Anyway...booting the machine via the memstick image demonstrates the > LSISAS 3008 controller attaching via mpr(4) (whose manpage describes the > controller being supported[1]): > > mpr0@pci0:3:0:0: class=0x010700 card=0x080815d9 chip=0x00971000 rev=0x02 > hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS3008 PCI-Express Fusion-MPT SAS-3' > class = mass storage > subclass = SAS > > The only inserted disk attaches as da0 as illustrated by dmesg: > > ses0: pass0,da0: Elemne t descriptor: 'Slot00' > da0 at mpr0 bus 0 scbus0 target 8 lun 0 > ses0: pass0,da0: SAS Device Slot Element: 1 Phys at Slot 0 > ses0: phy 0: SAS device type 1 id 0 > ses0: phy 0: protocols: initiator( None ) Target( SSP ) > ses0: phy 0: parent 500304801e870bff addr 5000c500a012814d > da0: Fixed Direct Access SPC-4 SCSI device > da0: Serial Number $serial_number > da0: 1200.000MB/s transfers > da0: Command queueing enabled > da0: 1907729MB (488378648 4096 byte sectors) > > The original goal was to boot via zfs root, but when that failed, > subsequent installations used the "Auto (UFS) option" to partition the > disk. For example, the first installation gpart'd the disk as: > > # gpart show da0 > => 6 488378635 da0 GPT (1.8T) > 6 128 1 freebsd-boot (512K) > 134 487325568 2 freebsd-ufs (1.8T) > 487325702 1048576 3 freebsd-swap (4.0G) > 488374278 4363 - free - (17M) > > The result was a reboot loop. When the system reached the point of reading > the disk, it just rebooted and continued doing so. There was no loader or > beastie menu. Thus, thinking that it could be the partition layout > requirements of the 4Kn disks, it was gpart'd like the below[2][3]. This > was done by exiting to the shell during the partition phase of bsdinstall > and manually gpart'ing the disk according to the below, mounting da0p2 at > /mnt and placing an fstab at /tmp/bsdinstall_etc/fstab that included mount > entries for /dev/da0p2 at / and /dev/da0p3 as swap. > > # gpart show da0 > => 6 488378635 da0 GPT (1.8T) > 6 34 - free - (136K) > 40 512 1 freebsd-boot (2.0M) > 552 419430400 2 freebsd-ufs (1.6T) > 419430952 1048576 3 freebsd-swap (4.0G) > 420479528 67899113 - free - (259G) > > When configured as such, the system rebooted at the completion of the > install and appeared to roll through the boot order, which specifies the > HDD first, then CD/DVD, then network. It did attempt to boot via network, > but is irrelevant here. > > All the hardware is alleged to be supported by FreeBSD as best I can tell > and OS installation apparently works. I'm at a loss as to why the OS won't > boot. Does someone have feedback or input that may expose why it doesn't > boot? > > FWIW, a RHEL7 install was also attempted, which also does not boot. > > [1] > https://www.freebsd.org/cgi/man.cgi?query=mpr&apropos=0&sektion=4&manpath=FreeBSD+11.1-RELEASE&arch=default&format=html > [2] > https://lists.freebsd.org/pipermail/freebsd-hardware/2013-September/007380.html > [3] http://www.wonkity.com/~wblock/docs/html/disksetup.html > > -- > Take care > Rick Miller > -- Take care Rick Miller