Linux LVM users
 help / color / mirror / Atom feed
From: Heine Laursen <maillist@gozar.dynu.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM1 Bad harddisk. How do I het data off the Volume?
Date: Thu, 24 Feb 2005 21:16:20 +0100	[thread overview]
Message-ID: <421E3614.5010107@gozar.dynu.com> (raw)

Hi.

One of my harddisks in my 2 harddisk LVM 1 setup, The bad harddisk is a 
120 GB Maxtor harddisk, who now identifies itself to the system as:
hde: Oaztor"6[120R0" " " " " " " " " " " " ", ATA DISK drive
The bios reports that the size of the harddisk is 80GB!

And of curse, I can't access any LVM volumes!

debian:~# pvscan -v
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/hdf1"  is associated to unknown VG "vg" (run 
vgscan)
pvscan -- total: 1 [76.34 GB] / in use: 1 [76.34 GB] / in no VG: 0 [0]

debian:~# vgscan -v
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- reading data of volume group "vg" from physical volume(s)
vgscan -- ERROR "vg_read_with_pv_and_lv(): current PV" can't get data of 
volume group "vg" from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

As I understand, I have to run vgcfgrestore to get access to the volume.
But what about the faulty hde, is it also possebill to get data off this 
disk?
debian:~# fdisk -l /dev/hde

Disk /dev/hde: 16 heads, 63 sectors, 16383 cylinders
Units = cylinders of 1008 * 512 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hde1         33289    271505 120060832+  8e  Linux LVM
/dev/hde2         33289     66578  16777472    0  Empty
Partition 2 does not end on cylinder boundary:
      phys=(2, 2, 0) should be (2, 15, 63)
/dev/hde3         33289     66578  16777472    0  Empty
Partition 3 does not end on cylinder boundary:
      phys=(2, 2, 0) should be (2, 15, 63)
/dev/hde4         33289     66578  16777472    0  Empty
Partition 4 does not end on cylinder boundary:
      phys=(2, 2, 0) should be (2, 15, 63)

How can I rescue as mutch data as possebill?
I do not have access to a spare harddisk to do a dd_rescue on.

I'm useinf debian woody, and LVM 1.
Please advice. I'm afraid i'll do more damage, than rescue!
Thanks.
-- 
Sincerley
Heine Laursen

             reply	other threads:[~2005-02-24 20:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 20:16 Heine Laursen [this message]
2005-02-28  2:49 ` [linux-lvm] LVM1 Bad harddisk. How do I het data off the Volume? Heine Laursen
2005-02-28  2:55   ` David Mohr
2005-02-28 23:49   ` Dan Stromberg
2005-02-28  8:36 ` Patrick Caulfield
2005-02-28 11:19   ` go0ogl3
2005-02-28 17:16     ` Heine Laursen
2005-02-28 18:03       ` M. Matt Colgin
2005-03-01  0:02         ` langelino
2005-02-28 17:14   ` Heine Laursen

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=421E3614.5010107@gozar.dynu.com \
    --to=maillist@gozar.dynu.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