|
Bugzilla – Full Text Bug Listing |
| Summary: | RAID settings failures on remove and /dev/md255 problem | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Leah Cunningham <leah> |
| Component: | YaST2 | Assignee: | Thomas Fehr <fehr> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot of /dev/md255 error
Screenshot of my RAID settings screen |
||
|
Description
Leah Cunningham
2005-08-18 22:45:56 UTC
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. 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. |