Bug 53547
| Summary: | Installer stops after format | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <mintvelt> |
| Component: | anaconda | Assignee: | Brent Fox <bfox> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | ||
| 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: | 2001-11-19 09:40:12 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
Need Real Name
2001-09-11 08:52:32 UTC
This sounds like an install code bug. Reassigning to the component anaconda and the owner of that component. Can you attach the complete debug error message? Do you mean the complete contents of the screen after linux stops responding or do I have to do anything special to obtain a "complete debug error message"? Well, when you see the message "HeaderLoad: assertion "rdlen == dl" failed.", is there any more information on the screen with it? Usually when a crash occurs, a bunch of information is written to the screen that gives us a clue as to where the crash occured. If there's more information on the screen, tell us what it says. I can't really say what the problem is at this point, and I haven't seen this problem before. I'm a little confused as to why the computer works with the old hard drive, but not the new one...but the new hard drive works in a different computer. This makes it seem like a hardware problem to me, but I can't say for sure. Does the BIOS identify the new drive? Closing due to inactivity. Please reopen if you have more information. Sorry to keep you waiting. Just back from vacation. I will have a replacement server in 2 weeks. After that i'll be able to do a new install on the compaq to reproduce the message. I'll be back. P.S. In case you're wondering. I have completed the install and the machine is being used as a mailserver. It boots from floppy and that seems to work. Although sometimes I can see CRC errors on the screen which isn't very comforting. - the maxtor drives passed all the tests on the maxtor diagnostic diskettes. - I ran windows NT server 4.0 SP 6a on it for 90 days without any problems although I used the WD 2.1 GB drive to boot during that period. Anyway. I'll have more info in a couple of weeks Ok, I'm reopening the bug report and will put in Needinfo state until your new server comes in. Have you made any progress? The replacement server will hopefully arrive on monday. I'll have more on tuesday. Ok. Ok here it is:
#Top of the screen show the following message a number of times (+/- 7 times)
Gtk-CRITICAL **: file gtkaccelgroup.c: line 188 (gtk_accel_group_attach):
assertion 'g_slist_find (accel_group->attach_objects, object) == NULL' failed
#then the following text
python: header.c:511: headerload: Assertion 'rdlen == dl' failed
install exited abnormally
sending termination signals...done
sending kill signals...done
disabling swap...
/tmp/swap/hda9
/tmp/swap/hdd1
unmounting filesystems...
/mnt/sysimage/boot
/mnt/sysimage/home
/mnt/sysimage/proc
/mnt/sysimage/var
/mnt/sysimage/usr
/mnt/sysimage
/mnt/runtime
/mnt/source umount failed ()
/dev/pts
/proc
you may safely reboot your system
Can you try doing the install in text mode? Just boot the installer by typing 'text'. Does that help? #During install it says: WARNING: Unknown EDD version 0x1600 supported In dont know if this message shows up during a graphical install. The rest is the same. Python: headerload asserttion failed etc. etc. Doesn't work. This looks like a dupe of bug #37280 *** This bug has been marked as a duplicate of 37280 *** |