Bug 105712 - Delete Partition Table and Disk Label does not clear RAID partitions of type fd
Summary: Delete Partition Table and Disk Label does not clear RAID partitions of type fd
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: i686 All
: P5 - None : Normal
Target Milestone: Beta 3
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 22:33 UTC by Leah Cunningham
Modified: 2005-08-22 10:58 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
result of fdisk -l (1.75 KB, text/plain)
2005-08-18 22:34 UTC, Leah Cunningham 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Leah Cunningham 2005-08-18 22:33:08 UTC 
I am unsure if this is expected behavior, so let me know if so.

If you have disks with existing RAID type partitions, in the expert partitioner
when you select Expert > Delete Partition Table and Disk Label it will delete
all partitions but those of type "fd" "Linux raid autodetect".

I will attach the output of fdisk -l on the system.
Comment 1 Leah Cunningham 2005-08-18 22:34:47 UTC 
Created attachment 46611 [details]
result of fdisk -l
Comment 2 Leah Cunningham 2005-08-18 23:13:56 UTC 
This specifically occurs when there were active MD devices still in the list. 
If you enter the RAID menu and remove all of the drives first, the parition
tables will clear correctly.  However, this is perhaps not the most intuitive thing.
Comment 3 Arvin Schnell 2005-08-19 07:02:37 UTC 
Please provide YaST2 logs of the attempt that did not work, see:
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST
Comment 5 Thomas Fehr 2005-08-22 10:58:39 UTC 
This is also caused by the failed raid removal. Since raid ist still active
kernel refuses the partitions belonging to that raid being deleted.
So this strange behaviour should be fixed with fix of raid removal in 
libstorage. 

If possible please retry with beta#3.
If it still fails in beta#3 please reopen and attach y2log files.