LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 09-24-2008, 05:55 AM   #1
sjreilly
Member
 
Registered: Oct 2007
Location: Edinburgh, Scotland
Distribution: Debian, CentOS, RHEL, Mint, Ubuntu
Posts: 79

Rep: Reputation: 15
LVM config lost after reboot - CentOS4


Hi,

I have a machine with two drives. First drive has a 10G root partition. The remaining areas of the two drives are combined in one volume group (VolGroup00) which contains three logical volumes. These LV's are formatted XFS.

Recently I updated the OS to CentOS 5 but after a while found that I needed to go back to CentOS 4.
When I loaded my stock CentOS 4 image I found that the LV's were not being recognised and not mounted and messages during boot;

lvm.static: Couldn't find device with uuid 'fqVX3d-z0WZ-dgAv-F0rC-qHls-d4jQ-eKgjV1'.
lvm.static: Couldn't find all physical volumes for volume group VolGroup00.

I can run vgchange -a y VolGroup00 and the LV's are found and I can then mount them and access the data.

However, after a reboot I have to go through the same;

vgchange -a y VolGroup00; mount -a

cycle.

What am I missing?

TIA,
Steve
 
Old 09-25-2008, 01:56 AM   #2
born4linux
Senior Member
 
Registered: Sep 2002
Location: Philippines
Distribution: Slackware, RHEL&variants, AIX, SuSE
Posts: 1,127

Rep: Reputation: 49
does "vgck" return any errors? try:

vgck -vvv VolGroup00

try renaming the file /etc/lvm/cache/.cache in your system. then
run vgs and reboot.
also, do you have any custom filter definition in your lvm.conf?
 
Old 09-25-2008, 03:35 AM   #3
sjreilly
Member
 
Registered: Oct 2007
Location: Edinburgh, Scotland
Distribution: Debian, CentOS, RHEL, Mint, Ubuntu
Posts: 79

Original Poster
Rep: Reputation: 15
Hi,
Thanks for the reply.

Here is the output from vgck. Doesn't look like any errors.
I tried deleting the .cache file and running vgs as you suggested but the same message occurs during boot.

# vgck -vvv VolGroup00
Processing: vgck -vvv VolGroup00
O_DIRECT will be used
Setting global/locking_type to 1
File-based locking selected.
Setting global/locking_dir to /var/lock/lvm
Using volume group(s) on command line
Locking /var/lock/lvm/V_VolGroup00 RB
Finding volume group "VolGroup00"
/dev/ramdisk: Not using O_DIRECT
Opened /dev/ramdisk RO
/dev/ramdisk: block size is 1024 bytes
/dev/ramdisk: No label detected
Closed /dev/ramdisk
/dev/ram: Not using O_DIRECT
Opened /dev/ram RO
/dev/ram: block size is 1024 bytes
/dev/ram: No label detected
Closed /dev/ram
Opened /dev/root RO O_DIRECT
/dev/root: block size is 4096 bytes
/dev/root: No label detected
Closed /dev/root
Opened /dev/sda1 RO O_DIRECT
/dev/sda1: block size is 1024 bytes
/dev/sda1: lvm2 label detected
lvmcache: /dev/sda1: now in VG #orphans_lvm2 (#orphans_lvm2)
/dev/sda1: Found metadata at 8704 size 1657 (in area at 4096 size 192512) for VolGroup00 (u69ame-JmRp-9Lvo-cEDC-xu3C-2eKz-pmsz09)
lvmcache: /dev/sda1: now in VG VolGroup00
lvmcache: /dev/sda1: setting VolGroup00 VGID to u69ameJmRp9LvocEDCxu3C2eKzpmsz09
lvmcache: /dev/sda1: VG VolGroup00: Set creation host to desktop01.
/dev/ram2: Not using O_DIRECT
Opened /dev/ram2 RO
/dev/ram2: block size is 1024 bytes
/dev/ram2: No label detected
Closed /dev/ram2
/dev/ram3: Not using O_DIRECT
Opened /dev/ram3 RO
/dev/ram3: block size is 1024 bytes
/dev/ram3: No label detected
Closed /dev/ram3
/dev/ram4: Not using O_DIRECT
Opened /dev/ram4 RO
/dev/ram4: block size is 1024 bytes
/dev/ram4: No label detected
Closed /dev/ram4
/dev/ram5: Not using O_DIRECT
Opened /dev/ram5 RO
/dev/ram5: block size is 1024 bytes
/dev/ram5: No label detected
Closed /dev/ram5
Opened /dev/hda5 RO O_DIRECT
/dev/hda5: block size is 4096 bytes
/dev/hda5: No label detected
Closed /dev/hda5
/dev/ram6: Not using O_DIRECT
Opened /dev/ram6 RO
/dev/ram6: block size is 1024 bytes
/dev/ram6: No label detected
Closed /dev/ram6
Opened /dev/hda6 RO O_DIRECT
/dev/hda6: block size is 512 bytes
/dev/hda6: lvm2 label detected
lvmcache: /dev/hda6: now in VG #orphans_lvm2 (#orphans_lvm2)
/dev/hda6: Found metadata at 9728 size 1657 (in area at 4096 size 192512) for VolGroup00 (u69ame-JmRp-9Lvo-cEDC-xu3C-2eKz-pmsz09)
lvmcache: /dev/hda6: now in VG VolGroup00 (u69ameJmRp9LvocEDCxu3C2eKzpmsz09)
/dev/ram7: Not using O_DIRECT
Opened /dev/ram7 RO
/dev/ram7: block size is 1024 bytes
/dev/ram7: No label detected
Closed /dev/ram7
/dev/ram8: Not using O_DIRECT
Opened /dev/ram8 RO
/dev/ram8: block size is 1024 bytes
/dev/ram8: No label detected
Closed /dev/ram8
/dev/ram9: Not using O_DIRECT
Opened /dev/ram9 RO
/dev/ram9: block size is 1024 bytes
/dev/ram9: No label detected
Closed /dev/ram9
/dev/ram10: Not using O_DIRECT
Opened /dev/ram10 RO
/dev/ram10: block size is 1024 bytes
/dev/ram10: No label detected
Closed /dev/ram10
/dev/ram11: Not using O_DIRECT
Opened /dev/ram11 RO
/dev/ram11: block size is 1024 bytes
/dev/ram11: No label detected
Closed /dev/ram11
/dev/ram12: Not using O_DIRECT
Opened /dev/ram12 RO
/dev/ram12: block size is 1024 bytes
/dev/ram12: No label detected
Closed /dev/ram12
/dev/ram13: Not using O_DIRECT
Opened /dev/ram13 RO
/dev/ram13: block size is 1024 bytes
/dev/ram13: No label detected
Closed /dev/ram13
/dev/ram14: Not using O_DIRECT
Opened /dev/ram14 RO
/dev/ram14: block size is 1024 bytes
/dev/ram14: No label detected
Closed /dev/ram14
/dev/ram15: Not using O_DIRECT
Opened /dev/ram15 RO
/dev/ram15: block size is 1024 bytes
/dev/ram15: No label detected
Closed /dev/ram15
Using cached label for /dev/sda1
Using cached label for /dev/hda6
Using cached label for /dev/hda6
Using cached label for /dev/sda1
Read VolGroup00 metadata (5) from /dev/sda1 at 8704 size 1657
Using cached label for /dev/hda6
Using cached label for /dev/sda1
Read VolGroup00 metadata (5) from /dev/hda6 at 9728 size 1657
/dev/hda6 0: 0 15978: native(28898:0)
/dev/sda1 0: 0 15360: backup(0:0)
/dev/sda1 1: 15360 15360: opt(0:0)
/dev/sda1 2: 30720 28898: native(0:0)
Unlocking /var/lock/lvm/V_VolGroup00
Closed /dev/sda1
Closed /dev/hda6
 
Old 09-29-2008, 06:31 AM   #4
sjreilly
Member
 
Registered: Oct 2007
Location: Edinburgh, Scotland
Distribution: Debian, CentOS, RHEL, Mint, Ubuntu
Posts: 79

Original Poster
Rep: Reputation: 15
I've tried removing the LV's and VG's from LVM then rebuilding the LVM but it made no difference.

Any more suggestions?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 12.1, LVM and reboot. plenty Slackware 1 06-10-2008 11:45 AM
LVM not visible after reboot lord_darkhelmet Linux - General 3 10-05-2006 12:48 AM
LVM disk is offline after reboot Lada Red Hat 2 08-20-2006 06:05 PM
wlan config lost after reboot dblklk Mandriva 2 08-14-2005 02:10 PM
Lost mouse after reboot+lost modem BACTRATE Mandriva 3 04-07-2005 06:45 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 05:19 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration