Bug 91622
| Summary: | Boot error after upgrading to kernel 2.4.20-13.8smp | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | rolandbreedveld <roland> |
| Component: | up2date | Assignee: | Bret McMillan <bretm> |
| Status: | CLOSED CANTFIX | QA Contact: | Fanny Augustin <fmoquete> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | gafton, mihai.ibanescu, worley |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-10-18 16:59:28 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
rolandbreedveld
2003-05-26 07:50:09 UTC
could I get a copy of the /boot/grub/grub.conf? Hi Adrian, Also tried the newest kernel 2.4.20-18.8, same problem as 20-13.8 2.4.18-27.8.0 (smp) works still fine #grub.conf #boot=/dev/sda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.18-27.8.0smp) root (hd0,0) kernel /vmlinuz-2.4.18-27.8.0smp ro root=/dev/md1 initrd /initrd-2.4.18-27.8.0smp.img title Red Hat Linux (2.4.20-18.8smp) root (hd0,0) kernel /vmlinuz-2.4.20-18.8smp ro root=/dev/md1 initrd /initrd-2.4.20-18.8smp.img title Red Hat Linux (2.4.20-18.8) root (hd0,0) kernel /vmlinuz-2.4.20-18.8 ro root=/dev/md1 initrd /initrd-2.4.20-18.8.img title Red Hat Linux (2.4.20-13.8smp) root (hd0,0) kernel /vmlinuz-2.4.20-13.8smp ro root=/dev/md1 initrd /initrd-2.4.20-13.8smp.img title Red Hat Linux (2.4.20-13.8) root (hd0,0) kernel /vmlinuz-2.4.20-13.8 ro root=/dev/md1 initrd /initrd-2.4.20-13.8.img regards Roland Hi Also kernel 2.4.20-20.8(smp) won't boot Booting changed to lilo now, same results. looked with tune2fs, fs should be a correct ext-3 fs, with internal journal. When booting the old 2.4-18 kernel is see one row more that is missing with the new kernels: between "mounting root fs" and the "EXT3-fs: unable to read superblock" there should be : kjournaldaemon started, or something like that. Roland The messages reported above resemble the ones that I reported in bug 111631. See it for all the gory details, but the things to look out for are: - Do you have more than one line in /etc/fstab directing a partition to be mounted as '/'? - When installing the kernel RPM, did you see: awk: cmd. line:1: $2 == "Root awk: cmd. line:1: ^ unterminated string Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. Note that any bug still open against Red Hat Linux on will be closed as 'CANTFIX' on September 30, 2006. Thanks again for your help. Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX. |