Losetup and mount during boot

I want to use losetup to map a disk image file to a loopback device (dev/loop0) during boot.
I would also want to mount this device as my home partition.
The disk image is not located on the root partition, but on another separate partition.
I can do this manually by using following commands:
losetup --find --show /mnt/data/home-flat.vmdk
losetup -o 32256 /dev/loop1 /dev/loop0
mount /dev/loop1 /home
The reason I need this, is that I have a dualboot setup (windows,archlinux) but also want access to an arch system via a virtual machine from within windows.
So I basically have two arch-installations, which share a home partition(the disk image above).
I cannot just map a real partition for the vm, because my disk has a gpt partition map and vmware currently does not support that.
I've looked at creating a custom hook for this, but I am at a loss, especially because the disk image is itself located on a (ntfs)partition,
which itself needs to be mounted before executing the losetup commands.
Any ideas?

Sorry for the delayed response.  I've been away from the computer all weekend.
hungerfish wrote:
Thanks for the help.
I'm still using the init scripts, but will be migrating soon, so now I know where to look come the time
Your solution however doesn't quite work, as I had to add
mount /dev/loop1 /home/
to /etc/rc.local instead of /etc/fstab , because (I assume) losetup hadn't finished by the time fstab gets parsed.
This isn't ideal, but it certainly works, so again thank you for your post!
Hmmm.   The "sysinit_premount" parameter to add_hook should have made this happen before
/etc/fstab is even parsed.
Can you show your /etc/fstab entry?
Ok, I found that hitting scroll-lock pauses during boot/shutdown, so I was able to read:
loop: Write error at byte offset xxx, length 4096
Buffer I/O error on device loop0
Buffer I/O error on device loop1
JBD2 Error -5 detected when updating journal superblock
This pattern repeats a few times, always at different 'offsets'.
Maybe since the file is on an NTFS partition (I assume ntfs-3g?)  Perhaps it killed off the
fuse module that kept NTFS volume mounted before unmounting /home, or removing the
loop devices. Just a guess on that one.
I have used the technique I describe before to pre-setup loop devices for old loop-AES volumes, and it
worked for me.
EDIT3:
So I just had a really bad crash (running as vm), after which I needed to manually fsck and repair the filesystem on the virtual disk. So I guess I'm missing something... sad
Is it possible you suspended the VM rather than shutdown before mounting on linux?  That might cause this.

Similar Messages

  • [SOLVED] Does systemd/arch append -n to a mount during boot?

    Hi all,
    I tried gdrivefs from AUR:
    https://aur.archlinux.org/packages/gdrivefs/
    When I put an the following line into the fstab
    /var/cache/gdfs.creds /mnt/gdrivefs gdfs allow_other 0 0
    I get this error:
    Mär 29 23:39:25 c64 mount[294]: usage: mount.gdfs [-h] [-d] [-o OPT] auth_storage_file mountpoint
    Mär 29 23:39:25 c64 mount[294]: mount.gdfs: error: unrecognized arguments: -n
    Mär 29 23:39:25 c64 systemd[1]: mnt-gdrive.mount mount process exited, code=exited status=2
    Apparently, someone adds a "-n" option to the mount command.
    Interestingly, if I add this line after boot to the fstab,
    mount /mnt/gdrivefs
    works. I reported a bug upstream to add a dummy "-n" option to gdfs. However, the maintainer is wondering who actually adds this "-n" option:
    https://github.com/dsoprea/GDriveFS/iss … t-87722639
    Any systemd experts around who have a clue about what's going on and/or can hint me to some documentation?
    Last edited by knue (2015-03-31 14:56:33)

    systemd does require /etc/mtab to be a symlink to /proc/self/mounts and that is read-only, so passing -n seems to make sense.
    Furthermore, the man page mount(8) describes the interface for external helpers as follows:
    EXTERNAL HELPERS
           The syntax of external mount helpers is:
                  /sbin/mount.suffix  spec  dir [-sfnv] [-o options] [-t type.sub‐
                  type]
           where the suffix is the filesystem type and the -sfnvo options have the
           same  meaning  as  the normal mount options.  The -t option is used for
           filesystems with subtypes  support  (for  example  /sbin/mount.fuse  -t
           fuse.sshfs).
           The  command mount does not pass the mount options unbindable, runbind‐
           able, private, rprivate, slave, rslave, shared, rshared, auto,  noauto,
           comment, x-*, loop, offset and sizelimit to the mount.<suffix> helpers.
           All other options are used in a comma-separated list as argument to the
           -o option.
    Apparently the gdfs helper does not fully implement that interface.

  • P67A-GD65(B3) and freezes during boot, or rare reset

    Hi,
    I've got stupid issue. My mobo is rock solid under:
    * few Windowses (7/8/XP)
    * few Linuxes (Mandriva, Mageia, Ubuntu - in 32 and 64-bit revisions)
    * UEFI BIOS.
    But I've noticed it sometimes freezes on.. GRUB (ver 2, installed by Ubuntu) - when I press cursor keys too much, it just freezes  and all I can do is hard reset. Is it something wrong with keyboard support, or something ? Keyboard is fine and doesn't cause any issues under any OS though.
    I've tested memory with MemTest and all was fine. PSU is strong enough. Nothing is overheating (CPU/GPUs/bridge). System is not overclocked. Everything else works just brilliant (gaming, overclocking, testing under load). Oh, and GRUB is placed on my HDD, not SSD.
    Any suggestions, please ?
    P.S.
    And sometimes.. it's very rare, too - but when I choose Win 7 to boot from SSD (I've got multiboot system with GRUB/Win menu) it boots... but after 5-6 seconds (before log screen) my PC makes self-reset.
    BIOS: latest 1.19 (by CPU-Z)
    Keyboard: Microsoft Sidewinder X6 USB (plugged to upper left USB port)
    Mouse: Gigabyte M6900 USB (plugged tu upper right USB port)
    Memory: 8 GB (2x4 GB) G.Skill Ripjaws 1600 MHz CL9 1.50 V
    PSU: OCZ Z-Series 850 W
    GFX: 2x MSI GTX 460 Hawk
    CPU: i5 2300
    MSX: M-Audio Delta 2496 PCI
    OCZ Agility 3 60 GB + 2xSamsung 1 TB RAID-0

    Do you enable xmp profile to get 1600 mhz memspeed in bios or do you run mem @ 1333 mhz? I get this with win7-64 with my 2 X 4 gb corsair vengeance lp 1600 if I run it at 1600 with the p67a-c45. I was told that since this intel chipset has a max officially rated speed of 1333 mhz you can get strange things happening if you overclock the chipset. BTW performance gain with running @ 1600 mhz is almost zero anyway.

  • Macbook booting during start up and off during booting continously

    my macbook air when turn on it startup and turn off continuosly immediately after it show the apple logo and progress sign...what can should i do about this

    Stinkster,
    does your MacBook Pro have a removable battery? If so, then it originally came with grey installation DVDs. If it doesn’t have a removable battery, look on the bottom of your MacBook Pro for its serial number (it’s etched there in tiny print). If its serial number has eleven characters, write down the last three of them; if it has twelve, write down the last four. Include the three or four characters in your reply; they can determine which model MacBook Pro you have, and the model will determine whether it originally came with grey installation DVDs or not.
    If your MacBook Pro did originally come with grey installation DVDs, then you’re going to need to find them (or buy a replacement pair from Apple or iFixit) to reïnstall Mac OS X on your current hard drive, or to install it on a replacement hard drive.

  • Solaris 10/08 w/ ZFS rpool NFS doesn't mount at boot time?

    I've got an issue with NFS not mounting vfstab entered mounts during boot and was wondering if the latest Sol 10/08 with ZFS had anything to do with it.
    1) #vi /etc/vfstab
    server:/vol/share - /share nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
    server2:/vol/share2 - /share2 nfs - yes rw,bg,hard,nointr,rsize=32768,wsize=32768,noac,vers=3,timeo=600
    2) reboot -- -rv
    Upon rebooting, the shares do not show up, but doing a mountall mounts them finally:
    #mountall
    mount: /tmp is already mounted or swap is busy
    3) Doing a df -k at this point shows me they mounted.
    So what gives? Why are they not mounting at boot? I tried to get around it by doing removing the vfstab entries, adding them into auto_master and then using cachefs, but my employer was not satisfied with autofs and wants them at boot and persistent via the vfstab. So what can be done to get this to work?
    Thank you,
    --tom                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    It appears I didn't have all of the services set online correctly:
    #svcs |grep nfs
    online Jan_05 svc:/network/nfs/status:default
    online Jan_05 svc:/network/nfs/nlockmgr:default
    So, I enabled the following:
    #svcadm enable nfs/mapid
    #svcadm enable nfs/cbd
    #svcadm enable nfs/client
    #scvs |grep nfs
    Checked again:
    #svcs |grep nfs
    online Jan_05 svc:/network/nfs/status:default
    online Jan_05 svc:/network/nfs/nlockmgr:default
    online 15:48:24 svc:/network/nfs/mapid:default
    online 15:48:33 svc:/network/nfs/cbd:default
    online 15:48:42 svc:/network/nfs/client:default
    Tested to make sure no errors were reported:
    # svcs -xv
    Then rebooted again.
    Voila! It worked! Sometimes reading the documents on docs.sun.com pay off. I was just being too lazy to do it and gave up when I posted this. The solution is to check the services and ensure nfs/client is running correctly and then try rebooting again.

  • [solved]How to unlock LUKS using keyfile on usbdrive during boot?

    Hi all,
    I would like some advise for booting encrypted partitions using kefiles on a flashdrive. I'm setting up a Intel Atom based homeserver, and and want my data to be encrypted in case the server gets stolen. To save some encryption overhead I prefer to leave root unencrypted and only encrypt /home, and if this works, later on /var, /tmp and swap as well. My plan is to have a keyfile on a flash thumbdrive, and only have the thumbdrive plugged in while booting.
    I have read the dm-crypt wiki page, but it assumes an encrypted root, and this approach won't work in my situation, where only non-root mountpoints are encrypted. If i put 'ASK' in /etc/crypttab I get prompted for the passphrase and the LUKS container unlocks and mounts fine. I can also unlock the LUKS container manually using the keyfile that I created. However when I put the path to the keyfile in /etc/crypttab instead of 'ASK', and let the usbdrive automount using an udev rule the unlock at boot fails. It seems that my udev rule is only executed when I plug in a drive after booting, not when it is already plugged in during boot. How would I accomplish this? Mount it with fstab and automatically unmount it after booting, or some entirely different way?
    my /etc/fstab:
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/sda1 / ext4 defaults 0 1
    /dev/sda2 swap swap defaults 0 0
    /dev/mapper/home /home ext4 defaults 0 1
    /etc/crypttab:
    home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_home.key
    /etc/udev/rules.d/01.usbdrive_automount.rules (sdb is a second, currently unused harddisk):
    KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    <edit>
    Okay I have found a solution. The trick was to make sure the usbstick gets mounted first, so the keyfile is available for the unlocking/mounting during boot. To do so I have added 'usb' to the hooks line in /etc/mkinitcpio.conf and recompiled the initramfs as described in the wiki link above.
    Next I changed my /etc/udev/rules.d/01.usbdrive_automount.rules a little so that the mountpoint of the usbdrive stays after unplugging it:
    KERNEL=="sd[b-z]", NAME:="%k", SYMLINK+="usbhd-%k", GROUP:="users", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", SYMLINK+="usbhd-%k", GROUP:="users", NAME:="%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", PROGRAM=="/sbin/blkid -t %N", RESULT=="vfat", RUN+="/bin/mount -t vfat -o rw,noauto,flush,dirsync,noexec,nodev,noatime,dmask=000,fmask=111 /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="add", KERNEL=="sd[c-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,async,dirsync,noexec,nodev,noatime /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
    ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k", OPTIONS="last_rule"
    #ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
    #ACTION=="remove", KERNEL=="sd[c-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
    /etc/fstab:
    The usbdrive is put above the encrypted partition to make it get mounted first:
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/sdc1 /media/usbhd-sdc1 ext2 defaults 0 0
    /dev/sda1 / ext4 defaults 0 1
    /dev/sda2 swap swap defaults 0 0
    /dev/mapper/home /home ext4 defaults 0 1
    /etc/crypttab:
    home /dev/sda3 /media/usbhd-sdc1/keyfiles/arch_server_-_luks.key
    So now I plug in the flashdrive, turn on the server, unplug the flashdrive and udev automatically unmounts the flashdrive while leaving the mountpoint /media/usbhd-sdc1 for the next boot.
    </edit>
    Last edited by rwd (2009-12-04 19:36:14)

    graysky wrote:@ratcheer - You can try now if it's a major pain in the balls by enabling [testing] and using the updated linux package.
    If you do enable testing make sure you aren't like myself: I'm not competent enough to enable testing..
    Edit:
    To elaborate a bit.  If you enable testing and then just do a "pacman -Syu" then you are going to pull in all sorts of packages you may not want and it may be complicated to get rid of later.  To avoid this I would enable testing, do this:
    sudo pacman -Syy
    sudo pacman -S testing/linux
    So it would pull in the absolute minimum that I wanted from testing.  Then I would disable the testing repository and pacman -Syy again.  That would convert the new linux package and packages it requires to manual packages.  E.g. they would be shown under "pacman -Qm"
    Because once you start pulling packages in from testing it is almost a one-way street.  As I instructed above, that is my gross understanding.  I don't use testing at all, it is supposed to be used if you are actively testing Arch and providing feedback while doing so.
    Last edited by headkase (2012-10-03 01:51:51)

  • Searching for local disks--keeps coming on during boot up--HELP!

    I installed 10.3 on my G4 recently. Everything worked fine for about a week, and then during boot up the progress bar gets about 75% done and gets stuck on "Searching for local disks". It never moves on. I tried going to disk utility, I get to the first page asking which language to use and I hit english. It moves to the next page, to prepare installation, and it just freezes. I can move the cursor, but nothing will happen. I cannot run disk utility or reinstall. It just stalls at this point. Any ideas?!

    Will it boot in Safe Mode? See
    What is Safe Boot, Safe Mode? (Mac OS X)
    http://docs.info.apple.com/article.html?artnum=107392
    Takes a while to run, but it usually "fixes" problems.
     Cheers, Tom

  • Eth0 is being up and down for several time during boot

    My wicd doesn't connect to eth0 on the first attempt after boot up. It is configured to eth0 always have a higher priority to connect.
    My dmesg shows that eth0 being up and down for several time during boot. I have e1000e in my MODULES list.
    Here is my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK=""
    TIMEZONE="Asia/Hong_Kong"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MOD_AUTOLOAD="yes"
    MODULES=(acpi-cpufreq fuse tp_smapi vboxdrv e1000e)
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="antony-tp"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="yes"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(!hwclock syslog-ng dbus !network !dhcpcd rpcbind acpid @wicd nfs-common netfs @crond cups @laptop-mode @alsa @sensors ntpd @slim bluetooth)
    Here is a segment of my dmesg
    [ 2.759302] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
    [ 2.759304] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
    [ 2.759338] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    [ 2.759348] e1000e 0000:00:19.0: setting latency timer to 64
    [ 2.759467] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 2.766107] tpm_tis 00:0a: 1.2 TPM (device-id 0x0, rev-id 78)
    [ 2.766808] ACPI: AC Adapter [AC] (on-line)
    [ 2.776492] wmi: Mapper loaded
    [ 2.777212] mei: module is from the staging directory, the quality is unknown, you have been warned.
    [ 2.777781] thermal LNXTHERM:00: registered as thermal_zone0
    [ 2.777783] ACPI: Thermal Zone [THM0] (66 C)
    [ 2.778291] iTCO_vendor_support: vendor-support=0
    [ 2.780137] ACPI: Battery Slot [BAT0] (battery present)
    [ 2.780958] input: PC Speaker as /devices/platform/pcspkr/input/input4
    [ 2.781462] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
    [ 2.781547] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
    [ 2.781919] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 2.783139] cfg80211: Calling CRDA to update world regulatory domain
    [ 2.789182] [drm] Initialized drm 1.1.0 20060810
    [ 2.789538] hub 4-1:1.0: USB hub found
    [ 2.789616] hub 4-1:1.0: 8 ports detected
    [ 2.792925] Non-volatile memory driver v1.3
    [ 2.795877] thinkpad_acpi: ThinkPad ACPI Extras v0.24
    [ 2.795879] thinkpad_acpi: http://ibm-acpi.sf.net/
    [ 2.795881] thinkpad_acpi: ThinkPad BIOS 8DET54WW (1.24 ), EC unknown
    [ 2.795882] thinkpad_acpi: Lenovo ThinkPad X220, model 4290NL5
    [ 2.797236] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
    [ 2.797352] thinkpad_acpi: radio switch found; radios are enabled
    [ 2.797466] thinkpad_acpi: possible tablet mode switch found; ThinkPad in laptop mode
    [ 2.799752] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
    [ 2.800067] Registered led device: tpacpi::thinklight
    [ 2.800091] Registered led device: tpacpi::power
    [ 2.800106] Registered led device: tpacpi::standby
    [ 2.800120] Registered led device: tpacpi::thinkvantage
    [ 2.800192] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
    [ 2.800254] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
    [ 2.801077] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
    [ 2.801162] sdhci: Secure Digital Host Controller Interface driver
    [ 2.801164] sdhci: Copyright(c) Pierre Ossman
    [ 2.801707] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [ 2.801709] Copyright(c) 2003-2011 Intel Corporation
    [ 2.801744] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [ 2.801753] iwlwifi 0000:03:00.0: setting latency timer to 64
    [ 2.801789] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [ 2.801791] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90005abc000
    [ 2.801793] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
    [ 2.801877] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
    [ 2.801913] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
    [ 2.801962] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 2.802045] sdhci-pci 0000:0d:00.0: SDHCI controller found [1180:e822] (rev 7)
    [ 2.802067] sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 2.802107] sdhci-pci 0000:0d:00.0: setting latency timer to 64
    [ 2.802118] _regulator_get: 0000:0d:00.0 supply vmmc not found, using dummy regulator
    [ 2.802188] Registered led device: mmc0::
    [ 2.803329] mmc0: SDHCI controller on PCI [0000:0d:00.0] using DMA
    [ 2.815226] iwlwifi 0000:03:00.0: device EEPROM VER=0x715, CALIB=0x6
    [ 2.815229] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
    [ 2.815231] iwlwifi 0000:03:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3
    [ 2.815247] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [ 2.845674] iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301
    [ 2.845820] Registered led device: phy0-led
    [ 2.850630] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
    [ 2.862431] usb 1-1.2: new low-speed USB device number 3 using ehci_hcd
    [ 2.943648] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:92:77:26
    [ 2.943651] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
    [ 2.943712] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
    [ 2.943734] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 2.943739] mei 0000:00:16.0: setting latency timer to 64
    [ 2.943817] mei 0000:00:16.0: irq 50 for MSI/MSI-X
    [ 2.944502] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
    [ 2.945021] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
    [ 2.946341] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16).
    [ 2.946452] watchdog: error registering /dev/watchdog (err=-16).
    [ 2.946523] mei: unable to register watchdog device.
    [ 2.946598] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
    [ 2.946692] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    [ 2.946734] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    [ 2.948359] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    [ 2.948422] snd_hda_intel 0000:00:1b.0: irq 51 for MSI/MSI-X
    [ 2.948444] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
    [ 3.022245] usb 1-1.3: new full-speed USB device number 4 using ehci_hcd
    [ 3.172080] usb 1-1.4: new full-speed USB device number 5 using ehci_hcd
    [ 3.274597] Bluetooth: Core ver 2.16
    [ 3.274611] NET: Registered protocol family 31
    [ 3.274612] Bluetooth: HCI device and connection manager initialized
    [ 3.274614] Bluetooth: HCI socket layer initialized
    [ 3.274614] Bluetooth: L2CAP socket layer initialized
    [ 3.274618] Bluetooth: SCO socket layer initialized
    [ 3.275535] Bluetooth: Generic Bluetooth USB driver ver 0.6
    [ 3.276006] usbcore: registered new interface driver btusb
    [ 3.338454] usb 1-1.6: new high-speed USB device number 6 using ehci_hcd
    [ 3.444567] Linux media interface: v0.10
    [ 3.447387] Linux video capture interface: v2.00
    [ 3.448573] input: Logitech Trackball as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input6
    [ 3.448671] generic-usb 0003:046D:C404.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1a.0-1.2/input0
    [ 3.448690] usbcore: registered new interface driver usbhid
    [ 3.448691] usbhid: USB HID core driver
    [ 3.449136] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217)
    [ 3.450945] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input7
    [ 3.450987] usbcore: registered new interface driver uvcvideo
    [ 3.450988] USB Video Class driver (1.1.1)
    [ 3.484049] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
    [ 3.491137] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
    [ 3.491298] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
    [ 3.491486] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0
    [ 3.491637] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 3.491709] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    [ 3.491765] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    [ 3.492050] i915 0000:00:02.0: power state changed by ACPI to D0
    [ 3.492053] i915 0000:00:02.0: power state changed by ACPI to D0
    [ 3.492059] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 3.492062] i915 0000:00:02.0: setting latency timer to 64
    [ 3.538056] mtrr: no more MTRRs available
    [ 3.538058] [drm] MTRR allocation failed. Graphics performance may suffer.
    [ 3.538266] i915 0000:00:02.0: irq 52 for MSI/MSI-X
    [ 3.538270] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 3.538271] [drm] Driver supports precise vblank timestamp query.
    [ 3.538292] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [ 3.664501] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
    [ 3.664518] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
    [ 3.716317] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12
    [ 4.407165] fbcon: inteldrmfb (fb0) is primary device
    [ 4.575259] Console: switching to colour frame buffer device 170x48
    [ 4.577042] fb0: inteldrmfb frame buffer device
    [ 4.577043] drm: registered panic notifier
    [ 4.607860] acpi device:01: registered as cooling_device4
    [ 4.607985] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input13
    [ 4.608039] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
    [ 4.608122] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 4.757243] EXT4-fs (sda3): re-mounted. Opts: discard
    [ 4.765917] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: discard
    [ 4.776777] Adding 262140k swap on /dev/sda2. Priority:-1 extents:1 across:262140k SS
    [ 5.099467] NET: Registered protocol family 10
    [ 6.048650] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 6.098038] Bluetooth: RFCOMM TTY layer initialized
    [ 6.098055] Bluetooth: RFCOMM socket layer initialized
    [ 6.098057] Bluetooth: RFCOMM ver 1.11
    [ 6.278766] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 6.278893] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 6.568639] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 6.568775] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 6.684082] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 7.176563] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 7.226662] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 7.227110] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 10.229345] IBM TrackPoint firmware: 0x0e, buttons: 3/3
    [ 10.490618] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
    [ 10.817814] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [ 10.819315] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 11.186166] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 11.186292] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 11.313367] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 11.665342] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 11.717591] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 11.718042] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 11.964795] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 12.017213] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 12.017720] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 13.811264] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
    [ 13.826031] EXT4-fs (sda4): re-mounted. Opts: discard,commit=0
    [ 15.178905] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [ 15.180472] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 25.663056] eth0: no IPv6 routers present
    Any hint for tracing the root of this problem? Thank you very much!

    Hi ...
    If you have moved the Safari application from the Applications folder, move it back.
    As far as the cache goes, there's a work around for that when you can't empty the Safari cache from the menu bar.
    Go to    ~/Library/Caches/com.aple.Safari.Cache.db.  Move the Cache.db file to the Trash.
    Try Safari.
    Mac OS X (10.7.2)   <  from your profile
    If that is corrrect, you need to update your system software. Click your Apple menu icon top left in your screen. From the drop down menu click Software
    Update ...
    ~ (Tilde) character represents the Home folder.
    For Lion v10.7x:  To find the Home folder in OS X Lion, open the Finder, hold the Option key, and choose Go > Library

  • I am getting frequent lock-ups and blue screens during boot up. The lock ups occur during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button. Ideas?

    I am getting frequent lock-ups and blue screens during boot up on my Mac Pro.  The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
    I had the Mac Defender malware and I have used apple jack but still having issues.

    I am getting frequent lock-ups and blue screens during boot up on my Mac Pro.  The lock- ups occur sometimes during normal use and I cannot click anything or force quit. The cursor shows something is loading, but never stops. I have to use power button.
    I had the Mac Defender malware and I have used apple jack but still having issues.

  • I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 2011 MBP upgraded to Mavericks.

    hello,
    And thank you in advance.
    I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 20011 MBP upgraded to OS X 10.9 Mavericks. Any ideas?
    I've downloaded the Window support option software and the WindowSetupBox.exe and copied it to the USB drive. I tried to create an iso image from my Windows XP machine but recieved messages that Windows 8.1 could not run on XP.  I've ordered the Windows 8.1 backup media.
    Any way to proceed?
    Thanks  Tim

    download the win 8 iso from here;
    http://getintopc.com/softwares/operating-systems/download-windows-8-pro/
    then start over. install on to your usb along with the support software.

  • Installer disk not found message during boot camp 5 and windows 8 install on late 2001 MBP running Mavericks?

    I'm getting "Installer disk not found" message during boot camp 5 and windows 8 install on late 2001 MBP running Mavericks. Any ideas?
    I've downloaded the Window support option software and the WindowSetupBox.exe and copied it to the USB drive.
    Thanks  Tim 

    You might have better luck in the Boot Camp community. I'll ask the hosts to relocate your post.
    Boot Camp Community

  • I'm getting the grey screen during start up and can't boot the computer. I did a cmnd R but worried it would automatically wipe my hard drive and reinstall OS.  Is there a risk at cmnd R will result in wiped HD without me actively making that choice?

    I'm getting the grey screen during start up and can't boot the computer - MacBook Pro with lion.
    I did a command r after doing some research but got nervous that it would automatically wipe my hard drive and reinstall OS.
    I was nervous because it asked me for language for software use before any options were presented (such as repair via disk utility). It looked similar to an OS install.So I powered off....Is there a risk at command r will result in wiped HD without me actively making that choice?

    Repair the Hard Drive and Permissions - Mavericks, Lion/Mountain Lion
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.
    Reinstall Mountain Lion or Mavericks
    OS X Mavericks- Reinstall OS X
    OS X Mountain Lion- Reinstall OS X
         Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is
                    three times faster than wireless.

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

  • My ipod is freezing during booting and my pc doesnt recognize it

    Hi
    I did a restore ipod from my ipod and after it completed it , my ipod cant boot. It freezes during booting and my computer doesnt recognize it when i plug it.
    Is there anything I can do ?
    Thanks.

    http://support.apple.com/kb/ht1808

  • Using wpa_supplicant and iwconfig to setup wifi during boot.

    I have my gnome desktop running.  My wireless network at my house is hidden and secured via wpa passkey.
    Eitherway, I have two commands that need to be run during boot...
    iwconfig eth1 essid xxxxx
    wpa_supplicant -Dwext -ieth1 -c/etc/wpa_details.conf
    Where would be the best place to stick that?
    On the other hand!!!
    If there is a better way to do it, please by all means suggest it!
    Thanks,
    Rich

    pacman -S netcfg and you can use either the wpa-config or wpa options for security. Take a look at the provided examples, and the wiki
    http://wiki.archlinux.org/index.php/Network_profiles

Maybe you are looking for