Bug 183966
Summary: | newly installed x86_64 system does not boot (kernel panic) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Juergen Bullinger <juergen.bullinger> |
Component: | anaconda | Assignee: | Peter Jones <pjones> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | mike |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-05-05 20:51:55 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: |
Description
Juergen Bullinger
2006-03-04 07:24:02 UTC
could you please help me to recover this install? where is the reverence to this mapper device? is it compiled in the kernel? I would rather recompile and install a kernel on my newly installed FC5.3 partition which doesn't work at the moment as to install FC 5 Test 3 again :o( Sorry, but it really was a nightmare. Do you think that would work? Are there less laborious ways which could be successfull? I created the image using the following command: su --command="cdrecord -v speed=4 -tao $1" I created the image using the following command: su --command="cdrecord -v speed=4 -tao $1" I think this is fixed post test3. Peter -- can you verify? In the meantime I compiled a kernel, had several fights with grub but now it works, also with the latest kernel packages of FC5 Test 3 installed by yum update. I am also having this problem. Installing FC5-T3 onto new server, specs: - GA-K8N51GMF-9 board, NVidia NForce Raid - 2 x 232.88gb SATA II drives - AMD Athlon 64 X2 Dual Core 3800+ Install works fine, but upon first reboot after install, I get this kernel panic. Here is a screen shot of someone else who also has the exact same problem: http://www.joffer.net/webshare/files/20060225-FC5-test3-kernel_panic.jpg Any suggestions, and ideas when this might be fixed? Hi, no I think it is not exactly the same bug. In my case the kernel seemed to miss the mapper device for the harddisk (not the partition). Why does it need the reference to the harddisc at all? It really printed the name of the mapper device (/dev/mapper/...bajeiib or something like this) not the original name /dev/sda These should both be fixed in the current tree -- are either of you still having a problem? Closing due to lack of response from reporters. No, I don't. It was a problem in one of the pre releases of fc 5. Final seems not to be affected. |