From owner-freebsd-questions@freebsd.org Sat Jan 20 23:24:48 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 891A0ECD02F for ; Sat, 20 Jan 2018 23:24:48 +0000 (UTC) (envelope-from srs0=vfrx=ep=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id 78B0B6FC0D for ; Sat, 20 Jan 2018 23:24:48 +0000 (UTC) (envelope-from srs0=vfrx=ep=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3zPD9B1vLBz2fjVf for ; Sat, 20 Jan 2018 15:16:46 -0800 (PST) From: Doug Hardie Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Hang in boot process Message-Id: <6682876F-CD99-4A3D-862B-9C7814D91B81@mail.sermon-archive.info> Date: Sat, 20 Jan 2018 15:16:45 -0800 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3445.5.20) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean 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: Sat, 20 Jan 2018 23:24:48 -0000 I used restore to put a working dump over an old drive. I did a newfs = on the slice first. When booting, it puts out the message loading the = kernel and hangs for over an hour. I booted in verbose mode and got = some more information. It puts out the message about starting init = before the hang, but that's the last message. I know it is reading the = drive properly because I changed fstab from the physical entry for root = to the label and the boot message properly showed the new label entry. = Just before the init message there are a number of messages about = alignment not being correct. I understand that the performance of the = drive would be affected by that, but I didn't think that should cause a = hang. Lots of information and test measurements on the performance, but = no indications that it should hang. I suspect that particular drive was = formatted many years ago and it's highly likely its not 4k aligned. I = am going to try again later today after restructuring the drive. -- Doug