Mailinglist Archive: opensuse-bugs (10046 mails)

< Previous Next >
[Bug 231221] New: LVM Volume Creation on NVIDIA RAID failed with error code -4017
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 1 Jan 2007 11:45:54 -0700 (MST)
  • Message-id: <bug-231221-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=231221

Summary: LVM Volume Creation on NVIDIA RAID failed with error
code -4017
Product: openSUSE 10.2
Version: Final
Platform: x86-64
OS/Version: Linux
Status: NEW
Keywords: Install
Severity: Major
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: bhoelcker@xxxxxxxx
QAContact: jsrain@xxxxxxxxxx


Content
=======
Discription
Installation history
Steps after installation
System information
Additional information
Logfiles


Discription
===========
trying to create a logical volume with yast on a dmraid failed with error code
-4017.

HW:
Chipset Nvidia N570, RAID Controller "JMicron JMB363 P-/S-ATA Controller"
HD: 2x SATA

RAID:
RAID1 with 2x SATA disks in JMicron ROM RAID Setup configured. Bootflag
enabled.

Installation History
====================
During installation the raid was detected an d configured as
/dev/mapper/nvidia_ehjbbcgc
There are 2 partitions:
/dev/mapper/nvidia_ehjbbcgc_part1 (/boot)
/dev/mapper/nvidia_ehjbbcgc_part2 (/)

Steps after installation
========================
1) Calling
yast partitioner
to create /dev/mapper/nvidia_ehjbbcgc_part3 as LVM partition
2) reboot
3) calling
yast lvm
Yast LVM ->
new Group 'xen' ->
add pv '/dev/mapper/nvidia_ehjbbcgc_part3' to group 'xen' ->
create lv 'dom0' in group 'xen' ->
Apply.
This results in the following yast2 error message (box):
----
Error
Failure occurred during following action:
Creating volume group xen from /dev/mapper/nvidia_ehjbbcgc_part3

System error code was: -4017
----

System Information
==================
xen0:/ # uname -a
Linux xen0 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 x86_64
x86_64 x86_64 GNU/Linux

xen0:/home/bernd # lsmod
Module Size Used by
..
pata_jmicron 24576 0
generic 23172 0 [permanent]
ohci1394 52040 0
ieee1394 130552 1 ohci1394
i2c_nforce2 24960 0
i2c_core 41472 1 i2c_nforce2
forcedeth 60548 0
mbcache 27016 1 ext3
jbd 90872 1 ext3
dm_mirror 39168 2
dm_snapshot 34360 0
dm_mod 81872 11 dm_mirror,dm_snapshot
ahci 41604 0
sata_nv 30084 2
libata 145056 3 pata_jmicron,ahci,sata_nv
amd74xx 32176 0 [permanent]
..

xen0:/ # dmsetup info
Name: nvidia_ehjbbcgc
State: ACTIVE
Tables present: LIVE
Open count: 3
Event number: 0
Major, minor: 253, 0
Number of targets: 1
UUID: dmraid-nvidia_ehjbbcgc

Name: xen-dom0
State: ACTIVE
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 4
Number of targets: 1
UUID: LVM-9tVz8keqry7rKDkww77cKOgHqyhDV80oBtIr3izhuqihms7u6p8Zlv4dP2kIf6An

Name: nvidia_ehjbbcgc_part3
State: ACTIVE
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 253, 3
Number of targets: 1
UUID: part3-dmraid-nvidia_ehjbbcgc

Name: nvidia_ehjbbcgc_part2
State: ACTIVE
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 253, 2
Number of targets: 1
UUID: part2-dmraid-nvidia_ehjbbcgc

Name: nvidia_ehjbbcgc_part1
State: ACTIVE
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 1
Number of targets: 1
UUID: part1-dmraid-nvidia_ehjbbcgc


Please have a look at the attached y2log snippet for this action.



Additional information
======================
1) During the creation of the partition /dev/mapper/nvidia_ehjbbcgc_part3 there
was an error from kpartx which about failed rereading the partition table. This
was solved with the reboot.
2) Calling
xen0:/ # pvcreate /dev/mapper/nvidia_ehjbbcgc_part3
Physical volume "/dev/mapper/nvidia_ehjbbcgc_part3" successfully created
xen0:/ # vgcreate xen /dev/mapper/nvidia_ehjbbcgc_part3
Volume group "xen" successfully created
xen0:/ # lvcreate -L 5G -n dom0 xen
Logical volume "dom0" created
xen0:/ # ll /dev/mapper/
brw------- 1 root root 253, 3 Jan 1 11:42 nvidia_ehjbbcgc_part3
brw------- 1 root root 253, 4 Jan 1 11:53 xen-dom0

created the desired lv, so i assume this is not a hw/kernelmodule issue or a
problem with the backend tools.


Logfiles
========
1) y2log
s. attachment y2log_lvm_1


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >