Mailinglist Archive: opensuse (1473 mails)

< Previous Next >
Re: [opensuse] UUID=>0x and LVM
  • From: "Boyd Stephen Smith Jr." <bss@xxxxxxxxxxxxxxxxx>
  • Date: Tue, 16 Jun 2009 13:31:54 -0500
  • Message-id: <200906161331.58734.bss@xxxxxxxxxxxxxxxxx>
In <web-42182587@xxxxxxxxxxxxxxxxx>, Philip Mötteli wrote:
Quoting "Boyd Stephen Smith Jr." <bss@xxxxxxxxxxxxxxxxx>:
In Monday 15 June 2009, you wrote:
Booting from the system, this gives:

Couldn't find device with uuid '
lLWxB7-QmLl-FMXX-KQRW-EDH2-EHLL-o7D21b'
Couldn't find device with uuid
' lLWxB7-QmLl-FMXX-KQRW-EDH2-EHLL-o7D21b'
Couldn't find device with
uuid ' lLWxB7-QmLl-FMXX-KQRW-EDH2-EHLL-o7D21b'
PV /dev/sda4 with UUID
ecQz2l-Yl5S-s1AR-delt-5zXF-Wnjs-P2y2dH VG system lvm2 [113.03 GB
/
0 free]
PV /dev/sdb1 with UUID
5P6jGx-ePjX-43Az-wyLL-wuF5-R4Vt-vP9Uff VG
system lvm2 [465.76 / 0 free]
PV unknown device with UUID lLWxB7-QmLl-FMXX-KQRW-EDHZ-EHLL-o7DZ1b VG
system lvm2 [465.76 GB / 224.54 GB free]
Total: 3 [1.02 TB] / in use: 3 [1.02 TB] / in no VG: 0 [0 ]

When I boot from the GParted live-CD:

PV /dev/sdb4 with UUID ecQz2l-Yl5S-s1AR-delt-5zXF-Wnjs-P2y2dH VG
system lvm2 [113.03 GB / 0 free]
PV /dev/sdc1 with UUID 5P6jGx-ePjX-43Az-wyLL-wuF5-R4Vt-vP9Uff VG
system lvm2 [465.76 GB / 0 free]
PV /dev/sda with UUID lLWxB7-QmLl-FMXX-KQRW-EDHZ-EHLL-o7DZ1b VG system
lvm2 [465.76 GB / 224.54 GB free]
Total: 3 [1.02 TB] /in use: 3 [1.02 TB] / in no VG: 0 [0 ]

No error at all. How does the GParted Live-CD do that?

Are the LVM versions different?

This is something different. As the GParted Live-CD shows, the device
has the correct UUID. This means that, for whatever reason, LVM is not
scanning the correct device(s) to find a UUID.

When you boot the system normally, which device is the drive that LVM
can't find?

sdc

You may simply be missing the correct kernel module for the disk
controller.

How could I verify that?

If it is showing up as a device, you've got the right modules loaded.

If your device is rejected (name

How could I find its name? Is it 'sdc'?

Filtering is based on absolute pathname. So "/dev/sdc", which should be
accepted and not rejected your rules.

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc doesn't contain a valid partition table

That's normal for a whole disk PV.

Disk /dev/dm-0: 858.9 GB, 858993459200 bytes
Disk /dev/dm-1: 21.4 GB, 21474836480 bytes

Hrm, are either one of these claiming the /dev/sdc device as a component
device? LVM might skip devices that are part of an active dm device.

You might try issuing the command:
pvscan -vv
as root in the booted system. It might provide some information as to why
LVM is not treating /dev/sdc as a PV.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/

< Previous Next >
Follow Ups
References