Hide Forgot
I'm not sure against which component to report this, so I am reporting it against the distribution. Description of problem: After changing mdadm raid configuration, the new array works fine, but on the next reboot, Fedora will freeze during boot, printing a stack trace of mdadm. Version-Release number of selected component (if applicable): kernel 2.6.35.12-88.fc14.x8_64 How reproducible: I did not attempt to reproduce the problem. Steps to Reproduce: 1. Create a raid 10 from four drives (/dev/sd{a,b,c,d}) 2. Create partitions on the new array 3. Install Fedora on the system, using a different HDD for the OS. 4. List the mdraid partitions in fstab. 5. Fail and remove /dev/sda from the array 6. Create a partition encompassing the entire drive. 7. Add /dev/sda1 to the array. 8. Wait for the array to rebuild. 9. Repeat 5->8 for sdb, sdc, and sdd 10. Use array 11. Reboot Actual results: Array reconfiguration works, the array continues to operate, no data is lost. On next reboot, a stack trace of mdadm is printed, and boot stops on "Starting HAL daemon" Expected results: On step 11, Fedora automatically detects and assembles the reconfigured array, and boot completes without any error message. Additional info: Kernel arguments: ro root=UUID=... rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=... SYSFONT=... KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet drm.debug=0x04 nouveau.noaccel=1 Removing rd_NO_MD and/or rd_NO_DM does not change anything.
What's the stack trace? (Attach a screenshot/digital camera picture if necessary)
Sorry, I didn't think of capturing the stack trace at that moment. I'll try to reproduce in a virtual environment.
I am unable to reproduce the problem in a VM.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping