From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m0L35Sat030325 for ; Sun, 20 Jan 2008 22:05:28 -0500 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id m0L358cb028445 for ; Sun, 20 Jan 2008 22:05:08 -0500 Received: by py-out-1112.google.com with SMTP id a29so2249706pyi.0 for ; Sun, 20 Jan 2008 19:05:07 -0800 (PST) Message-ID: Date: Sun, 20 Jan 2008 21:05:07 -0600 From: "Cory Zerwas" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16932_6782295.1200884707441" Subject: [linux-lvm] Moved unexported VGs to replacement system after MB failure Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: linux-lvm@redhat.com ------=_Part_16932_6782295.1200884707441 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have a 3ware 9500S-8 which is hosting a 1.14Tb and a 465Gb LVM volgrp. This storage was in a system that smoked it's onboard video and subsequently the entire bus; or enough of it to bring the machine down hard (was a Fedora Core 6 box). I moved the RAID card along with disks to a new system and I find that lvscan, pvscan, and vgscan all come up with the previously-existing LVM partitions/volgrps but I do not see the moved volgrps. I suspect that the partitions were created improperly as a type 83 linux partition or whole-disk LVM but perhaps it's possible that the move to the new system somehow changed the partition type? The latter doesn't seem very likely to me but I am running logical disk verification on my RAID controller to be sure that the disk set is intact. Since this was an abrupt event I did not have the opportunity to export the volume groups first. I do see the following on an lvmdiskscan: /dev/ramdisk [ 16.00 MB] /dev/dm-0 [ 19.53 GB] /dev/ram [ 16.00 MB] /dev/sda1 [ 196.08 MB] /dev/dm-1 [ 323.41 GB] /dev/ram2 [ 16.00 MB] /dev/sda2 [ 344.92 GB] LVM physical volume /dev/dm-2 [ 1.94 GB] /dev/ram3 [ 16.00 MB] /dev/ram4 [ 16.00 MB] /dev/ram5 [ 16.00 MB] /dev/ram6 [ 16.00 MB] /dev/ram7 [ 16.00 MB] /dev/ram8 [ 16.00 MB] /dev/ram9 [ 16.00 MB] /dev/ram10 [ 16.00 MB] /dev/ram11 [ 16.00 MB] /dev/ram12 [ 16.00 MB] /dev/ram13 [ 16.00 MB] /dev/ram14 [ 16.00 MB] /dev/ram15 [ 16.00 MB] /dev/sdb1 [ 1.14 TB] /dev/sdc1 [ 465.64 GB] 2 disks 20 partitions 0 LVM physical volume whole disks 1 LVM physical volume There are the RAID logical drives/LUNs that should contain the volgrps I want, /dev/sdb1 and sdc1. The volgrp on /dev/sda2 is the host system's existing volgrp. Could this really be as simple as changing the partition type to 8e, Linux LVM? I am hesitant since while I do have a backup of the important data I would like to keep all of it if possible. It is possible that one of the volgrps from the old system has the same default name of VolGroup00 if that makes a difference during recovery steps. I have definitely learned to backup the /etc directory, can't keep it all in my brain any more. Plus it'd be handy to have the original LVM files from the old system. I will see if I can get the old root partition drive fired up in a USB enclosure to perhaps recover some useful LVM data. Since that is also an LVM vol group, argh... Doubt that will go well. LVM ver info: # lvm> version LVM version: 2.02.28 (2007-08-24) Library version: 1.02.22 (2007-08-21) Driver version: 4.11.0 Kernel ver: # uname -r -v -i 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:36 EST 2007 x86_64 This is a fedora 8 system. Output from scans: # pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sda2 VG VolGroup00 lvm2 [344.91 GB / 32.00 MB free] Total: 1 [344.91 GB] / in use: 1 [344.91 GB] / in no VG: 0 [0 ] # lvscan -v Finding all logical volumes ACTIVE '/dev/VolGroup00/LogVolRootFS' [19.53 GB] inherit ACTIVE '/dev/VolGroup00/LogVolMythstor' [323.41 GB] inherit ACTIVE '/dev/VolGroup00/LogVol01' [1.94 GB] inherit # vgscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Reading all physical volumes. This may take a while... Finding all volume groups Finding volume group "VolGroup00" Found volume group "VolGroup00" using metadata type lvm2 Any advice would be appreciated, please let me know if there's more info I can provide to provide a more clear picture. Cory ------=_Part_16932_6782295.1200884707441 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I have a 3ware 9500S-8 which is hosting a 1.14Tb and a 465Gb LVM volgrp.&nb= sp; This storage was in a system that smoked it's onboard video and sub= sequently the entire bus; or enough of it to bring the machine down hard (w= as a Fedora Core 6 box).  I moved the RAID card along with disks to a = new system and I find that lvscan, pvscan, and vgscan all come up with the = previously-existing LVM partitions/volgrps but I do not see the moved volgr= ps.  I suspect that the partitions were created improperly as a type 8= 3 linux partition or whole-disk LVM but perhaps it's possible that the = move to the new system somehow changed the partition type?  The latter= doesn't seem very likely to me but I am running logical disk verificat= ion on my RAID controller to be sure that the disk set is intact.  Sin= ce this was an abrupt event I did not have the opportunity to export the vo= lume groups first.

I do see the following on an lvmdiskscan:
  /dev/ramdisk [&= nbsp;      16.00 MB]
  /dev/dm-0 &nb= sp;  [       19.53 GB]
  /dev/r= am     [       16.00 MB] =
  /dev/sda1    [      196.= 08 MB]
  /dev/dm-1    [    &nbs= p;=20 323.41 GB]
  /dev/ram2    [    =    16.00 MB]
  /dev/sda2    [  =     344.92 GB] LVM physical volume
  /dev/dm-2 =    [        1.94 GB]
 = ; /dev/ram3    [       16.00 M= B]
  /dev/ram4    [     &n= bsp; 16.00 MB]
  /dev/ram5    [   &n= bsp;  =20 16.00 MB]
  /dev/ram6    [    &= nbsp;  16.00 MB]
  /dev/ram7    [  &= nbsp;    16.00 MB]
  /dev/ram8    [&= nbsp;      16.00 MB]
  /dev/ram9 &nb= sp;  [       16.00 MB]
  /dev/r= am10   [       16.00 MB]
 = /dev/ram11   [      =20 16.00 MB]
  /dev/ram12   [     =   16.00 MB]
  /dev/ram13   [    = ;   16.00 MB]
  /dev/ram14   [  &nbs= p;    16.00 MB]
  /dev/ram15   [ &nb= sp;     16.00 MB]
  /dev/sdb1   = ; [        1.14 TB]
  /dev/sdc1=     [     =20 465.64 GB]
  2 disks
  20 partitions
  0 LVM physi= cal volume whole disks
  1 LVM physical volume

There are the= RAID logical drives/LUNs that should contain the volgrps I want, /dev/sdb1= and sdc1.  The volgrp on /dev/sda2 is the host system's existing = volgrp.  Could this really be as simple as changing the partition type= to 8e, Linux LVM?  I am hesitant since while I do have a backup of th= e important data I would like to keep all of it if possible.  It is po= ssible that one of the volgrps from the old system has the same default nam= e of VolGroup00 if that makes a difference during recovery steps.  I h= ave definitely learned to backup the /etc directory, can't keep it all = in my brain any more.  Plus it'd be handy to have the original LVM= files from the old system.  I will see if I can get the old root part= ition drive fired up in a USB enclosure to perhaps recover some useful LVM = data.  Since that is also an LVM vol group, argh... Doubt that will go= well.

LVM ver info:
# lvm> version
  LVM version: &nbs= p;   2.02.28 (2007-08-24)
  Library version: 1.02.22 (200= 7-08-21)
  Driver version:  4.11.0

Kernel ver:
# un= ame -r -v -i
2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:36 EST 2007 x86_64

This is a fedora 8 system.  Output from scans:

# pvscan= -v
    Wiping cache of LVM-capable devices
 &nbs= p;  Wiping internal VG cache
    Walking through all= physical volumes
  PV /dev/sda2   VG VolGroup00 &nb= sp; lvm2 [ 344.91 GB / 32.00 MB free]
  Total: 1 [344.91 GB] / in use: 1 [344.= 91 GB] / in no VG: 0 [0   ]

# lvscan -v
  &nb= sp; Finding all logical volumes
  ACTIVE    &nb= sp;       '/dev/VolGroup00/LogVolRootFS&#= 39; [19.53 GB] inherit
  ACTIVE         &nbs= p;  '/dev/VolGroup00/LogVolMythstor' [323.41 GB] inherit
&n= bsp; ACTIVE          &nbs= p; '/dev/VolGroup00/LogVol01' [1.94 GB] inherit

# vgscan -v =
    Wiping cache of LVM-capable devices
    Wiping internal VG cache
  Reading all physi= cal volumes.  This may take a while...
    Finding a= ll volume groups
    Finding volume group "VolGroup0= 0"
  Found volume group "VolGroup00" using metadata = type lvm2

Any advice would be appreciated, please let me know if there's = more info I can provide to provide a more clear picture.
Cory
------=_Part_16932_6782295.1200884707441--