Bug 461240

Summary: LiveCD install fails when partitioning disc
Product: [openSUSE] openSUSE 11.1 Reporter: Daniel Ferber <daniel4321>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P1 - Urgent CC: astro64m
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.1   
Whiteboard:
Found By: Community User Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Daniel Ferber 2008-12-20 21:04:09 UTC
I started the opensuse 11.1 gnome livecd.
I clicked on install icon and left default values on all screens.
I changed partition layout, however, this bug happens regardless of this partition layout change.
I provided a user name and password.

When installer starts applying the partition layout to the disc, the installer fails with a failure message that varies (often its a message like "device busy").

I notice that Nautilus automatically opens the newly created partition. I suspect that this is a race condition that prevents the installer to continue successfully. Also, the new created partition remains mounted until I unmout it as root.

When unmouting the partition and starting the installer again, the problem persist.

I tried to disable automount, but the installer still goes into the same failure.

Sometimes (very rare), the installation is able to advance further, I suspect that automount was not fast enough to launch Nautilus, and installer continues successfully.
Comment 1 Andreas Jaeger 2009-01-16 21:18:39 UTC
Please attach the YaST log files as explained at http://en.opensuse.org/Bugs/YaST
Comment 2 jonson jammy 2009-02-07 08:46:45 UTC
Same issue on Suse 11.1 x64 Gnome live CD

Cause of this problem was described here
https://bugzilla.novell.com/show_bug.cgi?id=464453

This workaround worked for me
https://bugzilla.novell.com/show_bug.cgi?id=464453#c13
Comment 3 Jiri Srain 2009-02-18 10:52:57 UTC

*** This bug has been marked as a duplicate of bug 464453 ***