From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgchange doesn't activate the logical volume
Date: Wed, 21 Jun 2006 10:42:11 +0200 [thread overview]
Message-ID: <44990663.60400@conterra.de> (raw)
In-Reply-To: <004001c69509$fa226440$713a14ac@iai.co.il>
Daniel Loney wrote:
> suse01:~ # vgdisplay -v vg02| more
> Using volume group(s) on command line
> Finding volume group "vg02"
> /dev/sda: read failed after 0 of 4096 at 0: Input/output error
looks like a bad sector/read error on /dev/sda.
You may verify this either by a simple
dd if=/dev/sda of=/dev/null bs=512 iflag=direct
to find the bad sectors number. Or you may run
"badblocks -s /dev/sda", which does roughly the same.
I strongly suggest to use smartctl to monitor the state of your
disk (see http://smartmontools.sourceforge.net). Most problems
show up here some time before your disk finally dies.
Try "smartctl -d ata -a /dev/sda" to display the disks error log.
If you did not use it before, you might have to enable it by:
"smartctl -d ata -s on /dev/sda".
All disks have spare sectors they can use, if some sector gets broken
But the sector is not automatically replaced, as most people believe.
This does not happen until some new data is written to that sector.
If your bad sector occurs within the LVM metadata description of /dev/sda
you may recover it by using "vgcfgrestore" to repair the broken LVM header.
I did not use vgcfgrestore before, so I can't describe the necessary steps
in detail. May be someone else can help here...
Dieter.
next prev parent reply other threads:[~2006-06-21 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 8:09 [linux-lvm] vgchange doesn't activate the logical volume Daniel Loney
2006-06-21 8:37 ` Patrick Caulfield
2006-06-21 8:42 ` Dieter Stüken [this message]
2006-06-22 7:07 ` Daniel Loney
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=44990663.60400@conterra.de \
--to=stueken@conterra.de \
--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;
as well as URLs for NNTP newsgroup(s).