Bug 1100191
| Summary: | Fails to include required cciss driver | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | tc | ||||||||
| Component: | mkinitrd | Assignee: | Brian Lane <bcl> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 5.10 | CC: | ddumas, jherrman, tc | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: |
Previously, mkinitrd searched an incorrect path for the cciss block driver device and the findstoragedriver() function could therefore not find cciss in the /sys/block directory. Consequently, the kernel failed to boot after it was updated. This update amends the cciss path and findstoragedriver() is thus able to detect cciss devices correctly. As a result, the kernel now boots as expected.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-05-22 15:07:11 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
tc
2014-05-22 08:22:42 UTC
*** This bug has been marked as a duplicate of bug 988020 *** Thanks BCL. " You are not authorized to access bug #988020. " Can you elaborate why this is a duplicate ? Created attachment 898491 [details]
patch for ccis driver
Sorry about that. It is fixed in the current release -- here's the patch.
Ohh, thanks, that looks like the culprit. By 'current release' you mean a mkinitrd later than that that ships with EL5.10 ? Are there plans to back port this to the mkinitrd v5.1 in EL5.10 then ? It's a nasty bug... It will be fixed in 5.11 No back port even though it kills systems on Kernel updates ? The patch doesn't work after applying to mkinitrd here, the output from a patched mkinitrd is better : ... Looking for deps of module jbd Looking for driver for device cciss/c0d0p2 Looking for driver for cciss device cciss/c0d0p2 Looking for deps of module pci:v00000E11d00000046sv00000E11sd00004091bc01sc04i00: scsi_mod Looking for deps of module scsi_mod Looking for deps of module sd_mod: scsi_mod ... but the initrd still doesn't contain the cciss module in lib/ or an entry in the init script to load it. There's no reference to it in the various 'copy from' lines. If it's any help I have a /dev/cciss/c0d0p1 and a /sys/block/cciss!c0d0/cciss!c0d0p1 I don't know why, but cciss/c0d0p2 != cciss/c0d0p1 You could try running with: bash -x mkinitrd -v -f initrd-`uname -r`.img `uname -r` and attach the output here as a text/plain attachment. Sorry, I should have been clearer with my devices - that was an example, here are my actual /boot mount points: # mount|grep boot /dev/cciss/c0d0p1 on /boot type ext3 (rw) # ls -lah /sys/block/cciss\!c0d0/cciss\!c0d0p1 total 0 drwxr-xr-x 3 root root 0 May 23 11:47 . drwxr-xr-x 7 root root 0 May 23 11:47 .. -r--r--r-- 1 root root 4.0K May 28 08:05 dev drwxr-xr-x 2 root root 0 May 17 17:56 holders -r--r--r-- 1 root root 4.0K May 28 08:05 size -r--r--r-- 1 root root 4.0K May 28 08:05 start -r--r--r-- 1 root root 4.0K May 28 08:05 stat lrwxrwxrwx 1 root root 0 May 28 08:05 subsystem -> ../../../block --w------- 1 root root 4.0K May 28 08:05 uevent My root FS uses LVM on /dev/cciss/c0d0p2 : # mount|grep LogVol00 /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) # pvdisplay --- Physical volume --- PV Name /dev/cciss/c0d0p2 VG Name VolGroup00 PV Size 33.81 GB / not usable 479.00 KB Allocatable yes PE Size (KByte) 32768 Total PE 1082 Free PE 23 Allocated PE 1059 PV UUID Rb75NE-yGGn-QN4u-4UYi-obXM-Eu8I-TkE0qy # ls -lah /sys/block/cciss\!c0d0/cciss\!c0d0p2 total 0 drwxr-xr-x 3 root root 0 May 28 08:08 . drwxr-xr-x 7 root root 0 May 28 08:08 .. -r--r--r-- 1 root root 4.0K May 28 08:08 dev drwxr-xr-x 2 root root 0 May 23 11:47 holders -r--r--r-- 1 root root 4.0K May 28 08:12 size -r--r--r-- 1 root root 4.0K May 28 08:12 start -r--r--r-- 1 root root 4.0K May 28 08:12 stat lrwxrwxrwx 1 root root 0 May 28 08:12 subsystem -> ../../../block --w------- 1 root root 4.0K May 28 08:12 uevent I will attach patched and unpatched logs in a sec. Created attachment 899872 [details]
bash -x output from unpatched mkinitrd
Created attachment 899873 [details]
bash -x output from npatched mkinitrd
Our other 2.6.18-371.6.1.el5debug w/ mkinitrd-5.1.19.6-81.el5_10 box just picked up a new kernel, and included the driver OK. What else does mkinitrd depend on ? I checked, and the paths look the same on both boxes. Are there any additional debugging steps I can take ? FYI this was resolved when https://rhn.redhat.com/errata/RHBA-2014-1224.html was rolled out this week, as part of http://lists.centos.org/pipermail/centos-announce/2014-September/020632.html |