From: Digimer <lists@alteeve.ca>
To: Tom+Dale <tdmyth@yahoo.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Logical Volume Inaccessible
Date: Sun, 12 Jan 2014 00:17:01 -0500 [thread overview]
Message-ID: <52D2254D.5090802@alteeve.ca> (raw)
In-Reply-To: <1389502767.50207.YahooMailNeo@web161703.mail.bf1.yahoo.com>
On 11/01/14 11:59 PM, Tom+Dale wrote:
>
>> What does 'pvscan; vgscan; lvscan' show? If the LVs show 'inactive', try
>
>> 'lvchange -ay <lv_path>', then 'lvscan' should show the LV as 'ACTIVE'.
>> If so, try mounting the LV.
>> --
>> Digimer
>> Papers and Projects: https://alteeve.ca/w/
>> What if the cure for cancer is trapped in the mind of a person without
>> access to education?
>
> Here is what I got:
>
> [root@localhost ~]# pvscan
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> No matching physical volumes found
> [root@localhost ~]# lvscan
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> [root@localhost ~]# vgscan
> Reading all physical volumes. This may take a while...
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> [root@localhost ~]# lvchange -ay /dev/sda2
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 0: Input/output error
> /dev/sda2: read failed after 0 of 1024 at 4096: Input/output error
> /dev/sda2: read failed after 0 of 2048 at 0: Input/output error
> Volume group "sda2" not found
> Skipping volume group sda2
> [root@localhost ~]#
Eep,
That looks like the drive might be failing. If you don't have a good
backup, then you might want to stop. If the data on the drive is very
valuable, I would do nothing more and call a data recovery house. If
that's not feasible, then the first thing I would do is connect another
drive of equal or larger size and dd the bad drive to the other drive.
For example, if the bad drive comes up as /dev/sdb and the
spare/backup drive comes up as /dev/sdc, you would want to run something
like 'dd if=/dev/sdb of=/dev/sdc bs=8k'. That will clone, byte for byte,
sdb onto sdc (and erase whatever was on sdc, of course). Then set aside
the failing drive and try to recover the data on sdc (possibly copy it
again to a 3rd drive, just to be extra safe). This way, if something
goes wrong, you can start over.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
next prev parent reply other threads:[~2014-01-12 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 4:28 [linux-lvm] Logical Volume Inaccessible Tom+Dale
2014-01-12 4:34 ` Digimer
2014-01-12 4:59 ` Tom+Dale
2014-01-12 5:17 ` Digimer [this message]
2014-01-12 9:38 ` Gabriel
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=52D2254D.5090802@alteeve.ca \
--to=lists@alteeve.ca \
--cc=linux-lvm@redhat.com \
--cc=tdmyth@yahoo.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