[~SOLVED] 1 min hang during boot while mounting xfs partitions (LVM)

Hi all,
After the upgrade I did yesterday (which included linux-3.12.8-1 and lvm2), the boot time has increased by 1 minute as the system hangs while mounting two partitions formatted as xfs and residing on logical volumes.
$ systemd-analyze blame
1min 13.676s home-VDP76-videos.mount
1min 13.111s home-VDP76-VBox_VMs.mount
2.980s [email protected]
I have the fsck hook as second-to-last entry in my mkinitcpio.conf, but the fstab entries for these partitions include
... xfs defaults 0 0
so, as far as I undertstand, the partitions should not be checked, am I missing something!?
I have googled for similar issues but I did not find anything useful, any suggestion would be greatly appreciated.
Thanks
edit: I blame the check disk because of what reported on the system journal (note the time stamps):
Jan 23 00:10:37 ArchTP kernel: psmouse serio5: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
Jan 23 00:10:39 ArchTP kernel: psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
Jan 23 00:10:40 ArchTP kernel: input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio4/serio5/input/input25
Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/VBox_VMs.
Jan 23 00:11:47 ArchTP kernel: XFS (dm-4): Ending clean mount
Jan 23 00:11:47 ArchTP kernel: XFS (dm-3): Ending clean mount
Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/videos.
Jan 23 00:11:47 ArchTP systemd[1]: Starting Local File Systems.
Jan 23 00:11:47 ArchTP systemd[1]: Reached target Local File Systems.
I should also add that the involved partitions are ~20 Gb each and quite full...
edit2: I have freed up almost all space on the video partition and the time for mounting those partitions has now decreased to 8 sec...I will mark the thread as solved, but I still would appreciate an input on the reasons why the partitions are checked regardless of the fstab setting, for example, is this pertinent!?
dumpe2fs -h /dev/mapper/waldorf-video | grep -i 'mount count'
dumpe2fs 1.42.8 (20-Jun-2013)
dumpe2fs: Bad magic number in super-block while trying to open /dev/mapper/waldorf-video
Last edited by VDP76 (2014-01-22 23:38:25)

WonderWoofy wrote:I don't think that the fsck.xfs is really a fsck at all.  It is there for compatibility purposes, and a real check can be done with xfs_check and xfs_repair.  So the fsck.xfs will just always give an exit status of zero.
exactly..in fact the man page says
fsck.xfs(8) wrote:fsck.xfs - do nothing, successfully
so fsck.xfs simply exits with a zero exit status.
running xfs_check gives
xfs_check is deprecated and scheduled for removal in June 2014.
Please use xfs_repair -n <dev> instead.
and xfs_repair does not find errors on both partitions.
Still, I do not understand how nothing being done can take up so much time.
By the way, a short S.M.A.R.T. self-test did not report errors...
In the meanwhile, there has been another kernel upgrade and the timing issue persists, so I am assuming it has something to do with the last lvm2 upgrade.

Similar Messages

  • K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

    Heres the problem...
    My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
    Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
    I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
    I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
    All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
    No phsysical signs of bad caps on the system board.
    I ran ran Memtest86 for 18 hours striaght with no errors.
    Ran CPU stress test with no problems.
    No IRQ,DMA,etc conflicts found.
    Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
    I have tried min install to no avail.
    Bois is retaining its settings (so bios battery is good)
    I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
    I am down to a possible cold solder joint on the system board?
    This problem started to occur about a month ago.
    If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge 
    I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
    Specs..
    Athlon 64 3500+
    2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB)  Ran in Dual config
    Geforce 6800  (BFG 6800 GT oc)
    Creative X-Fi XtremeMusic
    Antec NeoPower 480
    2 WD 36gig SATA Raptors in raid 0 (system partition)
    2 WD 120gig IDE  in raid 0 (data partition)
    Windows XP Pro
    all drivers and bios are manufacture ref and up-to-date.
    Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
    This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
    What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
    So what have we learned class?
    1. check the obvious
    2. do a complete physical inspection of your system
    3. KISS  -- keep it simple stupid

    Is this your ram:
    Quote
    Part Number: PQI3200-1024SB
    Quality Control: Comprehensively and rigorously tested
    Package: 1024MB single pack
    Organization: 128M x 64-bit
    CAS Latency: 3-4-4-8
    Test Voltage: 2.6 V
    PCB Board: 8 Layers PCB
    Heat Spreader: Mirrored Black Copper
    Speed: DDR 400 MHz (PC3200)
    Type: 184-pin DDR SDRAM
    Error Checking: Non-ECC
    Registered/Unbuffered: Unbuffered
    Warranty: Lifetime
    This is a quote from MSI web site:
    Quote
    Main Memory
      • Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
    • Supports the memory size up to 4GB 
    • Supports 2.5v DDR SDRAM DIMM 
    Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
    Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
    For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
    Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
    If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
    Post back results as there are more things one can try but lets start with the simple stuff and work up.

  • Ultra 5 Hangs During Boot

    My Ultra 5 hangs during boot at the following point....
    setting default ipv4 interface......
    I have tried resetting my router, unplugging the network cable, and nothing seems to work.
    John

    jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
    If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
    If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

  • P205-s6237 Hangs during boot to recovery after replace HDD

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

  • Mac Mini keeps hanging during boot

    My ~3 year old Mac Mini keeps freezing during booting with the error message "You need to restart your computer. Hold down the Power button...". This happens every time. Booting in safe mode works.
    This happened with Mac OS X Tiger but keeps happening even after I have completely reformatted that hard disk and reinstalled Leopard from scratch. There are no external devices connected to the computer besides the monitor and a bluetooth mouse and keyboard.
    After reading some discussion forums I have already tried starting into Open Bootware and running "reset-nvram" and "reset-all" but to no avail.

    Welcome to Apple Discussions!
    What you are suffering is a Kernel Panic, and given you have reformatted your drive and reinstalled MacOS, it would tend to suggest the issue is hardware related - most common culprit being RAM.
    http://docs.info.apple.com/article.html?artnum=106227 explains what kernel panics are, and http://www.thexlab.com/faqs/kernelpanics.html and http://www.index-site.com/kernelpanic.html may give some assistance in working through the problem to determine the cause.
    The one good thing is that your system appears sufficiently stable to allow you to boot to the Leopard installer and complete a full install. This makes it less likely there is a fundamental issue with the most expensive component of the system, the logic board.

  • [SOLVED] New installation hangs on boot at two different places

    Hello
    I recently made my another attempt at installing arch on a new desktop build. Previous successful attempts were old laptops.
    I followed the Beginner's Guide on the Arch wiki.
    Currently it stops at one of two places in the boot process:
    1. [ OK ] Found device Samsung_SSD_850_EVO_500GB BOOTARCH
        Starting File System Check on /dev/sdb6…
    2.  [ OK ] Started Journal Service
        [ OK ] Started udev Kernel Device Manager
    I can not consistently recreate either scenario, but it seems to be random which of the two places it stops. Cold boot and CTRL ALT Delete. I doubt that has anything to do with it, but thought I'd add it anyway.
    Current setup:
    Hardware:
    Motherboard - ASUS Z97 Pro (using ethernet adapter and sound on here)
    Processor - Intel 4790K
    Memory - 16 GB
    Graphics - Gigabyte G1 Nvidia GTX 970 SLI x2
    Storage - Samsung 850 SSD 500 GB and WD Black HDD 3 TB
    I've also configured it to use a static IP
    I started this journey by using the live Gparted CD to create partitions. I created two partitions on the SSD. One for windows 8.1 and one for linux. I then created two partitions on the HDD. One for windows, one for linux.
    I installed windows 8.1 first. It divided up the partition I gave it. I am able to run Windows. Once that was done I began installing Arch.
    I used the Feb 2015 ISO from the torrent.
    Current partition scheme for linux:
    sda1 /home
    sda3 /swap
    sda4 /var
    sdb1 /
    sdb6 /boot
    sda is the HDD and sdb is the SSD
    The other partitions not listed are for windows. To boot into windows, I use F8 to choose the windows boot manager partition. It currently defaults to the linux partition.
    During the install, I mounted the root partition first. I then created directories for each of the other partitions and then mounted them. Home, var, and root are all ext4. Boot is FAT32, and Swap is swap.
    I read where I made a couple of mistakes the first attempt on this computer and did a wipe and reinstall again. First mistake was not knowing that /boot needed to be FAT. I then learned that /swap does not need to be in the fstab. I also learned that a FAT partition can not use UUID in the fstab so I took that out and just used /dev/sdb6 instead.
    I have run out of things to search for at this point and need help to continue moving forward.
    Bellow is the current /etc/fstab. It was generated using
    genfstab -U -p /mnt >> /mnt/etc/fstab
    and then edited as noted above
    #/dev/sdb1 LABEL=archroot
    UUID=xxxxxxxxxxxxxxx / ext4 rw,relatime,data=ordered 0 1
    #/dev/sdb6 LABEL=BOOTARCH
    #UUID=xxxxxxxxx
    /dev/sdb6 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda1 LABEL=linux\134x20home
    UUID=xxxxxxxx /home ext4 rw,relatime,data=ordered 0 2
    #/dev/sda4 LABEL=archvar
    UUID=xxxxxxxxxx /var ext4 rw,relatime,data=ordered 0 2
    #/dev/sda3
    #UUID=xxxxxxxxxxxxxx none swap defaults 0 0
    Thanks for any help that can be provided
    Jason
    Last edited by p2ranger (2015-02-14 22:20:14)

    I tried removing gummiboot and installed GRUB2. That didn't work.
    As to the UUID's, I just typed in xxxxx's for the post because I didn't feel like transcribing random letters and numbers.
    So after reading Head_on_a_Stick's suggestion, I redid my partitions and reinstalled arch again following the Beginner's wiki page and using gummiboot
    New Partitions are as follows:
    sda1  /home
    sda3  /swap
    sda4  /var
    sdb1  /
    sdb3  /boot (originally created from windows install)
    Also, I took a screenshot from Gparted of the two disks if there is any info on there that may be of use
    http://cotting.us/gparted-sda.jpg
    http://cotting.us/gparted-sdb.jpg
    Below is the contents and output requested
    arch.conf
    title Arch Linux
    linux /vmlinuz-linux
    initrd /initramfs-linux.img
    options root=/dev/sdb1 rw
    loader.conf
    timeout5
    #default 875966af283d44de9e754c1d68848eab-*
    default arch
    gdisk -l /dev/sda
    GPT fdisk (gdisk) version 0.8.10
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 5860533168 sectors, 2.7 Tib
    Logical sector size: 512 bytes
    Disk identifier (GUID): E11d436B-ED6D-47AD-BCD0-F04384ED50B8
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2925 sectors (1.4 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 45672447 21.8GiB 8300
    2 2871662592 5860532223 1.4 TiB 0700
    3 2854432768 2871662591 8.2 GiB 8200
    4 45672448 285443277 1.3 TiB 8300
    gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 0.8.10
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 5860533168 sectors, 465.8 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): DA9A6AF9-066B-4C1A-8778-93CCE5A68D97
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 976773134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2029 sectors (1014.5 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 410247167 195.6 GiB 8300
    2 410247168 410861567 300.0 MiB 2700 Basic data partition
    3 410861568 411066367 100.0 MiB EF00 EFI system partition
    4 411066368 411328511 128.0 MiB 0C01 Microsoft reserved …
    5 411328512 976773119 269.6 GiB 0700 Basic data partition
    lsblk -f
    sda
    -sda1 /home
    -sda2
    -sda3 [SWAP]
    -sda4 /var
    sdb
    -sdb1 /
    -sdb2
    -sdb3 /boot
    -sdb4
    -sdb5
    sdd
    -sdd1
    -sdd2
    sr0
    loop0
    loop1
    -arch_airootfs /etc/resolv.conf
    loop2
    -arch_airootfs /etc/resolv.conf
    Since my fstab is changed, here is the new one
    # /dev/sdb1 LABEL=archroot
    UUID=xxxxxxxxxxxxxxxxxx / ext4 rw,relatime,data=ordered 0 1
    # /dev/sdb3
    #UUID=xxxxxxxx
    /dev/sdb3 /boot vfat rw,relatime,fmask=0022,dmask=0022, codepage=437,iocharset=iso8859-1, shortname=mixed, errors=remount-ro 0 2
    # /dev/sda1 LABEL=archvar
    UUID=xxxxxxxxxxxxxxxxxx /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda4 LABEL=archome
    UUID=xxxxxxxxxxxxxxxxx /var ext4 rw,relatime,data=ordered 0 2
    # /dev/sda3
    #UUID=xxxxxxxxxxxxxxx none swap defaults 0 0
    After another install, it still hangs on booting. Here are some of the last lines it displays:
    ( OK ) Started create system users
    Starting Create static device nodes in /dev...
    ( OK ) Started Journal service.
    ( OK ) Started create static device nodes in /dev.
    ( OK ) Reached target Local File systems (Pre).
    ( OK ) Started Rebuild hardware database
    Starting udev Kernel Device Manager....
    ( OK ) Started Rebuild Dynamic linker cache
    ( OK ) Started udev Kernel Device Manager
    I’m glad people like my setup. I spent a lot of time reading and comparing before I came up with what I bought.
    Thanks for your help
    Jason
    Last edited by p2ranger (2015-02-13 23:52:29)

  • Mac Mini hangs on boot with grey Screen. No response to Keyboard

    Hello,
    yesterday my Mac Mini (C2Duo, fifth generation unibody) startet to behave strangely. First thing was that it was not responding to the mouse(connected throught the keyboard)
    I replaced the mouse and everything seemed to be ok.
    I then did the latest update available on Mountain Lion and went home.
    When I came back this morning, the Mac Mini hang with grey screen. I restarted. Again grey screen.
    Chime comes. Then nothing.
    Tried everything from http://support.apple.com/kb/ts2570 but nothing worked. The Mac Mini does not seem to be responding
    to any keyboard command to enter safe mode, select boot device etc. No firmware password has been set.
    Any help/ suggestions would be appreciated.
    Yours,
    Andreas

    Have you reset the SMC, then held down the mouse button while restarting to get the CD out?
    Reset SMC:
    Shut down the computer.
    Unplug the computer's power cord.
    Wait fifteen seconds.
    Attach the computer's power cord.
    Wait five seconds, then press the power button to turn on the computer.

  • Arch Live CD x64 hanging during boot at "triggering uevents"

    Hello!
    I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
    I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
    Here is a picture:
    http://i.imgur.com/Y8P41nf.jpg
    I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
    Thank you!
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
    (Sorry, missed that. My bad!)
    Last edited by RalphORama (2013-09-07 03:09:13)

    frank604 wrote:
    You can try nomodeset.  Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it. 
    Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
    Results:
    https://bbs.archlinux.org/viewtopic.php?id=151259
    https://bbs.archlinux.org/viewtopic.php?id=140426
    Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

  • Hangs during boot after upgrading to Kernel 2.6.39

    I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
    The end of /var/log/everything.log is posted below.
    Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
    Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
    Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
    Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
    Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
    Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
    Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
    Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
    Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
    Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
    Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
    Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
    Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
    Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
    Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
    Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
    Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
    Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
    Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
    Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
    Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
    Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
    Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
    Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
    Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
    Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
    Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
    Any help fixing this would be greatly appreciated.

    I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
    pacman -S kernel26
    which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
    I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
    The additional logs in errors.log in the reboot that failed are as follows.
    ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
    Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    The end of kernel.log is as follows:
    Sat Jul 9 14:57:41 CEST 2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
    Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
    And this is the end of daemon.log
    Jul 26 16:27:49 O313 init: Switching to runlevel: 6
    Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
    Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
    Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
    Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
    Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
    Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    Jul 26 16:28:39 O313 init: Entering runlevel: 3
    Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
    Last edited by TheStatsMan (2011-07-26 07:40:48)

  • Mini hangs at boot up screen

    My mini hangs at the grey bootup screen and will not continue beyond it.
    I recently had an old Macbook pro hardrive attached to the Mini via USB to transfer some data.
    This old drive also had a recent version of OSX on it but I never booted to this drive.
    The Mini read the drive, I transferred the data, shut it down, and the next day it would not boot and would only hang on the grey boot up screen.
    It won't boot up whether or not I have the old Macbook drive attached or not.
    I tried a PRAM reset.
    Did I somehow make the Mini look for a wrong boot drive and is there anyhting I can do to fix or reset it without having to reformat?

    It was purchased in August 2012 and I'm pretty sure it's dual i5's with 8GB ram running the latest OS.
    I don't have the recover disk at the moment as the computer was recently loaned to me. Does this typically come on thumbdrive with the computer?  (If so I cn have the owner search for it but he say's he does not recall it.)
    It has no drive for CD/DVD reinstall.
    If I had an external USB drive with the same OS on it would I be able to boot to that drive? And from there backup the main drive to the USB drive and then reformat the main drive if necessary?

  • Multiple cPCI Graphics cards - System Hangs during Boot

    We have 2 Kontron dual output CP332 cPCI graphics cards to install into a NI PXI rack in order to give us 4 graphics outputs.
    When one card is installed it acts as the Primary graphics card and it is required to disable to NI on-board graphics card in order for this to boot and function correctley.
    If a 2nd Kontron CP322 card is added the system will hang during WinXP boot, as it switches from VGA to SVGA mode.
    Disabling the 2nd card via device manager allows the system to boot.
    Re-enabling the 2nd card once booted, then configuring with the ATI driver application allows the 4 graphics output to work as expected.
    If the system is re-powered it will once again hang during WinXp booting.
    Is there anything that can be configured on the NI Embedded PC (BIOS) to prevent this ?
    Is there anything in windows that can be set to prevent this ?
    Can we control the windows device manager from labview in order to enable/disable the 2nd card after power-on and before shutdown.
    many thanks

    Hi Scott,
    I have some more information for you regarding your issue. We have tested the Kontron CP332 with the PXI-8196.
    However when we tested the setup, we had 3 monitors working, the on-board graphics and the dual output from the card.
    Until we get the on-board graphics working with a single CP332 I don't think we will get bot CP332's working.
    So these are the steps to get on-board graphics working with a single Kontron card the steps come from talking to our PXI Product Support Engineer:
    "The first thing you need to make sure is that you are using the
    driver for Windows XP, and not the one for Windows 2000. Here's a link
    to the driver download page:
    http://us.kontron.com/index.php?searchword=cp+332&id=363
    Notice that the first two driver downloads look just the same, but if
    you hover over them and look at the url, you'll notice that the first
    one is for Windows 2000 (w2k), and the second one is for Windows XP
    (wxp). So, just make sure you are using the second one. The PSE did
    mention that she was initially using the Win 2k driver, and was having
    some issues with it hanging and all. Here's the information she sent me
    about how she was able to get things working:
    "Here is the info. My controller has BIOS version 1.3 but have him try this first before updating the BIOS.
    The Kontron Board is the CP 332. I was able to get all three monitors working with the PXI-8196.
    Configuration steps:
    1) Insert both the controller and the kontron board in the chassis.
    Note: When the computer is starting it will give you the Windows boot
    up screen on the DVI 1 on the Kontron board and then give you the login
    screen on the monitor connected to the 8196 so make sure you still have
    a monitor connected to the controller.
    2) Cancel the NI installation wizard if it comes up.
    3)
    Unzip the drivers and run the setup.exe file. Make sure you install
    both the ATI display driver and the ATI Control Panel. (Check the zip
    name to make sure you have the xp version of the driver)
    4) After
    restart go to the Display Properties and under the Settings tab you
    should have monitors 1 and 2 on Mobility Radeon 9000 (Kontron CP-332)."
    If you don't have BIOS version 1.20 or higher, please upgrade to BIOS version 1.30, if you need to upgrade the BIOS please make sure you fully understand the readme file. Then follow the steps above to enable triple output on the graphics cards.
    When you have this working please try adding the second Kontron card.
    Regards
    JamesC
    NIUK and Ireland

  • [SOLVED] "Filesystem check failed" during boot process

    I was using XFCE on my netbook recently and clicked "shutdown".  It logged out to the command prompt and nothing happened.  Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update...  And moments later it suddenly started the shutdown process.
    Now, whenever I boot up, I see the message below.  I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
    Can anyone suggest what I might need to do to fix the problem?
    rootfs: clean, 11026/246512 files, 477083/984576 blocks
    home: clean, 4386/527280 files, 237183/2105344 blocks
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    ************* FILESYSTEM CHECK FAILED ************
    * Please repair manually and reboot. Note that the root
    * file system is currently mounted read-only. To remount
    * it read-write type: mount -n -o remount,rw /
    * when you exit the maintenance shell the system will
    * reboot automatically.
    Give root password for maintenance
    (or type Control-D to continue):
    Last edited by esuhl (2012-03-27 01:20:07)

    Thank you all for your replies :-)
    hadrons123 wrote:What happens when you do try the suggestion given by it?
    I don't exactly know how I should "repair manually"...  I thought a filesystem check in GParted would have been enough...
    lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
    DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
    Thanks.  I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition.  The check completed, but the problem persists...  I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
    fsck from util-linux 2.20.1
    e2fsck 1.41.14 (22-Dec-2010)
    usr was not cleanly unmounted, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
    Gcool wrote:
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
    I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it?  Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...?  Anyway, the partition details from /etc/fstab are below.
    <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    /dev/sda1 / ext2 defaults,noatime 0 1
    /dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
    /dev/sdb2 /usr ext2 defaults,noatime 0 1
    I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
    Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
    If I type "umount /dev/sdb2" at the prompt, I get the following error:
    umount: /usr: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
    I also booted into GParted, but there is no option to "unmount" /dev/sdb2.  There is a "mount" option in the menu, but it is greyed out.  If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
    umount: /dev/sdb2: not mounted
    DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
    No (as shown above).  I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

  • [SOLVED][Duplicate]Garbage output during boot

    During boot you can see something like "666666666666" constantly printed amoung other messages:
    http://i.imgur.com/2YOShSMl.jpg
    This continues even after we are booted and ready to login into the system:
    http://i.imgur.com/THZWZT4l.jpg
    The first time I've noticed this was about half a year ago. It didn't really bothered me, because kdm still worked and you could successfully log into system.
    Yesterday, however, I tried install arch on my new ssd and bumped into this problem even during booting from usb drive with installation iso.
    Any ideas what could this be? I'm not even sure where to look for the root of the problem.
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
    Last edited by konart (2013-06-07 17:30:39)

    Could it possibly be the Logitech G710+ ?
    UPD:
    Oh, I see now: https://bbs.archlinux.org/viewtopic.php?id=153752 Thanks for your directions
    Last edited by konart (2013-06-06 10:34:08)

  • OSX hangs during boot or install

    Hello all,
    I'm writing this because I'm not really sure where else to post this at to get an indepth answer. Currently I have a dual G4 450mhz AGP PowerMac that I bought used. When I purchased it, it had 768mb of ram and the only thing it didn't have was a working hard drive. After putting in a new hard drive the system worked great when i intially installed OS9 and later OSX for fun.
    However I had to remove the 768mb of RAM because a client PC needed it and that took priority over my dual G4 at the time. Just the other week I purchased 2 x 256mb of RAM from Omni Technologies (omnitechnologies.biz) which guarantees working ram for specified Apple systems.
    Upon receiving that ram and installing it, I powered on the G4 only to find it would "hang" when booting OSX (10.3.9). The symptoms are as follows: When powering on I hear the normal chime and the white screen with gray apple logo appears. Seconds later the spinning progress indicator shows up spinning in circles as OSX is booting. However after about 5 minutes with no DVD/hdd activitity, the system then hangs. The gray apple logo changes to a gray 'prohibited' logo. It's the logo of the circle with the slash through it. Like the kind you see over no-smoking signs.
    I figured the hard drive was messed up and I decided to reinstall OSX cleanly. However when I booted from the CD by pressing 'c', the EXACT SAME symptoms above happened. It was at this point I started getting really worried. So I decided to remove the hard drive temporarily and boot from the CD just to make sure it really was booting from the CD. Unfortunately the exact same symptoms happened.
    Out of desperation to make sure that my hardware was OK, I decided to install OS 9.2.1 which installed and WORKED perfectly. I also installed UbuntuPPC and Slackintosh versions of linux which also installed and worked perfectly.
    The issue appears to reside with OSX. I've borrowed friends cd's of 10.2-10.3 and all of them will NOT install. They start to boot from the CD, but never even make it to the first window.
    Help!!
    Brad

    Actually trying one stick in each individual slot was one of the first things I did. Unfortunately that did not provide a resolution for me.
    Thanks for the links regarding the broken folder/prohibitory sign. I read those and they made mention of resetting the nvram and pram. I just did that a bit earlier today but logging into the open firmware by pressing Option-Command-F-O and typing: reset-nvram; set-defaults; reset-all.
    Upon the reboot and after I plugged the hdd with OSX on it back into the system, the resolution was a bit off as I figured. But this time there was no progress indicator. Instead only the gray apple logo showed and there was no response from the hdd or cdrom drive.
    I also noticed that the USB mouses red light went out within the first 45 seconds of booting. I swapped out keyboards and mice and the new ones did the same thing as well. I also tested the memory in an imac I have and OSX that is installed ont heimac works gerat with that stick of memory. I'm leaning towards the fact that the memory I have is fine, being that it was ordered from a company that specifically guaranteed it to work on macs of all kinds.
    Any other thoughts or ideas?

  • [SOLVED] rEfInd Started Hanging on Boot

    I have my computer set up to dual boot Arch and Windows 8 using EFISTUB and rEFIfind as described in the beginners' guide. This had been functioning well for the last month or two but this morning I found that the computer would just hang after printing out:
    Starting vmlinuz-arch.efi
    Using load options 'root=/dev/sda7 ro rootfstype=ext4 systemd.unit=graphical.target'
    The only thing that I've done since my last Arch boot is to install and run DiskInternals Linux Reader 1.6.4.0 on my Windows partition. I needed to grab a file from the Arch ext4 root partition and didn't think that a read operation could result in any corruption. I can still run this program in Windows and everything appears to be in order on the ext4 partition so I'm not entirely sure if this is related.
    I did forget to set up systemd to copy over '/boot/vmlinuz-linux', '/boot/initramfs-linux.img', and '/boot/initramfs-linux-fallback.img' to the efi partition when they change which I thought might have caused this problem. I did this manually from Windows however and it had no impact on the behavior. If anybody could point me in the right direction here I would really appreciate it.
    My refind_linux.conf contents are the following:
    "Boot to X" "root=/dev/sda7 ro rootfstype=ext4 systemd.unit=graphical.target"
    "Boot to console" "root=/dev/sda7 ro rootfstype=ext4 systemd.unit=multi-user.target"
    Last edited by neon (2013-02-21 21:49:56)

    neon wrote:
    Last night I updated all of the packages on my system and this issue returned. I tried doing the fsck again (it said it was clean) but it made no difference. I also tried copying the necessary files from /boot to the EFI partition by hand and this all made no difference. When I updated the system the kernel was updated to 3.7.9-1.
    Anybody have any other ideas for what I could try?
    Try reverting to kernel 3.7.7. There are some as-yet-mysterious glitches involving booting via EFI with Arch kernels 3.7.8, 3.7.9, and possibly some other releases of the 3.7.x series. The EFI problem doesn't seem to affect Arch kernel 3.7.7, though.
    If you want to read about the problems -- and possibly get further confused! -- you could take a look at this thread.
    Either way, I don't believe your problem is related to filesystem errors, which is what fsck addresses.
    Last edited by dhave (2013-02-21 19:01:27)

Maybe you are looking for