Bug 204420
Summary: | Unhandled Exception after installing files | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim Alberts <tim_alberts> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-08-29 23:49:33 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
Tim Alberts
2006-08-28 23:13:27 UTC
Created attachment 135095 [details]
Anaconda Installer Dump
I submitted a request for help to the fedora user list with no response yet... I am trying to use the Installation program with FC5 to setup a new system with 2 SATA drives. The motherboard has a 'hardware raid' but after a few years of monkeying with this system and drivers, software raid is the correct way to go. However, I am installing FC5 on new hard drives. The installation finishes, I reboot and the boot loader sometimes isn't found at all, or is found, but doesn't have a kernel to boot? The times that the installer puts a boot loader in without a kernel, I type in the parameters: root(hd0,0) kernel... initrd... and the system boots for the first time and I get through the 'first boot stuff (setting soundcard etc)', then I boot again (if I'm lucky) and the system boots. However, at this point is the real symptom of the problem. The raid never has both drives in each partition. The system is configured to have /boot as /dev/md0 (/dev/sda1 + /dev/sdb1)... / as /dev/md1 (/dev/sda2 + /dev/sdb2)... swap as /dev/md2 (/dev/sda3 + /dev/sdb3) except the system is only using sda in partion md0 and sdb in partion md1 and sda in partion md2. Never are both drives in their assigned partitions. So my first question, I've looked through the mailing list archives back a few months and I see no related issues. Is anyone aware of bugs with the software raid installation in FC5? I guess my second question is a general 'help'? Thank you in advance. I think I found the problem. The SATA drives are powered off an adapter cable that appears to have an unreliable connection. After changing the power connections, the system appears MUCH more stable. |