[Bug 604255] New: Formatting and mounting fails - System error code was: -3030
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c0 Summary: Formatting and mounting fails - System error code was: -3030 Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: a.winzer@koenig-dey.de QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729) Hello, first I had an openSUSE 11.2 with an (faked) RAID 1 on a Promise Fasttrack S150 TX2plus (BIOS 1.00.0.37) and I tried to upgrade it with zypper. I used the ISO of the 11.3 MS6 x86 DVD as the only repository. After reboot I got the error described here: https://bugzilla.novell.com/show_bug.cgi?id=538189. So I tried a fresh installation. The installation system recognizes the hdds as RAID at all. After partitioning and choosing the software parts, grub destination, firewall, ssh etc. the formatting and mounting fails. I always get the message: "System error code was: -3030" I can't understand that. I've already tried a search maschine without a helping result. I don't even know, what error code -3030 means. I'm also not sure about "the component". Is my old Fasttrack not supported any more. If so, I wont keep reporting my trouble ... Otherwise I don't know, why this seems to happen with every new openSUSE. Thanks Alex Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Running installation at least for GM. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c1 Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |aschnell@novell.com InfoProvider| |a.winzer@koenig-dey.de --- Comment #1 from Arvin Schnell <aschnell@novell.com> 2010-05-10 14:52:59 UTC --- Could be a duplicate of bug #598193. Please provide YaST logs, see http://en.opensuse.org/Bugs/YaST. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c2 Alexander Winzer <a.winzer@koenig-dey.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.winzer@koenig-dey.de --- Comment #2 from Alexander Winzer <a.winzer@koenig-dey.de> 2010-05-12 14:44:05 UTC --- How do I do that? I've read this articel. Until I'm not a native english speaker I couldn't find out how to get the logs on an unistalled system. At least the logs are not saved ond a hdd untils it's not formatted. I also tried the console Strg + Alt + F1 (etc.) but can't get access to any kind of filesystem with my knowledge. Sorry. Could you please give me more advice? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c3 Alexander Winzer <a.winzer@koenig-dey.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|a.winzer@koenig-dey.de | --- Comment #3 from Alexander Winzer <a.winzer@koenig-dey.de> 2010-05-18 15:38:36 UTC --- Created an attachment (id=362968) --> (http://bugzilla.novell.com/attachment.cgi?id=362968) The required logs Finally I found how to make it. Here you are. I hope it helps somehow. Alex -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c4 Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #4 from Arvin Schnell <aschnell@novell.com> 2010-05-18 16:13:13 UTC --- Thanks for the logs. The device nodes for partitions of the DM RAID are missing. Looks like a duplicate of bug #592378. Should be fixed in Milestone 7. *** This bug has been marked as a duplicate of bug 592378 *** http://bugzilla.novell.com/show_bug.cgi?id=592378 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c5 Alexander Winzer <a.winzer@koenig-dey.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|Milestone 6 |Milestone 7 Resolution|DUPLICATE | --- Comment #5 from Alexander Winzer <a.winzer@koenig-dey.de> 2010-06-09 13:24:17 UTC --- Unfortunately it didn't change in Milestone 7. Right now I can at least format the partitions and install the system. After reboot I got exactly the same messages as described here https://bugzilla.novell.com/show_bug.cgi?id=538189#c0. I tried to boot into the fail installed system without success. In YaST (installer) I always get the messages in the mentioned sequence: "Calling the YaST Module `inst_repair has failed" If I choose go back or continue the next Message which says "Calling the YaST Module `inst_mode has failed" What further Information do you need? Should I leave this bug report status as resolved an open a new one? Yours, Alex -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c6 Martin Wilck <martin.wilck@ts.fujitsu.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck@ts.fujitsu.com --- Comment #6 from Martin Wilck <martin.wilck@ts.fujitsu.com> 2010-06-18 21:02:32 UTC --- 2010-05-18 17:05:15 <1> linux(2826) [libstorage] Storage.cc(showInfoCb):5766 INSTALL INFO info:Formatting raid partition pdc_cjgcdfhf_part5 (78.44 MB) with ext4 2010-05-18 17:05:15 <1> linux(2826) [YCP] StorageClients.ycp:64 Current action: 8, total stage progress: 66 2010-05-18 17:05:15 <1> linux(2826) [libstorage] Volume.cc(checkDevice):1191 checkDevice:/dev/mapper/pdc_cjgcdfhf_part5 ret:-3030 The device link under /dev/mapper is missing. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c7 --- Comment #7 from Martin Wilck <martin.wilck@ts.fujitsu.com> 2010-06-18 21:28:08 UTC --- I got exactly the same error on my system (y2log see https://bugzilla.novell.com/attachment.cgi?id=370205) with a logical volume. The LV had existed before, I had chosen to format and mount it (as /). Formatting the device worked, but it was not mounted (error -3030). I found the following situation: /dev/dm-6 existed /dev/vg/os11.2 -> /dev/mapper/vg-os11.2 But /dev/mapper/vg-os11.2 did not exist! I solved the problem by symlinking /dev/mapper/vg-os11.2 -> ../dm-6 manually from the command line. Installation continued successfully.
From my y2log:
Creating the file system works: 2010-06-18 20:34:55 <1> linux(2899) [libstorage] Volume.cc(doFormat):749 device:/dev/vg/os11.2 2010-06-18 20:34:55 <1> linux(2899) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/mke2fs -O dir_index -t ext4 -v '/dev/vg/os11.2'" 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 12.531096s for "/sbin/mke2fs -O dir_index -t ext4 -v '/dev/vg/os11.2'" 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:0 The next step is already strange: "blkid -c /dev/null /dev/vg/os11.2" didn't generate any output, as it should have done. 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"BLKID_SKIP_CHECK_MDRAID=1 /sbin/blkid -c /dev/null '/dev/vg/os11.2'" 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(doExecute):279 stopwatch 0.014073s for "BLKID_SKIP_CHECK_MDRAID=1 /sbin/blkid -c /dev/null '/dev/vg/os11.2'" 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(doExecute):299 system() Returns:2 The following dmsetup command shows that the dmsetup knows about the device: .. 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(addLine):582 Adding Line 4 "vg-os11.2 (253, 6)" Now comes the first indication of a problem (/dev/mapper/os11.2 missing): 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(execute):90 SystemCmd Executing:"/sbin/dmsetup info" 2010-06-18 20:35:07 <1> linux(2899) [libstorage] SystemCmd.cc(addLine):582 Adding Line 1 "/dev/mapper/vg-os11.2: open failed: No such file or directory" A few lines below the actual error: 2010-06-18 20:35:08 <1> linux(2899) [libstorage] Storage.cc(showInfoCb):5778 INSTALL INFO info:Mounting /dev/vg/os11.2 to / 2010-06-18 20:35:08 <1> linux(2899) [YCP] StorageClients.ycp:64 Current action: 5, total stage progress: 50 2010-06-18 20:35:08 <1> linux(2899) [libstorage] Volume.cc(checkDevice):1192 checkDevice:/dev/vg/os11.2 ret:-3030 2010-06-18 20:35:08 <1> linux(2899) [libstorage] Volume.cc(doMount):1238 ret:-3030 2010-06-18 20:35:08 <1> linux(2899) [libstorage] Container.cc(commitChanges):242 ret:-3030 2010-06-18 20:35:08 <1> linux(2899) [libstorage] Storage.cc(commitPair):4627 err at stage:3 type:4 cont:false dest:false name:os11.2 2010-06-18 20:35:08 <1> linux(2899) [libstorage] Storage.cc(commitErrorPopupCb):5814 COMMIT ERROR POPUP error:-3030 last_action:Mounting /dev/vg/os11.2 to / extended_message: 2010-06-18 20:35:08 <1> linux(2899) [YCP] StorageClients.ycp:89 CommitErrorPopup error-3030 last_actionMounting /dev/vg/os11.2 to / extended_message: 2010-06-18 20:35:08 <1> linux(2899) [YCP] Report.ycp:349 Failure occurred during following action: Mounting /dev/vg/os11.2 to / System error code was: -3030 Continue despite the error? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c8 --- Comment #8 from Martin Wilck <martin.wilck@ts.fujitsu.com> 2010-06-18 22:02:21 UTC --- I have a test case for this problem that I can reproduce in an installed system. The problem is the command "echo add >/sys/block/dm-<XY>/uevent" that YaST executes. It seems to make udev think that the device is no longer a dm device. athene:/etc/udev/rules.d # lvcreate -L 100M -n TEST vg Logical volume "TEST" created athene:/etc/udev/rules.d # ls -l /dev/mapper/vg-TEST /dev/vg/TEST lrwxrwxrwx 1 root root 7 Jun 18 23:56 /dev/mapper/vg-TEST -> ../dm-7 lrwxrwxrwx 1 root root 7 Jun 18 23:56 /dev/vg/TEST -> ../dm-7 athene:/etc/udev/rules.d # echo 'add' >/sys/block/dm-7/uevent athene:/etc/udev/rules.d # ls -l /dev/mapper/vg-TEST /dev/vg/TEST ls: cannot access /dev/mapper/vg-TEST: No such file or directory ls: cannot access /dev/vg/TEST: No such file or directory -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c9 --- Comment #9 from Martin Wilck <martin.wilck@ts.fujitsu.com> 2010-06-18 22:14:51 UTC --- Created an attachment (id=370233) --> (http://bugzilla.novell.com/attachment.cgi?id=370233) udev log file from previous example At the end of the log file the problem can be watched: Jun 18 23:57:59 athene udevd[526]: seq 1710 queued, 'add' 'block' Jun 18 23:57:59 athene udevd[526]: passed 170 bytes to netlink monitor 0x806b0d8 Jun 18 23:57:59 athene udevd-work[29690]: seq 1710 running Jun 18 23:57:59 athene udevd-work[29690]: device 0x807c330 has devpath '/devices/virtual/block/dm-7' Jun 18 23:57:59 athene udevd-work[29690]: device 0x807c330 filled with db file data Jun 18 23:57:59 athene udevd-work[29690]: removing watch on '/dev/dm-7' Jun 18 23:57:59 athene udevd-work[29690]: LINK 'block/253:7' /lib/udev/rules.d/50-udev-default.rules:3 Jun 18 23:57:59 athene udevd-work[29690]: GROUP 6 /lib/udev/rules.d/50-udev-default.rules:74 Jun 18 23:57:59 athene udevd-work[29690]: RUN 'socket:/org/kernel/dm/multipath_event' /etc/udev/rules.d/71-multipath.rules:7 Jun 18 23:57:59 athene udevd-work[29690]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Jun 18 23:57:59 athene udevd-work[29690]: no node name set, will use kernel supplied name 'dm-7' Jun 18 23:57:59 athene udevd-work[29690]: created db file for '/devices/virtual/block/dm-7' in '/dev/.udev/db/block:dm-7' Jun 18 23:57:59 athene udevd-work[29690]: update old name, '/dev/mapper/vg-TEST' no longer belonging to '/devices/virtual/block/dm-7' Jun 18 23:57:59 athene udevd-work[29690]: no reference left, remove '/dev/mapper/vg-TEST' Jun 18 23:57:59 athene udevd-work[29690]: update old name, '/dev/vg/TEST' no longer belonging to '/devices/virtual/block/dm-7' Jun 18 23:57:59 athene udevd-work[29690]: no reference left, remove '/dev/vg/TEST' This clearly shows that echoing "add" into the uevent file of an already existing dm device has undesired effects. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c10 --- Comment #10 from Martin Wilck <martin.wilck@ts.fujitsu.com> 2010-06-18 22:21:29 UTC --- I omitted the line in comment #7, but you can see it in the y2log: 2010-06-18 20:35:07 <1> linux(2899) [libstorage] Volume.cc(triggerUdevUpdate):992 writing "add" to /sys/block/dm-6/uevent Hmm, I can't find this line in Alexander's log file. So perhaps I found a different problem after all? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=604255 http://bugzilla.novell.com/show_bug.cgi?id=604255#c11 Alexander Winzer <a.winzer@koenig-dey.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #11 from Alexander Winzer <a.winzer@koenig-dey.de> 2010-06-22 20:49:22 UTC --- I installed openSUSE 11.3 RC1. Now I could make partitions and format them. I still have problems with LVM. I could set up a LVM and format a Volume. But I can't mount/access it. Until this (new) problem is listes under openSUSE 11.3 most annoying bugs, I set the status of this bug to resolved. Thank you for fixing! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com