Bugzilla – Bug 769982
error 3030 formating fails
Last modified: 2012-12-05 12:08:36 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0 This has happend to me with build 454 and 451. After this messege installation proceeds, but of cours nothing is written to the disk. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: just try a new installation. Expected Results: nothing is written to the disk. Since nothing is writen to the disk I dont know what to attach. The disk itself is a dmraid disk, but the live cd (451) is able to nount its partitions after running dmraid -ay.
Hi Arvin, can you suggest anything here? Thanks.
Error 3030 from libstorage means that some device is not present. E.g. should be that udev doesn't generate the device node for a partition on dmraid or that there is a race condition as we had so often with udev. But without the YaST logs I cannot say more. The YaST log are available since they are initially written to the ram disk during installation. See http://en.opensuse.org/openSUSE:Bugreport_YaST.
My guess was right: When I create a partition on a Intel Software RAID (from the installation system) using parted no device node in /dev/mapper is generated for the partition. This looks like a udev or parted problem.
*** Bug 768861 has been marked as a duplicate of this bug. ***
I think this problems is already solved for bnc#768861, but the bug doesn't seem the same as this one. Also can I get some actual facts, like how it suppose to look like and how does it look like, some some logs, etc.
I'm assigning it to Petr Uzel as he is the parted maintainer.
Created attachment 498079 [details] hwinfo.txt
(In reply to comment #7) > Created an attachment (id=498079) [details] > hwinfo.txt
The installation media had been DVD 451 fo x86_64.
Created attachment 498080 [details] y2logs.tgz
Created attachment 498081 [details] yast2-000.png error msg on initrd creation failure
Created attachment 498082 [details] yast2-001.png error msg on grub2 creation failure
Actualy an intrd had been created. Its size is 12.2 MB . Is there a way to attache it too? this had been possible after creating symbolic links from the new /dev/mapper/.......p1 to the old /dev/mapper/...._part1 etc. However, after rebooting the system coukd not mount / on the fake raid arrey.
I believe I know where the problem is but I don't have time to verify it right now. Israel, would you be able to verify the tentative fix if I give you parted.rpm with it? See http://en.opensuse.org/SDB:Linuxrc#p_driverupdate for instructions on how to put it to installation system.
This problem seems to be caused by changes in device-mapper nodes handling - previously, these were created by udev rules (via kpartx) and we patched [*] parted to rely on this. Now the rules are gone and device-mapper manages the nodes on its own, so we need to revert the patch in parted. I'm investigating how to fix this properly (simple revert does not work).
(In reply to comment #15) > I'm investigating how to fix this properly (simple revert does not work). I meant 'simple revert of the patch marked with [*] in comment #15 does not work'.
After all I decided to update kpartx.rules to create the device mapper nodes on behalf of parted, so it works the same as in 12.1. Update is on it's way: SR#128928