Bug 799569 - systemd Failed to start Arbitrary Executable File Formats
Summary: systemd Failed to start Arbitrary Executable File Formats
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-03 05:21 UTC by Tom
Modified: 2012-03-08 15:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-08 15:26:24 UTC
Type: ---


Attachments (Terms of Use)
dmesg (122.12 KB, text/plain)
2012-03-03 05:21 UTC, Tom
no flags Details
/var/log/messages (62.12 KB, text/plain)
2012-03-03 05:22 UTC, Tom
no flags Details
systemd-dump.txt (408.73 KB, text/plain)
2012-03-03 05:22 UTC, Tom
no flags Details
systemd-test.txt (404.34 KB, text/plain)
2012-03-03 05:23 UTC, Tom
no flags Details

Description Tom 2012-03-03 05:21:30 UTC
Created attachment 567227 [details]
dmesg

Description of problem:
System boots with "Failed to start Arbitrary Executable File Formats File System
systemctl status proc-sys-fs-binfmt_misc.mount"
After booting, no network, sound mixer, etc.

Version-Release number of selected component (if applicable):
systemd 43-2

How reproducible:
Everytime

Steps to Reproduce:
1.Update working Rawhide installation
2.Reboot
3.Computer fails to boot with network, sound mixer, etc.
  
Actual results:


Expected results:


Additional info:
Because of current dracut bug 797322, I modified my /etc/fstab to only include /dev/mapper/ listings for home, root, and swap without using UUID. My grub boot command also has UUID taken out. I'm unsure if this is correct.

Comment 1 Tom 2012-03-03 05:22:17 UTC
Created attachment 567228 [details]
/var/log/messages

Comment 2 Tom 2012-03-03 05:22:50 UTC
Created attachment 567229 [details]
systemd-dump.txt

Comment 3 Tom 2012-03-03 05:23:34 UTC
Created attachment 567230 [details]
systemd-test.txt

Comment 4 Tom 2012-03-03 16:26:07 UTC
Kernel was updated with chroot using install DVD, and grub2 menu wasn't updated. Once I reinstalled grub2 using chroot with live CD instead, everything works.

Here's the chroot error I got while trying to reinstall grub2 with install DVD:
/sbin/grub2-probe --device-map="/boot/grub2/device.map" --target=fs -v /boot/grub2
/sbin/grub2-probe: info: Scanning for dmraid_nv RAID devices on disk hd0.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: scanning hd0 for LVM.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: no LVM signature found.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos3.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos2.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos1.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos3.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos2.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos1.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: scanning hd0 for LVM.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: no LVM signature found.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: scanning hd0,msdos3 for LVM.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: no LVM signature found.
/sbin/grub2-probe: info: scanning hd0,msdos2 for LVM.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: no LVM signature found.
/sbin/grub2-probe: info: scanning hd0,msdos1 for LVM.
/sbin/grub2-probe: info: the size of hd0 is 976773168.
/sbin/grub2-probe: info: no LVM signature found.
/sbin/grub2-probe: info: changing current directory to /dev.
/sbin/grub2-probe: info: changing current directory to mqueue.
/sbin/grub2-probe: info: changing current directory to hugepages.
/sbin/grub2-probe: info: changing current directory to vg_tom3000.
/sbin/grub2-probe: info: changing current directory to disk.
/sbin/grub2-probe: info: changing current directory to by-label.
/sbin/grub2-probe: info: changing current directory to by-uuid.
/sbin/grub2-probe: info: changing current directory to by-path.
/sbin/grub2-probe: info: changing current directory to by-id.
/sbin/grub2-probe: info: changing current directory to block.
/sbin/grub2-probe: info: changing current directory to usb.
/sbin/grub2-probe: info: changing current directory to dri.
/sbin/grub2-probe: info: changing current directory to char.
/sbin/grub2-probe: info: changing current directory to shm.
/sbin/grub2-probe: info: changing current directory to pts.
/sbin/grub2-probe: info: changing current directory to bsg.
/sbin/grub2-probe: info: changing current directory to mapper.
/sbin/grub2-probe: info: opening vg_tom3000-lv_root.
/sbin/grub2-probe: error: no such disk.

Comment 5 Tom 2012-03-04 17:25:42 UTC
Here's more on the grub2 error I get:

# grub2-probe /dev/sda
grub2-probe: error: cannot stat `devtmpfs'.

# mount
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime,seclabel)
devtmpfs on /dev type devtmpfs (rw,nosuid,relatime,seclabel,size=1967804k,nr_inodes=491951,mode=755)
devpts on /dev/pts type devpts (rw,relatime,seclabel,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime,seclabel)
/dev/mapper/vg_tom3000-lv_root on / type btrfs (rw,relatime,seclabel,nospace_cache)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,seclabel,mode=755)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel,mode=755)
mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mapper/vg_tom3000-lv_home on /home type btrfs (rw,relatime,seclabel,nospace_cache)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfs-fuse-daemon on /run/user/tom/gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

And my current altered /etc/fstab:
tmpfs                           /dev/shm  tmpfs   defaults        0 0
devpts                          /dev/pts  devpts  gid=5,mode=620  0 0
sysfs                           /sys      sysfs   defaults        0 0
proc                            /proc     proc    defaults        0 0
/dev/mapper/vg_tom3000-lv_root  /         btrfs   defaults        0 0
/dev/mapper/vg_tom3000-lv_home  /home     btrfs   defaults        0 0
/dev/mapper/vg_tom3000-lv_swap  swap      swap    defaults        0 0

Comment 6 Tom 2012-03-08 02:52:03 UTC
Kernel now updates ok on its own on my fresh Rawhide install. However, Anaconda gives an error for installing bootloader at end of install for both 17 and Rawhide. I used Super Grub Disk to boot and then reinstalled grub2 normally instead of using chroot.

I still get these errors that have to be overridden with --force:
# grub2-probe /dev/sda
grub2-probe: error: cannot stat `devtmpfs'.

# grub2-install /dev/sda
/sbin/grub2-setup: warn: Your embedding area is unusually small.  core.img won't fit in it..
/sbin/grub2-setup: warn: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
/sbin/grub2-setup: error: will not proceed with blocklists.

I dual boot with Windows 7.

Comment 7 Michal Schmidt 2012-03-08 11:00:58 UTC
(In reply to comment #0)
> System boots with "Failed to start Arbitrary Executable File Formats File
> System
> systemctl status proc-sys-fs-binfmt_misc.mount"

Do you see any error messages from "mount" in the output of "systemd-journalctl"?

> After booting, no network, sound mixer, etc.

I doubt that's related.
NetworkManager seems to be running, so whatever the problem with the network is, it's not likely to be caused by systemd.

I don't know much about grub2, but since the system boots, the problems are unlikely to be related to grub2 either.

Comment 8 Tom 2012-03-08 15:21:35 UTC
I don't have any systemd problems anymore and if the attached logs aren't helpful, feel free to close. I only have continuing grub problems at install.

Comment 9 Michal Schmidt 2012-03-08 15:26:24 UTC
OK, closing.
Consider filing a bug against grub2, or maybe anaconda.


Note You need to log in before you can comment on or make changes to this bug.