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. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
