From: Lawrence Strydom <laurie@midafrica.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LV recovery
Date: Mon Dec 9 09:31:01 2002 [thread overview]
Message-ID: <1039448039.1422.42.camel@lawrence> (raw)
In-Reply-To: <20021209143005.A19400@sistina.com>
Hi Heinz,
I get the following output:
insmod: /lib/modules/2.4.7-4GB/kernel/drivers/md/lvm-mod.o: insmod
char-major-109 failed.
vgscan -- LVM driver module not loaded
That freaks me out a bit because the module is present. When I try to
load it manually with insmod I get the same error. Does this mean the
metadata has been overwritten?
Thanks
Lawrence
On Mon, 2002-12-09 at 15:30, Heinz J . Mauelshagen wrote:
>
> Lawrence,
>
> vgscan should recognize your VG fine if nothing overwrote the LVM metadata
> on /dev/hdc.
> What does vgscan dispay ?
>
> On Mon, Dec 09, 2002 at 02:45:36PM +0200, Lawrence Strydom wrote:
> > Hi,
> > My company uses a SuSE email server III solution. The box has 2 IDE
> > drives, hda with /boot, /, and swap partintions on. The second, hdc, was
> > placed in a LVG with a LV for /var occupying all availlable space.
> > While I was away (quick absolution of self) one of the junior guys did
> > an online update of the software after which the system wouldn't start
> > again. To make a long story short, I managed to get the system going
> > again BUT..... /var cannot be mounted.
> > /etc/fstab points to /dev/system/VAR. Upon inspection, this binary file
> > turns out to contain nothing but an error message about being unable to
> > write to /lib/modules/2.4.18-nnnnn/modules.dep. Ooops...
> > Now my question is this: Is it possible to recover the data from the
> > /var LV if the /dev/system/VAR file has gone AWOL?
> > Any pointers to documentation/tools will be very much appreciated.
> >
> > Thanks,
> > Lawrence
> >
> >
> >
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> --
>
> Regards,
> Heinz -- The LVM Guy --
>
> *** Software bugs are stupid.
> Nevertheless it needs not so stupid people to solve them ***
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> Heinz Mauelshagen Sistina Software Inc.
> Senior Consultant/Developer Am Sonnenhang 11
> 56242 Marienrachdorf
> Germany
> Mauelshagen@Sistina.com +49 2626 141200
> FAX 924446
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2002-12-09 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 6:42 [linux-lvm] LV recovery Lawrence Strydom
2002-12-09 7:38 ` Heinz J . Mauelshagen
2002-12-09 9:31 ` Lawrence Strydom [this message]
2002-12-09 12:15 ` Heinz J . Mauelshagen
2002-12-09 13:15 ` Lawrence Strydom
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=1039448039.1422.42.camel@lawrence \
--to=laurie@midafrica.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