Bug 56026
| Summary: | mkbootdisk fails on recent "smp" and "enterprise" kernels | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Dmitri A. Sergatskov <dasergatskov> |
| Component: | mkbootdisk | Assignee: | Matt Wilson <msw> |
| Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.2 | CC: | ewt, khill160, smoehle, stj |
| 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: | 2002-04-20 04:35:42 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
Dmitri A. Sergatskov
2001-11-11 03:32:33 UTC
This also happens with the standard 2.4.9-13 kernel (at least the Athlon version). I find that 2.4.9-13 for UP athlon is the last kernel for which I can make a boot disk. Both -21 and -31 fail. Maybe it is time for a mkbootcd command. I'm using the SGI XFS installer based on either RedHat 7.1 or RedHat 7.2. With the XFS enabled kernel it was never possible to create a bootdisk because of the XFS code which enlarged the kernel too much. It seems that 'mainstream' RedHat kernels suffer the same problem now. I have created patched RPMs of mkbootdisk which allows to create overformatted bootdisks and I have not found any pc until now which could not boot such a disk. Updated mkbootdisk RPMs are here: http://home.datacomm.ch/simix/XFS/rh-7.2/ Create bootdisk as usual, but use a different device: mkbootdisk --device /dev/fd0u1722 2.4.9-31enterprise Would be nice to see the patch integrated into the next RedHat release. It doesnt work for 2.4.9-31 on a intel system either. However a grub boot disk can hold the current size of the vmlinuz image (952 kb). For automated boot you would have make the appropriate entries into menu file. There of course is the rescue mode on the iso image cdroms. Of course this boots the image of the iso, but it can help you fix a boot problem. Maybe someone could write a utility to create boot cd rom from your current kernel. "out of space" isn't a bug in mkbootdisk, though it is a limitation that's becoming more and more important. Hi !! "Out of space" isn't a bug in mkbootdisk, well is then a limitation in glibc? This is incredible annoying, I am running Red Hat Linux Enterprise 2.1 AS 2.4.9-e.27 SMP and I was able to create the bootdisk when I ran at the 2.4.9-e.3 SMP levl, no I am left outside the door. Red Hat Support tells me that this bug has been seen in Red Hat 9 as well, but I am running Red Hat Linux Enterprise 2.1 AS 2.4.9-e.27 so I really don't care, I have purchased a product and I expect it to work. If my server craches how do I then get access the a kernel having my detected SCSI devices discovered? Now I have been told to play with the mkbootdisk --iso -- device /root/boot.img command and I still keep asking myself, why on earth shall I start to use time on this. Have anyone of you played with the iso-stuff? I have a Red Hat Linux Enterprise 3.0 AS running next to me and there it works fine, but I really need to get something going on the Red Hat Linux Enterprise 2.1 AS level //Steen |