PDA

View Full Version : [SOLVED] Can only boot with F14 kernel


downer
1st November 2010, 06:12 PM
I got systemd running on F14 Updates-Testing by adding "init=/bin/systemd systemd.unit=graphical.target" to the kernel line. But when I upgraded to Rawhide through yum "yum install fedora-release-rawhide, yum --disablerepo=* --enablerepo=rawhide update" I can't boot into the Rawhide kernel.
I get these errors and others with the Rawhide kernel at boot: "Failed to open syslog for logging: No such file or directory", "udevd [104] can not read '/etc/udev/rules.d/10-console.rules'", "can't access tty; job control turned off"
I can still boot into Rawhide with the latest F14 Updates-Testing kernel, and even a fresh install of Rawhide gives me the same errors, or upgrading F14 without systemd running. Adding the systemd kernel lines from F14 to Rawhide doesn't help either.
Any suggestions?
Update: Compiling a Rawhide kernel with basic changes and trying the first Rawhide kernel from Koji doesn't help either.

downer
3rd November 2010, 05:35 PM
This is my dmesg log with error. "rhgb quiet" removed from kernel boot line in grub.

[ 4.710621] sd 2:0:0:0: [sda] Attached SCSI disk
[ 4.717083] ehci_hcd 0000:00:03.3: PCI INT D disabled
[ 4.717731] ehci_hcd 0000:00:03.3: PME# enabled
[ 4.977843] ata4: SATA link down (SStatus 0 SControl 300)
[ 5.424209] dracut: Scanning devices sda2 for LVM logical volumes vg_user/lv_root vg_user/lv_swap
[ 5.523518] dracut: inactive '/dev/vg_user/lv_root' [50.00 GiB] inherit
[ 5.524816] dracut: inactive '/dev/vg_user/lv_home' [94.59 GiB] inherit
[ 5.525770] dracut: inactive '/dev/vg_user/lv_swap' [3.94 GiB] inherit
[ 5.712267] ohci_hcd 0000:00:03.2: PCI INT C disabled
[ 6.200109] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 6.290823] dracut: Checking filesystems
[ 6.291548] dracut: fsck -T -t noopts=_netdev -A
[ 6.306076] dracut Warning:
[ 6.306241] dracut Warning: fsck returned with error code 8
[ 6.306390] dracut Warning: *** An error occurred during the file system check.
[ 6.306540] dracut Warning: *** Dropping you to a shell; the system will retry
[ 6.306689] dracut Warning: *** to mount the system, when you leave the shell.
[ 166.389432] dracut: Remounting /dev/mapper/vg_user-lv_root with -o ro,
[ 166.452270] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 166.492807] dracut: Mounted root filesystem /dev/mapper/vg_user-lv_root

I'm able to type "exit" in dracut debug console and boot normally.
Any suggestions on how to fix? I'll look up the error code later and make a bug report.

jvillain
3rd November 2010, 07:33 PM

What ever they did it hosed my file system. I am currently booting off a DVD to see if I can salvage any thing. I am choked that I had gotten all of dracut out of my system and they added it back in and forced it to be the default again. Grrrrr.

downer
4th November 2010, 02:51 AM
Yes, I have to use my install CD to rescue my system a lot more times than I'd like. Downgrading dracut to F14 doesn't work.

If I'm reading it right, error code is for corrupted disk or partition not given right size. I didn't use a partition editor and the partition sizes seem ok in Logical Volume Management. Also, fsck shows both "/dev/sda1" and "/dev/mapper/vg_user-lv_root" and "home" as clean, even after forcing a check. The option "fsck -T -t noopts=_netdev -A" doesn't seem to work for dracut shell.
I'll make a bug report later, but I might have missed something...
(Ctrl-D also lets me out of dracut shell.)

downer
4th November 2010, 08:35 PM
Added bug https://bugzilla.redhat.com/show_bug.cgi?id=649913

jvillain
7th November 2010, 08:58 PM
I'm finally making progress. I was getting the same issues with Dracut as you were. You will notice in dmesg that it is whining about a problem with fsck. The last 2 versions of dracut have been to add an fsck and then do a fix.


* Wed Nov 03 2010 Harald Hoyer <harald@redhat.com> - 008-0.8 - fixed fsck -a option *
Fri Oct 29 2010 Harald Hoyer <harald@redhat.com> 008-0.7 - added fsck to initramfs

I did a

yum remove dracut

That also took out plymouth-scripts

I then ran

rpm -ivh http://kojipkgs.fedoraproject.org/packages/dracut/008/0.6.git353ef76.fc15/noarch/dracut-008-0.6.git353ef76.fc15.noarch.rpm

Then

yum install plymouth-scripts

Followed by

dracut -f

The dracut problem is now gone. Now I am just hashing through my systemd problems.

Two good pages to book mark

Debugging Dracut
https://fedoraproject.org/wiki/How_to_debug_Dracut_problems

How to debug Systemd problems
https://fedoraproject.org/wiki/How_to_debug_Systemd_problems