From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2658F1381F3 for ; Fri, 9 Aug 2013 13:43:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E811FE0D3C; Fri, 9 Aug 2013 13:43:16 +0000 (UTC) Received: from dizzy.wrkhors.com (68-188-122-34.static.stls.mo.charter.com [68.188.122.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 2C9ABE0D22 for ; Fri, 9 Aug 2013 13:43:15 +0000 (UTC) Received: from wrkhors.com (localhost [127.0.0.1]) by dizzy.wrkhors.com (Postfix) with ESMTP id A197E59E4480; Fri, 9 Aug 2013 08:43:31 -0500 (CDT) Date: Fri, 9 Aug 2013 08:44:46 -0500 From: Steven Lembark To: gentoo-amd64@lists.gentoo.org Cc: lembark@wrkhors.com Subject: Re: [gentoo-amd64] Re: early boot failure, not sure how to diagnose Message-ID: <20130809084446.3d1356ba.lembark@wrkhors.com> In-Reply-To: References: Organization: Workhorse Computing X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) X-Workhorse-Host: Cannibal Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 337df4ea-0c59-44bc-9cf5-fab0940b6a60 X-Archives-Hash: 9482c8a61a512f0adcf73e8824370323 On Thu, 8 Aug 2013 22:08:50 +1000 Daiajo Tibdixious wrote: > > What happens if you add init=/bin/bash ? Does /that/ get you a It is also easy to build a q&d initrd with nothing more than busybox and something like: #!/bin/busybox sh /bin/busybox --install -s; mkdir /proc; mkdir /sys; mount /proc; mount /sys; lvm vgscan -v; lvm vgchange -v -a y; exec /bin/busybox 'sh'; At that point you can poke around with the busybox util's and see what is going on. If you use RAID then make a static copy of mdadm; ditto "lvm" if you use that. Go through the steps you expect to work by hand and see what happens. At that point you can get more specific error messages without having them all stream by on the screeen. You can build the initrd from a single directory with nothing more than an /etc/fstab, busybox, mdadm, lvm in the bin dir, and /dev populated with null, zero, console, tty, and the sd* devices you really have on the device. Cpio+gzip it into something like /boot/rescue.cpio.gz and use it with initrd. -- Steven Lembark 3646 Flora Pl Workhorse Computing St Louis, MO 63110 lembark@wrkhors.com +1 888 359 3508