[systemd-devel] systemd .device units timing out

Kay Sievers kay.sievers at vrfy.org
Mon Jun 6 09:25:40 PDT 2011


On Mon, Jun 6, 2011 at 17:58, Avi Kivity <avi at redhat.com> wrote:
> On 06/06/2011 06:47 PM, Kay Sievers wrote:
>> On Mon, Jun 6, 2011 at 15:01, Avi Kivity<avi at redhat.com>  wrote:
>> >  I have a system which was upgraded to F15 and thus systemd.  During the
>> > boot
>> >  process it times out starting various .device units, like sda1.device.
>> >  If I
>> >  let it alone it will boot in about a week or so, but meanwhile it is
>> >  unusable.  I am able to start it up using emergency.target and various
>> >  hacks, but it won't boot cleanly.
>> >
>> >  Any hints?
>>
>> What's in /etc/fstab?
>
> /dev/vg0/fedora         /                       ext4    defaults        1 1
> /dev/sda1               /boot                   ext3    defaults        1 2
> /dev/sda2               /boot_alt               ext3    defaults        1 2

These are the ones that time out? These partitions exist in /dev on
the running system?

> /dev/vg0/local        /local            ext4    defaults    1 3
> 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/vg0/swap           swap                    swap    defaults        0 0
> #/dev/vg0/images        /images            btrfs    noatime        1 3
> /dev/vg0/ccache        /ccache            ext4    noatime        1 4
> #cleo:/svn        /svn            nfs    noauto        1 5
> debugfs            /sys/kernel/debug    debugfs    defaults    0 0

All the virtual fs entries are not needed, but nothing looks like it
should fail.

Kay


More information about the systemd-devel mailing list