Red Hat Bugzilla – Bug 120292
system boot fail with lvm2/jfs and latest kernel 2.6.4-1.305
Last modified: 2007-11-30 17:10:39 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
Description of problem:
Have latest lvm2 and kernel from rawhide and on reboot it fails with
the message superblock is corrupt and cannot be repaired since both
primary and secondary copies are corrupt.
fsck.jfs is at 1.1.4.
Going back to previous kernel, everything is ok.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Reboot system
Actual Results: CANNOT CONTINUE.
Expected Results: System boot ok.
Please supply the exact kernel log and error messages you get when the
problem occurs. From the limited summary here, I can't tell if the
message is coming from the LVM layer or from JFS.
Created attachment 99199 [details]
dmesg log output
The log doesn't show much, is there some other log or how can I turn
Is the updated fedora kernel built with all the required modules for
You can set up a serial console to capture the full boot logs, or just
copy it down. But we really need to see the actual error you're
getting, and that doesn't appear to be in the kernel logs here.
This is everything that is on screen. It's not much...
fsck.jfs version 1.1.4, 30-Oct-2003
processing started 4/8/2004 10.32.54
The current device is: /dev/mapper/rootvg-lvroot
Superblock is corrupt and cannot be repaired
since both primary and secondary copies are corrupt.
*** An error occurred during the file system check
*** Dropping you to a shell...
Oh, so you do actually get to a shell prompt? What does "ls -l
/dev/mapper/rootvg-lvroot" and "ls -l
/initrd/dev/mapper/rootvg-lvroot" show at that prompt, what does "cat
/proc/devices" show for the device-mapper entry?
How many volume groups do you have ? If you have more than 1
volumegroup Bug #126565 could be a duplicate. Do you have your "/" on
No response; many changes since this was reported so closing.