From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Ubuntu distro with lvm2, raid 1, not booting anymore.
Date: Fri, 3 Feb 2006 08:31:27 +0100 [thread overview]
Message-ID: <20060203073127.GD5971@percy.comedia.it> (raw)
In-Reply-To: <43E254B5.5080107@poczta.onet.pl>
On Thu, Feb 02, 2006 at 07:51:33PM +0100, Maciej S?ojewski wrote:
>Welcome!
>
>I have the serious problem with booting of my machine. It is run on
>Ubuntu distro (5.10), with lvm2 raid 1 on two identical sata hard disks.
>Lilo bootloader. The problem is that after small change in lilo.conf and
>running /sbin/lilo my system is no longer bootable. I see 'kernel panic'
>message. When I try to run lilo again (from Ubuntu Live! cd) I see some
>comments somehow related to dev-mapper:
>
>Warning: /proc/partitions does not match /dev directory structure
>Name change: /dev/cloop 0 -> /tmp/dev.0
>(...)
>Fatal: is_primary: Not a valid device
what is exactly that you are doing to reinstall lilo?
i don't use ubuntu, but generally:
you should mount your original root fs on, say, /root
mount --bind /dev /root/dev
mount --bind /proc /root/proc
mount --bind /sys /root/sys
chroot /root /sbin/lilo
>
>I will quote the kernel messages:
>RAMDISK: ran out of compressed data
>invalid compressed format (err=1)
looks like your initrd is hosed
check that lilo is pointing to a correct initrd and/or regenerate
initrd. (no i don't remember the debian way to regenerate initrd)
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-02-03 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 18:51 [linux-lvm] Ubuntu distro with lvm2, raid 1, not booting anymore Maciej Słojewski
2006-02-03 7:31 ` Luca Berra [this message]
2006-02-03 18:22 ` Maciej Słojewski
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=20060203073127.GD5971@percy.comedia.it \
--to=bluca@comedia.it \
--cc=linux-lvm@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.