From: John Hearns <john.hearns@streamline-computing.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Inactive volume at boot time
Date: Fri, 18 May 2007 12:17:23 +0100 [thread overview]
Message-ID: <464D8B43.6040703@streamline-computing.com> (raw)
I've just had a system which had a problem mounting a logical volume.
SuSE 9.3 and
I log in and lvscan says the volume is inactive.
vgchange -a y and it is active, and mounts first time.
In the boot log:
Scanning for LVM volume groups...
Reading all physical volumes. This may take a while...
No volume groups found
Activating LVM volume groups...
No volume groups found
Is there any other way of checking why it couldn't find the volumes at
boot time? The two physical drives are seen OK just before the LVM start.
I guess another reboot will be the acid test, just wondering if there is
another diagnostic I can run.
--
John Hearns
Senior HPC Engineer
Streamline Computing,
The Innovation Centre, Warwick Technology Park,
Gallows Hill, Warwick CV34 6UW
Office: 01926 623130 Mobile: 07841 231235
reply other threads:[~2007-05-18 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=464D8B43.6040703@streamline-computing.com \
--to=john.hearns@streamline-computing.com \
--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).