linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bill Mair <bill.mair@web.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: HELP: LVM1 not starting automatically
Date: Mon, 23 May 2005 00:52:41 +0200	[thread overview]
Message-ID: <d6qrbv$f5k$1@sea.gmane.org> (raw)
In-Reply-To: <d6pnof$irl$1@sea.gmane.org>

Bill Mair wrote:
> Hi all,
> 
> After a HD failure "mid-pvmove" no less, my LVM won't start 
> automatically :(
> 
> System: Debian sarge with LVM1.

<snip/>

Many thanks to Robot101 (Robert McQueen) for his help on IRC (irc.freenode.net
on the #lvm channel).

It back up and running now, I had to upgrade to LVM2, and it was happy with 
the situation.

Because my kernel already had device-mapper support compiled in, it wasn't a
problem to move to LVM2.

What I did (under Robert's instruction) was the following:

1) Grabbed the lvm2 package (without installing)
  apt-get -d install lvms

2) Unpacked it to access the tools
   mkdir lvm2
   cd lvm2
   dpkg -x /var/cache/apt/archives/lvm2 .... .deb

3) Rebooted to single user mode

4) cd lvm2/lib/lvm-200

** USE LOCAL LVM2 TOOLS !

5) ./vgscan

-- LVM2 found rootvg without a problem

** USE LOCAL LVM2 TOOLS !

6) ./vgchange -a y

-- LVM2 activated rootvg without a problem

7) Installed lvm2

   dpkg -i /var/cache/apt/archives/lvm2 .... .deb

8) reboot

Voila, no more LVM problems.

After that I unitsalled lvm10 and adjusted /etc/lvm/lvm.conf so that it
wasn't looking for LVM devices on the loop back interface or /dev/hd.*

Everythings working now as I wanted, so once again many thanks to
Robot101 :)

--
Bill

      reply	other threads:[~2005-05-22 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-22 10:44 [linux-lvm] HELP: LVM1 not starting automatically Bill Mair
2005-05-22 22:52 ` Bill Mair [this message]

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='d6qrbv$f5k$1@sea.gmane.org' \
    --to=bill.mair@web.de \
    --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 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).