Bug 192165
| Summary: | Kernel does not boot after regular update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joao Batista Gomes de Freitas <boaojatista> |
| Component: | kernel | Assignee: | Alasdair Kergon <agk> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
| Severity: | urgent | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | davej, wtogami |
| 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-05-27 13:07:46 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
Joao Batista Gomes de Freitas
2006-05-18 02:06:26 UTC
I hoped that it would be fixed in new kernel release but it happened again in version 2.6.16-1.2122. This is what I see in my screen when I try to reboot: Root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.16-1.2122_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1e00, size=0x16e862] initrd /initrd-2.6.16-1.2122_FC5.img [Linux-initrd @ 0x37e3c000, 0x1b3698 bytes] Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 5.0.32 starting device-mapper: dm-stripe: Target length not divisible by chunk size device-mapper: reload ioctl failed: Invalid argument Unable to open /dev/mapper/nvidia_acaafeee â unrecognised disk label. Reading all physical volumes. This may take a while... No volume groups found Unable to find volume group âVolGroup00â Unable to access resume device (/dev/VolGroup00/LogVol01) mount: could not find filesystem `/dev/root` setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic â not syncing: Attempted to kill init! After many tests I just realize that the problem is related to kernel version 2.6.16-* and the nw implementation of sata_nv. Yesterday I installed a IDE disk im my machine. Then I installed FC5 (version 2.6.15-1.2054) and updated to the most recent kernel version. So now I have two VolumeGroups: VolGroup00 : 2 Samsung s-ata 250G with RAID 0 enabled in the controller. VolGroup01 : 1 IBM IDE 25 G FC5 is installed in both disks and 2 kernel version in each (2.6.15-1.2054 and 2.6.16-1.2122). So now when it boots the 2.6.15.-1.2054 version, I have no problems it doesn't matter from wich disk I am booting. But when I use kernel version 2.6.16-1.2122 it issues the same error related to VolGroup00 and the only difference is that when I use IBM disk it boots anyway because it does not need anything from VolGroup00. I have debug option turned on in the grub.conf file and the error is the same : [CODE]device-mapper: dm-stripe: Target length not divisible by chunk size[/CODE] the dm-stripe warning is likely the cause of this. Alasdair, any ideas what changed in this area in 2.6.16 that could cause this? |