Linux LVM users
 help / color / mirror / Atom feed
From: Daniel Roth <daniel@danielroth.se>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: Can't mount after crash
Date: Fri, 07 Jan 2005 00:03:59 +0100	[thread overview]
Message-ID: <41DDC3DF.80009@danielroth.se> (raw)
In-Reply-To: <20041221204852.GR26670@agk.surrey.redhat.com>

Alasdair G Kergon wrote:

>On Sun, Dec 12, 2004 at 12:19:42AM +0100, Daniel Roth wrote:
>  
>
>>My lvm-system crashed a day ago and I was really lost in how to do. 
>>    
>>
>
>You don't say how you actually first discovered something had gone wrong,
>or give any clues about what might have led up to the problem causing it.
>
>Your message doesn't show any LVM problems.
>
>Did something scribble over your disks?
>Have you tried mounting with alternative superblocks?
>  
>
Ok. I did an upgrade of my Debian system.apt-get update && apt-get 
upgrade *. lvm version got
updated as well. Afterwards I did a reboot to put in some extra hw 
(memory). After reboot I couldn't
mount my volume at all. No VG was found et.c. I tried to vgcfgrestore 
without any halp whatsoever
It only said that the pv could not be found or equiv so I restored them 
with the pvcreate line below,
which worked fine on the volumes and a vg and lvm was set up 
appropriately. Still unmountable,
Still unable to fsck.ext2 it with some diffrent superblocks.

I'd be happy to give any specific information you might need to find out 
any way to restore, since
I have run completely out of ideas. If the file system only is "wrapped" 
into the lvm I'd like to
find a tool which can scan disks and recognize superblocks, since I only 
have tried the 3-4 first
I could count up to.

>>I found the metadatafile and could with
>>pvcreate --uuid ... --restorefile ... .... /hdg5,
>>    
>>
>
>You should only use those if you've lost a disk or accidentally overwritten
>the start of one and vgcfgrestore isn't working.
>
>Alasdair
>  
>

"or accidentally overwritten the start of one" is maybe just what has happened.


Daniel

      reply	other threads:[~2005-01-06 23:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 23:19 [linux-lvm] Can't mount after crash Daniel Roth
2004-12-15  4:49 ` Daniel Roth
2004-12-16 18:25   ` Daniel Roth
2004-12-16 18:49     ` Dan Stromberg
2004-12-21 21:10       ` Alasdair G Kergon
2004-12-21 21:53         ` Dan Stromberg
2005-01-09 21:51           ` Daniel Roth
2004-12-21 20:48 ` [linux-lvm] " Alasdair G Kergon
2005-01-06 23:03   ` Daniel Roth [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=41DDC3DF.80009@danielroth.se \
    --to=daniel@danielroth.se \
    --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