From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Debian, lilo and LVM won't boot
Date: Mon, 13 Oct 2008 19:06:47 +0800 [thread overview]
Message-ID: <0EDF8D2F58BA45B2A3D247D10E821695@bouncy> (raw)
In-Reply-To: <48F31A67.8020507@baechler.net>
Perhaps the people on irc.freenote.net or similar can help;
I use mkinitramfs to generate my initial ram disks and you need devmapper
support in the kernel you're trying to boot lvm on.
Perhaps the speakup kernel is badly configured no idea.
Regards, Kerry.
----- Original Message -----
From: "Tony Baechler" <tony@baechler.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, October 13, 2008 5:52 PM
Subject: Re: Debian, lilo and LVM won't boot
Kerry Hoath wrote:
> You need to rebuild the initrd with update-initrams I believe it is called
> so it knows about the lvm setup.
> You also need to edit the configuration files for
> mkinitramfs so it includes all modules including lvm.
>
I did, several times. Unfortunately, I can't boot to the correct
2.6.25-2-686 kernel because that is on the second drive and the
initramfs won't boot, so the only way I can get to my system is with the
rescue CD with a custom kernel. I've ran update-initramfs several times
and it complains that it can't find /proc/modules. Of course it can't,
/proc isn't mounted but I don't think it would matter because the
modules are for the wrong kernel anyway. The rescue CD has xfs, lvm and
such built in, not loaded as modules, so I don't think that
/proc/modules from that kernel would be correct. I've verified that
these things are built-in with lsmod.
Also, even when it builds an image, it's slightly bigger than my old
backups as one would expect, but it still seems to make no difference.
After it updates, it runs lilo and lilo gives no errors or warnings but
still no boot. I usually run this command:
update-initramfs -u
I had to use -t at one point because it said I had a custom initramfs
when I know I didn't. I could try -c and have it make a new one from
scratch but see above about running different kernels.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Tony Baechler
` Kerry Hoath
` Tony Baechler
` Kerry Hoath [this message]
` Tony Baechler
` Kerry Hoath
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=0EDF8D2F58BA45B2A3D247D10E821695@bouncy \
--to=kerry@gotss.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).