Bug 339077

Summary: incorrect partition selection ...
Product: [openSUSE] openSUSE 10.3 Reporter: Michael Meeks <mmeeks>
Component: YaST2Assignee: Thomas Fehr <fehr>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: aschnell
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: step1
step2
step3
step4
detailed view (later)

Description Michael Meeks 2007-11-05 12:46:37 UTC
So ... I was using the Gnome live-install CD to get an installation, and tried not to use the 'Expert' partitioner that I'd normally use.

Slide-show of what was done. With the 2nd try with 'detailed' view next.
Fortunately I noticed the proposal was radically different to what I'd asked for - otherwise ... smoke :-) selecting /dev/sda5 and /dev/sda8 - I would expect only these to be formatted.

Also (to avoid confusion) - it would be far better to use alphabetic shortcuts on the drives IMHO; having '2' -> /dev/sda2 and '3' -> /dev/sda5 is not obvious or ideal.
Comment 1 Michael Meeks 2007-11-05 12:47:08 UTC
Created attachment 182015 [details]
step1
Comment 2 Michael Meeks 2007-11-05 12:47:21 UTC
Created attachment 182016 [details]
step2
Comment 3 Michael Meeks 2007-11-05 12:47:35 UTC
Created attachment 182017 [details]
step3
Comment 4 Michael Meeks 2007-11-05 12:47:57 UTC
Created attachment 182018 [details]
step4
Comment 5 Michael Meeks 2007-11-05 12:50:06 UTC
Created attachment 182019 [details]
detailed view (later)
Comment 6 Arvin Schnell 2007-11-12 09:43:13 UTC
If I understand you correctly your problem is that you did not select the
partitions sda9 and sda10 to be used but see the partitions sda9 to sda11
being created.

This might be due to renumbering of logical partitions. Please provide the
YaST2 logs.
Comment 7 Michael Meeks 2008-02-19 13:04:49 UTC
I don't believe I have the logs. I tried to provide a clear way to reproduce this; clearly this is a potential data-loss / partition mangling issue.
Sorry.
Comment 8 Thomas Fehr 2008-02-19 14:14:24 UTC
Without logs I do not see what I can do.