[Bug 231221] New: LVM Volume Creation on NVIDIA RAID failed with error code -4017
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@forge.provo.novell.com ReportedBy: bhoelcker@arcor.de QAContact: jsrain@novell.com 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 ------- Comment #1 from bhoelcker@arcor.de 2007-01-01 11:47 MST ------- Created an attachment (id=111235) --> (https://bugzilla.novell.com/attachment.cgi?id=111235&action=view) y2log -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |fehr@novell.com |screening@forge.provo.novell| |.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from fehr@novell.com 2007-01-08 09:54 MST ------- Your assumptions are right. YaST2 gets confused because it adds /dev/mapper/nvidia_ehjbbcgc_part3 to the VG but vgdisplay shows dm-3 as PV name. This is (wrongly) considered as an unexpected inconsitency and therefore the error code is reported. If course it should know that dm-3 and and /dev/mapper/nvidia_ehjbbcgc_part3 is equivalent in this case. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #3 from fehr@novell.com 2007-01-09 09:51 MST ------- Fixed for STABLE and SLES10 SP1 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 angellafuente@solid-rock-it.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |angellafuente@solid-rock-it.com ------- Comment #4 from angellafuente@solid-rock-it.com 2007-02-07 05:42 MST ------- I would like if I got the same bug described here: System: x84_64 Asus M2N32-SLI Deluxe Motherboard RAID Controler: Nvidia nForce 590 SLI Disks: Two SATA disks 300 GB in mirror created by RAID controller OpenSUSE Release: 10.2 and Factory realease (2007-02-07) Error: YAST crash on install when I try to create de LVM structure. Error transcription: ******************** Error creating volume group system from /dev/mapper/nvidia/dbgjddaa_part2 System error code was: -4000 echo y| pvcreate -ff -M" /dev/mapper/nvidia/dbgjddaa_part2 Device /dev/mapper/nvidia/dbgjddaa_part2 not found ******************* After this error YAST crashed and I got ncurses instalation interface. Questions: - If the bug is "Fixed for STABLE and SLES10 SP1", that means that I can't make installation with LVM over RAID until next release. - Is there any kind of patch or workaround? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 ------- Comment #5 from angellafuente@solid-rock-it.com 2007-02-07 05:58 MST ------- Created an attachment (id=117811) --> (https://bugzilla.novell.com/attachment.cgi?id=117811&action=view) YAST install log The log from YAST related to my comment. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 ------- Comment #6 from fehr@novell.com 2007-02-07 06:13 MST ------- This is another problem. It seems that somehow YaST2 misses to activate the partitions on the raid. I will investigate that. A possible workaround should be that you execute the following command: "kpartx -a -p _part /dev/mapper/nvidia_dbgjddaa" on the command line of the second console before YaST2 starts the installation. Nevertheless you will still hit the problem in this bug and for this there is no workaround in YaST2. It would probably work to setup lvm completely manually and tell YaST2 to "Reread partition table" in expert partitioner so that it picks up the manually created LVM volumes. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoenig@novell.com ------- Comment #7 from fehr@novell.com 2007-02-07 07:29 MST ------- My first investigations showed that dmraid seems not to activate partitions when it activated the raid. On my test machine (which has a PDC raid controller) it does that. Matthias could you check why dmraid seems not to activate raid partitions on NVIDIA raid controllers while it activates the on other controllers. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 angellafuente@solid-rock-it.com changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |AppArmor ------- Comment #8 from angellafuente@solid-rock-it.com 2007-02-07 09:22 MST ------- Thank you so much Thomas! I will try to create the LVM structure manually (with kpart or via lvm commands) and I will inform you. One doubt from a Bugzilla newbie. Should I create a new bug for this issue and separate from the bug #231221? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 ------- Comment #9 from fehr@novell.com 2007-02-07 09:26 MST ------- It would be best to create a new bug and provide a link to this bug so that one can see recent comments and attachments. For future: if in doubt it is always better to create a new bug than to reopen an existing one since it is extremly easy to declare a bug as duplicate of another one but it is not easily possible to split one bug into two. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=231221 ------- Comment #10 from angellafuente@solid-rock-it.com 2007-02-07 09:52 MST ------- Thomas. A news bug has been created: https://bugzilla.novell.com/show_bug.cgi?id=243160 -- 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.
participants (1)
-
bugzilla_noreply＠novell.com