From: trylinux <trylinux@nc.rr.com>
To: linux-lvm@sistina.com
Cc: trylinux@nc.rr.com
Subject: [linux-lvm] No Subject
Date: Wed Jan 14 18:23:11 2004 [thread overview]
Message-ID: <6413350.1074097638140.JavaMail.Administrator@atp> (raw)
First things first. Is there a FAQ for this group?
Now then, I'm running Fedore Core/1 (Red Hat 9) with LVM 1.0.3-13 (or at
least RPM says it's 1.0.3). I have a single volume group containing a single
disk. While /boot is NOT in the volume group (for obvious reasons),
everything else, include / is. / is a ext3 filesystem.
I recently used vgrename to rename the volume group (from rootvol to rootvg
-- just a test to learn some more), and it seemed to succeed. I was able to
run afterwards with no problems. On the first reboot after this, though, my
system can no longer boot. Here's a rough transscription of what's going on:
...kernel booting/initializing...
Loading lvm-mod.o module
LVM version 1.0.5+(22/07/2002) module loaded
Loading jbd.o module
Journalled Block Device driver loaded
Loading ext3.o module
Mounting /proc filesystem
Creating block devices
Scanning logical volumes
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found inactive volume group "rootvg"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a BGDA backup of your volume
group
Activating logical volumes
vgchange -- volume group "rootvg" successfully activated
Mounting root filesystem
mount: error 2 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrt) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 136k freed
Kernel panic: No init found. Try passing init= option to kernel.
I'd be happy to provide more info if it would help anyone. (grub.conf,
fstab,
etc.)
Cheers,
Rob
next reply other threads:[~2004-01-14 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 18:23 trylinux [this message]
2004-01-15 8:49 ` [linux-lvm] No Subject Ken Fuchs
2004-01-15 8:49 ` Brant Katkansky
2004-01-15 17:05 ` Ken Fuchs
2004-01-16 8:57 ` Rob Cash
2004-01-15 8:54 ` Luca Berra
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=6413350.1074097638140.JavaMail.Administrator@atp \
--to=trylinux@nc.rr.com \
--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 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.