Boot: "Waiting 10 seconds for device" - mkinitcpio doesnt fix

I've recently started experiencing an issue which is occurring regularly.
On bootup directly after the kernel begins loading I get the error
Waiting 10 seconds for device /dev/by-id/xxx-xxx-xxx-xx...
and then get dropped to jail root shell.
I have had this problem occur a few times and each time was easily fixed by booting up rescue, chrooting, ensuring pacman is up to date and re-running mkinitcpio -p linux
This time that doesn't work. Does anyone know where else I can look?

https://wiki.archlinux.org/index.php/Pa … onger_boot

Similar Messages

[SOLVED] Waiting 10 seconds for device...

I'm getting a "waiting 10 seconds for device..." on boot, and then it waits 10 seconds and boots me to a recoverely shell.
I do realise a lot of people have had this problem, but the solutions all imply the Fallback. When I boot to fallback, I get the exact same error, so I can't use those solutions.
It seems that I have to run "mkinitcpio -p linux", can I do that from a livecd. If yes, how?
Any ideas? Thank you.
Last edited by ephan (2012-11-09 17:02:52)

I'm glad you fixed it. But you don't have to reinstall packages, just run mkinitcpio -p linux and you'll be fine (reinstallation also works because mkinitcpio -p linux is invoked during the process).

Waiting 10 seconds for device....

I have serious problem detecting hard disk during startup.
There is a message: Waiting 10 seconds for device, but it won't wait 10 seconds.
Sometimes it passes and system boots.
Sometimes it fails at that point, and I can only reboot because it's not able to mount root.
Where exactly is the script which waits 10 seconds? I can't find it in /etc at all.

Jacek Poplawski wrote:Correction - I am dumped into recovery shell. There is a message "you are on your own", so that's why I think the problem is root mount.
But it never waits 10s.
It only waits 10 sec if needed, it should read "waiting maximally 10 sec for root device...". If it finds the device or an unrecoverable error occurs, it wouldn't make sense to keep on waiting.
As suggested above, the problem is probably due to device nodes getting swapped. Read this article and use UUIDs or labels in fstab and grub.
Edit: typo.
Last edited by Ramses de Norre (2011-06-11 12:33:36)

[Solved] Boot messages waiting 10 secodns for device...

Hello.
When i'm boot my arch i got message waiting 10 secdonds for device /dev/sda1 (arch partition).
I have in mkinitcpio this modules:
ahci ext4 scsi_mod sd_mod libata.
That's all what can i do run arch wihout waiting 10 secodns?
Last edited by SpeedVin (2009-06-26 13:56:57)

paranoos wrote:
after a little digging, i realized this is caused by mkinitcpio. it defaults to 10 seconds, but most drives don't need to wait at all. this delay is available for people booting off usb devices which take a few seconds to initialize. the default should be no waiting, with an option for those who need it (by setting the kernel rootdelay manually).
afaict this is a bug, here is the fix
edit /lib/initcpio/init; where it says
# If rootdelay is empty or not a non-negative integer, set it to 10
if [ -z "${rootdelay}" -o ! "${rootdelay}" -ge 0 ]; then
export rootdelay=10
fi
change it to export rootdelay=0 -- this way, the default is not to wait
also edit /lib/initcpio/init_functions; where it says
if [ "$2" -gt 0 ]; then
seconds="$2"
change -gt 0 to -ge 0 -- this way, it will accept a setting of 0 and not ignore it.
Great that's working thamk you

ACNS wait 120 seconds for reply not long enough

Hello
Using CE-7305A-K9 with ACNS 5.5.5 for outgoing proxy towards the Internet. A POST is send via the proxy and TCP ack'd by the application provider. The HTTP reply comes back from the application almost 4 minutes later. ACNS only waits for 120 seconds (I think) and then sends an error message to the client browser. The browser waits for 5 minutes so this works when the proxy is not there.
Can this max time that the proxy waits for a reply be increased ?
Thanks

This problem occurs when the first configured name server is down and replies with ICMP unreachable for the DNS queries.
or
CSCef67934
Symptom: The proxy autoconfiguration file is missing from the Content Engine after you switch from group settings to device settings, and then switch back to group settings.
Condition: This problem occurs in the following circumstances:
a. You have specified values in the Client Proxy Autoconfig Device Group window of the Content Distribution Manager GUI.
b. You override these values through the Client Proxy Autoconfig Device window of the Content Distribution Manager GUI.
c. You revert the Content Engine back to the device group settings (you click the Force device group settings button in the device group window or you select the device group from the drop-down menu in the device window).
The autoconfiguration file is not found, but the proxy autoconfiguration feature is shown as enabled.
Workaround: Return to the device window in the Content Distribution Manager GUI, delete the values from the proxy autoconfiguration fields in the device window, and then select device group from the drop-down menu.

Change Seconds Waiting for Device during boot

During boot at the section: "Waiting 10 Seconds for Device", I am often dropped to a shell. I think it may be because I need to increase the wait time. How can I do this? I've looked in several places but I'm not sure what to look for.

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine. I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
Waiting for 10 seconds for device /dev/md2 ...
Root device '/dev/md2' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/md2'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]#
As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
I think I've included all the appropriate bits of config here that should be working. I assume I've missed something fundamental - any ideas?
menu.lst:
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/md2 ro
initrd /kernel26.img
mkinitcpio.conf:
HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
fstab:
/dev/md1 /boot ext3 defaults 0 1
/dev/md2 / ext3 defaults 0 1
mdadm.conf
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
47a9fe:d45dbc0c
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
043406:dbdabe38
Thanks!

Hi magec, that's quite helfpul - I've certainly got further.
Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
mount /dev/md2 /mnt
mount /dev/md1 /mnt/boot
mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
chroot /mnt /bin/bash
But based on your suggestion it's working better
mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
mount /dev/md2 /mnt
mount /dev/md1 /mnt/boot
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
mount -n -t ramfs none /mnt/dev
cp -Rp /dev/* /mnt/dev
chroot /mnt /bin/bash
The boot is now getting further, but now I'm getting:
md: md2 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 32218349568
mdadm: /dev/md2 has been started with 2 drives.
md2: Waiting 10 seconds for device /dev/md2 ...
unknown partition table
mount: mounting /dev/md2 on /new_root failed: No such device
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
/bin/sh: can't access tty; job contol turned off
[ramfs /]#
The bit that really confuses me is this:
[ramfs /]# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda2[0] sdb2[1]
31463232 blocks [2/2] [UU]
md1 : active raid1 sda1[0] sdb1[1]
208704 blocks [2/2] [UU]
unused devices: <none>
[ramfs /]# mount /dev/md2 /new_root
mount: mounting /dev/md2 on /new_root failed: No such file or directory
[ramfs /]# ls /dev/md2
/dev/md2
[ramfs /]#
So the array is up, the device node is there but it can't be mounted? Very strange.
Last edited by chas (2010-05-02 11:24:09)

[SOLVED]Grub fails to open dm-crypt+LUKS volume on boot(Waiting 10s..)

I know there are quite a few solved posts like these but it's usually because of "mkinitcpio -p linux" not being regenerated.
My problem is after boot Grub says:
running hook [udev]
running hook [encrypt]
Waiting 10 seconds for device /dev/disk/by-uuid/d1d0825c-25d1-4cbe-811f-725d9ef8d034>...
ERROR: device 'UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034' not found. Skipping fsck.
ERROR: Unable to find root device 'UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034'.
Here are all the files that I think would be needed for this:
/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
#/dev/mapper/cryptroot / ext4 rw,realtime,data=ordered 0 1
UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034 / ext4 rw,relatime,data=ordered 0 1
#/dev/sda5 /boot ext4 rw,relatime,data=ordered 0 2
UUID=d04b37b1-4dfb-451c-b582-b9d95ca8fe22 /boot ext4 rw,relatime,data=ordered 0 2
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 298.1G 0 disk
├─sda1 8:1 0 100M 0 part
├─sda2 8:2 0 97.6G 0 part
├─sda3 8:3 0 1K 0 part
├─sda5 8:5 0 300M 0 part
├─sda6 8:6 0 50G 0 part
│ └─cryptroot 254:1 0 50G 0 crypt /
├─sda7 8:7 0 1G 0 part
└─sda8 8:8 0 149.1G 0 part
sdb 8:16 1 29.3G 0 disk
├─sdb1 8:17 1 558M 0 part
└─sdb2 8:18 1 31M 0 part
sdc 8:32 1 15G 0 disk
└─sdc1 8:33 1 15G 0 part /mnt/usb
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 240.9M 1 loop
loop1 7:1 0 1.5G 1 loop
└─arch_root-image 254:0 0 1.5G 0 dm /etc/resolv.conf
loop2 7:2 0 1.5G 0 loop
└─arch_root-image 254:0 0 1.5G 0 dm /etc/resolv.conf
blkid
/dev/sda1: LABEL="System Reserved" UUID="3A481C2D481BE703" TYPE="ntfs" PARTUUID="850a6169-01"
/dev/sda2: UUID="EE3443C234438D11" TYPE="ntfs" PARTUUID="850a6169-02"
/dev/sda5: UUID="d04b37b1-4dfb-451c-b582-b9d95ca8fe22" TYPE="ext4" PARTUUID="850a6169-05"
/dev/sda6: UUID="691c218e-658f-47ff-8296-6b266b2c06c9" TYPE="crypto_LUKS" PARTUUID="850a6169-06"
/dev/sdb1: UUID="2014-07-03-18-41-56-00" LABEL="ARCH_201407" TYPE="iso9660" PTUUID="6039e1c4" PTTYPE="dos" PARTUUID="6039e1c4-01"
/dev/sdb2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="3B47-A69A" TYPE="vfat" PARTUUID="6039e1c4-02"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="5857fcdc-02d9-4d16-aeb5-00d786995ffc" TYPE="ext4"
/dev/loop2: UUID="5857fcdc-02d9-4d16-aeb5-00d786995ffc" TYPE="ext4"
/dev/mapper/arch_root-image: UUID="5857fcdc-02d9-4d16-aeb5-00d786995ffc" TYPE="ext4"
/dev/mapper/cryptroot: UUID="d1d0825c-25d1-4cbe-811f-725d9ef8d034" TYPE="ext4"
/dev/sdc1: UUID="86D3-3C7E" TYPE="vfat" PARTUUID="c3072e18-01"
/dev/sda7: PARTUUID="850a6169-07"
/dev/sda8: PARTUUID="850a6169-08"
/etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda6:cryptroot"
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
/boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if loadfont unicode ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-d1d0825c-25d1-4cbe-811f-725d9ef8d034' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod cryptodisk luks gcry_rijndael gcry_rijndael gcry_sha1
insmod ext2
set root='cryptouuid/691c218e658f47ff82966b266b2c06c9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='cryptouuid/691c218e658f47ff82966b266b2c06c9' d1d0825c-25d1-4cbe-811f-725d9ef8d034
else
search --no-floppy --fs-uuid --set=root d1d0825c-25d1-4cbe-811f-725d9ef8d034
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034 rw cryptdevice=/dev/sda6:cryptroot quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-d1d0825c-25d1-4cbe-811f-725d9ef8d034' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-d1d0825c-25d1-4cbe-811f-725d9ef8d034' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod cryptodisk luks gcry_rijndael gcry_rijndael gcry_sha1
insmod ext2
set root='cryptouuid/691c218e658f47ff82966b266b2c06c9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='cryptouuid/691c218e658f47ff82966b266b2c06c9' d1d0825c-25d1-4cbe-811f-725d9ef8d034
else
search --no-floppy --fs-uuid --set=root d1d0825c-25d1-4cbe-811f-725d9ef8d034
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034 rw cryptdevice=/dev/sda6:cryptroot quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-d1d0825c-25d1-4cbe-811f-725d9ef8d034' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod cryptodisk luks gcry_rijndael gcry_rijndael gcry_sha1
insmod ext2
set root='cryptouuid/691c218e658f47ff82966b266b2c06c9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='cryptouuid/691c218e658f47ff82966b266b2c06c9' d1d0825c-25d1-4cbe-811f-725d9ef8d034
else
search --no-floppy --fs-uuid --set=root d1d0825c-25d1-4cbe-811f-725d9ef8d034
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034 rw cryptdevice=/dev/sda6:cryptroot quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
Things I tried:
Replace this line in grub.cfg with
linux /boot/vmlinuz-linux root=UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034 rw cryptdevice=UUID=d1d0825c-25d1-4cbe-811f-725d9ef8d034:cryptroot quiet
Do mkinitcpio -p linux but the hook ecrypt is there, so I assume it's a grub issue.
In
/etc/default/grub
replace GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda6:cryptroot" with actual UUID, etc.
Grub config was made with
grub-mkconfig -o /boot/grub/grub.cfg
Grub was installed with
grub-install --target=i386-pc --recheck /dev/sda
Last edited by shape (2014-07-21 15:23:05)

Welcome to the forum :-)
Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.

[SOLVED] dmraid "Timed out waiting for device" at boot

Created a bug report with solution proposal: https://bugs.archlinux.org/task/33166
I created a virtual machine to demonstrate the problem
https://docs.google.com/open?id=0B40Hp1 … WZUQ21xZk0
The root and the other mount points are all on one raid disk. Although the root mounts quickly, other mount points cause timeouts at boot time.
dmraid prints that all /dev/mapper/isw_* devices are created.
I think /dev/disk/by-uuid/* links are created too, but for some reason systemd doesn't see them.
After boot I can execute "mount -a" without errors.
here's my fstab:
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=e89249d8-49a5-415b-8f9b-97de5cfbe82d / ext3 defaults
UUID=c37f8bdd-3d6c-495f-bf8a-5ef059e55254 swap swap defaults 0 0
UUID=91988343-dd89-43b9-8975-babb0b9510a2 /media/ARCHLINUXNEW ext4 nofail 0 1
UUID=62C813E9C813B9ED /media/distrpart ntfs-3g rw,nofail
UUID=E0A1-D623 /media/realboot vfat rw,codepage=866,iocharset=utf8,umask=002,noatime,nofail
# journalctl -b
Dec 15 00:25:24 localhost kernel: firewire_core 0000:05:03.0: created device fw0: GUID 0011d800017a5dd7, S400
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-E0A1\x2dD623.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/realboot.
Dec 15 00:26:50 localhost systemd[1]: Job media-realboot.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-E0A1\x2dD623.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-62C813E9C813B9ED.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/distrpart.
Dec 15 00:26:50 localhost systemd[1]: Job media-distrpart.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-62C813E9C813B9ED.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start timed out.
Dec 15 00:26:50 localhost systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /media/ARCHLINUXNEW.
Dec 15 00:26:50 localhost systemd[1]: Job media-ARCHLINUXNEW.mount/start failed with result 'dependency'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/91988343-dd89-43b9-8975-babb0b9510a2.
Dec 15 00:26:50 localhost systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.service/start failed with result 'dependency
Dec 15 00:26:50 localhost systemd[1]: Job dev-disk-by\x2duuid-91988343\x2ddd89\x2d43b9\x2d8975\x2dbabb0b9510a2.device/start failed with result 'timeout'.
Dec 15 00:26:50 localhost systemd[1]: Dependency failed for /dev/disk/by-uuid/c37f8bdd-3d6c-495f-bf8a-5ef059e55254.
Dec 15 00:26:50 localhost systemd[1]: Reached target Swap.
Note the 1.5 minute pause
# mount | grep /dev/mapper
/dev/mapper/isw_ebaifefjbf_Volume0p9 on / type ext3 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p1 on /media/realboot type vfat (rw,noatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp866,iocharset=utf8,shortname=mixed,errors=remount-ro)
/dev/mapper/isw_ebaifefjbf_Volume0p8 on /media/ARCHLINUXNEW type ext4 (rw,relatime,stripe=64,data=ordered)
/dev/mapper/isw_ebaifefjbf_Volume0p5 on /media/distrpart type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
Last edited by leniviy (2012-12-22 16:06:25)

I've ran into exactly same problem lately, but finally solved it.
Setup: Intel Fake RAID, mirror, partitioned as:
/dev/mapper/isw_dfjeffgfaj_rootvol1 /boot
/dev/mapper/isw_dfjeffgfaj_rootvol2 /
/dev/mapper/isw_dfjeffgfaj_rootvol3 /home (dm-crypted)
In /etc/fstab i had following mountpoints:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
/dev/mapper/isw_dfjeffgfaj_rootvolp1 /boot ext4 rw,relatime,data=ordered 0 2
and boot hung on waiting for /dev/mapper/isw_dfjeffgfaj_rootvolp1. Solution involves changing dev path to UUID:
# file /etc/fstab
/dev/mapper/isw_dfjeffgfaj_rootvolp2 / ext4 rw,relatime,data=ordered 0 1
UUID=44809529-11d9-4f53-9652-7b97ed077225 /boot ext4 rw,relatime,data=ordered 0 2
For some reason symlinks /dev/mapper/isw* are not present during systemd mount.

Force fsck on boot and timeout waiting for device issues [SOLVED]

Archlinux starts checking fs on every boot since linux and systemd packages were updated last night.
systemd --->213-5
linux ---->3.14.5-1
Another issue appears with last update
Timed out waiting for device dev-disk-by\x2duuid-9f780ada\x2d0671\
Dependency failed for /dev/disk/by-uuid/9f780ada-0671-43d8-b036-f9
Dependency failed for Swap.
I have this issue on my laptop which was updated yesterday.I have also desktop running archlinux again I've just checked out the systemd and linux versions.The systemd package is not the latest one it's 212-3.I havent any problem on that machine.I guess systemd is responsible of this cause.
I've just reboot and realized that systemd-fsck says Super block last write is in the future.Date and time is correct in BIOS same as on linux
Last edited by gecici90 (2014-06-05 21:10:52)

I had the same problem, I get in the recovery But downgrading systemd and systemd-sysvcompat The sorted list of the upgraded packages:
[2014-06-05 21:11] [PACMAN] installed libx264 [2014-06-05 21:11] [PACMAN] upgraded btrfs-progs [2014-06-05 21:11] [PACMAN] upgraded cifs-utils [2014-06-05 21:11] [PACMAN] upgraded imagemagick [2014-06-05 21:11] [PACMAN] upgraded filesystem [2014-06-05 21:11] [PACMAN] upgraded lib32-libdbus [2014-06-05 21:11] [PACMAN] upgraded libproxy [2014-06-05 21:11] [PACMAN] upgraded libpurple [2014-06-05 21:11] [PACMAN] upgraded libsystemd [2014-06-05 21:11] [PACMAN] upgraded libwbclient [2014-06-05 21:11] [PACMAN] upgraded openssl [2014-06-05 21:11] [PACMAN] upgraded perl [2014-06-05 21:11] [PACMAN] upgraded perl-xml-parser [2014-06-05 21:11] [PACMAN] upgraded perl-yaml-syck [2014-06-05 21:11] [PACMAN] upgraded pidgin [2014-06-05 21:11] [PACMAN] upgraded postgresql-libs [2014-06-05 21:11] [PACMAN] upgraded python2 [2014-06-05 21:11] [PACMAN] upgraded smbclient [2014-06-05 21:11] [PACMAN] upgraded subversion [2014-06-05 21:11] [PACMAN] upgraded systemd [2014-06-05 21:11] [PACMAN] upgraded [2014-06-05 21:11] [PACMAN] upgraded x264 [2014-06-05 21:11] [PACMAN] upgraded xchat [2014-06-05 21:11] [PACMAN] upgraded xfconf Downgrading systemd and systemd-sysvcompat [2014-06-05 21:43] [PACMAN] Running 'pacman [2014-06-05 21:43] [PACMAN] downgraded systemd [2014-06-05 21:43] [PACMAN] downgraded console after forced fsck.
to their previous version made it all work back again.
(1:142.20140311-4)
(3.14.1-1 -> 3.14.2-2)
(6.2-1 -> 6.3-1)
(6.8.9.1-2 -> 6.8.9.1-3)
(2013.05-2 -> 2014.05-2)
(1.8.0-1 -> 1.8.2-1)
(0.4.11-2 -> 0.4.11-3)
(2.10.9-1 -> 2.10.9-2)
(212-3 -> 213-5)
(4.1.7-1 -> 4.1.8-1)
(1.0.1.g-1 -> 1.0.1.h-1)
(5.18.2-2 -> 5.20.0-2)
(2.41-4 -> 2.41-5)
(1.27-1 -> 1.27-2)
(2.10.9-1 -> 2.10.9-2)
(9.3.4-1 -> 9.3.4-2)
(2.7.6-3 -> 2.7.7-1)
(4.1.7-1 -> 4.1.8-1)
(1.8.9-1 -> 1.8.9-2)
(212-3 -> 213-5)
systemd-sysvcompat (212-3 -> 213-5)
(1:142.20140311-1 -> 1:142.20140311-4)
(2.8.8-13 -> 2.8.8-14)
(4.10.0-3 -> 4.10.0-4)
makes my computer boots normally:
-U /var/cache/pacman/pkg/systemd-212-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-212-3-x86_64.pkg.tar.xz'
(213-5 -> 212-3)
systemd-sysvcompat (213-5 -> 212-3)

Timed out waiting for device sys-subsystem-net-devices-enp69s0.device

Hi all,
Since quite some time I have been waiting for Arch Linux to startup (and shutdown), and today I wanted to figure out what was going wrong. I found out that I could find the boot log file with journalctl, and this seems to be the issue:
Oct 13 21:01:52 localhost systemd[1]: Job sys-subsystem-net-devices-enp69s0.device/start timed out.
Oct 13 21:01:52 localhost systemd[1]: Timed out waiting for device sys-subsystem-net-devices-enp69s0.device.
Oct 13 21:01:52 localhost systemd[1]: Dependency failed for dhcpcd on enp69s0.
Oct 13 21:01:52 localhost systemd[1]: Starting Network.
Oct 13 21:01:52 localhost systemd[1]: Reached target Network.
Oct 13 21:01:52 localhost systemd[1]: Mounting /mnt/homesrv/storage...
Now, enp69s0 is my LAN network interface, which I barely use, and my WLAN connection is handled by NetworkManager. However, I can't find out what I'm supposed to do to stop this behaviour. I tried:
systemctl disable sys-subsystem-net-devices-enp69s0.device
But that does not seem to solve anything. Can anyone help me out?
Last edited by Hmail (2013-10-13 19:09:53)

Andreaskem wrote:Maybe try "systemctl disable [email protected]".
That did the trick! I didn't want to disable the device because I might use it once in a while.
The shutdown issue is not solved yet, but that seems to be an issue with a samba share that is unmounted after the network services are shutdown. I'll delve in the wiki to figure out how to fix that. But for now, I can at least start my machine up within seconds. Thanks a lot!

IPhone: Stuck on "Waiting for device to connect.."

I just had to reinstall the latest 2.0 build after something trashed my iPod Touch, and now I can no longer install software on it. I get the very non-specific "Waiting for device to become ready in 5 seconds". When that expires, nothing happens.
Any ideas?

Found it: Something in xcode got confused. Rebooting the machine got things talking to each other again.

I own a MacBook Pro 2.4 ghz non unibody. I turn on my laptop for ten seconds and it freezes. It boots perfectly and runs for ten seconds until everything freezes. Please help!

I own a MacBook Pro 2.4 ghz non unibody. I turn on my laptop for ten seconds and it freezes. It boots perfectly and runs for ten seconds until everything freezes. Please help!

See if you can boot into single user mode with Command S.

Hp LaserJet 1200 Generic Class: Waiting for device

I have 2 computers that I want to print to my hp Laserjet 1200 printer. We are using an iogear 4-port usb 2.0 sharing switch. One computer prints fine but the other always displays a message "Generic Class: Waiting for device." Help!

Both computers have the printer driver installed. The usb device does not have a driver to install. You just plug in the usb cords to each computer and the printer. You only install a driver if using a pc operating system.

HP LaserJet 5200 - Yet another "GenericClass: waiting for device" problem

I have an HP LaserJet 5200 that worked until today. I have changed nothing and replaced nothing and now I'm getting the ol' "GenericClass: waiting for device." It worked when I first went to 10.5.4, so that's not the issue. The connection obviously works because the computer recognizes the printer. I've deleted and reinstalled everything under the sun related to printing to no avail.
Any ideas? I'm hoping I don't have a $2000 paper weight.
Thanks in advance
Message was edited by: Wesley Johnson

Several Leopard users are reporting that HP printers no longer work with USB-parallel adapter cables. I don't know why.
The best solution is to put the printer on the network, either by buying the jetdirect card that fits that model (on eBay), or by buying a used parallel port print server.

Boot: "Waiting 10 seconds for device" - mkinitcpio doesnt fix

Similar Messages

Maybe you are looking for