From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: [linux-lvm] recover data from a pv that has first 4k damaged?
Date: Wed, 28 Jul 2004 02:01:42 -0400 [thread overview]
Message-ID: <1090994503.29875.41.camel@pc> (raw)
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
~sigh~
I sure was hoping I would never be one of those posting here with a
"help, my volume group has fallen and it can't get up" messages. But
the the time has come and the hard disk Grimm Reaper is standing over
me.
I have the following set up:
IDE0 Master: hda1: ext3 /boot
hda2: PV 1/2 of a single VG, but empty/unused
IDE1 Master: hdc: PV 2/2 of the same single VG
So all data is on hdc, which is the 2nd "part" of a 2 part VG. The
first part (hda2) is completely unused (because that disk sucks in terms
of performance).
Now for some reason, the first 4k (exactly 4096 bytes) of hdc is
unreadable. It gives up all kinds of errors trying to read it. However
I can read from 4096 bytes and beyond (dd if=/dev/hdc bs=4096 skip=1)
just fine.
hdc is large. 80GB or 160GB, I don't remember, and currently we are not
using but a few GB of it, so I am copying the first 20GB of the disk to
a spare 20GB HD here in my workstation, including 4096 empty bytes at
the beginning of the target disk:
(dd if=/dev/zero bs=4096 count=1 && dd if=/dev/hdc bs=4096 skip=1) |
ssh root@pc "dd of=/dev/hdc bs=1024k"
so that everything lines up, block offset wise.
Remember hda seems to be fine. hdc is the one in trouble.
What can I do to get as much data off of hdc as possible? Presumably if
I can get the lvm metadata back on it (the 20GB disk where there will be
no read errors in the 4096 bytes) and fsck (or debugfs) the filesystems,
only a few files (hopefully system binaries, etc. -- easily restorable)
will be damaged.
Thots?
Thanx,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-07-28 6:02 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=1090994503.29875.41.camel@pc \
--to=brian@interlinx.bc.ca \
--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