(In reply to comment #0)
> Lots of missing binaries in 30{dm,md}-shutdown.sh:
> 
> dmsetup not found
> mdadm not found
> cat not found
> reboot not found
> kbd_mode not found
> stty not found
> setfont not found
> 
> Dropping to debug shell.

which dracut version?

what is your grub.cfg entry of the booted kernel?

what is the output of:

# lsinitrd /boot/initramfs-$(uname -r).img

Giving for current version of kernel which I installed since this bug report.

(In reply to comment #1)
> which dracut version?

dracut-018-12.git20120416.fc17.noarch
 
> what is your grub.cfg entry of the booted kernel?

$ cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.3.2-1.fc17.x86_64 root=/dev/mapper/vg_munich-lv_root ro quiet rhgb SYSFONT=latarcyrheb-sun16 LANG=en_GB.UTF-8 KEYTABLE=de-latin1-nodeadkeys

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.3.2-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os {
        savedefault
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set=root 4baec165-a740-489c-bd52-471023b2f27a
        echo 'Loading Fedora (3.3.2-1.fc17.x86_64)'
        linux   /vmlinuz-3.3.2-1.fc17.x86_64 root=/dev/mapper/vg_munich-lv_root ro quiet rhgb SYSFONT=latarcyrheb-sun16 LANG=en_GB.UTF-8 KEYTABLE=de-l
atin1-nodeadkeys
        echo 'Loading initial ramdisk ...'
        initrd /initramfs-3.3.2-1.fc17.x86_64.img
}

> what is the output of:
> 
> # lsinitrd /boot/initramfs-$(uname -r).img

Will attach.

Created attachment 578042 [details]
lsinitrd output

Could you please create the following file /usr/lib/systemd/system-shutdown/dmesg:

#!/bin/sh
mount / -orw,remount
dmesg > /dmesg.save
mount / -oro,remount

And then chmod +x it. Then, reboot with "systemd.log_level=debug systemd.log_target=kmsg" on the kernel cmdline, and shutdown. On next reboot please provide us with the contents of /dmesg.save.

oh.. and please test, if dracut-018-22.git20120418.fc18 fixes the issue.

Hi,

Since comment 3, I have been able to reboot without problems.

I had been getting a lot of selinux errors since upgrading to F17a and so I've run a relabel since filing the bug report. I don't know whether this is relevant.

Since I can no longer reproduce the problem I reported, would it still make sense to carry out the steps in comments 4 and 5?

Thanks.

it happens also here after upgrading from F16 and fully updating my system

it happens also here after upgrading from F16 and fully updating my system

(In reply to comment #8)
> it happens also here after upgrading from F16 and fully updating my system

so, open a new bug for F16 and give the infos requested in previous comments, please.

after upgrading my F17 Beta system, these warnings disappeared...

I think that tests are not necessary any longer

After updating my Fedora 16 to 17, I have the same problem with shutdown my notebook. What kind of logs and other information do I make to solve this problem?

(In reply to comment #11)
> After updating my Fedora 16 to 17, I have the same problem with shutdown my
> notebook. What kind of logs and other information do I make to solve this
> problem?

what is the output of:

# lsinitrd /boot/initramfs-$(uname -r).img

and:

# find /run/initramfs

(In reply to comment #12)
> (In reply to comment #11)
> > After updating my Fedora 16 to 17, I have the same problem with shutdown my
> > notebook. What kind of logs and other information do I make to solve this
> > problem?
> 
> what is the output of:
> 
> # lsinitrd /boot/initramfs-$(uname -r).img

Sorry guys, but I solved the problem. The problem was in the latest kernel, at the time of my upgrade (3.3.5x to f16 vs 3.3.4x in f17). After installing the native kernel on Fedora 17 - my laptop normal reboot/off.

The F17 kernel did not work (failed to find root file system, some error about device mapper), and is currently booting the last f16 kernel with the rest of F17.

Both are 3.3.7-1, so that's curious. Also saw the kernel panic on shutdown, lots of udev stuff missing, etc... quite ugly...

Pretty sure the initial report is the same as 831634, so duping to that. Please reopen if I'm wrong

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