Gentoo Archives: gentoo-amd64

From: Steven Lembark <lembark@×××××××.com>
To: gentoo-amd64@l.g.o
Cc: lembark@×××××××.com
Subject: Re: [gentoo-amd64] Re: early boot failure, not sure how to diagnose
Date: Fri, 09 Aug 2013 13:43:18
Message-Id: 20130809084446.3d1356ba.lembark@wrkhors.com
In Reply to: Re: [gentoo-amd64] Re: early boot failure, not sure how to diagnose by Daiajo Tibdixious
1 On Thu, 8 Aug 2013 22:08:50 +1000
2 Daiajo Tibdixious <daiajo@×××××.com> wrote:
3
4 > > What happens if you add init=/bin/bash ? Does /that/ get you a
5
6 It is also easy to build a q&d initrd with nothing more than
7 busybox and something like:
8
9 #!/bin/busybox sh
10
11 /bin/busybox --install -s;
12
13 mkdir /proc;
14 mkdir /sys;
15
16 mount /proc;
17 mount /sys;
18
19 lvm vgscan -v;
20 lvm vgchange -v -a y;
21
22 exec /bin/busybox 'sh';
23
24 At that point you can poke around with the busybox util's and
25 see what is going on. If you use RAID then make a static copy
26 of mdadm; ditto "lvm" if you use that. Go through the steps you
27 expect to work by hand and see what happens. At that point you
28 can get more specific error messages without having them all
29 stream by on the screeen.
30
31 You can build the initrd from a single directory with nothing
32 more than an /etc/fstab, busybox, mdadm, lvm in the bin dir,
33 and /dev populated with null, zero, console, tty, and the
34 sd* devices you really have on the device. Cpio+gzip it into
35 something like /boot/rescue.cpio.gz and use it with initrd.
36
37 --
38 Steven Lembark 3646 Flora Pl
39 Workhorse Computing St Louis, MO 63110
40 lembark@×××××××.com +1 888 359 3508