From: Steven Lembark <lembark@wrkhors.com>
To: gentoo-amd64@lists.gentoo.org
Cc: lembark@wrkhors.com
Subject: Re: [gentoo-amd64] Re: early boot failure, not sure how to diagnose
Date: Fri, 9 Aug 2013 08:44:46 -0500 [thread overview]
Message-ID: <20130809084446.3d1356ba.lembark@wrkhors.com> (raw)
In-Reply-To: <CAC4mkfu7dudgJXX4x0BiBxXX-wuPFv4J0QaoDJxdsz2_aQbgog@mail.gmail.com>
On Thu, 8 Aug 2013 22:08:50 +1000
Daiajo Tibdixious <daiajo@gmail.com> 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
prev parent reply other threads:[~2013-08-09 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC4mkfuV-cdqm1zh8QobysPJ9pJdvT3v-jXEba-f7JByr4HUZw@mail.gmail. com>
2013-08-08 9:40 ` [gentoo-amd64] Re: early boot failure, not sure how to diagnose Duncan
2013-08-08 12:08 ` Daiajo Tibdixious
2013-08-09 13:44 ` Steven Lembark [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130809084446.3d1356ba.lembark@wrkhors.com \
--to=lembark@wrkhors.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox