Bug 605528
Summary: | MDRaidError: mddeactivate failed for /dev/md0: 09:51:58,247 ERROR : Perhaps a running process, mounted filesystem or active volume group? | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Ales Kozumplik <akozumpl> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Release Test Team <release-test-team-automation> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6.0 | CC: | jzeleny | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | anaconda_trace_hash:1a69746fc8f7969dfd621145678ce2b974c83900831b8ff5ae75adb3ba267705 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-06-21 12:39:34 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Ales Kozumplik
2010-06-18 07:50:35 UTC
Created attachment 425030 [details]
Attached traceback automatically from anaconda.
1) installed 0617.0 rhel6 nightly where the root partition is md0 raid over 2 raid partitions, each 3 GB 2) ran 0615.1 rhel6 installer. The crash occurs during 'examining storage devices' step. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Is /mnt/sysimage still mounted when you hit this error message? I see that it tried to run mount and then immediately after run umount, but there's no errors listed. Perhaps the unmount failed? hmm. I am unable to reproduce it today, but I can not think of anything that is different Let's close this and see if I someone runs into it again. |