From owner-freebsd-questions@freebsd.org Thu Feb 22 22:35:05 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 73848F0778E for ; Thu, 22 Feb 2018 22:35:05 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 044DC7CC69 for ; Thu, 22 Feb 2018 22:35:05 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: by mail-vk0-x232.google.com with SMTP id z190so4165428vkg.1 for ; Thu, 22 Feb 2018 14:35:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tIsMRIx3agJj6j97fS6jq4zsPxXe8lFFARPJUquv4zc=; b=kaa+tN53y/SOkH4La1ZJTErY3IuAWEirVeIqDXweHV4mHmkYMy8USzYXRQ00vf6DY/ wyEgk8fpgqVDteDRHM+FdPAXvuVQaBVfv9qgy0B2DfiwLmhBvS0C+Ngj0uv6IxThBm3V OoY5dNp+pjxL9HlGZHn5C9YMwnA3sJQ98LjvzYyIU8CB8FKB5G0c8Kz7bE1jGWTHq+kC ZWdzOSV6i2mF/IS103gqWezJIq434swZdTrN6lHAYR1Fzzi7/cVwq/NZBlAvfGmZZbg4 FrRGmol6vik7fHWrRObbkrt95P/jKG8jsU+90spxOEhURaDkZ5hTf+h8SOR9Pn6OB7cs 37cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tIsMRIx3agJj6j97fS6jq4zsPxXe8lFFARPJUquv4zc=; b=Efvf9qkFMGogaMVxSl11HlWknfTKhmpNWFejtVfOOIQqW1dFKGKi7Cs6SinMG4gYtu 2SOl4dkpDXMeAtrAKwzOiTddyLG2An7nfva2/rZMCOePV9uTRFBXQ+YdA9XWzw4/K8TG O5Xb4U4/4T0hO69Tt3FnoeTyohWZozVzIC8JTq8wihanX9qz1gz0amxHwM8QoZZ6At+f CfSFFKfUqv3RAWQvI8wFgv2iTR77tjvWcOHx20LBdjl8f9sxvGBGXlkkJaHpDsN7xLbq cNRR5pBIlEV50gCK5vSJHmxH9WahG08p/AO9EOnRpc7k2AH7WywcTHBpYdLkWPaVML4b LRgA== X-Gm-Message-State: APf1xPDbUBQxPub6gpcBeKDqv9I9MCObIvWeFgoLQIe8Ox1AT/iLrIT7 2Pf6acah1zip3MZfUsDqXevBajrPV2Z97uXYBig= X-Google-Smtp-Source: AH8x227SCwA7pILvPnXAzIySsdU231kPZc64DeDs/hohbRgzWZOcPepMKErxO2kET1zqJFWTg4SNfncBjUTfT2tbsD0= X-Received: by 10.31.192.80 with SMTP id q77mr6231159vkf.7.1519338904442; Thu, 22 Feb 2018 14:35:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.60.11 with HTTP; Thu, 22 Feb 2018 14:35:04 -0800 (PST) In-Reply-To: <20180222134439.GA3888@aurora.oekb.co.at> References: <20180222134439.GA3888@aurora.oekb.co.at> From: Rick Miller Date: Thu, 22 Feb 2018 17:35:04 -0500 Message-ID: Subject: Re: HP Proliant DL385 Gen10 refuses to boot FreeBSD 11 To: Ewald Jenisch Cc: FreeBSD Questions 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: Thu, 22 Feb 2018 22:35:05 -0000 On Thu, Feb 22, 2018 at 8:44 AM, Ewald Jenisch wrote: > Hi, > > Got a new HP Proliant DL385 Gen10 Server and wanted to install > FreeBSD. Starting from FreeBSD-11.1-RELEASE-amd64-bootonly.iso mounted > via the iLo virtual CD device the system started with the usual > install boot, but then suddenly crashed and rebooted the whole system > - boot loop basically. > > I started playing around in the BIOS of the System trying UEFI > vs. legacy BIOS, as well a bunch of other parameters but to no extent: > the system just crashes when upon booting from the installation media :-( > > To cross check I tried to boot a Linux installation media (Ubuntu > Server 16.04) and the server booted from the Linux ISO without any > problem. So I'm pretty sure it's something FreeBSD related. > > My questions: > > o) Anybody else out there seen a problem like this on a HP DL385 Gen10? > > o) Any cure against it? > You'd do well by making sure the RAID controller is supported by FreeBSD. Some time in the last 6 months or so, I heard this generation was introducing a new RAID controller that would require a new driver. If it does, indeed, have a new RAID controller it could likely be your problem. -- Take care Rick Miller