So /dev/sdv is a disk with no mounted file system on it - then “pvcreate” shouldn’t complain. I’d actually try that manually and if it indeed fails, too, then try to get more details from pvcreate than the YaST-wrapped call exposes.
Is there a partition table on /dev/sdv? Then you might want to add the actual partition (or, for a test, zap the PT via “dd if=/dev/zero of=/dev/sdv bs=512 count=1” and try to re-run pvcreate).
Might it be that /dev/sdv does already contain a VG on it, from an earlier use? Then maybe some auto-something (probably udev) could have picked that up and activated that VG… or secretly added the PV to your exisiting VG (I have that problem with Xen DomUs if the VGs are equally named within Dom0 and DomU). Does “pvdisplay /dev/sdv” provide any hints?
Here’s the pvcreate command:
Can’t open /dev/sdv exclusively. Mounted filesystem?
Here is the pvdisplay command:
No physical volume label read from /dev/sdv
Failed to read physical volume “/dev/sdv”
And here is some fdisk info:
The number of cylinders for this disk is set to 13315.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
- software that runs at boot time (e.g., old versions of LILO)
- booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdv: 109.5 GB, 109521666048 bytes
255 heads, 63 sectors/track, 13315 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000e261f
Device Boot Start End Blocks Id System
Command (m for help): m
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition’s system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): v
213909503 unallocated 512-byte sectors
NOTE: This is not a previously used disk. It is a LUN that was created and exported to me. I should see it as a new disk. The disk should be empty and the info above seems to corroborate that. What do you think? And, thanks for your help.