Bugzilla – Bug 105716
RAID settings failures on remove and /dev/md255 problem
Last modified: 2005-08-22 10:56:18 UTC
See Bug 105712 for an fdisk listing of the drive I am working with. If you go into RAID settings and do a Remove RAID on a highlighted disk, the first one will clear the Type back to Linux native (say if you selected /dev/hda1). If you then highlight the next device (/dev/hda2) and select Remove Raid, you are returned back to /dev/hda1 being highlighted, and the Type is not changed for /dev/hda2. If you continue to do this, Remove RAID will cycle through prompts of: Do you really want to delete partition /dev/{md1,md2,md3,md4} and then, after md4, the prompt changes to "Do you really want to delete partition /dev/md255". I will attach a screenshot. This system did have four md partitions on it.
Created attachment 46612 [details] Screenshot of /dev/md255 error
Created attachment 46613 [details] Screenshot of my RAID settings screen
I should mention that this disk already had RAID type partitions on it.
Upon further investigation, this odd behavior depends on having attempted to delete the partition table on both drives first, as I explained in Bug 105712. It is not seen if you have not done this step. However even when you have RAID devices that do remove correctly, the /dev/md255 issue will occur if you select Remove RAID when there are no more RAID devices left.
Please provide YaST2 logs.
See attachment 46624 [details]
There was a bug in libstorage handling raid removal (it tried to remove /dev/mdmd0 instead of /dev/md0) in libstorage that will be fixed in beta#3. If possible, please retry your tests with beta#3.