From: "Ben Holness" <ben@bens-house.org.uk>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] LVM Boot = /sbin/modprobe: error while loading shared libraries: libzso.1
Date: Wed Dec 26 19:28:02 2001 [thread overview]
Message-ID: <000401c18e76$2917df40$0b00a8c0@homelan.org> (raw)
In-Reply-To: <000201c18e66$847edec0$0b00a8c0@homelan.org>
>> did you run lilo again after creatinh the initrd?
>
> <sheepish grin> No </sheepish grin>
>
> OK, ran lilo and it got back to stage one again - cannot open
> libz.so.1
> (error exactly the same as per my first LVM root mail) :(
And having looked around a bit more, I discovered that the newer version
creates an image in /boot that is not called initrd :)
So I changed /boot/lilo.conf to reflect the new boot image and tried again.
This time the image decompresses OK and then I get:
****
VFS: Mounted root (ext2 filesystem)
VFS: Cannot open root device "3a01" or 3a:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 3a:01
****
> I had some trouble with pvcreate because MDK set my system up with devfs
> enabled.
> Could this be playing some part in the problem?
I should also mention that I ran lvmcreate_initrd with the -D option, but
that didn't help.
Cheers,
Ben
next prev parent reply other threads:[~2001-12-26 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-25 22:01 [linux-lvm] LVM Boot = /sbin/modprobe: error while loading shared libraries: libzso.1 Ben Holness
2001-12-26 3:56 ` Luca Berra
2001-12-26 5:22 ` Ben Holness
2001-12-26 16:47 ` Luca Berra
2001-12-26 17:36 ` Ben Holness
2001-12-26 19:28 ` Ben Holness [this message]
2001-12-27 1:43 ` Luca Berra
2001-12-27 13:29 ` Ben Holness
2001-12-27 18:13 ` Luca Berra
2001-12-27 19:34 ` Steven Lembark
2001-12-28 4:47 ` Ben Holness
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='000401c18e76$2917df40$0b00a8c0@homelan.org' \
--to=ben@bens-house.org.uk \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox