Login or Register to Ask a Question and Join Our Community


Linux

LVM VG recovery

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux LVM VG recovery
# 1  
Old 02-16-2017
LVM VG recovery
Hi all,
I been trying to recover a volume group of single PV.
vgcfgrestore output
Code:
[root@tkdb ~]# vgcfgrestore vgoraData
  Couldn't find device with uuid 'a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43'.
  Cannot restore Volume Group vgoraData with 1 PVs marked as missing.
  Restore failed.

fdisk output
Code:
[root@tkdb ~]# fdisk -l

Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14         144     1052257+  82  Linux swap / Solaris
/dev/sda3             145        1044     7229250   8e  Linux LVM

Disk /dev/sdb: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        1305    10482381   83  Linux

Disk /dev/sdc: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        6527    52428096   83  Linux

Disk /dev/sdd: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1        1044     8385898+  82  Linux swap / Solaris

Disk /dev/sde: 64.4 GB, 64424509440 bytes
255 heads, 63 sectors/track, 7832 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1        7833    62914559+  8e  Linux LVM

Disk /dev/sdf: 12.8 GB, 12884901888 bytes
255 heads, 63 sectors/track, 1566 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1               1        1566    12578863+  8e  Linux LVM

Disk /dev/sdg: 25.7 GB, 25769803776 bytes
255 heads, 63 sectors/track, 3133 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1               1        3133    25165791   8e  Linux LVM

Disk /dev/sdh: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1               1         522     4192933+  8e  Linux LVM

Disk /dev/sdi: 6442 MB, 6442450944 bytes
255 heads, 63 sectors/track, 783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdi1               1         783     6289416   8e  Linux LVM

Disk /dev/sdj: 11.8 GB, 11811160064 bytes
255 heads, 63 sectors/track, 1435 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

 


Code:



  Device Boot      Start         End      Blocks   Id  System
/dev/sdj1               1        1435    11526606   83  Linux

The disk which holds LVM metadata and data
Code:
[root@tkdb ~]# fdisk /dev/sdj

The number of cylinders for this disk is set to 1435.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdj: 11.8 GB, 11811160064 bytes
255 heads, 63 sectors/track, 1435 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdj1               1        1435    11526606   83  Linux

Command (m for help): q

pvcreate output
Code:
[root@tkdb ~]# pvcreate -u a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43 --restorefile /etc/lvm/backup/vgoraData /dev/sdj
  Couldn't find device with uuid 'a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43'.
  Device /dev/sdj not found (or ignored by filtering).

pvcreate with verbose output
Code:
[root@tkdb ~]# pvcreate -vv -u a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43 --restorefile /etc/lvm/backup/vgoraData /dev/sdj
      Setting global/locking_type to 1
      File-based locking selected.
      Setting global/locking_dir to /var/lock/lvm
      /dev/ramdisk: size is 32768 sectors
      /dev/ramdisk: size is 32768 sectors
      /dev/ramdisk: No label detected
      /dev/sda: size is 16777216 sectors
      /dev/md0: size is 0 sectors
      /dev/root: size is 10223616 sectors
      /dev/root: size is 10223616 sectors
      /dev/root: No label detected
      /dev/ram: size is 32768 sectors
      /dev/ram: size is 32768 sectors
      /dev/ram: No label detected
      /dev/sda1: size is 208782 sectors
      /dev/sda1: size is 208782 sectors
      /dev/sda1: No label detected
      /dev/vg00/lv_home: size is 2097152 sectors
      /dev/vg00/lv_home: size is 2097152 sectors
      /dev/vg00/lv_home: No label detected
      /dev/ram2: size is 32768 sectors
      /dev/ram2: size is 32768 sectors
      /dev/ram2: No label detected
      /dev/sda2: size is 2104515 sectors
      /dev/sda2: size is 2104515 sectors
      /dev/sda2: No label detected
      /dev/vg00/lv_var: size is 2097152 sectors
      /dev/vg00/lv_var: size is 2097152 sectors
      /dev/vg00/lv_var: No label detected
      /dev/ram3: size is 32768 sectors
      /dev/ram3: size is 32768 sectors
      /dev/ram3: No label detected
      /dev/sda3: size is 14458500 sectors
      /dev/sda3: size is 14458500 sectors
      /dev/sda3: lvm2 label detected
      /dev/vgSLab/lv-oraHome: size is 14671872 sectors
      /dev/vgSLab/lv-oraHome: size is 14671872 sectors
      /dev/vgSLab/lv-oraHome: No label detected
      /dev/ram4: size is 32768 sectors
      /dev/ram4: size is 32768 sectors
      /dev/ram4: No label detected
      /dev/vgSLab/lv-oraDB: size is 48226304 sectors
      /dev/vgSLab/lv-oraDB: size is 48226304 sectors
      /dev/vgSLab/lv-oraDB: No label detected
      /dev/ram5: size is 32768 sectors
      /dev/ram5: size is 32768 sectors
      /dev/ram5: No label detected
      /dev/vgSLabUAT/lv-oraUAT: size is 33529856 sectors
      /dev/vgSLabUAT/lv-oraUAT: size is 33529856 sectors
      /dev/vgSLabUAT/lv-oraUAT: No label detected
      /dev/ram6: size is 32768 sectors
      /dev/ram6: size is 32768 sectors
      /dev/ram6: No label detected
      /dev/ram7: size is 32768 sectors
      /dev/ram7: size is 32768 sectors
      /dev/ram7: No label detected
      /dev/ram8: size is 32768 sectors
      /dev/ram8: size is 32768 sectors
      /dev/ram8: No label detected
      /dev/ram9: size is 32768 sectors
      /dev/ram9: size is 32768 sectors
      /dev/ram9: No label detected
      /dev/ram10: size is 32768 sectors
      /dev/ram10: size is 32768 sectors
      /dev/ram10: No label detected
      /dev/ram11: size is 32768 sectors
      /dev/ram11: size is 32768 sectors
      /dev/ram11: No label detected
      /dev/ram12: size is 32768 sectors
      /dev/ram12: size is 32768 sectors
      /dev/ram12: No label detected
      /dev/ram13: size is 32768 sectors
      /dev/ram13: size is 32768 sectors
      /dev/ram13: No label detected
      /dev/ram14: size is 32768 sectors
      /dev/ram14: size is 32768 sectors
      /dev/ram14: No label detected
      /dev/ram15: size is 32768 sectors
      /dev/ram15: size is 32768 sectors
      /dev/ram15: No label detected
      /dev/sdb: size is 20971520 sectors
      /dev/sdb1: size is 20964762 sectors
      /dev/sdb1: size is 20964762 sectors
      /dev/sdb1: No label detected
      /dev/sdc: size is 104857600 sectors
      /dev/sdc1: size is 104856192 sectors
      /dev/sdc1: size is 104856192 sectors
      /dev/sdc1: No label detected
      /dev/sdd: size is 16777216 sectors
      /dev/sdd1: size is 16771797 sectors
      /dev/sdd1: size is 16771797 sectors
      /dev/sdd1: No label detected
      /dev/sde: size is 125829120 sectors
      /dev/sde1: size is 125829119 sectors
      /dev/sde1: size is 125829119 sectors
      /dev/sde1: No label detected
      /dev/sdf: size is 25165824 sectors
      /dev/sdf1: size is 25157727 sectors
      /dev/sdf1: size is 25157727 sectors
      /dev/sdf1: lvm2 label detected
      /dev/sdg: size is 50331648 sectors
      /dev/sdg1: size is 50331582 sectors
      /dev/sdg1: size is 50331582 sectors
      /dev/sdg1: lvm2 label detected
      /dev/sdh: size is 8388608 sectors
      /dev/sdh1: size is 8385867 sectors
      /dev/sdh1: size is 8385867 sectors
      /dev/sdh1: lvm2 label detected
      /dev/sdi: size is 12582912 sectors
      /dev/sdi1: size is 12578832 sectors
      /dev/sdi1: size is 12578832 sectors
      /dev/sdi1: lvm2 label detected
      /dev/sdj: size is 23068672 sectors
      /dev/sdj1: size is 23053212 sectors
      /dev/sdj1: size is 23053212 sectors
      /dev/sdj1: No label detected
      /dev/ramdisk: No label detected
      /dev/root: No label detected
      /dev/ram: No label detected
      /dev/sda1: No label detected
      /dev/vg00/lv_home: No label detected
      /dev/ram2: No label detected
      /dev/sda2: No label detected
      /dev/vg00/lv_var: No label detected
      /dev/ram3: No label detected
      /dev/vgSLab/lv-oraHome: No label detected
      /dev/ram4: No label detected
      /dev/vgSLab/lv-oraDB: No label detected
      /dev/ram5: No label detected
      /dev/vgSLabUAT/lv-oraUAT: No label detected
      /dev/ram6: No label detected
      /dev/ram7: No label detected
      /dev/ram8: No label detected
      /dev/ram9: No label detected
      /dev/ram10: No label detected
      /dev/ram11: No label detected
      /dev/ram12: No label detected
      /dev/ram13: No label detected
      /dev/ram14: No label detected
      /dev/ram15: No label detected
      /dev/sdb1: No label detected
      /dev/sdc1: No label detected
      /dev/sdd1: No label detected
      /dev/sde1: No label detected
      /dev/sdj1: No label detected
  Couldn't find device with uuid 'a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43'.
      metadata/pvmetadatasize not found in config: defaulting to 255
      metadata/pvmetadatacopies not found in config: defaulting to 1
      /dev/ramdisk: No label detected
      /dev/root: No label detected
      /dev/ram: No label detected
      /dev/sda1: No label detected
      /dev/vg00/lv_home: No label detected
      /dev/ram2: No label detected
      /dev/sda2: No label detected
      /dev/vg00/lv_var: No label detected
      /dev/ram3: No label detected
      /dev/vgSLab/lv-oraHome: No label detected
      /dev/ram4: No label detected
      /dev/vgSLab/lv-oraDB: No label detected
      /dev/ram5: No label detected
      /dev/vgSLabUAT/lv-oraUAT: No label detected
      /dev/ram6: No label detected
      /dev/ram7: No label detected
      /dev/ram8: No label detected
      /dev/ram9: No label detected
      /dev/ram10: No label detected
      /dev/ram11: No label detected
      /dev/ram12: No label detected
      /dev/ram13: No label detected
      /dev/ram14: No label detected
      /dev/ram15: No label detected
      /dev/sdb1: No label detected
      /dev/sdc1: No label detected
      /dev/sdd1: No label detected
      /dev/sde1: No label detected
      /dev/sdj1: No label detected
      Locking /var/lock/lvm/P_orphans WB
      Unlocking /var/lock/lvm/P_orphans
    Wiping cache of LVM-capable devices
    Wiping internal VG cache
      Locking /var/lock/lvm/P_orphans WB
      /dev/sdj: size is 23068672 sectors
  Device /dev/sdj not found (or ignored by filtering).
      Unlocking /var/lock/lvm/P_orphans

LVM version

Code:
[root@tkdb ~]# lvm version
  LVM version:     2.02.46-RHEL5 (2009-06-18)
  Library version: 1.02.32 (2009-05-21)
  Driver version:  4.11.5

most recent backup of VG definition
Code:
[root@tkdb ~]# cat /etc/lvm/backup/vgoraData
# Generated by LVM2 version 2.02.46-RHEL5 (2009-06-18): Tue Feb  7 14:33:32 2017

contents = "Text Format Volume Group"
version = 1

description = "Created *after* executing 'lvextend -L +2044 /dev/vgoraData/lv-oraData'"

creation_host = "tkdb"  # Linux tkdb 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64
creation_time = 1486470812      # Tue Feb  7 14:33:32 2017

vgoraData {
        id = "nJMcgg-cZFm-l7wy-guaX-g6lX-Z913-gGZTX9"
        seqno = 3
        status = ["RESIZEABLE", "READ", "WRITE"]
        flags = []
        extent_size = 8192              # 4 Megabytes
        max_lv = 0
        max_pv = 0

        physical_volumes {

                pv0 {
                        id = "a3onP5-RdbR-fdgq-sDkS-ZtFs-83Q5-kFJj43"
                        device = "/dev/sdj"     # Hint only

                        status = ["ALLOCATABLE"]
                        flags = []
                        dev_size = 23068672     # 11 Gigabytes
                        pe_start = 384
                        pe_count = 2815 # 10.9961 Gigabytes
                }
        }

        logical_volumes {

                lv-oraData {
                        id = "6gEJLx-ZNAR-ljGD-74Jm-FtvZ-lb5g-9G9uPw"
                        status = ["READ", "WRITE", "VISIBLE"]
                        flags = []
                        segment_count = 1

                        segment1 {
                                start_extent = 0
                                extent_count = 2815     # 10.9961 Gigabytes

                                type = "striped"
                                stripe_count = 1        # linear

                                stripes = [
                                        "pv0", 0
                                ]
                        }
                }
        }
}


Does anyone have idea what could be the problem?
Last edited by h@foorsa.biz; 02-16-2017 at 04:11 AM..
# 2  
Old 03-11-2017
What is the response from blkid?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

LVM recovery, Hard disk broken

Hi I am new on your forum, because I need some help. I have a server with debian and proxmox 2. The HardDisk is broken. I am in rescue mode, and I can't mount LVM partition to recover my backups. What I've already done : # fdisk -l Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255... (0 Replies)
Discussion started by: pppplu
0 Replies

2. UNIX for Dummies Questions & Answers

How to convert non LVM root partition to LVM?

Hi Guys, I m using redhat 6, I have installed root partition as non-LVM . Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies

3. Linux

LVM

Hi , I have 500 GB hard drive in my office server, previous employee installed fedora in to it, with 50 GB / and 120 GB (/opt/backup 15GB, /opt/test 5GB so on) . i have 180 GB free space left , so I have created LVM in 180 GB and moved all data from 120 GB to 180 . Now i need to create lvm in... (1 Reply)
Discussion started by: ram5019
1 Replies

4. Red Hat

LVM Help

Hi, I have extended the logical drive on my SMART ARRAY on a BL460 C class blade from 72G to 300G (disk upgrade RAID0+1). It went fine and the new larger disks have now sync'ed up. I now need to create additional disk space on my linux OS (RH) via LVM but I am unable to see the additional... (9 Replies)
Discussion started by: Duffs22
9 Replies

5. AIX

Help with lvm

i have os 5.1 and i do mirror with hdisk0 and hdisk1 on rootvg at the end i get error in mail that: At least one partition mirror is broken please call sysadmin hd5 boot 1 2 2 closed/stale N/A the other fs seems ok and sync what to do about the hd5??? (4 Replies)
Discussion started by: amitt74
4 Replies

6. HP-UX

How to reduce LVM to create another LVM

Hi, I'm new to HP-UX. I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3 Thanks (4 Replies)
Discussion started by: lamoul
4 Replies

7. Red Hat

lvm with -- on the name

Hi All, I created an lvm filesystem with a name with dash in the middle, like xxx-yyy (note, that it's only one dash). I was able to create it smoothly with this instructions. lvcreate -L 1G uservg -n xxx-yyy ls /dev/uservg/xxx-yyy (check) mkfs.ext3 /dev/uservg/xxx-yyy mount... (1 Reply)
Discussion started by: itik
1 Replies

8. Filesystems, Disks and Memory

LVM restore / recovery

Hello, I would really appreciate help on recovering some data. I have a RAID1 array under /dev/md0 composed of devices /dev/sdb and /dev/sdc. I had lvm on the raid with 3 lv, the last of which was a snapshot partition. My / is on /dev/sda. Recently, I reinstalled the system (Debian lenny)... (7 Replies)
Discussion started by: Zburatorul
7 Replies

9. UNIX for Advanced & Expert Users

Data Recovery from file system overwritten with LVM.

Hey peeps, Here is somethin u might find interestin.... Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :) I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies

10. Linux

LVM Help

Hi guys, I have been Linux for quite a while yet, but am only getting into the LVM world just now, so I do want to ask a pretty basic question (I believe for someone with experience with it) I have a physical volume of /dev/sdc1 which contains a volume group call backup that contains 2 logical... (0 Replies)
Discussion started by: pasha
0 Replies
Login or Register to Ask a Question