[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

Similar Messages

  • O/S Message: Inappropriate ioctl for device

    Hi everyone,
    In a shell (sh) script, on Solaris 5.9, the following is being done:
    sqlplus /nolog <<EOF
    whenever oserror exit 1
    whenever sqlerror exit 1
    connect DBUSER/DBPASSWORD
    select * from sometable;
    EOF
    This produces the following output and exits with return value 1:
    SQL*Plus: Release 9.2.0.8.0 - Production on Wed Feb 13 04:21:40 2008
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    SQL> SQL> SQL> O/S Message: Inappropriate ioctl for device
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.8.0 - Production
    The same happens when the above is being pasted in a bash session.
    When doing it line by line in an sqlplus session, everything is fine.
    Additional data:
    # uname -a
    SunOS kpn-sup-smp 5.9 Generic_117171-07 sun4u sparc SUNW,UltraAX-i2
    SQL> select * from v$version;
    BANNER
    Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
    PL/SQL Release 9.2.0.8.0 - Production
    CORE 9.2.0.8.0 Production
    TNS for Solaris: Version 9.2.0.8.0 - Production
    NLSRTL Version 9.2.0.8.0 - Production
    # opatch lsinventory
    [ ... prolog cut ... ]
    Installed Patch List:
    =====================
    1) Patch 5606601 applied on Tue Feb 12 03:36:14 CET 2008
    [ Base Bug(s): 5606601  ]
    2) Patch 5495695 applied on Tue Feb 12 03:33:37 CET 2008
    [ Base Bug(s): 5495695  ]
    3) Patch 4008133 applied on Tue Feb 12 03:30:01 CET 2008
    [ Base Bug(s): 4008133  ]
    Any ideas ...? TIA.
    Cheers,
    Benjamin.

    I just came across this issue after upgrading from 9.2.0.6 to 9.2.0.8:
    It appears that putting "connect" as the first line resolves the problem.
    i.e.:
    sqlplus /nolog <<EOF
    connect DBUSER/DBPASSWORD
    whenever oserror exit 1
    whenever sqlerror exit 1
    select * from sometable;
    EOF
    Kind regards
    Christos

  • [Solved]Boot from USB HDD - Root device doesn't exist. Major/minor

    My problem is that the kernel seems (or starts) to load, but then I get an error:
    Root device 'UUID=1234 . . .' doesn't exist.
    Attempting to create it.
    ERROR: Unable to determine major/minor number of root device "UUID=1234 . . .'
    You are being dropped into recovery shell
    I found a few links on the web and in the forums, but nothing that really solved it for me. The solved ones usually downgraded the kernel.  I haven't done that yet.  I thought I'd try here first.
    I have a 320GB USB HDD that I have been using to experiment with different linux distros.  I have a few working successfully (OpenSUSE,Mint,Ubuntu,Debian,Fedora,etc).  I'm very new at this but have been reading a lot and putting a lot of time into it.  I have legacy grub loaded on the MBR and use the menu.lst on my openSUSE partition to boot everything.  Because the partitions for some of the distros are so far into the disk I needed to create directories on openSUSE's /boot directory to contain the kernel and initrramfs files (like /boot/fedora).  This seems to work for the other distros.  I did the same thing for Arch.
    So when I installed Arch I haven't used the bootloader section of the installation.
    I'm using the 2011.08.09-netinstall-i686.iso Live CD.
    I tried a few things including:
    1.    changing the HOOKS in /etc/mkinitcpio.conf
        a.    adding usb to the "HOOKS"
        b.    removing and adding autodetect
        c.    adding and removing "sata_sil" (although I'm not even sure if my device uses it)
    2.    changing the kernel line:
        a.    from using "UUID=" to (hd0,1) to sdb1.
        b.    added rootdelay=8
    3.    repartition all of my arch partitions using cfdisk from my Live CD and reinstall. I used gparted on OpenSUSE to do it the first time.
    This may be connected. When I fdisk -l from the Arch Live CD I get extra data and an error for each of my arch partitions (and only my arch partitions):
    Disk does't contain a valid partition table
    When I fdisk -l from OpenSUSE I don't get the data paragraphs or errors about the arch partitions?
    Here is my /etc/fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    UUID=0e7556ef-b832-43e9-a8ba-c68dd2cd6143 /var reiserfs defaults 0 1
    UUID=510bb601-13c1-46ec-87c0-a800dd2efb8b / ext4 defaults 0 1
    UUID=cd78ab04-742d-4ba5-9727-90727de2dd14 swap swap defaults 0 0
    UUID=dc5685e3-35b0-46d4-b259-61f2530ff36a /home ext3 defaults 0 1
    And my HOOKS:
    HOOKS="base udev autodetect pata scsi sata usb filesystems usbinput"
    And my menu.lst:
    1
    default 0
    timeout 32
    gfxmenu (hd0,1)/boot/message
    ###openSUSE on sda2 - legacy grub
    title openSUSE 11.4 - Celadon - gnome
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.7-default root=/dev/disk/by-id/usb-Seagate_FreeAgent_GoFlex_NA0E702X-0:0-part2 resume=/dev/disk/by-id/usb-Seagate_FreeAgent_GoFlex_NA0E702X-0:0-part1 splash=silent quiet showopts nomodeset vga=0x314
    initrd /boot/initrd-2.6.37.6-0.7-default
    ###openSUSE failsafe on sda2 - legacy grub
    title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.7
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.7-default root=/dev/disk/by-id/usb-Seagate_FreeAgent_GoFlex_NA0E702X-0:0-part2 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314
    initrd /boot/initrd-2.6.37.6-0.7-default
    ###floppy###
    #title Floppy
    # rootnoverify (fd0)
    # chainloader +1
    ###Fedora on sda5 - legacy grub
    title Fedora 15-Lovelock gnome
    root (hd0,4)
    configfile /boot/grub/grub.conf
    ###Mint on sda6 - grub2
    title Mint 9 Lucid Lynx gnome
    root (hd0,5)
    kernel /boot/grub/core.img
    savedefault
    boot
    ###PCLinux on sda7 - legacy grub
    title PCLinuxOS 2011.6 KDE
    root (hd0,6)
    chainloader +1
    ###Ubuntu on sda8 - grub2
    title Ubuntu 10.04.2 gnome
    root (hd0,7)
    kernel /boot/grub/core.img
    savedefault
    boot
    ####arch on sda10 - legacy grub
    title ARCH
    root (hd0,1)
    #root UUID=XXXXXXXXXX44c5a3cd-dcb5-4cf1-933e-7a8ebac2a992
    kernel /boot/arch/vmlinuz-linux root=UUID=510bb601-13c1-46ec-87c0-a800dd2efb8b ro rootdelay=8
    #kernel /boot/arch/vmlinuz-linux root=(hd0,9)
    #kernel /boot/arch/vmlinuz-linux root=/dev/sda10
    initrd /boot/arch/initramfs-linux.img
    savedefault
    boot
    ###Debian on sda11 - grub2
    title Debian 6.0.2.1 squeeze gnome
    root (hd0,1)
    kernel /boot/debian/vmlinuz-2.6.32-5-686 root=UUID=2b6052e2-ecdf-4796-81c8-b9e9142ca159 ro
    initrd /boot/debian/initrd.img-2.6.32-5-686
    savedefault
    boot
    ###Mandriva on sda12 - legacy grub
    title Mandriva 2011 KDE
    root (hd0,1)
    kernel /boot/mandriva/vmlinuz-2.6.38.7-desktop-1mnb2 root=UUID=5033f7fb-cac7-4db5-920c-c8bd2b51365f ro
    initrd /boot/mandriva/initramfs-2.6.38.7-desktop-1mnb2.img
    savedefault
    boot
    Here is my fdisk -l from OpenSUSE.  I'm not quite swift enough to mount the hard drive and use the script utility from the Live CD yet, at least not tonight:
    Disk /dev/sda: 320.1 GB, 320072932864 bytes
    255 heads, 63 sectors/track, 38913 cylinders, total 625142447 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000c3bbb
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 4208639 2103296 82 Linux swap / Solaris
    /dev/sda2 4208640 46153727 20972544 83 Linux
    /dev/sda3 46153728 87113727 20480000 83 Linux
    /dev/sda4 87115770 614031755 263457993 5 Extended
    /dev/sda5 87115776 128075775 20480000 83 Linux
    /dev/sda6 128077824 169037823 20480000 83 Linux
    /dev/sda7 169039872 209999871 20480000 83 Linux
    /dev/sda8 210001920 250961919 20480000 83 Linux
    /dev/sda9 250963968 291923967 20480000 83 Linux
    /dev/sda10 291924031 332886015 20480992+ 83 Linux
    /dev/sda11 332888064 373848063 20480000 83 Linux
    /dev/sda12 373848678 414992383 20571853 83 Linux
    /dev/sda13 414994432 435474431 10240000 83 Linux
    /dev/sda14 435474495 455956829 10241167+ 83 Linux
    /dev/sda15 455958528 578881535 61461504 b W95 FAT32
    /dev/sda16 578881599 614031755 17575078+ 83 Linux
    Disk /dev/sdb: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x95aa95aa
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 63 294889139 147444538+ 7 HPFS/NTFS/exFAT
    /dev/sdb2 294889140 312576704 8843782+ 7 HPFS/NTFS/exFAT
    That's it for now.
    Last edited by newbie55 (2011-09-23 22:19:58)

    I'm IN!  Thanks everyone for your suggestions!
    The arch system didn't like the identifier I was using for the root partition. By looking at the /dev/disk/by-id while the arch system was running, I could see what the system wanted me to call the partition.  So after the system error'd-out and I was in the recovery shell at the [ramfs /] prompt:
    # ls -lF /dev/disk/by-id > by-id.txt
    # vi by-id.txt
    I could have used any of the identifiers listed in the by-id (there were 3), by-uuid(1), by-label(1) or by path(1). I tried them all. I had to write these down by hand because it is a ram filesystem.
    The article that finally got me there is:
    https://wiki.archlinux.org/index.php/Pe … ice_naming
    Anyway my openSUSE grub menu.lst ended up like this:
    ####arch on sda10 - legacy grub
    title ARCH
    root (hd0,1)
    kernel /boot/arch/vmlinuz-linux root=/dev/disk/by-uuid/510bb601-13c1-46ec-87c0-a800dd2efb8b ro rootdelay=8 rootfstype=ext4
    initrd /boot/arch/initramfs-linux.img
    savedefault
    boot
    It's easy once you: 1. beat your head against the wall
                        2. read further
                3. repeat 1 and 2
    Back to the "Beginner's Guide",4 Post-Installation.  Yikes!

  • SPA303 Message Waiting Indicator for specific line only

    I have an SPA303 configured with 2 lines (extensions).
    I want the message waiting indicator to only show for line 2, not line 1.
    I've tried going to Advanced, Voice, Ext1 and setting "Message Waiting" to No
    and for Ext2 setting it to Yes. 
    Hit "Submit All Changes"
    After phone reboots, Ext1 still says Yes, and Ext2 still says No.  I cant seem to change these.
    Is this the correct way to accomplish my request?

    I have no SPA303 here, but it is almost identical hardware and exactly the same firmware (I assume you have the latest) as other SPA[35]0x models. I have no problem to set Message Waiting independently. I can't repeat the behavior you described.
    So either your setting is overwritten by remote provisioning, or it's a complex issue related to overall configuration of phone.
    Can you change setting for one extension only ? Have you provisioning configured ? Can you turn on syslog&debug and capture output ?
    It may or may not help to analyze the issue.
    By the way, wrong forum. Your question have nothing to do with XML application. (Updated: has been moved to the correct one)

  • [SOLVED] Boot message: [ SKIP ] Ordering cycle found, skipping Timers

    During boot I get this message:
    [ SKIP ] Ordering cycle found, skipping Timers
    What does this mean and do I have to do something?
    Last edited by Markus00000 (2014-06-09 10:30:12)

    It seems to have to do with NFS entries in /etc/fstab and a bug in systemd as indicated in this Debian bug report
    Now, excuse me while I go find some brain bleach.  That search result was buried in a bunch of hits on the human reproductive cycle and failures of birth control methods

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

  • 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] 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).

  • 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

  • I have a Laserjet 2550L. When I try to print 2nd time get message "Waiting for printer to become ava

    Laserjet 2550L being used with Mac OSX Lion 10.7.3. After turning on, it will print once. When trying to print a second time I get a message "waiting for printer to become available." I have to turn it off and then back on to get it to print again.

    Hum. Let's uninstall with the 'scrubber option' like this:
    1. Go to Applications/Hewlett Packard/ click on HP Uninstaller and click Continue
    2. Highlight your device on the left pane
    3. Hold the Ctrl, Opt and Cmd keys and click on Uninstall
    4. There will be a pop up that asks if you are sure you want to uninstall ALL hp software. (At this point, if you continue, any HP printers you have installed will need to be reinstalled)
    5. Click Continue and let it finish
    Now, run a Software Update. This can be done by clicking the Apple in the top left of the screen then clicking Software Updates.
     Next, let's reset the printing system:
    Go to System Preferences > Print & Scan
    - Right (or control) click in the rectangle listing your printers and select Reset Printing System.
    WARNING - this will delete ALL of your printers!
    - Select the plus sign to re-add a printer. Select the Default tab on the top of the window. Look for the printer, select it and wait until the "Add" button becomes available. Click it.
    Let me know how this works for you.
    -------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

  • 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

  • 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!

  • 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] [Xorg+KMS+Intel] Can't see login console / boot messages!

    Hi,
    My problem is that using an Intel video card (with KMS) after latest Xorg 1.8 update, I can't see boot messagges and the login console anymore.
    I've just noticed that after last Xorg update I can't access anymore to runlevel 3 on boot.
    I've got an Intel video card so KMS is enabled by default (and mandatory).
    I always used SLiM as a display manager, configured through /etc/inittab to go to runlevel 5 on boot:
    # /etc/inittab
    # Runlevels:
    # 0 Halt
    # 1(S) Single-user
    # 2 Not used
    # 3 Multi-user
    # 4 Not used
    # 5 X11
    # 6 Reboot
    ## Only one of the following two lines can be uncommented!
    # Boot to console
    #id:3:initdefault:
    # Boot to X11
    id:5:initdefault:
    rc::sysinit:/etc/rc.sysinit
    rs:S1:wait:/etc/rc.single
    rm:2345:wait:/etc/rc.multi
    rh:06:wait:/etc/rc.shutdown
    su:S:wait:/sbin/sulogin -p
    # -8 options fixes umlauts problem on login
    c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
    c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
    c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
    c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
    c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
    c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
    # Hypervisor Virtual Console for Xen and KVM
    #h0:2345:respawn:/sbin/agetty -8 38400 hvc0 linux
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    # Example lines for starting a login manager
    #x:5:respawn:/usr/bin/xdm -nodaemon
    #x:5:respawn:/usr/sbin/gdm -nodaemon
    #x:5:respawn:/usr/bin/kdm -nodaemon
    x:5:respawn:/usr/bin/slim >& /dev/null
    To enable runlevel 3 at boot,  I commented the id:5:initdefault: and the x:5:respawn:/usr/bin/slim >& /dev/null lines and uncommented id:3:initdefault:.
    Now, during boot, the last thing I see is Loading UDev modules..., then the screen becomes dark gray and I can't see any other boot messages (actually this appened also before, after xorg update).
    The problem is that before slim started but now I can't see any login console.
    I also figured out that typing my username, password and then startx, starts X normally, so the problem is just that I can't see the tty console anymore.
    Once I am in X I can switch to ttys normally.
    What can I do?
    I just wanted to get rid of slim and start X automatically after console login but I can't see the console login!
    I hope to have been clear enough, thanks for your help!
    Last edited by rent0n (2010-07-04 11:36:38)

    rent0n wrote:
    Well, it seems I spoke too early. It doesn't work as expected at every startup, sometimes I still have the black screen.
    Now I'm trying with:
    video=SVIDEO-1:d
    that seems to work, but I just tested it one time and I'm starting to think that screen blanking happens randomly...
    Any hint is more than welcomed.
    After a few reboots, I can confirm this workaround seems to work.
    This is weird indeed as I don't have any SVIDEO-1 interface listed by xrandr -q, but still.
    Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
    VGA1 disconnected (normal left inverted right x axis y axis)
    LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
    1280x800 60.0*+
    1024x768 60.0
    800x600 60.3 56.2
    640x480 59.9
    TV1 disconnected (normal left inverted right x axis y axis)
    The only problem is that now boot lasts a lot of time  and, between UDev modules loading and disks checking, I have to wait for at least 30 seconds with a black screen and a central white dash flashing.
    Anyone experiencing the same thing?

Maybe you are looking for