From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscan -- no volume groups found
Date: Wed, 4 Apr 2001 14:35:07 -0600 (MDT) [thread overview]
Message-ID: <200104042035.f34KZ8M09891@webber.adilger.int> (raw)
In-Reply-To: <005c01c0bd15$707ee0a0$0400a8c0@ci696011a.lxintn1.ky.home.com> from Jonathan DeHaan at "Apr 4, 2001 10:42:14 am"
You write:
> Having successfully installed LVM on /dev/md0 (sd[ab]1) including root on
> LVM, I was finally ready to kill my online backup on /dev/hda6. I pvcreated
> it, vgextended it, and lvextended an lv that needed more room. When I
> rebooted, however, vgscan cannot find my vg. I am using kernel 2.4.2 and
> 0.9.1_beta5.
>
> I downloaded beta6 tools and created a separate initrd on another machine
> that gives me a bash prompt, but vgscan now complains of invalid i/o
> protocol v. 11. I did try the UUID trick found in the mailing list archives,
> and I have verified that both my PV's have the correct list of UUIDs in
> order, but beta5 vgscan still complains of no volume groups found.
Beta5 was a strange beast, and it is the only one with IOP 11. You need
to run beta5 tools with a beta5 kernel. Otherwise, you should run beta6
tools with beta6 kernel, or beta[234] tools with beta[2346] kernel.
I don't recall which problems were fixed beta5 -> beta6. Is it possible
for you to get another kernel (beta6 preferrably) so you can run beta6
tools?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-04-04 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 14:42 [linux-lvm] vgscan -- no volume groups found Jonathan DeHaan
2001-04-04 20:35 ` Andreas Dilger [this message]
2001-04-04 21:06 ` Jonathan DeHaan
2001-04-04 21:19 ` Les Hazelton
2001-04-04 21:56 ` Andreas Dilger
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=200104042035.f34KZ8M09891@webber.adilger.int \
--to=adilger@turbolinux.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 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 NNTP newsgroup(s).