- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: LVM Traces of old disk
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2010 10:46 PM
тАО09-08-2010 10:46 PM
LVM Traces of old disk
We have a SLES 10 version. Recently one of the disks out of RAID 0 got failed. (sdb1) . Which had 2 disks /dev/sdb1 & /dev/sdc1
We have replaced the faulty disk of bigger size. Which is now /dev/sdd1.
But the problem is whenever we run pvdisplay or vgdisplay , we get
# pvdisplay
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
--- Physical volume ---
PV Name /dev/sdd1
VG Name data
PV Size 68.36 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 17500
Free PE 7260
Allocated PE 10240
PV UUID qRZIwB-zs6I-klfc-BpL6-MTQ4-tu4J-8ME0iy
So the problem is , the /dev/sdb1 read failed error occurs.
I have already tried,
pvremove /dev/sdb1 but it says ,
# pvremove /dev/sdb1
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
No physical volume label read from /dev/sdb1
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
Labels on physical volume "/dev/sdb1" successfully wiped
So how to remove the traces of the failed/removed disk /dev/sdb1 ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 04:49 AM
тАО09-09-2010 04:49 AM
Re: LVM Traces of old disk
if you really want to remove the entry have you also tried pvremove -f /dev/sdb1 ??
regards
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 04:52 AM
тАО09-09-2010 04:52 AM
Re: LVM Traces of old disk
# pvremove -f /dev/sdb1
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
No physical volume label read from /dev/sdb1
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
Labels on physical volume "/dev/sdb1" successfully wiped
# pvdisplay
/dev/sdb: read failed after 0 of 2048 at 0: Input/output error
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
--- Physical volume ---
PV Name /dev/sdd1
VG Name data
PV Size 68.36 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 17500
Free PE 7260
Allocated PE 10240
PV UUID qRZIwB-zs6I-klfc-BpL6-MTQ4-tu4J-8ME0iy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 04:57 AM
тАО09-09-2010 04:57 AM
Re: LVM Traces of old disk
regards
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 04:58 AM
тАО09-09-2010 04:58 AM
Re: LVM Traces of old disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 05:01 AM
тАО09-09-2010 05:01 AM
Re: LVM Traces of old disk
see this post:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1284100
for how to use vgreduce on failed disks
hope that helps
regards
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 05:03 AM
тАО09-09-2010 05:03 AM
Re: LVM Traces of old disk
vgreduce --test --removemissing ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 05:11 AM
тАО09-09-2010 05:11 AM
Re: LVM Traces of old disk
the suggestion in that post is to run
vgreduce -l vg pv
but i did not find the -l parameter in man vgreduce.
Btw I tried below command. But no help.
# vgreduce --removemissing data
/dev/sdb: read failed after 0 of 2048 at 0: Input/output error
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
Volume group "data" is already consistent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 05:13 AM
тАО09-09-2010 05:13 AM
Re: LVM Traces of old disk
# vgreduce data /dev/sdb1
/dev/sdb: read failed after 0 of 2048 at 0: Input/output error
/dev/sdb1: read failed after 0 of 2048 at 0: Input/output error
Physical Volume "/dev/sdb1" not found in Volume Group "data"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2010 05:19 AM
тАО09-09-2010 05:19 AM
Re: LVM Traces of old disk
the approach you now take really depends on the order you may have executed LVM commands up to this point.
I would try several things:
make sure you have a full backup
make sure you have a backup of vgcfg and lvmtab
run the few commands at the bottom of this post, which explains better than I can the sort of issues you can have if you get it wrong :-)
http://bisqwit.iki.fi/story/howto/undopvremove/
Go down to where it says 'problem averted'
key points are:
pvs (see if your failed disk is listed here) - please let me know
vgreduce
pvremove
run pvs again and see if your failed disk is no longer listed.
This has worked for me in the past
regards
Matt