Bug 474599

Summary: Installation with Yast never successful always a partition problem that stops the whole installation proccess
Product: [openSUSE] openSUSE 11.1 Reporter: Carlos Alberto <gato303co>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i386   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Carlos Alberto 2009-02-11 01:46:48 UTC 
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6

I tried several times to install OpenSuSe with a Live CD (11.1) on a PC with AMD Athlon64, 1GB RAM DDR, 160GB Hard Disk.

i have an extended partition with about 41GB prevously created for an early Linux Ubuntu 8.04 installation with 1GB for swap, 20GB for / (root) and 20GB for /home (both formated with ext3) also two ntfs partitions for windows system and windows files both with 30GB.

I configured the installation of OpenSuSe to reuse the Ubuntu partitions, same for swap, root and /home, (formatting the old /root) but the problem i got always is that when i am in the process of configuring installation, for some strange reason, the Windows partitions get automatically mounted with no previous advice.  I unmounted them manually, but later when i click "install" and then the installation process begin, for some strange reason the windows and linux partitions mount themselves again, and the installation process stops suddenly since the installer can install on mounted partitions.

i tried several times but always the same error, I dont know why the partitions mount themselves on the live CD executing while running the installation with the Yast.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Jiri Srain 2009-02-18 11:22:23 UTC 
Looks like a known problem with GNOME live CD.

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