[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).

Similar Messages

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

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)

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.

[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.

[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

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.

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.

Stuck on waiting for device to become ready...

I did a slide show on iDVD now I'm trying to burn it on a Phillips dvd but it reads waiting for device to become ready. this continues & it does not burn the dvd. I tried the save as disk image but the same thing happens. the utility was no help on getting it started

Hi Don't:
Just assuming here (which is always dangerous)...
Is there any audio associated with your slideshow?
Sue
PS Verbatim DVD-R (you are using DVD-R, right?) is about the best there is....

HT4623 I upgraded my iPad 2 and now it keeps locking up. It takes 45 seconds to to unlock the device. When I try to reply to an email it takes 10 to 12 seconds for each letter to appear.

I have recently upgraded my iPad 2 to iOS7. I am not happy because it is locking up. It takes almost 45 seconds to enter my four digit code. When I type an email it takes 10 to 12 seconds for the letters to appear.

Resetting your settings
You can also try resetting all settings. Settings>General>Reset>Reset All Settings. You will have to enter all of your device settings again.... All of the settings in the settings app will have to be re-entered. You won't lose any data, but it takes time to enter all of the settings again.
Resetting your device
Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears. Apple recommends this only if you are unable to restart it.
Or if this doesn't work and nobody else on the blog doesn't have a better idea you can contact Apple.
Here is a link to their contacts with most of the information below.
http://www.apple.com/contact/

Is it possible to wait longer for USB with mkinitcpio-solved

Hi,
I recently installed from an arch0.7.2-base CD, but can't boot after the mkiniticpio upgrade, including with the kernel26-fallback.img.
My root partiition is on a USB hard-drive, and it seems like the drive isn't being detected in time.
With mkinitrd I could specify a delay to wait for USB devices to settle, but there doesn't appear to be anything similar in mkinitcpio, is there?
This may not be the problem at all, of course, but on one occasion when I booted with break=y, just after the message about break requested, there is no ls binary etc.,
usb2-4: new fullspeed USB device using OHCI_HCD address 2
came up, which looked like it had found the USB device, but too late.
(This is after it says it failed to detect the filesytem type etc.)
When I do break=y and echo /dev/*, my hda devices are there, but there are no sda devices, just a series of usbdev files (e.g. usbdev1.1_ep00 ). Is that normal?
Sorry for posting yet another mkinitcpio question.
Any suggestions would be greatly appreciated. Let me know if there's any other output I should post.
Thanks,
Fishonadish

Update:
I'm fairly certain the lack of wait time for USB is the problem now.
I can now boot into arch fine provided I use break=y.
I get the messages about about not finding the root device then the break requested section then, after the ramfs$ prompt appears I get
SCSI device sda: [number] 512-byte hdwr sectors [number] MB
and so on...
and when I type exit at the prompt it boots fine.
To get this far I rebuilt the kernel26.img with the following in mkinitcpio.conf:
MODULES="usb-storage ext3"
HOOKS="base udev autodetect usb filesystems"
(Not sure about this, but it seems putting usb-storage in modules got me this far?)
I still need to get it to delay for USB for a bit longer so I don't have to type 'exit' at the ramfs prompt every time I want to boot, or is it some other problem?
If this has been dealt with before, then sorry for the repetition, but I can't find anything covering it elsewhere.
Thanks.
Fishonadish

"Waiting for device to become ready" can't burn additional copies

I created an iMovie and burned about six copies on iDVD. When i went to put in the seventh disk it sort of froze up with the "Waiting for device to become ready" message never going away. I attempted to shut everything down, even turned the computer off for awhile thinking maybe it was overheated but several hours later its doing the same thing. It will burn the first copy but get hung up when attempting to burn additional ones. Any suggestions???

It's often recommended areound here to let the optical drive cool down after burning 3-4 disks in a row.
See if you can burn any kind of disk via the Finder to make sure the drive is OK. Also I suggest you follow this workflow for future projects:
Once you have the project as you want it save it as a disk image via the File ➙ Save as Disk Image menu option. This will separate the encoding process from the burn process.
To check the encoding mount the disk image and launch DVD Player and play it. If it plays OK with DVD Player the encoding was good.
Then burn to disk with Disk Utility or Toast at the slowest speed available (2x-4x) to assure the best burn quality. Always use top quality media: Verbatim, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
The save as disk image as mishmumken recommended will save you from having to reencode the project if you want to burn another copy at a later date. It also lets you verify the encoding process before committing the project to disk.
OT

[SOLVED] Waiting 10 seconds for device...

Similar Messages

Maybe you are looking for