Bug 65627
| Summary: | System will not boot after upgrade | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Andrig T. Miller <andrig.t.miller> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | jmd, mitchloft |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.4.18-5 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-10-25 19:46:05 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: | |||
We have a customer <mitch> (no bugzilla account at this time) using ext3 on the root filesystem reporting the same error. I am also using dual Pentium III's instead of Athlon Are you sure the order of the modules is the same before and after the upgrade ? Also could you try using the aic7xxx_old module ? I am sure about the order of the modules. The root filesystem happens to be on the DAC960 hardware RAID controller, not on the Adaptec controller, so using the older aic7xxx_old module will have no affect. I preload aic7xxx and scsi_mod only for my CDRW. This is merely a convenience, and is not necessary for booting. My suspicion is that the DAC960 driver maybe were the problem is. Ok, I assume you are using grub? If so I think I know what the issue is; there's an interaction between our 2.4.18, grub and dac960. lilo works. all other controllers work with grub. but not dac960 and grub. I have a fix and we're working on releasing an erratum. I am using Grub as the boot loader. Thanks for looking into this. I see precisely this problem but I don't have a DAC960. This is a very ordinary uniprocessor system. The /boot and / are ext3 and the scsi controller is a sym53c875. The system boots fine with an older kernel. I upgraded to 2.4.18-5 with no change. This problem was fixed when I upgraded to the 2.4.18-5 kernel, but has come back with the 2.4.18-10 kernel. I am the original reporter on this, and I would appreciate it if someone could check out whether the patch just wasn't put into 2.4.18-10. Thanks. I have a client running Red Hat 7.2 on a Dell PowerEdge 2300 server. I applied the kernel errata to change their kernel from stock (2.4.7-10) to the latest security update, 2.4.18-18. The system no longer boots. A blank init_module error is shown. megaraid.o: init_module: insmod exited abnormally other error messages I copied down were: kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno=2 mount: error 6 mounting ext3 pivotroot: pivot_root(/sysroot, /sysroot/initrd) failed: 2 I switched grub to boot the stock kernel instead. They however are eager to have the security patches applied. Booting dies with the same message as the original reporter here mentioned, no init is found. Is there any way I can apply the 2.4.9-X kernel to this system in the mean time? RHN says those packages are obsoleted by the 2.4.18-X kernels and won't let you download them. I've just got the same symptoms, with the new erratum kernel - 2.4.20-18.7. My platform is i686, not athlon, and is VMWare rather than metal. ... VFS: Mounted root (ext2 filesystem) Red Hat nash version 3.3.10 starting Loading jbd module Journalled Block Device driver loaded Locading ext3 module Mounting /proc filesystem Creating root device Mounting root filesystem mount: error 6 mounting ext3 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 Freeing unused kernel memory: 120k freed Kernel panic: No init found. Try passing init= option to kernel. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523 Description of problem: I get the following error when trying to boot after upgrading to RedHat 7.3: pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 Freeing unused kernel memory: 304k freed Kernel panic: No init found. Try passing init= option to kernel. I looked up this error message via Google, and found someone who had the same problem, and said they fixed it by putting an empty /initrd directory back on their system. I checked for this condition, and found that I do indeed have an empty /initrd directory. This is a very severe problem, in that the upgrade removed my working 2.4.9-31smp kernel for some reason. I now have a working system. I managed to do this by getting the old kernel 2.4.9-31smp on my system again. I tried the newer 2.4.18-4smp kernel that replaced the 2.4.18-3smp kernel but it didn't work either. My system is a dual processor Athlon (1.2 GHz), with a hardware RAID controller, and an AIC7xxx SCSI controller as well. I preload the following modules through initrd to be able to boot: DAC960 reiserfs scsi_mod aic7xxx ext3 My root filesystem is reiserfs, and my /boot partition is ext3. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Upgrade from RedHat 7.2 to 7.3 2.Boot Actual Results: pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 Freeing unused kernel memory: 304k freed Kernel panic: No init found. Try passing init= option to kernel. Expected Results: Root filesystem should have been mounted, and the remaining portion of the boot process to get to runlevel 5 should have proceeded. Additional info: