[Solved] Bootup hangs

Several months ago I installed a 32-bit version of Arch on my MacBookPro (5.1, late 2008) in dual boot with Mac OS X 10.7 (Lion).
After experiencing some troubles, I decided of moving to a (fresh) installation of the 64-bit version.
I was able of booting the Linux kernel directly from rEFInd, and everything seems to work fine until it gets to:
Reached target Local File Sytems (Pre)
where it hangs, as shown by this picture.
The solution proposed elsewhere in the forum (eg, here, that is where the pic came from!) is to set the "nomodeset" kernel parameter.
This solution, however, did not work for me
Does anyone have any other suggestion?
Thank in advance for any help I can get
Alessia
***EDIT***
After some reboots I found two further problems, and to fix them allowed me to step further.
Specifically (perhaps it will be useful to someone!), the first problem was:
A start job is running for dev-disk-by/<some.letters.and.numebers>.device
where <some.letters.and.numebers>.device is '/home' (/dev/sda7). I fixed this by changing its entry in /etc/fstab as:
# /dev/sda7 LABEL=home
UUID=1283ab07-03cc-4fee-b5e3-913533ac2ec9 /home ext4 rw,relatime,data=ordered,noauto,x-systemd.automount 0 2
The second problem was:
ERROR: Firmware file "b43/ucode16_mimo.fw" not found
ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
That I fixed by installing the b43-firmware from AUR.
Now bootup hangs at "Reached target bluetooth": after this nothing happens (I waited for about 5 minutes)
Does anyone have any idea?
Thank again for any help
Some background:
/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda5
UUID=8348e061-f4c5-4185-83ba-3b4e7f0a053d / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=77a90775-c12e-41c0-8aaf-b9c4959d1e40 /boot ext4 rw,relatime,data=ordered 0 2
# /dev/sda6
UUID=6f65b8a6-68bb-41bd-b1c5-c600089fe681 /var ext4 rw,relatime,data=ordered 0 2
# /dev/sda7 LABEL=home
UUID=1283ab07-03cc-4fee-b5e3-913533ac2ec9 /home ext4 rw,relatime,data=ordered 0 2
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 200M 0 part
├─sda2 8:2 0 95.3G 0 part
├─sda3 8:3 0 619.9M 0 part
├─sda4 8:4 0 95M 0 part /boot
├─sda5 8:5 0 19.1G 0 part /
├─sda6 8:6 0 11.5G 0 part /var
└─sda7 8:7 0 103.5G 0 part /home
refind_linux.config
"Boot with standard options" "ro root=UUID=8348e061-f4c5-4185-83ba-3b4e7f0a053d
PARTUUID=8dce1cec-49ad-4bf1-9df2-4530816bd69b nomodeset "
"Boot to single-user mode" "ro root=UUID=8348e061-f4c5-4185-83ba-3b4e7f0a053d
PARTUUID=8dce1cec-49ad-4bf1-9df2-4530816bd69b nomodeset single"
"Boot with minimal options" "ro root=UUID=8348e061-f4c5-4185-83ba-3b4e7f0a053d
PARTUUID=8dce1cec-49ad-4bf1-9df2-4530816bd69b nomodeset"
Last edited by alesssia (2013-07-28 16:32:55)

When it says the thing about bluetooth, are you sure that it is not just printing messages after giving you a login prompt?  Systemd is a bit too fast for itself.  So sometimes people get confused because the system is able to give you a login prompt before all the bootup stuff has completed.  So unless you have "quiet" in your kernel command line, it will continue to print the messages like you have told it to.  But unfortunately, it will do this on top of (or rather after) the login prompt is reached.
When you think it has frozen after reaching the bluetooth.target, try hitting <enter> and see if the login prompt shows up for you.

Similar Messages

  • [SOLVED]Arch hangs on startup, unable to find root device Mac

    For posterity, I'm editing the post with how I solved both issues.
    Hi All,
    I'm trying to dual boot Arch and Mac 10.4.11 on an old 32 bit MacbookPro1,1. I did the following:
    1) Partitioned Drive with an EFI partition, Mac partition, root partition, home partition, and swap partition
    2) Installed Mac to its respective partition
    3) Installed rEFInd to the ESP
    4) Confirmed the rEFInd was able to boot Mac
    5) Installed Arch to the root partition and mounted the separate /home and swap partitions
    6) Followed the beginners guide for the rest of the installation
    7) Did NOT install a bootloader
    - I am just using rEFInd to boot Arch; I installed Ubuntu in a similar fashion on my other (2013) MBP. I didn't create a mount point for /boot, did not install GRUB, and it works perfectly
    8) Rebooted. Selected the Arch installation from the rEFInd menu, it launched, and shortly after I am presented with this message:
    ERROR: device 'UUID=142bf...777' not found. Skipping fsck.
    ERROR: Unable to find root device 'UUID=142bf...777'.
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    sh: can't access tty: job control turned off
    [rootfs /]#
    I then booted to the live cd to try and do some noob detective work:
    # mkdir /mnt/arch
    # mount /dev/sda3 /mnt/arch
    # cat /mnt/arch/etc/fstab
    # cat /mnt/arch/etc/mkinitcpio.conf # my searching suggested the HOOKS might be the issue
    HOOKS="base udev autodetect modconf block filestystems keyboard fsck"
    Here is the output of /etc/fstab
    I am including the outputs of
    # lsblk
    # fdisk -l /dev/sda
    # blkid
    as a photo.
    EDIT:
    I was able to use rEFInd's line editor to boot with the fallback image. Everything went well for the first five seconds and I got past the previously mentioned failure. However, it is now stuck at
    [ OK ] Started Rebuild Hardware Database
    I booted again, and it froze at:
    [ OK ] Started udev Kernel Device Manager.
    I did this a few more times and it froze at:
    [ OK ] Reached Target Swap.
    [ OK ] Reached Target Sound Card.
    and
    [ OK ] Started Flush Journal to Persistent Storage.
    Why is it freezing at different points each time I boot (with fallback)?
    EDIT 2 [HALF SOLVED]:
    By switching the order of the hooks ( I still have no idea what they do) as per this link, I am now able to boot in normal (not fallback) mode. For the record, here is what I did:
    # mkdir /mnt/arch
    # mount /dev/sda3 /mnt/arch
    # chroot /mnt/arch/ /bin/bash/
    # nano /etc/mkinitcpio.conf # here I put block before autodetect in the hooks line (Why isn't this the default if it prevents the system from booting?)
    # mount -t proc proc /proc
    # mount -t sysfs sys /sys
    # mount -t devtmpfs udev /dev
    # mkinitcpio -p linux
    I then rebooted and it started up, except now it is freezing at various points in the startup sequence like the fallback image did above. What could be causing this issue?
    EDIT 3 [SOLVED]
    I don't know why this worked, but after following this advice I am now able to boot into login. Steps:
    1) Select Arch in the rEFInd menu and press F2
    2) Press F2 again to edit the boot parameters
    3) Scan to the end of the line and add
    nomodeset
    after the linux image.
    Last edited by sonarforte (2015-04-25 22:46:22)

    Yes, the UUID displayed in the error message upon bootup is the same as the UUID for /dev/sda3 as found when running blkid which is the same as the UUID for the root partition in /etc/fstab.

  • [SOLVED] X hang * can't kill * kbd/mouse disabled

    Arch newbie.  New install of Arch 2009.02 FTP i686 on test hardware that successfully runs many Linux distros (Ubuntu Intrepid & all previous, Mepis, Fedora, Puppy, SliTaz, DSL, and many more.)
    Followed Install Guide and Beginner's Guide.  All is well until I get to X.
    I did not install libgl because I shouldn't need 3D for this old box.  Installed xorg & mesa (not sure if needed).  Did "lspci | grep VGA" and got "VGA compatible controller: 3Dfx Interactive, Inc. Voodoo Banshee (rev 03)"
    Copied over working xorg.conf from another distro on same box.  No video driver in xorg.conf.  Wasn't sure if correct driver was xf86-video-voodoo.  Wrong.  Tried xf86-video-tdfx.  Appeared to be correct.  Tried xterm test, got white xterm box & prompt, but kbd & mouse inoperative.  Couldn't kill X.
    Removed ...tdfx and ...vesa drivers & did fresh install of ...vesa.  Ran "Xorg-configure" followed by "X -config /root/xorg.conf.new"  Still hangs and can't kill X.
    Checked the Xorg.0.logs (saved from several attempts).  Keep getting
    (WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
    (WW) Disabling Mouse0
    (WW) Disabling Keyboard0
    Googled for - "xorg hang 'AllowEmptyInput is on'"  Found a few mentions, including one on Arch bbs, but they were very heavy going and I don't understand them.  Not having a kbd appears to be the reason I can't kill X.
    One (EE) error --
    (WW) Warning, couldn't open module freetype
    (II) UnloadModule: "freetype"
    (EE) Failed to load module "freetype" (module does not exist, 0)
    (II) LoadModule: "vesa"
    Can anyone suggest an approach to debugging these issues?
    Last edited by secdroid (2009-04-12 18:00:25)

    Appreciate the help.  Here's what I did --
    --- pacman -S xf86-input-evdev
    --- pacman -S xf86-video-tdfx   #(note: re-install)
    --- Added hal to DAEMONS section of rc.conf   #(note: hal starts dbus)
    --- Since default is US kbd, I didn't need to do any of the config steps in "Configuration section of http://wiki.archlinux.org/index.php/Xor … us_in_Arch
    X now started and stopped normally.  Did "Simple Baseline X Test" (xterm) successfully. 
    Did pacman -S lxde and tried to start X.  Failed because fam was not running.  Added fam to DAEMONS and I now have a working LXDE.  Still needs tweaks, of course, but I'm up!
    FWIW, "freetype" doesn't appear to be in xorg.conf.  Since it appears to be a non-critical "(EE)" X error, I'll pursue it later.
    Suggestions for "Beginners Guide" --
    --- Beginners really need pointer to http://wiki.archlinux.org/index.php/Xor … us_in_Arch in case of X start failures
    --- LXDE section is extremely weak compared to Arch wiki resources.  Suggest replacing current Beginners Guide LXDE materials with pointers to http://wiki.archlinux.org/index.php/LXDE and http://wiki.lxde.org/en/Main_Page
    Moderator: Please tag this thread as [SOLVED]  I would, if I knew how.

  • [SOLVED] sshfs - Hangs at different occations (reboot needed?)

    I'm using Thunar with gvfs and sshfs, both works fine and does the job.
    Only problem is that for some reason, sshfs when going back to a folder after a while (that's bookmarked if that matters) nothing happens, and if i try to "unmount" the remote filesystem it hangs thunar.
    I'm not quite sure which mount point to unmount so i usually go full out noob and reboot.
    But here's my mount:
    proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
    sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
    dev on /dev type devtmpfs (rw,nosuid,relatime,size=8194272k,nr_inodes=2048568,mode=755)
    run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
    /dev/sda2 on / type reiserfs (rw,relatime)
    securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
    tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
    cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
    pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
    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)
    systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
    tmpfs on /tmp type tmpfs (rw)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    configfs on /sys/kernel/config type configfs (rw,relatime)
    mqueue on /dev/mqueue type mqueue (rw,relatime)
    hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
    /dev/sda3 on /home type reiserfs (rw,relatime)
    fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
    gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=0)
    Last edited by Torxed (2013-08-15 18:30:02)

    Bha solved it (after living with it for weeks)...
    ps aux | grep ssh
    Just looked for anything suspicious and:
    ssh -oForwardX11 no -oForwardAgent no -oClearAllForwardings yes -oProtocol 2 -oNoHostAuthenticationForLocalhost yes -l user -s host sftp
    Just killed the correct pid.

  • [Solved] Bootup Freezes

    Hi all, been using Gentoo for a very long time and now I'm starting to transition to Arch. Loving it quite a lot.
    I have a problem on a new install I'm doing on my ancient Macbook Pro.
    I got everything setup with rEFInd and grub seems to be working ok.
    I get to the bootup chooser in grub and choose the Arch Linux option (I went in and took off the quiet option for this screenshot)
    It seems to be working ok until it gets to 'Reached target Local File Sytems (Pre)' and then it just hangs.
    I have my hdd setup as
    /dev/sda1 is the /boot/efi partition
    /dev/sda2 is the /boot/ partition
    /dev/sda3 is the swap partition.
    /dev/sda4 is the / partition.
    I have tried reinstalling systemd, mkinitcpio, and the kernel. I found something online that said to add 'ahci sd_mod' to the modules in mkinitcpio.conf but it didn't seem to help.
    Any ideas?
    https://i.imgur.com/lbWwvPL.jpg
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
    --edit My bad, thanks for just editing.
    Last edited by orthanc (2013-06-19 02:41:27)

    Yes it is an older Macbook Pro (april 2008). Yes I have read that I can use rEFInd to go directly to the kernel, but it took me ~12 hours just to get a working bootloader setup this far. It may not be pretty but it works so I'm not super worried about that.
    So I commented out a couple of lines in fstab and that seems to have helped
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda4
    UUID=e13b58db-f9bb-422c-b550-2bc6090414db / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda2
    # UUID=06bc77ab-578f-4e74-bd7c-1c70d8f019fc /boot ext2 rw,relatime 0 2
    # /dev/sda1
    # UUID=0D05-830A /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda3
    UUID=d25948a3-a1b2-4dc1-abd2-813f61290c98 none swap defaults 0 0
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 0 232.9G 0 disk
    ├─sda1 8:1 0 200M 0 part
    ├─sda2 8:2 0 100M 0 part
    ├─sda3 8:3 0 2G 0 part
    └─sda4 8:4 0 230.6G 0 part /
    sr0 11:0 1 523M 0 rom
    loop0 7:0 0 226.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
    Now it seems to hang at "Started Trigger Flushing of Journal to Persistent Storage"
    One time it got past there to where it complains I don't have the firmware for my b43 wireless card and froze there, but now it seems to stop at this point every time.
    https://i.imgur.com/2QYSOUh.jpg
    Last edited by orthanc (2013-06-18 04:43:19)

  • [SOLVED]Boot hang after recent updating issues

    I am having issues after the last update. First, I made a mistake of holding back the filesystem package. Because of this (at least I think so) I was having an error that said it could not boot because at boot it said "/sbin/init does not exist". I solved this by upgrading the filesystem package by chrooting from a live arch usb. Now I am having an issue where my system hangs at boot, I believe it is right after systemd runs fsck although I might be wrong. But after maybe 5 minutes it just starts as usual... my ususal boot time is less than a minute. What should I do?
    This is from a thread i accidentally hijacked:
    cfr wrote:
    Try systemctl --failed and or examine the journal for clues.
    Post fstab. Are all of the disks referred to there available when you boot? If systemd can't find them, it will basically wait until it times out and I think that's about 5 minutes and then it will continue booting (assuming it isn't missing anything critical, of course).
    My fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda6
    UUID=5dc84b70-a9f9-42eb-981c-40e84f7e9e75 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda6
    UUID=5dc84b70-a9f9-42eb-981c-40e84f7e9e75 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda5
    UUID=f7bccd4f-4b47-4dbb-a8f8-d8e374bb9867 /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda7
    UUID=07dcd099-50c4-4c35-a102-10a39b74ac0b none swap defaults 0 0
    Would deleting the second /dev/sda6 fix it?
    Last edited by life_enjoyer (2013-06-10 20:24:14)

    Thanks jasonwryan So my exact boot time was 1 minute and 34.151 seconds (which is not unbearable but like i said it used to be in a matter of seconds)... The kernel took  2.790 seconds and userspace took 1 minute and 31.361 Output of systemd-analyze blame :
    922ms systemd-logind.service
    832ms systemd-modules-load.service
    774ms systemd-fsck@dev-disk-by\x2duuid-f7bccd4f\x2d4b47\x2d4dbb\x2da8f8\x2dd8e374bb9867.service
    614ms udisks2.service
    545ms dev-mqueue.mount
    509ms sys-kernel-debug.mount
    499ms dev-hugepages.mount
    499ms systemd-udev-trigger.service
    497ms systemd-vconsole-setup.service
    478ms systemd-remount-fs.service
    477ms tmp.mount
    439ms systemd-tmpfiles-setup-dev.service
    365ms dhcpcd.service
    218ms temp-links-catalyst.service
    192ms upower.service
    169ms polkit.service
    165ms systemd-journal-flush.service
    151ms systemd-sysctl.service
    149ms systemd-udevd.service
    113ms systemd-update-utmp.service
    105ms gpm.service
    68ms home.mount
    68ms systemd-tmpfiles-setup.service
    57ms systemd-random-seed-load.service
    30ms systemd-user-sessions.service
    1ms sys-kernel-config.mount
    Now maybe I am wrong, but these don't add up to 1 min 31 seconds...It actually adds to about 9 seconds which is probably my old boot time.. What am I missing here?
    Last edited by life_enjoyer (2013-06-09 03:36:53)

  • [Solved] pacman hangs in step "resolving dependencies"

    Hi, Today i tried to update my system with pacman -Syu, however it hangs in the process of searching file conflicts. I read this thread https://bbs.archlinux.org/viewtopic.php?id=179638 tand followed the suggestions, it didn't worked.
    Here i  post SOME of the output of pacman -Syu --debug
    debug: checkdeps: package tea-37.2.0-1
    debug: checkdeps: package tzdata-2014b-1
    debug: checkdeps: package util-linux-2.24.1-4
    debug: checkdeps: package vde2-2.3.2-6
    debug: checkdeps: package vim-runtime-7.4.214-1
    debug: checkdeps: package vim-7.4.214-1
    debug: checkdeps: package virtualbox-host-dkms-4.3.10-1
    debug: checkdeps: package virtualbox-4.3.10-1
    debug: checkdeps: package virtualbox-sdk-4.3.10-1
    debug: checkdeps: package vlc-2.1.4-2
    debug: checkdeps: package xbmc-12.3-14
    debug: checkdeps: package xcb-proto-1.10-2
    debug: checkdeps: package xorg-util-macros-1.19.0-1
    debug: checkdeps: package xorg-xrandr-1.4.2-
    Getting to xorg-xrandr package pacman hangs, however i dont think it is related with the xorg-xrandr package since i try to reinstall pacman with:
    pacman -S pacman  --debug
    getting the following output:
    debug: looking for conflicts
    debug: check targets vs targets
    debug: check targets vs targets
    debug: check targets vs db and db vs targets
    debug: check targets vs db
    debug: check db vs targets
    debug: checking dependencies
    debug: checkdeps: package pacman-4.1.2-
    I have not any NFS or Samba storage mounted or configured, just one local disk. However i have just grown my root partition from 32 to 100 GB, using gparted in livecd since my arch partition became full, so i think this issue has something to do with that.
    Any ideas??
    Last edited by hydrosIII (2014-04-10 05:45:14)

    I solved the problem, it turned out to be my fault. Before i grew the partition i had another partition mounted in /var/cache/pacman to hold the pacman packages. I erased it to grow my root partition over it but i forgot to erase the entry in the fstab file, so the system was trying to mount the partition but it didnt exist anymore. The result was a broken mount, that was making pacman hang, since it searched for the files in /var/cache/pacman.
    Silly me!

  • [SOLVED] Virtualbox hangs the host computer

    Hi all,
    It's been some time since I experience this annoying bug :
    Virtualbox completely hangs my computer whenever I click on the "configuration" for any virtual machine.
    Even the magic sysreqs keys are not able to recover (they are enabled in /etc/sysctl.conf) , I'm obliged to hard reboot my machine
    However, I can go into other menus in the GUI without problems. VMs work ok as well.
    My host system :
    3.7.8-1-ARCH #1 SMP PREEMPT Fri Feb 15 03:39:05 EET 2013 x86_64 GNU/Linux
    virtualbox 4.2.6-1
    virtualbox-host-modules 4.2.6-6
    no proprietary extension pack.
    (kernel was upgraded today and the computer rebooted, virtualbox-host-modules were updated as well)
    Using KDE 4.10
    Nvidia integrated graphics (xf86-video-nouveau 1.0.6-1)
    Thanks for any help on how to overcome this bug!
    Last edited by fredo696 (2013-02-16 13:03:13)

    Problem seems to be solved.
    All I did was to click "remove all the warnings" in the Help menu, and remove some older VM files which might have been corrupt.

  • [DIS-SOLVED] Sudo hangs after a few uses

    I've been searching around for this for some time, but haven't found any enlightenment yet.
    Basically, after rebooting I can use sudo a few times (usually 3) successfully. After that, any sudo command just hangs. Interestingly, "sudo -k" still returns normally, but "sudo -v" hangs. It is worth noting that sudo gets as far as prompting me for my password before hanging.
    Background - possibly useful:
    I've had arch running for a few months now, and this just started happening yesterday, when I left my machine running overnight doing a large dd to an external drive as described here: https://wiki.archlinux.org/index.php/Di … _hard_disk . I woke up, found that the i/o was all finished (I could tell because I was using pv to monitor it), but the command ( which was "sudo dd if=/dev/sda conv=sync,noerror bs=32M | pv -pbert | gzip -c > /run/media/jimbo/Backup2/sda_82513.img.gz") hadn't returned and wasn't responding to SIGINTs. The hanging behavior started here, and I wasn't able to kill the process or unmount my external cleanly. I'm not sure exactly what I did then, but I'm pretty sure I just hard-rebooted my machine, and I've been seeing this behavior ever since.
    Any pointers or advice would be greatly appreciated. I'll post any config files you guys are interested in, with PII redacted.
    Last edited by jmagnare (2013-08-30 21:05:05)

    Thanks for the warm welcome! I'm having a blast using arch so far.
    So I restored from the dd that I had done, and things are working fine now. I'm not sure what I should do with this thread: should I mark it solved? I didn't actually discover the cause of the problem, so that doesn't seem right.
    To answer your questions:
    1. I may have had one of the partitions on sda mounted. Is this likely to have caused what I saw?
    2. pv, which I just discovered, allows you to see the progress of data through a pipeline. It's pretty neat. The p, b, e, r, and t flags should turn on the progress bar, byte counter, ETA timer, rate counter, and timer, respectively. After looking at the man page, it appears that this is actually the default behavior. So I could have just used pv with no options.
    Last edited by jmagnare (2013-08-29 17:03:00)

  • [SOLVED*] system hangs at startup after grub screen

    My system is hanged after the grub window. I choose Archlinux, like always, apparently starts to boot and the next screen is frozen. It says:
    /dev/sda2: recovering journal
    /dev/sda2: clean ....
    systemd-fsck[208]: /dev/sda1: recovering transactions file
    systemd-fsck[208]: /dev/sda1: clean ...
    systemd-fsck[221]: /dev/sda4: recovering transactions file
    systemd-fsck[221]: /dev/sda4: clean ...
    And that's it. It frozes in this point. I didn't make any update since 3 days ago. Yesterday the computer runs well.
    I tried to enter into Fallback mode, but I get to the same point.
    Any suggestions?
    Solved partially: I connected a second screen this morning. When I disconnect it, the system starts. Now I have to solve how to add a second screen because when I add it once the system is running, it hangs.
    Last edited by doblerone (2014-03-01 08:32:18)

    Have you looked at any logs whatsoever?
    Edit ::
    doblerone wrote:Solved partially: I connected a second screen this morning. When I disconnect it, the system starts. Now I have to solve how to add a second screen because when I add it once the system is running, it hangs.
    Thats more like you found a work around and is far from being solved
    Last edited by Kartious (2014-03-01 13:46:46)

  • [SOLVED]System Hang in Arch Linux

    I have tried distributions like ubuntu and fedora in hope for finding a stable system . So I move on to Arch Linux
    But this problem also exist on Arch. While using my Arch Linux (including ubuntu and fedora) my system hangs with a black screen with something written on the whole screen which cannot be pasted here as my system hangs and I have to push power button to restart.
    So I check my errors.log file and found these errors
    Jul  8 22:59:24 localhost kernel: [    1.680013] ata3: softreset failed (device not ready)
    Jul  8 22:59:24 localhost kernel: [    7.298612] SP5100 TCO timer: mmio address 0xfec000f0 already in use
    Jul  8 22:59:31 localhost kdm_greet[792]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
    I have a HCL K21 pdc notebook
    Note: In Ubuntu my notebook start with ata1: softreset failed error at boot time
    Most often this error occur while watching videos or listening music with VLC
    Last edited by Manuj19 (2011-07-09 10:13:24)

    ewaller wrote:It might be better to just post the output of lspci -nn  It will tell us a great deal more about the hardware related to the PCI bus, including specific chip set identifiers.
    Thanks for suggestion
    Here is output of lspci -nn
    00:00.0 Host bridge [0600]: ATI Technologies Inc Device [1002:5a31] (rev 01)
    00:01.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a3f]
    00:04.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a36]
    00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
    00:06.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a38]
    00:07.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a39]
    00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
    00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) [1002:4387]
    00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) [1002:4388]
    00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) [1002:4389]
    00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) [1002:438a]
    00:13.4 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) [1002:438b]
    00:13.5 USB Controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386]
    00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 13)
    00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c]
    00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383]
    00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d]
    00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384]
    01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RC410 [Radeon Xpress 200M] [1002:5a62]
    02:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5001 Wireless Network Adapter [168c:001c] (rev 01)
    08:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
    08:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08)
    08:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
    08:01.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 08)
    08:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
    Last edited by Manuj19 (2011-07-09 07:20:08)

  • [SOLVED] boot hangs after system update

    Hi, I upgraded to latest kernel26 and latest udev packages, but unfortunately my system hangs somewhere early at boot, the last lines I see are:
    sd 0:0:0:0: [sda] Attached SCSI disk
    done.
    Waiting 10 seconds for device /dev/disk/by-uuid/7133...
    EXT4-fs (sda3): mounted filesystem with ordered data mode
    mount: proc already mounted
    and after that nothing. No error or anything. I have no idea what's wrong. I tried downgrading my kernel to 2.6.33 and also tried downgrading udev to 251, but with no luck. However with an archlinux-livecd I am able to mount all my drives and chroot to the system.
    Does anyone have an idea, what might be wrong?
    greetings,
    Niclas
    EDIT: I just reinstalled archlinux, no problems so far
    Last edited by Niclas (2010-06-28 16:33:06)

    unfortunately not, I tried removing alsa-utils and also tried setting i915.modeset=0, but error remains. Anyway thanks for your help

  • [SOLVED] kdm hangs for ~20 seconds after entering pw

    Hi there,
    since i made some updates recently kdm hangs for 20 or more seconds after entering the password.
    I already updated font caches with `fc-cache -fv` but it didn't help.
    Where can I start looking?
    /var/log/kdm.log looks like this, but I honestly don't know what to make of it:
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension Present
    Initializing built-in extension DRI3
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    klauncher(303) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(297)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(297)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) AIGLX: Suspending AIGLX clients for VT switch
    setversion 1.4 failed: Permission denied
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Multiple definitions of the FOUR_LEVEL_KEYPAD key type
    > Earlier definition ignored
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    Thanks for your help!
    vincent
    Last edited by vincent7 (2014-05-16 21:57:27)

    sorry for bringing this up again...
    In the meantime I switched from KDE to MATE Desktop, using LightDM and then sddm as Display Managers. The Problem is still the same: everything is starting and booting fine, it's maybe 15 seconds from pressing the ON switch on my laptop until the Login-Dialog of sddm appears. When I enter my password and hit "Enter" the display manager just waits like 20-30 seconds until somethings happens, and MATE is loaded.
    This only happens on my first login, right after boot. When I logout and login again, it just takes some seconds until the desktop is loaded.
    I looked into "journalctl", but it does not show anything suspicious. It's just a 20-30 second black hole between entries.
    I get the exact same behaviour when I disable the display manager and boot into console login.
    Can someone please help me with that?

  • [SOLVED] Pacman hangs at sync

    Any idea why? I got my rt73 wireless working, and was able to go on the internet with links, but synchronizing with pacman is stuck at 'Synchronizing Package Databases'.
    Is it because pacman is too old and I need to upgrade it first or what?
    Last edited by Firepower (2009-12-17 04:36:40)

    Ok. Just solved it. Had to upgrade pacman. thanks.

  • [SOLVED] Processes hang on __blkdev_get

    Edit: A problem with the DVD reader, probably defective.
    I've edited the post now that I've figured out it's not a problem with the applications themselves. Some programs, ie. XBMC become interruptible when launched, this happens consistently a little while after boot (everything's fine before then).
    Thought it was because one of my disks has a corrupt partition table (btw, can that be rebuilt without losing data?), but physically detaching that drive didn't solve the problem. When looking at the processes, they all show up in Gnome's System Monitor with "Waiting Channel: __blkdev_get" written there, and can't be killed. I tried twice attaching gdb to a process, but it just keeps waiting.
    Trying to google for __blkdev_get didn't turn up any results I could understand much from. This started happening after I replaced a defective motherboard, but the new one seems to be working perfectly fine except for these problems I can't seem to figure out.
    Affected programs: XBMC, gxine, VirtualBox, TestDisk
    Any help would be much appreciated!!
    Old post:
    I have really no idea what's going on, but basically I've had problems with both XBMC and VirtualBox doing absolutely nothing after installing a new motherboard (the previous one was defective, causing all kinds of trouble). Now I have a computer that's running stable, but XBMC just creates unkillable processes without opening, and VirtualBox displays a blank interface. The programs work most of the time right after a reboot, but if I try to launch them twice, they won't run on the second attempt. XBMC has also frozen itself after a short while every time I've got it running.
    No idea what to conclude from this without any idea on where to start debugging. dbus is often unable to restart, no idea if it's related. Sorry for the vague description, but I'm failing to properly understand this myself. Any help would be much appreciated.
    Last edited by eirik (2010-04-25 12:39:52)

    the only thing I can think is that both of those applications have heavy video usage.  I might double check to see that your video driver is setup properly.  The blank interface you are describing with virtualbox really sounds like video driver mismatch with kernel or incompatible version.

Maybe you are looking for