All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jozsef Bakosi <jbakosi@gmu.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] No volume groups found at boot
Date: Tue, 24 May 2005 09:08:19 -0400	[thread overview]
Message-ID: <20050524130819.GA10277@debian> (raw)

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hello,

I have

LVM version:     2.01.04 (2005-02-09)
Library version: 1.01.00-ioctl (2005-01-17)
Driver version:  4.1.0

with two working volume groups on an AMD64 Athlon running kernel version
2.6.8 (root@backup) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Fri May 13
08:54:18 EDT 2005 with Debian sarge.

The problem is that /etc/init.d/lvm doesn't find the volume groups at
boot, thus /etc/init.d/checkfs.sh (the next script) stops for
maintenance because it can't find the volumes.

The disks are SATA and all nicely recongized before the init-lvm script
starts (by enforcing the loading of their drivers in /etc/modules).

After boot, I can do "vgscan" and "vgchange -a y", finding the volumes no
problem and can mount them as well.

The strangest thing is when I insert a "/sbin/sulogin $CONSOLE" right
before

/sbin/vgscan $IGNORELOCKINGFAILURES $MKNODES || true
/sbin/vgchange -a y $IGNORELOCKINGFAILURES

in /etc/init.d/lvm and do vgscan and vgchange manually, it works fine.

So what is the difference in between running a command from a script in
/etc/rcS.d/ and mannually from command line?

Jozsef

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-05-24 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 13:08 Jozsef Bakosi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-24 18:31 [linux-lvm] No volume groups found at boot Page, Jennifer (RBC Dain)

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=20050524130819.GA10277@debian \
    --to=jbakosi@gmu.edu \
    --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 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.