Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 192165

Summary: Kernel does not boot after regular update
Product: [Fedora] Fedora Reporter: Joao Batista Gomes de Freitas <boaojatista>
Component: kernelAssignee: Alasdair Kergon <agk>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: urgent Docs Contact:
Priority: medium    
Version: 5CC: 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
Description of problem: After a regular update the kernel panics and hangs


Version-Release number of selected component (if applicable):
2.6.16-1.2096
2.6.16-1.2111
How reproducible:
It always happens with message /dev/mapper/nvidia_acaafeee invalid or something
similar and then it hangs stating that it can not mount any partitions

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
I am using a ASUS A8N-E motherboard with nvidia sata controller.
The RAID BIOS support is enabled
I am using LVM and hardware RAID 0 with 2 sata HDs
It doesn't happens with the original installed kernel (2.6.15-1.2054) only after
a regular update (yum update)

Comment 1 Joao Batista Gomes de Freitas 2006-05-22 23:40:43 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!

Comment 2 Joao Batista Gomes de Freitas 2006-05-26 22:27:28 UTC
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]

Comment 3 Dave Jones 2006-05-27 04:26:58 UTC
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?

Comment 4 Joao Batista Gomes de Freitas 2006-05-27 13:07:46 UTC

*** This bug has been marked as a duplicate of 186842 ***