Results 1 to 5 of 5
Hi all,
I believe this RedHat system with fiber attached EMC Array was improperly shut down, and it appears that one of my PV's has gone belly up. I've tried ...
- 08-17-2011 #1Just Joined!
- Join Date
- May 2011
- Posts
- 5
Missing Device in my LVM
Hi all,
I believe this RedHat system with fiber attached EMC Array was improperly shut down, and it appears that one of my PV's has gone belly up. I've tried quite a few things to recover the lvm to no avail. So here I am asking if anyone has some thoughts on how I might proceed.
#uname -a
Linux removed.host.name 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
#pvscan
Couldn't find device with uuid i6KfNc-qcLb-x2b2-Yc6P-7cFq-1nGJ-9O0KmG.
PV /dev/emcpowera1 VG VOL_modelers lvm2 [2.69 TB / 0 free]
PV unknown device VG VOL_modelers lvm2 [2.64 TB / 130.99 GB free]
PV /dev/sda3 VG VolGroup_ID_10437 lvm2 [1.13 TB / 11.34 GB free]
PV /dev/sda1 VG VolGroup_ID_10437 lvm2 [232.81 GB / 0 free]
Total: 4 [6.68 TB] / in use: 4 [6.68 TB] / in no VG: 0 [0 ]
#cat /etc/lvm/archive/VOL_modelers_00005.vg
# Generated by LVM2 version 2.02.40-RHEL5 (2008-10-24): Wed May 13 16:09:17 2009
contents = "Text Format Volume Group"
version = 1
description = "Created *before* executing 'lvcreate VOL_modelers --name lvm01 --size 5320GB'"
creation_host = "removed.host.name.com" # Linux removed.host.name.com 2.6.18-128.1.10.el5 #1 SMP Wed Apr 29 13:53:08 EDT 2009 x86_64
creation_time = 1242256157 # Wed May 13 16:09:17 2009
VOL_modelers {
id = "ouKCkd-g2k2-gG6a-MG0V-ktEn-GVcB-Or3zYX"
seqno = 3
status = ["RESIZEABLE", "READ", "WRITE"]
flags = []
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
physical_volumes {
pv0 {
id = "oCTKiJ-XLAr-W791-6mD5-29vF-aG9m-IpVrDl"
device = "/dev/emcpowera1" # Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 5769265085 # 2.68652 Terabytes
pe_start = 384
pe_count = 704255 # 2.68652 Terabytes
}
pv1 {
id = "i6KfNc-qcLb-x2b2-Yc6P-7cFq-1nGJ-9O0KmG"
device = "/dev/emcpowerb1" # Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 5662310333 # 2.63672 Terabytes
pe_start = 384
pe_count = 691199 # 2.63671 Terabytes
}
}
}
#vgchange -an --partial
Partial mode. Incomplete logical volumes will be processed.
Couldn't find device with uuid i6KfNc-qcLb-x2b2-Yc6P-7cFq-1nGJ-9O0KmG.
0 logical volume(s) in volume group "VOL_modelers" now active
Can't deactivate volume group "VolGroup_ID_10437" with 6 open logical volume(s)
#pvcreate --uuid "i6KfNc-qcLb-x2b2-Yc6P-7cFq-1nGJ-9O0KmG" --restorefile /etc/lvm/archive/VOL_modelers_00005.vg /dev/emcpowerb1
Couldn't find device with uuid i6KfNc-qcLb-x2b2-Yc6P-7cFq-1nGJ-9O0KmG.
Device /dev/emcpowerb1 not found (or ignored by filtering).
***As you can tell from above I believe the "unknown device" should be /dev/emcpowerb1, based on the archive, but pvcreate wont assign the UUID, which I'm assuming I need to do in order to restore this lv... am I way up the wrong tree here or on the right track?
Thanks in advance for any and all guidance on this issue!
- 08-17-2011 #2Linux Guru
- Join Date
- Nov 2007
- Posts
- 1,695
This device is missing from the system. Reconnect it or find out the new device name if it's changed. Altho, if it were anywhere on the system, it should find the device by UUID. The blkid command will list the UUID of devices the kernel can see.Code:/dev/emcpowerb1
- 08-17-2011 #3Just Joined!
- Join Date
- May 2011
- Posts
- 5
Thanks for the quick reply!
So, you're saying the device itself is not physically attached? Since this is a fiber connected array, I suppose either the HBA or the physical fiber connection could be bad...
Wouldn't it not show up in pvscan then?
Here is the output of blkid
#blkid
/dev/mapper/VolGroup_ID_10437-LogVol0: TYPE="swap"
/dev/mapper/VolGroup_ID_10437-LogVol4: UUID="5d10620b-58e3-4766-a514-3cdb3bca75e6" TYPE="ext3"
/dev/mapper/VolGroup_ID_10437-LogVol5: UUID="bc5c005e-8a65-423e-944d-fc5b92bb4f1a" TYPE="ext3"
/dev/mapper/VolGroup_ID_10437-LogVol2: UUID="bc25876b-0507-4ce1-9758-c7e6cc0bcd12" TYPE="ext3"
/dev/mapper/VolGroup_ID_10437-LogVol1: UUID="69cc8a87-d8bb-4dc6-9ae5-85ab9af10cc9" TYPE="ext3"
/dev/sda2: LABEL="/boot" UUID="f9953782-8fbb-43e5-b05b-cd0b794e068a" TYPE="ext3"
/dev/VolGroup_ID_10437/LogVol1: UUID="69cc8a87-d8bb-4dc6-9ae5-85ab9af10cc9" SEC_TYPE="ext2" TYPE="ext3"
/dev/VolGroup_ID_10437/LogVol0: TYPE="swap"
/dev/mapper/VolGroup_ID_10437-LogVolHome: UUID="e82f5573-e160-4bb1-a980-352734c0dc14" TYPE="ext3"
- 08-17-2011 #4Linux Guru
- Join Date
- Nov 2007
- Posts
- 1,695
^ Missing deviceCode:PV unknown device VG VOL_modelers lvm2 [2.64 TB / 130.99 GB free]
You can check lssci (if you have it installed) or /proc/scsi/scsi to see what devices are seen by the kernel. If multiple disks come from the fabric and other disks are online, it's likely not an HBA issue. Refer to the array or masking on the array if a LUN is missing on the host.
Code:cat /proc/scsi/scsi ls -alh /dev/emc*
- 08-17-2011 #5Just Joined!
- Join Date
- May 2011
- Posts
- 5
It looks like it's seeing some of the attached drives, via /dev...
#cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 08 Lun: 00
Vendor: DP Model: BACKPLANE Rev: 1.05
Type: Enclosure ANSI SCSI revision: 05
Host: scsi0 Channel: 02 Id: 00 Lun: 00
Vendor: DELL Model: PERC 5/i Rev: 1.03
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: DGC Model: RAID 5 Rev: 0220
Type: Direct-Access ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: DGC Model: RAID 5 Rev: 0220
Type: Direct-Access ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: DGC Model: RAID 5 Rev: 0220
Type: Direct-Access ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 01 Lun: 01
Vendor: DGC Model: RAID 5 Rev: 0220
Type: Direct-Access ANSI SCSI revision: 04
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: Dell Model: Virtual CDROM Rev: 123
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: Dell Model: Virtual Floppy Rev: 123
Type: Direct-Access ANSI SCSI revision: 02
#ls -alh /dev/emc*
crw-r--r-- 1 root root 10, 62 Aug 16 20:05 /dev/emcpower
brw-r----- 1 root disk 120, 0 Aug 16 20:05 /dev/emcpowera
brw-r----- 1 root disk 120, 1 Aug 16 20:05 /dev/emcpowera1
brw-r----- 1 root disk 120, 16 Aug 16 20:05 /dev/emcpowerb


Reply With Quote