Bug 89166
| Summary: | first boot fails if OS is installed to a cciss controller that is not c0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Mike Miller (OS Dev) <mike.miller> |
| Component: | mkinitrd | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | ia64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-05-27 13:35:36 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: | |||
A work around is to boot the system using "root=6902" if root is on /dev/cciss/c1d0p2. The linuxrc file in the initrd can also be modified. However the pivotroot message still occurs, but the system completes boot. Since I don't have hardware configured like that here, can you try the new mkinitrd at http://people.redhat.com/~katzj/mkinitrd/.ia64/ to see if that fixes the problem? An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2003-170.html |
Description of problem: If the OS is installed to a cciss controller that is not the first cciss controller discovered the reboot will fail with: mount: error 6 mounting ext3 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 umount /initrd/proc failed: 2 Freeing unused kernel memory: 464kB freed Kernel panic: No init found. Try passing init= option to kernel. Version-Release number of selected component (if applicable): 2.4.18-e.27 How reproducible: Evey time Steps to Reproduce: 1. Set up a system with >1 smart array controller 2. Install the OS to something other than c0 3. Reboot the system after install completes Actual results: Kernel panic Expected results: Normal boot with no failures or errors Additional info: