10.4.11 upgrade to 10.5 unbootable

Finally got around to upgrading (mainly because my wife got a new Nano that requires iTunes 10), and used a full install retail disc I bought on eBay. The upgrade took quite a bit of time but after it finished I let it go to restart. The computer promptly shut down at the grey apple window before the spinning wheel. So I did a full install on my second hard drive, which did not take nearly as much time. It booted up fine and I updated to 10.5.8.
After several hours of normal use, I decided to use Migration Assistant to bring all my family's accounts and applications over from the original 10.4.11 boot drive (now unbootable 10.5).  Now my second hard drive won't boot and stops at exactly the same place as my other drive.  Right now I'm using my firewire drive on which I installed 10.5 using the same install disc. This second drive had one minor preference issue that DiskUtility fixed and no disk issues (for what it may matter, the preference check takes a ridiculously long time). The original drive checks out fine, too.
There must be something in one of the 10.4.11 system files that's being migrated that causes the drive to become unbootable, right?  Any clues what that might be? Or am I missing something obvious? Thanks!

Set one of those non-booting drives to be the Startup Disk, then Safe Boot from the HD, (holding Shift key down at bootup).
If it only does it in Regular Boot,but Works in Safe Mode then it could be some 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed. Also look in System Preferences' Other row.
Also look in these if they exist, some are invisible...
/private/var/run/StartupItems
/Library/StartupItems
/System/Library/StartupItems
/System/Library/LaunchDaemons
/Library/LaunchDaemons

Similar Messages

  • How can I perform an "in-place upgrade" on an unbootable Windows 7 machine or at least rebuild Safe Mode?

    Some strange glitch has erased every single unlocked & unprotected file on my C: drive. It wasn't a virus because I checked autorun records and running processes using the respective Sysinternals utilities and didn't find anything suspicious.
    I restored all data except for some system files and files that had "too long" of a path using shadow copies, which luckily for me were just a few hours old. Then, I decided to reboot into Recovery Environment and run System Restore from there. For even
    more strange reason, the available restore points in RE were dated November 2010 (it's May 2012 right now) and the recent save dates are nowhere to be found.
    To make matters worse, SFC doesn't work and Safe Mode shows BSOD after loading CLASSPNP.SYS.
    Error messages so far:
    RE's startup repair tool: System files integrity check and repair error code 0x2
    SFC: Windows Resource Protection could not perform the requested operation
    BSOD: 0x7B (0xFFFFF880009A9928, 0XFFFFFFFFC0000034, 0x0, 0x0), but the HDD is perfectly fine - it's a dual-boot machine
    CBS.log: Failed to get CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    What I need is a way to perform either an in-place upgrade without booting into Windows, or a way to fix the SXS Component Store, or rebuild the Safe Mode so that I could initiate upgrade install from there. A clean install isn't an option because I don't
    have the luxury of time to run through the reboot cycles when re-installing and updating other software (I'm using Windows 8 CP for now as my work tools are mostly in the cloud).

    "Den B" wrote in message news:9528356a-7e8f-45bf-9eee-30b40b5df4aa...
    Some strange glitch has erased every single unlocked & unprotected file on my C: drive. It wasn't a virus because I checked autorun records and running processes using the respective Sysinternals utilities and didn't find anything suspicious.
    I restored all data except for some system files and files that had "too long" of a path using shadow copies, which luckily for me were just a few hours old. Then, I decided to reboot into Recovery Environment and run System Restore from there. For even
    more strange reason, the available restore points in RE were dated November 2010 (it's May 2012 right now) and the recent save dates are nowhere to be found.
    To make matters worse, SFC doesn't work and Safe Mode shows BSOD after loading CLASSPNP.SYS.
    Error messages so far:
    RE's startup repair tool: System files integrity check and repair error code 0x2
    SFC: Windows Resource Protection could not perform the requested operation
    BSOD: 0x7B (0xFFFFF880009A9928, 0XFFFFFFFFC0000034, 0x0, 0x0), but the HDD is perfectly fine - it's a dual-boot machine
    CBS.log: Failed to get CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    What I need is a way to perform either an in-place upgrade without booting into Windows, or a way to fix the SXS Component Store, or rebuild the Safe Mode so that I could initiate upgrade install from there. A clean install isn't an option because I don't
    have the luxury of time to run through the reboot cycles when re-installing and updating other software (I'm using Windows 8 CP for now as my work tools are mostly in the cloud).
    It is not possible to do a repair install of a system unless you can boot to the system.
    Have you checked the hard drive for problems? - download the manufacturer's test utility, create the disk, and run the extended checks.
    Noel Paton | Nil Carborundum Illegitemi |
    CrashFixPC | The Three-toed Sloth

  • Mkinitcpio fails on pata hook: unbootable system - upgrade to 2.6.39

    Ran pacman -Syu this morning. Got the following errors:
    [2011-06-13 11:38] ==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2011-06-13 11:38] :: Begin build
    [2011-06-13 11:38] :: Parsing hook [base]
    [2011-06-13 11:38] :: Parsing hook [udev]
    [2011-06-13 11:38] :: Parsing hook [autodetect]
    [2011-06-13 11:38] :: Parsing hook [pata]
    [2011-06-13 11:38] grep: Unmatched [ or [^
    [2011-06-13 11:38] grep: Unmatched [ or [^
    [2011-06-13 11:38] grep: Unmatched [ or [^
    (many more follows, the same errors for hooks [scsi] and [sata]).
    Now the system fails to boot (in normal or fallback modes) with the error:
    Root device '<disk_uuid>' doesn't exist.
    This is x86_64. A somewhat similar system upgraded without any errors. What can I do about it? Any help would be greatly appreciated.
    Last edited by jasonwryan (2011-06-13 21:16:13)

    My mkinitcpio.conf is default one:
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run first, so it may be used to
    # override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten if already added)
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options
    # like so:
    # FILES="/etc/modprobe.d/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    ## This is identical to the above, except the old ide subsystem is
    ## used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    ## This setup assembles a pata raid array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H raid' for more information on raid devices.
    # HOOKS="base udev pata raid encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata filesystems"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
    # compression.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    Here is the output from running mkinitcpio command:
    ==> Building image "default"
    ==> Running command: /sbin/mkinitcpio -v -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    :: Begin build
    :: Parsing hook [base]
    adding dir /proc
    adding dir /sys
    adding dir /dev
    adding dir /bin
    adding dir /sbin
    adding dir /lib
    adding dir /usr
    adding dir /usr/bin
    adding dir /usr/lib
    adding dir /usr/sbin
    adding dir /run
    adding node /dev/null
    adding node /dev/zero
    adding node /dev/console
    adding node /dev/mem
    adding file /bin/busybox
    adding link /lib/libc.so.6 -> /lib/libc-2.13.so
    adding file /lib/libc-2.13.so
    adding link /lib/ld-linux-x86-64.so.2 -> /lib/ld-2.13.so
    adding file /lib/ld-2.13.so
    adding file /sbin/modprobe
    adding file /sbin/blkid
    adding link /lib/libblkid.so.1 -> /lib/libblkid.so.1.1.0
    adding file /lib/libblkid.so.1.1.0
    adding link /lib/libuuid.so.1 -> /lib/libuuid.so.1.3.0
    adding file /lib/libuuid.so.1.3.0
    adding file /init_functions
    adding file /init
    adding file /config
    adding dir /etc
    adding dir /etc/modprobe.d
    adding file /etc/modprobe.d/usb-load-ehci-first.conf
    :: Parsing hook [udev]
    adding file /sbin/udevd
    adding link /lib/librt.so.1 -> /lib/librt-2.13.so
    adding file /lib/librt-2.13.so
    adding link /lib/libpthread.so.0 -> /lib/libpthread-2.13.so
    adding file /lib/libpthread-2.13.so
    adding file /sbin/udevadm
    adding dir /lib/udev
    adding dir /lib/udev/rules.d
    adding file /lib/udev/rules.d/50-firmware.rules
    adding file /lib/udev/rules.d/50-udev-default.rules
    adding file /lib/udev/rules.d/60-persistent-storage.rules
    adding file /lib/udev/rules.d/80-drivers.rules
    adding file /lib/udev/firmware
    adding file /lib/udev/ata_id
    adding file /lib/udev/path_id
    adding file /lib/udev/scsi_id
    adding file /lib/udev/usb_id
    adding dir /etc/udev
    adding file /etc/udev/udev.conf
    adding dir /hooks
    adding file /hooks/udev
    :: Parsing hook [autodetect]
    :: Parsing hook [pata]
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    :: Parsing hook [scsi]
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    :: Parsing hook [sata]
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    grep: Unmatched [ or [^
    :: Parsing hook [filesystems]
    adding module mbcache
    adding dir /lib/modules
    adding dir /lib/modules/2.6.39-ARCH
    adding dir /lib/modules/2.6.39-ARCH/kernel
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/mbcache.ko.gz
    adding module jbd2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/jbd2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/jbd2/jbd2.ko.gz
    adding module crc16
    adding dir /lib/modules/2.6.39-ARCH/kernel/lib
    adding file /lib/modules/2.6.39-ARCH/kernel/lib/crc16.ko.gz
    adding module ext4
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ext4
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ext4/ext4.ko.gz
    :: Generating module dependencies
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/mbcache.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/jbd2/jbd2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/lib/crc16.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ext4/ext4.ko.gz': No such file or directory
    WARNING: Couldn't open directory /tmp/mkinitcpio.1arId8/lib/modules/2.6.39-ARCH: No such file or directory
    FATAL: Could not open /tmp/mkinitcpio.1arId8/lib/modules/2.6.39-ARCH/modules.dep.temp for writing: No such file or directory
    ERROR: file '/tmp/mkinitcpio.1arId8/lib/modules/2.6.39-ARCH/modules.dep' does not exist
    ERROR: file '/tmp/mkinitcpio.1arId8/lib/modules/2.6.39-ARCH/modules.alias' does not exist
    ERROR: file '/tmp/mkinitcpio.1arId8/lib/modules/2.6.39-ARCH/modules.symbols' does not exist
    :: Generating image '/boot/kernel26.img'
    :: Image generation successful
    ==> SUCCESS
    ==> Building image "fallback"
    ==> Running command: /sbin/mkinitcpio -v -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    :: Begin build
    :: Parsing hook [base]
    adding dir /proc
    adding dir /sys
    adding dir /dev
    adding dir /bin
    adding dir /sbin
    adding dir /lib
    adding dir /usr
    adding dir /usr/bin
    adding dir /usr/lib
    adding dir /usr/sbin
    adding dir /run
    adding node /dev/null
    adding node /dev/zero
    adding node /dev/console
    adding node /dev/mem
    adding file /bin/busybox
    adding link /lib/libc.so.6 -> /lib/libc-2.13.so
    adding file /lib/libc-2.13.so
    adding link /lib/ld-linux-x86-64.so.2 -> /lib/ld-2.13.so
    adding file /lib/ld-2.13.so
    adding file /sbin/modprobe
    adding file /sbin/blkid
    adding link /lib/libblkid.so.1 -> /lib/libblkid.so.1.1.0
    adding file /lib/libblkid.so.1.1.0
    adding link /lib/libuuid.so.1 -> /lib/libuuid.so.1.3.0
    adding file /lib/libuuid.so.1.3.0
    adding file /init_functions
    adding file /init
    adding file /config
    adding dir /etc
    adding dir /etc/modprobe.d
    adding file /etc/modprobe.d/usb-load-ehci-first.conf
    :: Parsing hook [udev]
    adding file /sbin/udevd
    adding link /lib/librt.so.1 -> /lib/librt-2.13.so
    adding file /lib/librt-2.13.so
    adding link /lib/libpthread.so.0 -> /lib/libpthread-2.13.so
    adding file /lib/libpthread-2.13.so
    adding file /sbin/udevadm
    adding dir /lib/udev
    adding dir /lib/udev/rules.d
    adding file /lib/udev/rules.d/50-firmware.rules
    adding file /lib/udev/rules.d/50-udev-default.rules
    adding file /lib/udev/rules.d/60-persistent-storage.rules
    adding file /lib/udev/rules.d/80-drivers.rules
    adding file /lib/udev/firmware
    adding file /lib/udev/ata_id
    adding file /lib/udev/path_id
    adding file /lib/udev/scsi_id
    adding file /lib/udev/usb_id
    adding dir /etc/udev
    adding file /etc/udev/udev.conf
    adding dir /hooks
    adding file /hooks/udev
    :: Parsing hook [pata]
    ERROR: module 'pata_acpi' not found
    ERROR: module 'pata_ali' not found
    ERROR: module 'pata_amd' not found
    ERROR: module 'pata_arasan_cf' not found
    ERROR: module 'pata_artop' not found
    ERROR: module 'pata_atiixp' not found
    ERROR: module 'pata_atp867x' not found
    ERROR: module 'pata_cmd640' not found
    ERROR: module 'pata_cmd64x' not found
    ERROR: module 'pata_cs5520' not found
    ERROR: module 'pata_cs5530' not found
    ERROR: module 'pata_cs5536' not found
    ERROR: module 'pata_cypress' not found
    ERROR: module 'pata_efar' not found
    ERROR: module 'pata_hpt366' not found
    ERROR: module 'pata_hpt37x' not found
    ERROR: module 'pata_hpt3x2n' not found
    ERROR: module 'pata_hpt3x3' not found
    ERROR: module 'pata_it8213' not found
    ERROR: module 'pata_it821x' not found
    ERROR: module 'pata_jmicron' not found
    ERROR: module 'pata_legacy' not found
    ERROR: module 'pata_marvell' not found
    ERROR: module 'pata_mpiix' not found
    ERROR: module 'pata_netcell' not found
    ERROR: module 'pata_ninja32' not found
    ERROR: module 'pata_ns87410' not found
    ERROR: module 'pata_ns87415' not found
    ERROR: module 'pata_oldpiix' not found
    ERROR: module 'pata_optidma' not found
    ERROR: module 'pata_opti' not found
    ERROR: module 'pata_pcmcia' not found
    ERROR: module 'pata_pdc2027x' not found
    ERROR: module 'pata_pdc202xx_old' not found
    ERROR: module 'pata_piccolo' not found
    ERROR: module 'pata_radisys' not found
    ERROR: module 'pata_rdc' not found
    ERROR: module 'pata_rz1000' not found
    ERROR: module 'pata_sc1200' not found
    ERROR: module 'pata_sch' not found
    ERROR: module 'pata_serverworks' not found
    ERROR: module 'pata_sil680' not found
    ERROR: module 'pata_sis' not found
    ERROR: module 'pata_sl82c105' not found
    ERROR: module 'pata_triflex' not found
    ERROR: module 'pata_via' not found
    ERROR: module 'ata_generic' not found
    ERROR: module 'ata_piix' not found
    adding module scsi[-_]mod
    adding dir /lib/modules
    adding dir /lib/modules/2.6.39-ARCH
    adding dir /lib/modules/2.6.39-ARCH/kernel
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
    adding module sd[-_]mod
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
    :: Parsing hook [scsi]
    ERROR: module '3w_9xxx' not found
    ERROR: module '3w_sas' not found
    ERROR: module '3w_xxxx' not found
    ERROR: module 'a100u2w' not found
    module scsi_mod was already added
    adding module aacraid
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aacraid
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aacraid/aacraid.ko.gz
    ERROR: module 'advansys' not found
    module scsi_mod was already added
    module scsi_mod was already added
    adding module scsi[-_]transport[-_]spi
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/scsi_transport_spi.ko.gz
    adding module aic79xx
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aic7xxx
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aic7xxx/aic79xx.ko.gz
    module scsi_mod was already added
    module scsi_transport_spi was already added
    adding module aic7xxx
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aic7xxx/aic7xxx.ko.gz
    module scsi_mod was already added
    adding module libata
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/ata
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/ata/libata.ko.gz
    module scsi_mod was already added
    adding module scsi[-_]transport[-_]sas
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/scsi_transport_sas.ko.gz
    module scsi_mod was already added
    adding module libsas
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/libsas
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/libsas/libsas.ko.gz
    module scsi_mod was already added
    module scsi_transport_sas was already added
    adding module aic94xx
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aic94xx
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/aic94xx/aic94xx.ko.gz
    module scsi_mod was already added
    adding module arcmsr
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/arcmsr
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/arcmsr/arcmsr.ko.gz
    ERROR: module 'atp870u' not found
    module scsi_mod was already added
    adding module scsi[-_]transport[-_]iscsi
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/scsi_transport_iscsi.ko.gz
    module scsi_mod was already added
    adding module libiscsi
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/libiscsi.ko.gz
    adding module iscsi[-_]boot[-_]sysfs
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/iscsi_boot_sysfs.ko.gz
    module scsi_transport_iscsi was already added
    module scsi_mod was already added
    adding module be2iscsi
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/be2iscsi
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/be2iscsi/be2iscsi.ko.gz
    module scsi_mod was already added
    module scsi_mod was already added
    adding module scsi[-_]transport[-_]fc
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/scsi_transport_fc.ko.gz
    adding module bfa
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/bfa
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/bfa/bfa.ko.gz
    module scsi_mod was already added
    module scsi_transport_fc was already added
    adding module libfc
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/libfc
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/libfc/libfc.ko.gz
    adding module libfcoe
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/fcoe
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/fcoe/libfcoe.ko.gz
    module libfc was already added
    module scsi_mod was already added
    module scsi_transport_fc was already added
    adding module uio
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/uio
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/uio/uio.ko.gz
    adding module ipv6
    adding dir /lib/modules/2.6.39-ARCH/kernel/net
    adding dir /lib/modules/2.6.39-ARCH/kernel/net/ipv6
    adding file /lib/modules/2.6.39-ARCH/kernel/net/ipv6/ipv6.ko.gz
    adding module cnic
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/net
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/net/cnic.ko.gz
    adding module bnx2fc
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/bnx2fc
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/bnx2fc/bnx2fc.ko.gz
    module scsi_transport_iscsi was already added
    module libiscsi was already added
    module scsi_mod was already added
    module cnic was already added
    adding module bnx2i
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/bnx2i
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/bnx2i/bnx2i.ko.gz
    ERROR: module 'BusLogic' not found
    ERROR: module 'ch' not found
    module libiscsi was already added
    module scsi_transport_iscsi was already added
    module libiscsi was already added
    module libiscsi was already added
    adding module libiscsi[-_]tcp
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/libiscsi_tcp.ko.gz
    module scsi_mod was already added
    adding module libcxgbi
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/cxgbi
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/cxgbi/libcxgbi.ko.gz
    module libiscsi_tcp was already added
    adding dir /lib/firmware
    adding dir /lib/firmware/cxgb3
    adding file /lib/firmware/cxgb3/ael2020_twx_edc.bin
    adding file /lib/firmware/cxgb3/ael2005_twx_edc.bin
    adding file /lib/firmware/cxgb3/ael2005_opt_edc.bin
    adding file /lib/firmware/cxgb3/t3c_psram-1.1.0.bin
    adding file /lib/firmware/cxgb3/t3b_psram-1.1.0.bin
    adding file /lib/firmware/cxgb3/t3fw-7.10.0.bin
    adding module mdio
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/net/mdio.ko.gz
    adding module cxgb3
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/net/cxgb3
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/net/cxgb3/cxgb3.ko.gz
    adding module cxgb3i
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/cxgbi/cxgb3i
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/cxgbi/cxgb3i/cxgb3i.ko.gz
    module libiscsi was already added
    module libcxgbi was already added
    module libiscsi_tcp was already added
    adding dir /lib/firmware/cxgb4
    adding file /lib/firmware/cxgb4/t4fw.bin
    adding module cxgb4
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/net/cxgb4
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/net/cxgb4/cxgb4.ko.gz
    adding module cxgb4i
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/cxgbi/cxgb4i
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/cxgbi/cxgb4i/cxgb4i.ko.gz
    module libcxgbi was already added
    ERROR: module 'dc395x' not found
    module scsi_mod was already added
    adding module scsi[-_]dh
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/device_handler
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/device_handler/scsi_dh.ko.gz
    module scsi_mod was already added
    adding module scsi[-_]dh[-_]alua
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko.gz
    module scsi_dh was already added
    module scsi_mod was already added
    adding module scsi[-_]dh[-_]emc
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/device_handler/scsi_dh_emc.ko.gz
    module scsi_dh was already added
    module scsi_mod was already added
    adding module scsi[-_]dh[-_]hp[-_]sw
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/device_handler/scsi_dh_hp_sw.ko.gz
    module scsi_dh was already added
    module scsi_dh was already added
    module scsi_mod was already added
    adding module scsi[-_]dh[-_]rdac
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/device_handler/scsi_dh_rdac.ko.gz
    ERROR: module 'dmx3191d' not found
    ERROR: module 'dpt_i2o' not found
    module libfc was already added
    module libfcoe was already added
    module scsi_transport_fc was already added
    module scsi_mod was already added
    adding module fcoe
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/fcoe/fcoe.ko.gz
    module libfcoe was already added
    ERROR: module 'fdomain' not found
    module libfcoe was already added
    module scsi_mod was already added
    module libfc was already added
    module scsi_transport_fc was already added
    adding module fnic
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/fnic
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/fnic/fnic.ko.gz
    ERROR: module 'gdth' not found
    ERROR: module 'hpsa' not found
    ERROR: module 'hptiop' not found
    ERROR: module 'initio' not found
    ERROR: module 'ipr' not found
    ERROR: module 'ips' not found
    ERROR: module 'iscsi_boot_sysfs' not found
    ERROR: module 'iscsi_tcp' not found
    module libfc was already added
    ERROR: module 'libiscsi' not found
    ERROR: module 'libiscsi_tcp' not found
    module libsas was already added
    ERROR: module 'libsrp' not found
    module scsi_mod was already added
    module scsi_transport_fc was already added
    adding module lpfc
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/lpfc
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/lpfc/lpfc.ko.gz
    ERROR: module 'megaraid' not found
    module scsi_mod was already added
    adding module megaraid[-_]mm
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/megaraid
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/megaraid/megaraid_mm.ko.gz
    adding module megaraid[-_]mbox
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/megaraid/megaraid_mbox.ko.gz
    module megaraid_mm was already added
    module scsi_mod was already added
    adding module megaraid[-_]sas
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/megaraid/megaraid_sas.ko.gz
    module scsi_mod was already added
    module scsi_transport_sas was already added
    module scsi_mod was already added
    adding module raid[-_]class
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/raid_class.ko.gz
    adding module mpt2sas
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/mpt2sas
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/mpt2sas/mpt2sas.ko.gz
    module libsas was already added
    module scsi_mod was already added
    module scsi_transport_sas was already added
    adding module mvsas
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/mvsas
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/mvsas/mvsas.ko.gz
    adding module libosd
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/osd
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/osd/libosd.ko.gz
    module libosd was already added
    module scsi_mod was already added
    adding module osd
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/osd/osd.ko.gz
    ERROR: module 'osst' not found
    module libsas was already added
    module scsi_mod was already added
    module scsi_transport_sas was already added
    adding module pm8001
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/pm8001
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/pm8001/pm8001.ko.gz
    ERROR: module 'pmcraid' not found
    ERROR: module 'ppa' not found
    ERROR: module 'qla1280' not found
    adding file /lib/firmware/ql2500_fw.bin
    adding file /lib/firmware/ql2400_fw.bin
    adding file /lib/firmware/ql2322_fw.bin
    adding file /lib/firmware/ql2300_fw.bin
    adding file /lib/firmware/ql2200_fw.bin
    adding file /lib/firmware/ql2100_fw.bin
    module scsi_mod was already added
    module scsi_transport_fc was already added
    adding module qla2xxx
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/qla2xxx
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/qla2xxx/qla2xxx.ko.gz
    module scsi_transport_iscsi was already added
    module scsi_mod was already added
    adding module qla4xxx
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/qla4xxx
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/qla4xxx/qla4xxx.ko.gz
    ERROR: module 'qlogicfas408' not found
    ERROR: module 'raid_class' not found
    ERROR: module 'scsi_mod' not found
    ERROR: module 'scsi_tgt' not found
    ERROR: module 'scsi_transport_fc' not found
    ERROR: module 'scsi_transport_iscsi' not found
    ERROR: module 'scsi_transport_sas' not found
    ERROR: module 'scsi_transport_spi' not found
    ERROR: module 'scsi_transport_srp' not found
    ERROR: module 'scsi_wait_scan' not found
    ERROR: module 'sd_mod' not found
    ERROR: module 'ses' not found
    ERROR: module 'sg' not found
    ERROR: module 'sr_mod' not found
    ERROR: module 'stex' not found
    ERROR: module 'st' not found
    module scsi_transport_spi was already added
    module scsi_mod was already added
    adding module sym53c8xx
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/sym53c8xx_2
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko.gz
    ERROR: module 'tmscsim' not found
    ERROR: module 'vmw_pvscsi' not found
    ERROR: module 'cciss' not found
    ERROR: module 'cpqarray' not found
    ERROR: module 'DAC960' not found
    ERROR: module 'mptbase' not found
    ERROR: module 'mptctl' not found
    ERROR: module 'mptfc' not found
    ERROR: module 'mptsas' not found
    ERROR: module 'mptscsih' not found
    ERROR: module 'mptspi' not found
    module sd_mod was already added
    :: Parsing hook [sata]
    ERROR: module 'eata' not found
    ERROR: module 'sx8' not found
    ERROR: module 'sata_inic162x' not found
    ERROR: module 'sata_mv' not found
    ERROR: module 'sata_nv' not found
    ERROR: module 'sata_promise' not found
    ERROR: module 'sata_qstor' not found
    ERROR: module 'sata_sil24' not found
    ERROR: module 'sata_sil' not found
    ERROR: module 'sata_sis' not found
    ERROR: module 'sata_svw' not found
    ERROR: module 'sata_sx4' not found
    ERROR: module 'sata_uli' not found
    ERROR: module 'sata_via' not found
    ERROR: module 'sata_vsc' not found
    ERROR: module 'ahci' not found
    ERROR: module 'ahci_platform' not found
    ERROR: module 'pdc_adma' not found
    ERROR: module 'ata_piix' not found
    module sd_mod was already added
    :: Parsing hook [filesystems]
    adding module fscache
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/fscache
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/fscache/fscache.ko.gz
    adding module 9pnet
    adding dir /lib/modules/2.6.39-ARCH/kernel/net/9p
    adding file /lib/modules/2.6.39-ARCH/kernel/net/9p/9pnet.ko.gz
    adding module 9p
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/9p
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/9p/9p.ko.gz
    adding module affs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/affs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/affs/affs.ko.gz
    module fscache was already added
    adding module af[-_]rxrpc
    adding dir /lib/modules/2.6.39-ARCH/kernel/net/rxrpc
    adding file /lib/modules/2.6.39-ARCH/kernel/net/rxrpc/af-rxrpc.ko.gz
    adding module kafs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/afs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/afs/kafs.ko.gz
    adding module autofs4
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/autofs4
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/autofs4/autofs4.ko.gz
    adding module befs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/befs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/befs/befs.ko.gz
    adding module libcrc32c
    adding dir /lib/modules/2.6.39-ARCH/kernel/lib
    adding file /lib/modules/2.6.39-ARCH/kernel/lib/libcrc32c.ko.gz
    adding module crc32c
    adding dir /lib/modules/2.6.39-ARCH/kernel/crypto
    adding file /lib/modules/2.6.39-ARCH/kernel/crypto/crc32c.ko.gz
    adding module crc32c[-_]intel
    adding dir /lib/modules/2.6.39-ARCH/kernel/arch
    adding dir /lib/modules/2.6.39-ARCH/kernel/arch/x86
    adding dir /lib/modules/2.6.39-ARCH/kernel/arch/x86/crypto
    adding file /lib/modules/2.6.39-ARCH/kernel/arch/x86/crypto/crc32c-intel.ko.gz
    adding module zlib[-_]deflate
    adding dir /lib/modules/2.6.39-ARCH/kernel/lib/zlib_deflate
    adding file /lib/modules/2.6.39-ARCH/kernel/lib/zlib_deflate/zlib_deflate.ko.gz
    adding module btrfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/btrfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/btrfs/btrfs.ko.gz
    module fscache was already added
    adding module cachefiles
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/cachefiles
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/cachefiles/cachefiles.ko.gz
    module libcrc32c was already added
    adding module libceph
    adding dir /lib/modules/2.6.39-ARCH/kernel/net/ceph
    adding file /lib/modules/2.6.39-ARCH/kernel/net/ceph/libceph.ko.gz
    adding module ceph
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ceph
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ceph/ceph.ko.gz
    module fscache was already added
    adding module cifs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/cifs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/cifs/cifs.ko.gz
    adding module coda
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/coda
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/coda/coda.ko.gz
    adding module configfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/configfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/configfs/configfs.ko.gz
    adding module cramfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/cramfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/cramfs/cramfs.ko.gz
    module configfs was already added
    adding module dlm
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/dlm
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/dlm/dlm.ko.gz
    adding module ecryptfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ecryptfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ecryptfs/ecryptfs.ko.gz
    module osd was already added
    module libosd was already added
    adding module exofs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/exofs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/exofs/exofs.ko.gz
    adding module mbcache
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/mbcache.ko.gz
    adding module ext2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ext2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ext2/ext2.ko.gz
    module mbcache was already added
    adding module jbd
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/jbd
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/jbd/jbd.ko.gz
    adding module ext3
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ext3
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ext3/ext3.ko.gz
    module mbcache was already added
    adding module jbd2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/jbd2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/jbd2/jbd2.ko.gz
    adding module crc16
    adding file /lib/modules/2.6.39-ARCH/kernel/lib/crc16.ko.gz
    adding module ext4
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ext4
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ext4/ext4.ko.gz
    adding module fat
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/fat
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/fat/fat.ko.gz
    adding module nls[-_]cp437
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/nls
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/nls/nls_cp437.ko.gz
    module fat was already added
    adding module msdos
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/fat/msdos.ko.gz
    module fat was already added
    adding module vfat
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/fat/vfat.ko.gz
    module fscache was already added
    adding module fuse
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/fuse
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/fuse/fuse.ko.gz
    adding module cuse
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/fuse/cuse.ko.gz
    module fuse was already added
    module dlm was already added
    adding module gfs2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/gfs2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/gfs2/gfs2.ko.gz
    adding module hfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/hfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/hfs/hfs.ko.gz
    adding module hfsplus
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/hfsplus
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/hfsplus/hfsplus.ko.gz
    adding module isofs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/isofs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/isofs/isofs.ko.gz
    module jbd2 was already added
    module jbd was already added
    module zlib_deflate was already added
    adding module mtd
    adding dir /lib/modules/2.6.39-ARCH/kernel/drivers/mtd
    adding file /lib/modules/2.6.39-ARCH/kernel/drivers/mtd/mtd.ko.gz
    adding module jffs2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/jffs2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/jffs2/jffs2.ko.gz
    adding module jfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/jfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/jfs/jfs.ko.gz
    adding module sunrpc
    adding dir /lib/modules/2.6.39-ARCH/kernel/net/sunrpc
    adding file /lib/modules/2.6.39-ARCH/kernel/net/sunrpc/sunrpc.ko.gz
    adding module lockd
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/lockd
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/lockd/lockd.ko.gz
    module zlib_deflate was already added
    adding module logfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/logfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/logfs/logfs.ko.gz
    module mbcache was already added
    adding module ncpfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ncpfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ncpfs/ncpfs.ko.gz
    module sunrpc was already added
    adding module nfs[-_]acl
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/nfs_common
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/nfs_common/nfs_acl.ko.gz
    module sunrpc was already added
    adding module auth[-_]rpcgss
    adding dir /lib/modules/2.6.39-ARCH/kernel/net/sunrpc/auth_gss
    adding file /lib/modules/2.6.39-ARCH/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko.gz
    module sunrpc was already added
    module lockd was already added
    module nfs_acl was already added
    adding module nfsd
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/nfsd
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/nfsd/nfsd.ko.gz
    module fscache was already added
    module sunrpc was already added
    module lockd was already added
    module auth_rpcgss was already added
    module nfs_acl was already added
    adding module nfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/nfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/nfs/nfs.ko.gz
    adding module nilfs2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/nilfs2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/nilfs2/nilfs2.ko.gz
    adding module ntfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ntfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ntfs/ntfs.ko.gz
    module configfs was already added
    adding module ocfs2[-_]nodemanager
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/cluster
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/cluster/ocfs2_nodemanager.ko.gz
    adding module ocfs2[-_]stackglue
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/ocfs2_stackglue.ko.gz
    module ocfs2_nodemanager was already added
    adding module ocfs2[-_]dlmfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/dlmfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/dlmfs/ocfs2_dlmfs.ko.gz
    module ocfs2_nodemanager was already added
    adding module ocfs2[-_]dlm
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/dlm
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko.gz
    module jbd2 was already added
    module ocfs2_stackglue was already added
    adding module quota[-_]tree
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/quota
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/quota/quota_tree.ko.gz
    module ocfs2_nodemanager was already added
    adding module ocfs2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/ocfs2.ko.gz
    module configfs was already added
    module ocfs2_stackglue was already added
    module ocfs2_dlm was already added
    module ocfs2_nodemanager was already added
    module ocfs2_stackglue was already added
    adding module ocfs2[-_]stack[-_]o2cb
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/ocfs2_stack_o2cb.ko.gz
    module dlm was already added
    module ocfs2_stackglue was already added
    adding module ocfs2[-_]stack[-_]user
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ocfs2/ocfs2_stack_user.ko.gz
    adding module crc[-_]itu[-_]t
    adding file /lib/modules/2.6.39-ARCH/kernel/lib/crc-itu-t.ko.gz
    adding module omfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/omfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/omfs/omfs.ko.gz
    module quota_tree was already added
    adding module quota[-_]v1
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/quota/quota_v1.ko.gz
    module quota_tree was already added
    adding module quota[-_]v2
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/quota/quota_v2.ko.gz
    adding module reiserfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/reiserfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/reiserfs/reiserfs.ko.gz
    adding module squashfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/squashfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/squashfs/squashfs.ko.gz
    module crc_itu_t was already added
    adding module udf
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/udf
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/udf/udf.ko.gz
    adding module ufs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/ufs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/ufs/ufs.ko.gz
    adding module xfs
    adding dir /lib/modules/2.6.39-ARCH/kernel/fs/xfs
    adding file /lib/modules/2.6.39-ARCH/kernel/fs/xfs/xfs.ko.gz
    :: Generating module dependencies
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/scsi_mod.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/sd_mod.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/aacraid/aacraid.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/scsi_transport_spi.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/aic7xxx/aic79xx.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/aic7xxx/aic7xxx.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/ata/libata.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/scsi_transport_sas.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/libsas/libsas.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/aic94xx/aic94xx.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/arcmsr/arcmsr.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/scsi_transport_iscsi.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/libiscsi.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/iscsi_boot_sysfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/be2iscsi/be2iscsi.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/scsi_transport_fc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/bfa/bfa.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/libfc/libfc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/fcoe/libfcoe.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/uio/uio.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/net/ipv6/ipv6.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/net/cnic.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/bnx2fc/bnx2fc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/bnx2i/bnx2i.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/libiscsi_tcp.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/cxgbi/libcxgbi.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/net/mdio.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/net/cxgb3/cxgb3.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/cxgbi/cxgb3i/cxgb3i.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/net/cxgb4/cxgb4.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/cxgbi/cxgb4i/cxgb4i.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/device_handler/scsi_dh.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/device_handler/scsi_dh_emc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/device_handler/scsi_dh_hp_sw.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/device_handler/scsi_dh_rdac.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/fcoe/fcoe.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/fnic/fnic.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/lpfc/lpfc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/megaraid/megaraid_mm.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/megaraid/megaraid_mbox.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/megaraid/megaraid_sas.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/raid_class.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/mpt2sas/mpt2sas.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/mvsas/mvsas.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/osd/libosd.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/osd/osd.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/pm8001/pm8001.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/qla2xxx/qla2xxx.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/qla4xxx/qla4xxx.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/fscache/fscache.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/net/9p/9pnet.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/9p/9p.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/affs/affs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/net/rxrpc/af-rxrpc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/afs/kafs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/autofs4/autofs4.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/befs/befs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/lib/libcrc32c.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/crypto/crc32c.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/arch/x86/crypto/crc32c-intel.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/lib/zlib_deflate/zlib_deflate.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/btrfs/btrfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/cachefiles/cachefiles.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/net/ceph/libceph.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ceph/ceph.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/cifs/cifs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/coda/coda.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/configfs/configfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/cramfs/cramfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/dlm/dlm.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ecryptfs/ecryptfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/exofs/exofs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/mbcache.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ext2/ext2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/jbd/jbd.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ext3/ext3.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/jbd2/jbd2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/lib/crc16.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ext4/ext4.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/fat/fat.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/nls/nls_cp437.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/fat/msdos.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/fat/vfat.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/fuse/fuse.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/fuse/cuse.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/gfs2/gfs2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/hfs/hfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/hfsplus/hfsplus.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/isofs/isofs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/drivers/mtd/mtd.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/jffs2/jffs2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/jfs/jfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/net/sunrpc/sunrpc.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/lockd/lockd.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/logfs/logfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ncpfs/ncpfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/nfs_common/nfs_acl.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/nfsd/nfsd.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/nfs/nfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/nilfs2/nilfs2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ntfs/ntfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/cluster/ocfs2_nodemanager.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/ocfs2_stackglue.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/dlmfs/ocfs2_dlmfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/quota/quota_tree.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/ocfs2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/ocfs2_stack_o2cb.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ocfs2/ocfs2_stack_user.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/lib/crc-itu-t.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/omfs/omfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/quota/quota_v1.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/quota/quota_v2.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/reiserfs/reiserfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/squashfs/squashfs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/udf/udf.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/ufs/ufs.ko.gz': No such file or directory
    install: cannot stat `/lib/modules/2.6.39-ARCH\033[m\033[K/kernel/fs/xfs/xfs.ko.gz': No such file or directory
    WARNING: Couldn't open directory /tmp/mkinitcpio.zHFFRR/lib/modules/2.6.39-ARCH: No such file or directory
    FATAL: Could not open /tmp/mkinitcpio.zHFFRR/lib/modules/2.6.39-ARCH/modules.dep.temp for writing: No such file or directory
    ERROR: file '/tmp/mkinitcpio.zHFFRR/lib/modules/2.6.39-ARCH/modules.dep' does not exist
    ERROR: file '/tmp/mkinitcpio.zHFFRR/lib/modules/2.6.39-ARCH/modules.alias' does not exist
    ERROR: file '/tmp/mkinitcpio.zHFFRR/lib/modules/2.6.39-ARCH/modules.symbols' does not exist
    :: Generating image '/boot/kernel26-fallback.img'
    :: Image generation successful
    ==> SUCCESS

  • Interrupted upgrade on an iBook = kernel panic

    I was trying to upgrade an old G3 iBook (10.2) to Tiger, and borrowed a firewire DVD drive from a friend. I won't bore you with why, but I had to interrupt the upgrade and start over. No matter what I do now, I get a kernel panic starting up. I've tried Disk Utility, both from an earlier install CD (I don't know how to start up from the firewire DVD drive) and from a G5 connected via firewire, starting the iBook while holding down "T" on the keyboard. Nothing helps.
    I can read and save most of the data via the firewire connection to the G5, but my iPod is linked to this computer, I'm editing two mailing lists from it, and a lot of my data is embedded in programs on it. Is there anything I can do to recover this disk, say by removing recently written and updated system files and rebooting?

    No, I can see the iBook drive from the G5 via "target disk mode". I just can't get it to boot by itself. Are you saying I can connect the unbootable iBook to the G5 by target disk mode and also connect the DVD drive by firewire and upgrade the iBook that way, by connecting the upgrade DVD to the iBook through a G5 intermediary?

  • Mid 2010 MBP wont upgrade

    Hello to the apple forums!
    I have a bit of a dilemma with my Mid 2010 Macbook Pro. My brother gave me this mac (it was his old one) and it ran Mountain Lion when he had it. He removed the hdd before he gave it to me, and in the process, the HDD cable tore. The Optical drive was allready dead, so I decided to replace the drive with a 2nd hdd caddy, throw my own hdd in the caddy and run from that.
    This is where the problems started for me. I tried to install mountain lion from my usb (made from the appstore installesd), and when booting, the apple logo & pinwheel would load, but then just freeze solid, no movement at all. So I asked my brother if that happened, and he said yes and that he needed to install snow leopard and upgrade from there. So, I grabbed the 10.6.3 usb disk from my old mid 2010 macbook air, and proceeded to install it. The install went great. I can use the OS and life was good. Then I decided that I actually wanted to use my purchased copy of Mountain Lion. The mac didnt like that. I tried to upgrade to 10.6.8, and the upgrade worked fine, but upon rebooting, it would freeze at the pinwheel screen. So, I booted in verbose mode, and this time it would get to the line "AirPort: Link down on en1. Reason 1 (Unspecified)" and just stop loading.
    So, I contacted apple care. I was sent through resetting the NVRAM/PRAM, SMC and trying to boot with internet recovery. All of which failed and I was told to bring the machine to an apple store. So I did just that. At the apple store, they tried all the same things I was walked through, and even tried booting off of several of their own network drives (including a 'triage' drive), all of which got stuck at the pinwheel. The apple tech took the pc in the back, tried disconnecting my hdd caddy and removing one of the ram chips (not like I hadn't allready tried that) and stated that it wasn't those particular pieces of hardware that were causing it, but he noticed something on the motherboard that looked like a spill, and that he couldn't do anymore with it.
    This particular spill happened before my brother got the mac. He was given the mac in an unbootable state, and was told if he could fix it, it was his. So he cleaned all of this mysterious, jelly like material, off of the motherboard and it worked perfectly for him in the 9 months that he had it.
    Anyways, after leaving apple, I had to reseat the ram because the moron who took it in back didn't seat it right, or check that the mac was in the same state as when he got it, and today I started noticing problems with the hdd (which I had not had before visiting apple). So I put a new hdd in, reinstalled SL and have been running on that. I decided for the 'lulz' to try and boot Internet Recovery in verbose mode, and to my surprise it worked!
    I watched the verbose messages, and the mac gets to the following line before freezing:
    using 64-bit bootcache playlist
    BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 No such file or directory
    Previous Shutdown Cause: 3
    SMC::smcHandleInterruptEvent WARNING status=0x0 (0x40 not set) notif=0x0
    SMC::smcInitHelper ERROR: MMIO regMap == NULL - fall back to old SMC mode
    ***** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- this = 0xffffff802441cc00
    NVDAStartup: Official
    NVDANV50HAL loaded and registered
    after that, it just sits there and looks at me like I'm stupid. I'm not sure whats causing this thing to fail, or why, after my brother had Mountain Lion on it for the past 9 months, that it fails to boot into even the mountain lion installer now.
    Mac Specs:
    13" Macbook Pro, Mid 2010 (7,1 I believe)
    Core 2 Duo @ 2.4ghz
    8gb DDR3 Ram
    Nvidia GeForce 320m (256mb)
    250gb Toshiba 5400rpm HDD
    Snow Leopard 10.6.3
    Any iput is greatly appreciated.
    -Gigawiz

    Finally, I have gotten OS X Mavericks installed on my Mid 2010 13” Macbook Pro!
    I ended up going to the hackintosh community (oddly enough) to fix it!
    As I stated before, I was stuck on 10.6.3, so in order for the Mavericks installer to work, I had to modify the (installed) system version, and do a clean install of mavericks, but it was FakeSMC and NullCPUPowerManagement, 2 kexts which are designed to allow OS X to run on non apple hardware, that saved the day!
    Using both the FakeSMC and NullCPUPowerManagement, I was able to get the Mavericks USB I created to boot in my mac without any freezes. Then, after install (and setup), I removed FakeSMC and Viola! I’m now running OS X Mavericks!
    Hope this helps anyone with the same problem as me!
    -Gigawiz

  • IPhoto library upgrade failed, one third of the photos lost, but the library works as normal. No corruption.

    Hello! I recently replaced my tragically crashed Macbook Pro 2008 with a newer model and transferred my volumous iphoto library of 20 000+ photos to my new machine. To be able to use my iphoto '08 library with Aperture I had to upgrade the library in the iphoto '11 version. I left the computer on during the day, and when I got back it seemed to work fine. I browsed my library in Aperture and could see all the thumbnails, but looking closer I noticed a small yellow warning triangle with an arrow in the corner of some pictures. Turns out all pictures from before ~2010 are lost! When I wiev the photos I see nothing but the infinite black of the data void.
    Here's how I've tried to fix the problem:
    1. Opening the iPhoto Library package in Finder. All the folders for the earlier dates are there, but they are empty. I notice no incorrect or impossible dating, which seemed to be a common problem among users who's libraries where corrupted during the upgrade process.
    2. Rebuilding the iphoto library in iphoto. No effect.
    3. Recovering the iphoto library from my Time Machine Backup. SInce my old hard drive was just 200 GB, I stored all pictures older than one year on my external hard drive (note that about half of those pictures were successfully imported/upgraded). Both the internal and the external hard drive where backed up using Time Machine on a NAS from Seagate (Black Armor 110, 3TB). I was able to access backed up files on my external drive through Time Machine on my old computer, but since it is now rendered unbootable I tried using Migration Assistant to let my new computer inherit the old backup. However, I could not find the backup of the external drive in Migration Assistant, just my old internal drive. When I tried to access the backup volume on my NAS through Finder it didn't show up (I could find it that way on my old computer).
    4. Googling "iPhoto library upgrade failed", or "Inheriting Time Machine backup of external drive", and similarily desperately specific phrases - Nothing useful. Other people seems to have had problems with corrupt Libraries, but I'm not sure that's the case here.
    My pictures must exist somewhere on my computer and in a backup on my NAS. I just can't find them! Do anyone have a clue to what may have gone wrong? I'm afraid the computer might have gone to sleep during the upgrade, because I didn't thinkabout adjusting the power saving settings before starting it. But since pictures 1-8000-something are missing, it doesn't seem to have worked properly during the whole beginning of the upgrade, not just during the middle. As I knew I had a backup of the library I didn't worry about upgrading the single functional copy. From now on I will think thrice before doing anything as serious as this.
    I am eternally grateful for any answers that might help me recovering my photos!
    //Teodor Nilson

      b) I split up my photo collection into two iphoto libraries. One for the new photos stored on my internal HD            and one for photos older than one year stored on my external HD
    And exactly How did you Split up your iPhoto library?
    c) I used Migration Assistant in an attempt to access the Time Machine backup of my old MBP from my new      MBP (by inheriting the backup). When I made my backups, I made sure Time Machine included the external      HD. But Migration Assistant could only find the backup of my Internal HD with the library of new photos!
    And again
    You should not use Migration assistant on an iPhoto library - it generally does not work
    and
         d)   When signing in and mounting the NAS in Finder, I used to be able to see a Time Machine backup      folder/icon. Now I was unable to locate it.
    I believe you are using your NAS for your Time Machine backup. If your Time Machine backup and/or your iPhoto library is on a NAS you will have problems - both need to be on Mac formatted volumes - the least troublsome is a volume formatted Mac OS extended (journaled)
    http://support.apple.com/kb/HT1427?viewlocale=en_US&locale=en_US
    Manually preparing a new disk for Time Machine
    If you want to erase a disk before using it with Time Machine, follow these steps:
    Open Disk Utility (located in the Utilities folder).
    Connect the disk if it isn't already attached.
    In the left side of the Disk Utility window, select the disk you want to use with Time Machine.
    Optional: If you want to partition the disk, click the Partition tab and select a layout. Make sure "Mac OS Extended (Journaled)" is selected in the Format menu for the partition that will be used for backups. Click Apply.
    Click the Erase tab.
    Optional: If you want to securely erase the disk, click Security Options to configure, then click OK.
    Click Erase.
    After erasing, open Time Machine preferences in System Preferences and configure as described in the section above.
    Are the iPhoto libraries kept on an external drive formated Mac OS extended (journaled)? Or are they on the NAS? - If you are using the NAS for iPhoto and/or Time Machine that is the source of your problems
    LN

  • Upgrade broke bluetooth - would like help diagnosing cause

    I ran two pacman -Syu cycles today and one or other (but I'm not sure which) has broken bluetooth. I would like, if possible, to figure out the most likely causes and whether there is anything which might have avoided this.
    A little background: bluetooth has always been dodgy on this machine. A BIOS upgrade helped but has not really resolved the issues under Linux. (Can't say about Windows as I don't use it.) Since the upgrade there is a reasonably certain way of restoring bluetooth but it is, frankly, a PITA. (It involves resetting BIOS to defaults which renders the machine unbootable as it wipes the EFI boot entry for grub. This is easily fixed but it is a pain to have to go through this all the time.)
    The issue is that bluetooth appears as hard blocked and nothing I've found short of the above reenables it.
    Here's pacman's log for today:
    [2012-10-28 00:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 00:01] synchronizing package lists
    [2012-10-28 00:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 00:17] synchronizing package lists
    [2012-10-28 01:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 01:01] synchronizing package lists
    [2012-10-28 01:05] Running 'pacman -Syu'
    [2012-10-28 01:05] synchronizing package lists
    [2012-10-28 01:05] starting full system upgrade
    [2012-10-28 01:07] upgraded firefox (16.0.1-1 -> 16.0.2-1)
    [2012-10-28 01:07] upgraded firefox-i18n-cy (16.0.1-1 -> 16.0.2-1)
    [2012-10-28 01:07] upgraded phonon (1:4.6.0-2 -> 1:4.6.0-3)
    [2012-10-28 01:07] upgraded wget (1.14-1 -> 1.14-2)
    [2012-10-28 01:07] Exited with code 0
    [2012-10-28 01:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 01:17] synchronizing package lists
    [2012-10-28 01:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 01:01] synchronizing package lists
    [2012-10-28 01:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 01:17] synchronizing package lists
    [2012-10-28 02:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 02:01] synchronizing package lists
    [2012-10-28 02:33] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 02:33] synchronizing package lists
    [2012-10-28 03:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 03:01] synchronizing package lists
    [2012-10-28 03:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 03:17] synchronizing package lists
    [2012-10-28 03:31] Running 'pacman -Syu'
    [2012-10-28 03:31] synchronizing package lists
    [2012-10-28 03:31] starting full system upgrade
    [2012-10-28 03:34] upgraded imagemagick (6.7.9.8-2 -> 6.8.0.3-1)
    [2012-10-28 03:34] upgraded calibre (0.9.4-1 -> 0.9.4-2)
    [2012-10-28 03:34] upgraded ilmbase (1.0.2-1 -> 1.0.3-1)
    [2012-10-28 03:34] upgraded openexr (1.7.1-1 -> 1.7.1-2)
    [2012-10-28 03:34] upgraded glew (1.8.0-2 -> 1.9.0-1)
    [2012-10-28 03:34] upgraded enblend-enfuse (4.0-7 -> 4.0-8)
    [2012-10-28 03:34] upgraded gambas3-runtime (3.3.3-2 -> 3.3.3-3)
    [2012-10-28 03:34] upgraded gambas3-devel (3.3.3-2 -> 3.3.3-3)
    [2012-10-28 03:34] upgraded gegl (0.2.0-4 -> 0.2.0-5)
    [2012-10-28 03:34] upgraded hugin (2011.4.0-6 -> 2011.4.0-7)
    [2012-10-28 03:34] upgraded imagemagick-doc (6.7.9.8-2 -> 6.8.0.3-1)
    [2012-10-28 03:35] upgraded inkscape (0.48.3.1-6 -> 0.48.3.1-7)
    [2012-10-28 03:35] upgraded kdelibs (4.9.2-2 -> 4.9.2-3)
    [2012-10-28 03:35] upgraded kdelibs3 (3.5.10-14 -> 3.5.10-15)
    [2012-10-28 03:35] upgraded obex-data-server (0.4.6-2 -> 0.4.6-3)
    [2012-10-28 03:35] upgraded xine-lib (1.2.2-2 -> 1.2.2-3)
    [2012-10-28 03:35] upgraded opencv (2.4.2-4 -> 2.4.2-5)
    [2012-10-28 03:35] upgraded pstoedit (3.60-2 -> 3.60-3)
    [2012-10-28 03:35] Exited with code 0
    [2012-10-28 16:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 16:01] synchronizing package lists
    [2012-10-28 17:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 17:01] synchronizing package lists
    [2012-10-28 17:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 17:17] synchronizing package lists
    [2012-10-28 18:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 18:01] synchronizing package lists
    [2012-10-28 18:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 18:17] synchronizing package lists
    [2012-10-28 19:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 19:01] synchronizing package lists
    [2012-10-28 19:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 19:17] synchronizing package lists
    [2012-10-28 20:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 20:01] synchronizing package lists
    [2012-10-28 20:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 20:17] synchronizing package lists
    [2012-10-28 20:32] Running 'pacman -Syu'
    [2012-10-28 20:32] synchronizing package lists
    [2012-10-28 20:33] starting full system upgrade
    [2012-10-28 20:37] upgraded linux-api-headers (3.5.5-1 -> 3.6.3-1)
    [2012-10-28 20:37] Generating locales...
    [2012-10-28 20:37] cy_GB.UTF-8... done
    [2012-10-28 20:37] cy_GB.ISO-8859-14... done
    [2012-10-28 20:37] en_GB.UTF-8... done
    [2012-10-28 20:37] en_GB.ISO-8859-1... done
    [2012-10-28 20:37] en_US.UTF-8... done
    [2012-10-28 20:37] en_US.ISO-8859-1... done
    [2012-10-28 20:37] Generation complete.
    [2012-10-28 20:37] upgraded glibc (2.16.0-4 -> 2.16.0-5)
    [2012-10-28 20:37] upgraded binutils-multilib (2.22-10 -> 2.23-1)
    [2012-10-28 20:37] upgraded colordiff (1.0.10-1 -> 1.0.12-1)
    [2012-10-28 20:37] upgraded lib32-glibc (2.16.0-4 -> 2.16.0-5)
    [2012-10-28 20:37] upgraded lib32-gcc-libs (4.7.2-1 -> 4.7.2-2)
    [2012-10-28 20:37] upgraded gcc-libs-multilib (4.7.2-1 -> 4.7.2-2)
    [2012-10-28 20:37] upgraded gcc-multilib (4.7.2-1 -> 4.7.2-2)
    [2012-10-28 20:37] upgraded monit (5.5-1 -> 5.5-2)
    [2012-10-28 20:37] upgraded powertop (2.1-1 -> 2.1.1-1)
    [2012-10-28 20:37] upgraded syslinux (4.05-7 -> 4.06-1)
    [2012-10-28 20:37] Exited with code 0
    [2012-10-28 20:46] Running 'pacman -U /home/software/packages/dropbox-cli-1-13-x86_64.pkg.tar.xz'
    [2012-10-28 20:46] upgraded dropbox-cli (1-12 -> 1-13)
    [2012-10-28 20:46] Exited with code 0
    [2012-10-28 21:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 21:01] synchronizing package lists
    [2012-10-28 21:17] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 21:17] synchronizing package lists
    [2012-10-28 22:01] Running 'pacman --dbpath /dev/shm/fakepacdb -Sy'
    [2012-10-28 22:01] synchronizing package lists
    I assume that obex-data-server is a plausible culprit but I'm not certain whether other things might be implicated such as glibc.
    systemctl shows this for bluetooth.service's status:
    bluetooth.service - Bluetooth service
    Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
    Active: active (running) since Sun, 2012-10-28 21:52:27 GMT; 17min ago
    Main PID: 415 (bluetoothd)
    CGroup: name=systemd:/system/bluetooth.service
    └ 415 /usr/sbin/bluetoothd -n
    Oct 28 21:52:20 <computername> bluetoothd[415]: Bluetooth daemon 4.101
    Oct 28 21:52:27 <computername> bluetoothd[415]: Starting SDP server
    Oct 28 21:52:29 <computername> bluetoothd[415]: Bluetooth Management interface initialized
    Oct 28 21:52:27 <computername> systemd[1]: Started Bluetooth service.
    Oct 28 21:52:30 <computername> bluetoothd[415]: bluetoothd[415]: Starting SDP server
    Oct 28 21:52:30 <computername> bluetoothd[415]: bluetoothd[415]: Bluetooth Management interface initialized
    errors.log includes these lines:
    Oct 28 15:36:28 localhost bluetoothd[447]: hci0: Remove UUID (0x0011) failed: Invalid Parameters (0x0d)
    Oct 28 15:36:28 localhost bluetoothd[447]: hci0: Remove UUID (0x0011) failed: Invalid Parameters (0x0d)
    journalctl includes:
    Oct 28 02:28:05 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (run/udev/data/+bluetooth:hci0)
    Oct 28 02:28:45 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/lib/modules/3.0.48-1-lts/kernel/net/bluetooth/)
    Oct 28 02:28:45 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/lib/modules/3.0.48-1-lts/kernel/net/bluetooth/bluetooth.ko.gz)
    Oct 28 02:28:45 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/lib/modules/3.0.48-1-lts/kernel/net/bluetooth/bnep/)
    Oct 28 02:28:45 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/lib/modules/3.0.48-1-lts/kernel/net/bluetooth/bnep/bnep.ko.gz)
    Oct 28 02:28:45 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/lib/modules/3.0.48-1-lts/kernel/net/bluetooth/hidp/)
    Oct 28 02:29:06 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/lib/systemd/system/bluetooth.target)
    Oct 28 02:30:48 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/share/mime/application/vnd.kde.bluedevil-audio.xml)
    Oct 28 02:30:48 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/share/mime/application/vnd.kde.bluedevil-input.xml)
    Oct 28 02:30:48 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/share/mime/application/vnd.kde.bluedevil-network-dun.xml)
    Oct 28 02:30:48 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/share/mime/application/vnd.kde.bluedevil-network-panu.xml)
    Oct 28 02:30:48 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (usr/share/mime/application/vnd.kde.bluedevil-sendfile.xml)
    Oct 28 02:32:29 <computername> /USR/SBIN/CROND[30610]: (root) CMDOUT (var/lib/bluetooth/***/config)
    Oct 28 15:36:24 <computername> systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
    Oct 28 15:36:24 <computername> systemd[1]: Stopping Bluetooth.
    Oct 28 15:36:24 <computername> systemd[1]: Stopped target Bluetooth.
    Oct 28 15:36:24 <computername> systemd[1]: Starting Bluetooth.
    Oct 28 15:36:24 <computername> systemd[1]: Reached target Bluetooth.
    Oct 28 15:36:25 <computername> bluetoothd[447]: bluetoothd[447]: Adapter /org/bluez/447/hci0 has been disabled
    Oct 28 15:36:25 <computername> bluetoothd[447]: Adapter /org/bluez/447/hci0 has been disabled
    Oct 28 15:36:25 <computername> bluetoothd[447]: Unregister path: /org/bluez/447/hci0
    Oct 28 15:36:25 <computername> bluetoothd[447]: bluetoothd[447]: Unregister path: /org/bluez/447/hci0
    Oct 28 15:36:25 <computername> bluetoothd[447]: bluetoothd[447]: input-headset driver probe failed for device ***
    Oct 28 15:36:25 <computername> bluetoothd[447]: input-headset driver probe failed for device ***
    Oct 28 15:36:25 <computername> bluetoothd[447]: Adapter /org/bluez/447/hci0 has been enabled
    Oct 28 15:36:25 <computername> bluetoothd[447]: bluetoothd[447]: Adapter /org/bluez/447/hci0 has been enabled
    Oct 28 15:36:28 <computername> bluetoothd[447]: bluetoothd[447]: hci0: Remove UUID (0x0011) failed: Invalid Parameters (0x0d)
    Oct 28 15:36:28 <computername> bluetoothd[447]: hci0: Remove UUID (0x0011) failed: Invalid Parameters (0x0d)
    Oct 28 15:36:28 <computername> bluetoothd[447]: bluetoothd[447]: hci0: Remove UUID (0x0011) failed: Invalid Parameters (0x0d)
    Oct 28 15:36:28 <computername> bluetoothd[447]: hci0: Remove UUID (0x0011) failed: Invalid Parameters (0x0d)
    Oct 28 16:11:55 <computername> systemd[1]: Stopping Bluetooth.
    Oct 28 16:11:55 <computername> systemd[1]: Stopped target Bluetooth.
    Oct 28 16:11:55 <computername> systemd[1]: Stopping Bluetooth service...
    Oct 28 16:11:55 <computername> bluetoothd[447]: bluetoothd[447]: Terminating
    Oct 28 16:11:55 <computername> bluetoothd[447]: Terminating
    Oct 28 16:11:55 <computername> bluetoothd[447]: Stopping SDP server
    Oct 28 16:11:55 <computername> bluetoothd[447]: Exit
    Oct 28 16:11:55 <computername> bluetoothd[447]: bluetoothd[447]: Stopping SDP server
    Oct 28 16:11:55 <computername> bluetoothd[447]: bluetoothd[447]: Exit
    Oct 28 16:11:56 <computername> systemd[1]: Stopped Bluetooth service.
    Oct 28 16:58:47 <computername> kernel: Bluetooth: Core ver 2.16
    Oct 28 16:58:47 <computername> kernel: Bluetooth: HCI device and connection manager initialized
    Oct 28 16:58:47 <computername> kernel: Bluetooth: HCI socket layer initialized
    Oct 28 16:58:47 <computername> kernel: Bluetooth: L2CAP socket layer initialized
    Oct 28 16:58:47 <computername> kernel: Bluetooth: SCO socket layer initialized
    Oct 28 16:58:47 <computername> kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
    Oct 28 16:58:54 <computername> bluetoothd[411]: Bluetooth daemon 4.101
    Oct 28 16:58:55 <computername> bluetoothd[411]: bluetoothd[411]: Bluetooth daemon 4.101
    Oct 28 16:59:00 <computername> bluetoothd[411]: Starting SDP server
    Oct 28 16:59:00 <computername> bluetoothd[411]: Bluetooth Management interface initialized
    Oct 28 16:59:09 <computername> bluetoothd[411]: bluetoothd[411]: Starting SDP server
    Oct 28 16:59:09 <computername> bluetoothd[411]: bluetoothd[411]: Bluetooth Management interface initialized
    Oct 28 16:59:00 <computername> systemd[1]: Started Bluetooth service.
    Oct 28 16:59:00 <computername> systemd[1]: Starting Bluetooth.
    Oct 28 16:59:00 <computername> systemd[1]: Reached target Bluetooth.
    Oct 28 16:59:00 <computername> systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
    Oct 28 16:59:00 <computername> systemd[1]: Stopping Bluetooth.
    Oct 28 16:59:00 <computername> systemd[1]: Stopped target Bluetooth.
    Oct 28 16:59:09 <computername> kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Oct 28 20:46:50 <computername> systemd[1]: Stopping Bluetooth service...
    Oct 28 20:46:50 <computername> bluetoothd[411]: bluetoothd[411]: Terminating
    Oct 28 20:46:50 <computername> bluetoothd[411]: Terminating
    Oct 28 20:46:50 <computername> bluetoothd[411]: Stopping SDP server
    Oct 28 20:46:50 <computername> bluetoothd[411]: Exit
    Oct 28 20:46:50 <computername> bluetoothd[411]: bluetoothd[411]: Stopping SDP server
    Oct 28 20:46:50 <computername> bluetoothd[411]: bluetoothd[411]: Exit
    Oct 28 20:46:50 <computername> systemd[1]: Stopped Bluetooth service.
    Oct 28 20:47:39 <computername> kernel: Bluetooth: Core ver 2.16
    Oct 28 20:47:39 <computername> kernel: Bluetooth: HCI device and connection manager initialized
    Oct 28 20:47:39 <computername> kernel: Bluetooth: HCI socket layer initialized
    Oct 28 20:47:39 <computername> kernel: Bluetooth: L2CAP socket layer initialized
    Oct 28 20:47:39 <computername> kernel: Bluetooth: SCO socket layer initialized
    Oct 28 20:47:39 <computername> kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
    Oct 28 20:47:45 <computername> bluetoothd[435]: Bluetooth daemon 4.101
    Oct 28 20:47:45 <computername> bluetoothd[435]: bluetoothd[435]: Bluetooth daemon 4.101
    Oct 28 20:47:52 <computername> systemd[1]: Started Bluetooth service.
    Oct 28 20:47:52 <computername> systemd[1]: Starting Bluetooth.
    Oct 28 20:47:52 <computername> systemd[1]: Reached target Bluetooth.
    Oct 28 20:47:52 <computername> systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
    Oct 28 20:47:52 <computername> systemd[1]: Stopping Bluetooth.
    Oct 28 20:47:52 <computername> systemd[1]: Stopped target Bluetooth.
    Oct 28 20:47:55 <computername> bluetoothd[435]: bluetoothd[435]: Starting SDP server
    Oct 28 20:47:55 <computername> bluetoothd[435]: bluetoothd[435]: Bluetooth Management interface initialized
    Oct 28 20:47:52 <computername> bluetoothd[435]: Starting SDP server
    Oct 28 20:47:55 <computername> bluetoothd[435]: Bluetooth Management interface initialized
    Oct 28 20:47:55 <computername> kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    Oct 28 21:51:35 <computername> systemd[1]: Stopping Bluetooth service...
    Oct 28 21:51:35 <computername> bluetoothd[435]: bluetoothd[435]: Terminating
    Oct 28 21:51:35 <computername> bluetoothd[435]: Terminating
    Oct 28 21:51:35 <computername> bluetoothd[435]: Stopping SDP server
    Oct 28 21:51:35 <computername> bluetoothd[435]: Exit
    Oct 28 21:51:35 <computername> bluetoothd[435]: bluetoothd[435]: Stopping SDP server
    Oct 28 21:51:35 <computername> bluetoothd[435]: bluetoothd[435]: Exit
    Oct 28 21:51:35 <computername> systemd[1]: Stopped Bluetooth service.
    Oct 28 21:52:03 <computername> kernel: Bluetooth: Core ver 2.16
    Oct 28 21:52:03 <computername> kernel: Bluetooth: HCI device and connection manager initialized
    Oct 28 21:52:03 <computername> kernel: Bluetooth: HCI socket layer initialized
    Oct 28 21:52:03 <computername> kernel: Bluetooth: L2CAP socket layer initialized
    Oct 28 21:52:03 <computername> kernel: Bluetooth: SCO socket layer initialized
    Oct 28 21:52:04 <computername> kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
    Oct 28 21:52:20 <computername> bluetoothd[415]: bluetoothd[415]: Bluetooth daemon 4.101
    Oct 28 21:52:20 <computername> bluetoothd[415]: Bluetooth daemon 4.101
    Oct 28 21:52:27 <computername> bluetoothd[415]: Starting SDP server
    Oct 28 21:52:29 <computername> bluetoothd[415]: Bluetooth Management interface initialized
    Oct 28 21:52:27 <computername> systemd[1]: Started Bluetooth service.
    Oct 28 21:52:27 <computername> systemd[1]: Starting Bluetooth.
    Oct 28 21:52:27 <computername> systemd[1]: Reached target Bluetooth.
    Oct 28 21:52:27 <computername> systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
    Oct 28 21:52:27 <computername> systemd[1]: Stopping Bluetooth.
    Oct 28 21:52:27 <computername> systemd[1]: Stopped target Bluetooth.
    Oct 28 21:52:30 <computername> bluetoothd[415]: bluetoothd[415]: Starting SDP server
    Oct 28 21:52:30 <computername> bluetoothd[415]: bluetoothd[415]: Bluetooth Management interface initialized
    Oct 28 21:52:30 <computername> kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    I'm not sure why "adaptor  /org/bluez/447/hci0" would be disabled? Or what would have disabled it? I guessing this is the key but is this a symptom or a cause?
    EDIT: I just realised that in the above output, CROND seems to be using the lts modules for bluetooth (not sure what cron does with bluetooth). The records show that I was not booted with the lts kernel at this point. (I had to check as I did try the lts kernel when my machine was badly overheating but it didn't seem to help.) I have no idea what those commands are trying to do, but is that expected?
    Last edited by cfr (2012-10-29 01:30:45)

    Well, what does your root crontab show?  I guess you should probably also dig around to see if you can figure out where those cronjobs are running from.  They indicate root, but I know that can also come from the set of scripts in /etc. 
    What happens if you modprobe that module.  Like maybe load it (and hope that it then loads the right one), or removing the module and reloading it.
    Also, the other day, I discovered that with UEFI, you can have a default efi program that doesn't require a boot manager entry.  Anything that is saved as \EFI\boot\bootx86.efi will automatically be booted when you select your device from the boot manager menu (like the hard drive itself, as if you were going to boot from the mbr).  I am not sure what would happen though if you were to have two efi system partitions though, but I am fairly certain you only have one. 
    So I have set my system up so that I have one boot manager entry for linux-ck, and then my hard drive is second in the boot list.  So if I selecy my hard drive, I have gummiboot set up as bootx64.efi, and from there I have all my other possible boot methods, including the shell.  Since you are a grub user, maybe you should copy grub to that position and see what happens.  I guess this is why the bios has a setting to switch whether uefi or bios should be tried first.

  • Solaris 9 live upgrade to solaris 10 segmentation fault

    pre-upgrade work:
    apply patch doc 72099
    upgrade live upgrade to solaris 10.
    lucreate-m /:/dev/dsk/c0t1d0s0:ufs -m /var:/dev/dsk/c0t1d0s1:ufs -m /opt:/dev/dsk/c0t1d0s3:ufs -n sol10
    it works well
    oot Environment Is Active Active Can Copy
    Name Complete Now On Reboot Delete Status
    sol9 yes yes yes no -
    sol10 yes no no yes -
    But luupgrade -u -n sol10 -s /sol11
    Validating the contents of the media </sol11>.
    The media is a standard Solaris media.
    The media contains an operating system upgrade image.
    The media contains <Solaris> version <11>.
    Constructing upgrade profile to use.
    Locating the operating system upgrade program.
    Checking for existence of previously scheduled Live Upgrade requests.
    Creating upgrade profile for BE <sol10>.
    Determining packages to install or upgrade for BE <sol10>.
    Performing the operating system upgrade of the BE <sol10>.
    CAUTION: Interrupting this process may leave the boot environment unstable
    or unbootable.
    /usr/sbin/luupgrade&#91;677&#93;: 6549 Segmentation Fault(coredump)
    ERROR: Installation of the packages from this media of the media failed; pfinstall returned these diagnostics:
    The Solaris upgrade of the boot environment <sol10> failed.

    I would break your mirror and do a liveupgrade on the available mirror. Then boot that disk.

  • Solaris 10 live upgrade failed

    I am trying to upgrade Solaris 10 U6 10/08 to U7 05/09 with live upgrade. But it failed with following errors:
    # luupgrade -u -n solaris_u7 -s /mnt/cdrom
    No entry for BE <solaris_u7> in GRUB menu
    Copying failsafe kernel from media.
    Uncompressing miniroot
    Creating miniroot device
    miniroot filesystem is <ufs>
    Mounting miniroot at </mnt/cdrom/Solaris_10/Tools/Boot>
    Validating the contents of the media </mnt/cdrom>.
    The media is a standard Solaris media.
    The media contains an operating system upgrade image.
    The media contains <Solaris> version <10>.
    Constructing upgrade profile to use.
    Locating the operating system upgrade program.
    Checking for existence of previously scheduled Live Upgrade requests.
    Creating upgrade profile for BE <solaris_u7>.
    Checking for GRUB menu on ABE <solaris_u7>.
    Saving GRUB menu on ABE <solaris_u7>.
    Checking for x86 boot partition on ABE.
    Determining packages to install or upgrade for BE <solaris_u7>.
    Performing the operating system upgrade of the BE <solaris_u7>.
    CAUTION: Interrupting this process may leave the boot environment unstable
    or unbootable.
    ERROR: Installation of the packages from this media of the media failed; pfinstall returned these diagnostics:
    Processing profile
    Loading local environment and services
    Generating upgrade actions
    WARNING: SUNWwgetu depends on SUNWgcmn, which is not selected
    WARNING: SUNWi15cs depends on SUNWi15rf, which is not selected
    WARNING: SUNWi1cs depends on SUNWxwplt, which is not selected
    WARNING: SUNWbind depends on SUNWbindr, which is not selected
    WARNING: SUNWale depends on SUNWxwrtl, which is not selected
    WARNING: SUNWale depends on SUNWxwplt, which is not selected
    ERROR: No upgradeable file systems found at specified mount point.
    Restoring GRUB menu on ABE <solaris_u7>.
    ABE boot partition backing deleted.
    PBE GRUB has no capability information.
    PBE GRUB has no versioning information.
    ABE GRUB is newer than PBE GRUB. Updating GRUB.
    GRUB update was successfull.
    Did it really fail due to file dependencies? Will it fix the problem by installing the missing packages on the running BE?

    You need to run this script from the CD or Install server: Solaris_10/Tools/Installers/liveupgrade20 when upgrading to 10 u7. I had run into this. Run the script and choose all the defaults. Liveupgrade will then not give the errors you have seen.
    Linuxbass :-)

  • 10.7.2 upgrade question for MacBook Pro 5,1?

    i am currently running 10.6.8 on a MacBook Pro 5,1. i'm gonna upgrade it to Lion.
    will this process install a recovery partition on my MacBook Pro hard drive? If so, how big?
    after i upgrade, will I still need my install discs readily available, or can i finally store them away?
    i am just trying to understand how life works after going to Lion on a MacBook Pro 5,1?
    it seems that i will only need my original discs for the Apple Hardware Test. Everything else can be done via the recovery partition?
    any tips? has anyone done this to a 5,1 yet?
    THANK YOU!

    Hello and welcome to Apple Support Communities...
    Erica M31 wrote:
    i am currently running 10.6.8 on a MacBook Pro 5,1. i'm gonna upgrade it to Lion.
    will this process install a recovery partition on my MacBook Pro hard drive? If so, how big?
    Yes, the OSX Lion installer will create a Recovery HD Partition in your HDD. It's about 650mb in space.
    Erica M31 wrote:
    after i upgrade, will I still need my install discs readily available, or can i finally store them away?
    Although you won't need your install discs after installing OSX Lion, I always advise to keep them in a reachable area should you want to "downgrade" back to Snow Leopard or install your MacBook's Windows drivers on a Bootcamp partition. I have my Snow Leopard Discs in my MacBook Pro box for the "just in case" scenario.
    Erica M31 wrote:
    it seems that i will only need my original discs for the Apple Hardware Test. Everything else can be done via the recovery partition?
    As stated in the last statement, I recommend that you keep your original MacBook Pro discs store in a place where you can easily reach them for the "just in case" scenarios. I will just tell you to keep your original OSX Installation & Apple Hardware Test discs that came with your computer and the SL upgrade disc (if your computer came with Snow Leopard).
    Although you can reinstall Lion via the Recovery HD, I always suggest upgrading users to create a back-up USB or DVD with the full installer. You see, the Recovery HD is stored in your HDD and it can become unbootable if your HDD dies in the future, therefore making it useless. Having a back-up DVD or USB installer, offers you a way to boot your Mac in case the HDD fails. The advantages of the USB or DVD installer is that you can install OSX Lion without the need of an internet connection; use it to install Lion on your other Macs; and have all the features of the Recovery HD partition.
    To create a back-up USB or DVD installer follow the instructions in these articles:
    For a DVD Installer:
    http://eggfreckles.com/notes/burning-a-lion-boot-disc/
    For a USB Install Key:
    http://www.eggfreckles.net/notes/installing-lion-clean/
    I own a MacBook Pro mid-2010 model and it runs OSX Lion fine, however I should warn that this OS has still some annoying bugs that need to be fixed. I would recommed you to hold buying OSX Lion until Apple releases the 10.7.3 update. After this release occurs it will release a OSX Lion installer that has that version bundled into it. This will install OSX Lion with the latest updates and create the appropiate caches for it, therefore eliminating the chances of corrupted caches.
    Hope this helps and write back if you have any questions!
    Happy Computing!
    EDIT:
    Forgot to mention that once you download the OSX Lion intaller it will launch automatically and guide you through the process. If you want to make a DVD or USB installer just close the installer and follow the instructions in the post. Under normal circumstances, the OSX Lion installer will delete itself one once the update is finished.
    Message was edited by: vea1083

  • Question: Upgrading 10.3.9 PDC to 10.4

    OK, so here's my situation:
    Running a Dual G5 Xserve with 10.3.9 as the Open Directory Master and the Primary Domain Controller for my Windows clients (around 150 Win PCs).
    I also have an old G4 Tower running 10.3.9 as an OD Replica.
    What is the best way to upgrade these machines to 10.4 while still maintaining my Windows domain? I attempted this upgrade a few months back, with disastrous results. I tried to upgrade 10.3 to 10.4, and the XServe was unbootable. So I did a clean install of 10.4, which worked, but screwed my Windows clients, as the new installation of 10.4 as a PDC gave the domain a new SID, and the Win clients refused to see it as the same domain.
    I found some hints on the web about resetting the SID to the original setting, but this did not work. Eventually, I rolled my XServe back to 10.3.9 and gave up on the whole thing. I'm about ready to try again, but would welcome any advice from people who have upgraded an OS X PDC. How did you do it?
    I know that in general, a clean install of 10.4 is recommended over an upgrade from 10.3. But it seems the only reliable way to keep the domain identification stable is by upgrading.
    Of course, if I were able to have a Backup Domain Controller (BDC), it would maintain the domain identification through this process. But 10.3 doesn't permit a BDC role, and a 10.4 server can't be a BDC for a 10.3 PDC. It's a Catch-22!!
    One strategy I've considered is just to build a temporary Windows NT box and use it as the BDC through this process, allowing it to maintain the domain consistency while the Macs are being upgraded. An inelegant solution, but if it works and saves me some headaches, I'm all for it. Has anyone done this? I'm imagining I would build the NT box, set its role to BDC, then take the XServe offline, promote the NT box to PDC, rebuild the XServe with Tiger, promote it to PDC and demote the NT box back to BDC.
    Eventually, I would then rebuild the G4 Tower or another Mac with Tiger server and use it as the OD Replica and BDC, and take the NT box out of the loop. Would this work? Would I still have to export/import my OD and password database? Or would it replicate to the NT BDC?
    Any suggestions from anyone who's already fought this battle would be greatly appreciated.

    Hey, let's revive this thread for a bit. I am going through some test simulations of our server setup, but I have a twist to it. First off, my primary server is similar to the situation described here, but I was successful doing a straight upgrade. It's phase 2 I am having issues with, and I'm wondering if anyone has experience with that. Specifically, setting up a BDC on a separate subnet and having it actually do what it's supposed to...
    So my saga so far:
    1) Set up an isolated network with it's own gateway router. Do the same for a second subnet. Connect the two with a cheap Linksys router set to router mode. This represents my Local LAN and my Remote LAN, connected by VPN tunnel.
    2) Clone my primary G5 running 10.3.9 as OD Master/PDC to a spare box. (SuperDuper Rules!) Boot it up on the test Local LAN. Immediately set a static route to the pseudo-VPN tunnel IP.
    3) Install brand new 10.4.6 on a different box on the second subnet in prep for the BDC test. Set the reverse static route. Make sure everybody pings happily. (For those that want to say don't set static routes in the host, set them in the gateway router, I tried that, but my crappy Linksys routers couldn't handle it.)
    4) Uninstall various 3rd party stuff like Norton Antivirus and retrospect from the clone. Clean up as best I can in prep for upgrade.
    5) Upgrade. (This didn't work at first using an external firewire drive, so I got a 250GB IDE drive for the simulation Mac, a Quicksilver 2002.) After upgrade, let it commune with Apple for a while to get to 10.4.6.
    6) For whatever reason, after the upgrade I had to go into Directory Access and set the LDAP path up again. That's not even Samba specific, so I'm surprised it's not covered by upgrades. Another issue unresolved is a corruption of my DNS config. In the GUI for DNS I would see zones active on the Overview tab, but nothing on the Configure Zones tab. I was resolving, but I wasn't able to modify the zone! After adding the same zone, deleting it again, and adding it again, (and maybe one more cycle, with odd behaviour all the time with fields blanking themselves out magically) it finally stabilized.
    At this point, I am able to log in from my Windows machines. Whew! But my task is half over.
    7) I go to my Remote box and set it up as OD replica, per the BDC tech note. Some glitches here, mostly having to do with static routes. (best way in 10.4 to make 'em persistant?) Eventually I can use Workgroup manager on either box and the changes are instantly mirrored. Yay!
    8) Modify the DNS on both to have the other as seconday zone. Set WINS on the replica to refer to the master. A question here: I would expect that to set WINS Proxy in the smb.conf file, but it doesn't?
    9) Make it a BDC!
    10) DHCP is set by the gateway router, not the Mac, so I make sure that DNS and WINS are set properly.
    11) Copy the login batch file from the primary to the replica NETLOGON directory.
    12) Add explicit Profile directories to the test user under the Windows tab. (\\server1\users\profiles\testuser)
    13) Move a test PC to the second subnet, boot up, add the correct persistent route, don't forget to remove the incorrect one! And yes, it logs in just fine, I get my profile shipped to me over the pseudoVPN, get my drives mapped by the batch file, Yay!
    For those of you that have stuck with me this far, Thanks! This is where I was late yesterday, and I did one final test. I shut down the Master, leaving the BDC system up. I rebooted the Windows PC. Tried to logon. Didn't work. Basically a domain controller failure. What do I do next? I went home.
    I will be working out a better documented pattern of behaviour later this week, but I'm fairly disappointed by early results. I need to test a Mac in the same model, to see if the OD replica is working or not, since Samba is pulling from it. Any sage advice from those of you with WAN links, trying to get a PDC/BDC model working reliably?
    TIA!
    jth
    Xserver G5 2GHz/1.0GB   Mac OS X (10.3.9)  

  • Grub2 1.98-2 upgrade no boot!

    I'm not sure if it was my fault, but the last upgrade of grub make my system unbootable, because moved /boot/grub.cfg to /boot/grub.cfg.pacsave and there was no /boot/grub.cfg anymore. When I rebooted the system showed the grub mini-shell.
    I had to restore using an usb-arch-install

    pressh wrote:
    yes sorry about that....
    it's already fixed in -3...failed to notice that grub.cfg would be removed when removing it from the backup array --> moved it back.
    also the example file is now installed as grub.cfg.example.
    You can be lucky about the fact, that I am not in the same room as you
    Here it is 24:00 CET and I just wanted to reboot my macbook, to test "all the new updates" and got the shock of my life!
    But in fact I thank you for your work, now I can boot manually with Grub2
    Everyone who is in panic and need help, read this:
    http://grub.enbug.org/Manual#head-4ec5b … a094d943bb
    *Read with cat /boot/grub/grub.conf.pacsave
    *load kernel configuration with linux /boot/kernelname root=/dev/... initrd ...
    *boot
    As Picard would say "Engage!".
    Goodnight from europe/germany.

  • BIOS upgrade? Or don't bother? Or Microcode ?

    Hi all, I have a Thinkpad X220 with the original "stone age" (2011) BIOS. I don't have problems with the laptop, but I don't want to miss possible later optimalisations. (The only problem I have is the fan going wild from time to time, I'm looking into "thinkfan" solutions, so I consider that solved)
    What do you guys advise regarding the BIOS? I am torn:
    a) Upgrade it to the latest Lenovo bios
    b) Leave it alone: "don't fix it if it ain't broken"
    c) Microcode. Per the Arch Wiki: " .... . Intel releases microcode updates to correct processor behavior .....While the regular approach to getting this microcode update is via a BIOS upgrade, Intel realizes that this can be an administrative hassle. The Linux operating system and VMware ESX products have a mechanism to update the microcode after booting....."
    [ d) coreboot. Unfortunately, flashing it is hard and it misses lot of functions.... This would have been the best solution, maybe later, when (if) the image is improved.... http://www.coreboot.org/Board:lenovo/x230     So I dismiss this solution for now ]
    My idea is a):  just upgrade to a newer BIOS.   What would you advise me?

    PieterGen wrote:
    Hi all, I have a Thinkpad X220 with the original "stone age" (2011) BIOS. I don't have problems with the laptop, but I don't want to miss possible later optimalisations. (The only problem I have is the fan going wild from time to time, I'm looking into "thinkfan" solutions, so I consider that solved)
    What do you guys advise regarding the BIOS? I am torn:
    a) Upgrade it to the latest Lenovo bios
    I recently upgraded the Intel bios on a Sandy Bridge board (an Intel board with sandy bridge i5, somewhat like yours).  It bricked the board.   Opinion in the Intel support forums was that the latest firmware would detect some sandy bridge boards as if they were Ivy Bridge and that _maybe_ my board would be able to boot if I upgraded the processor.  It's cheaper to upgrade the board so I ended up tossing a perfectly good but unbootable motherboard into the trash.  (and for the record, I am VERY happy with my new Gigabyte Z77 board -- GA-Z77X-UD3H).  You have been warned.

  • Does re-installing OSX from scratch make XP unbootable?

    I'm considering upgrading to Leopard, and in doing so would like to wipe my Tiger installation and start from scratch. Will doing so wipe some boot sector stuff so that my Bootcamp XP partition will be unbootable? I hardly use OSX and use Windows 99% of the time, so preserving my existing XP installation is far more important than upgrading OSX.
    Any advice appreciated.

    Hi minimoog,
    the 'boot'-informations are saved in the 200MB-EFI-partitions on the harddisk, which usually are invisible.
    If you only erase the Tiger partition and in no way alter the partitions or repartition your HD, the the Windows partition will stay intact and bootable.
    Personally I would suggest making a backup of your Windows partition before the Leopard installation, just in case.
    Regards
    Stefan

  • Upgrade MBP with SSD+HDD to Mountain Lion

    I have a MBP mid-2009 with 4Gb RAM, which I replaced the HDD with an SSD and moved the HDD to the optical bay. The current Snow Leopard OS boots from the SSD (all system files are in the SSD), however I keep the home folders (/Users) in the HDD. This is because my SSD is small while I have a lot of large personal files. Now I want to upgrade the OS to Mountain Lion (required to run certain apps). My main concern is whether the ML upgrade will break my system configuration (perhaps lose files, unbootable), because my SSD+HDD system configuration is nonstandard. Any experience or tips are very welcome. Thanks!

    You shouldn't have any problems. However, I will suggest the following:
    Repair your hard drive and permissions before upgrading.
    Make a backup of your current system, preferable a bootable one, just in case.
    After you download Mountain Lion, you might wish to do this:
    Make Your Own Mountain/Lion Installer
    1. After downloading Mountain/Lion you must first save the Install Mac OS X Mountain/
        Lion application. After Mountain/Lion downloads DO NOT click on the Install button.
        Go to your Applications folder and make a copy of the Mountain/Lion installer. Move
        the copy into your Downloads folder. Now you can click on the Install button. You
        must do this because the installer deletes itself automatically when it finishes
        installing.
    2. Get a USB flash drive that is at least 8 GBs. Prep this flash drive as follows:
      a. Open Disk Utility in your Utilities folder.
      b. After DU loads select your flash drive (this is the entry with the mfgr.'s ID and size) from the left
          side list. Click on the Partition tab in the DU main window.
      c. Under the Volume Scheme heading set the number of partitions from the drop down menu to one.     
          Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the
          partition scheme to GUID then click on the OK button. Click on the Partition button and wait until
          the process has completed.
      d. Select the volume you just created (this is the sub-entry under the drive entry) from the left side
          list. Click on the Erase tab in the DU main window.
      e. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the
          button for Zero Data and click on OK to return to the Erase window.
      f. Click on the Erase button. The format process can take up to an hour depending upon the flash
         drive size.
    3. Locate the saved Mountain/Lion installer in your Downloads folder. CTRL- or RIGHT-click on the installer and select Show Package Contents from the contextual menu. Double-click on the Contents folder to open it. Double-click on the SharedSupport folder. In this folder you will see a disc image named InstallESD.dmg.
    4. Plug in your freshly prepared USB flash drive. You are going to clone the content of the InstallESD.dmg disc image to the flash drive as follows:
      a. Double-click on the InstallESD.dmg file to mount it on your Desktop.
      b. Open Disk Utility.
      c. Select the USB flash drive from the left side list.
      d. Click on the Restore tab in the DU main window.
      e. Select the USB flash drive volume from the left side list and drag it to the Destination entry field.
      f. Drag the mounted disc icon from the Desktop into the Source entry field.
      g. Double-check you got it right, then click on the Restore button.
    When the clone is completed you have a fully bootable installer that you can use without having to re-download Mountain/Lion.
    Note: The term Mountain/Lion used above means Lion or Mountain Lion.
    As an alternative to the above (you still have to do your own download of Lion/Mountain Lion) you can try using Lion DiskMaker 2.0 that automates the process of Steps 2 through 4.

Maybe you are looking for

  • Trying to save as (print to) pdf, saves as multiple files

    Hello, I'm trying to print to a pdf file from my version of word (not the most recent version, but the one right before that). It is being saved as two separate files, the first containing the first page, the next containing the second and third page

  • Vista Share NOT showing up in OS X 10.5

    Okay here is the deal, I can view my Mac share just fine on the Vista machine, but the vista share does not show up on my mac machine in Finder. What's up? I can access the Vista share by typing: smb://192.168.1.106. Things work fine that way... But

  • WinXP, Adobe 9 Pro Extended Uninstall Error 2711 ('ARM')

    Using windows XP and trying to uninstall Adobe Acrobate 9 Pro Extended and i am getting the following error: Error 2711. The specified Feature name ('ARM') not found in Feature table. And it cancels the uninstall. Any advice?

  • How do I embed a PDF as an object in a Word document?

    Up until January 2014, I could easily embed a PDF ( or any other file ) in a Word document.  Now I cannot embed a PDF object as an icon.  Does anyone have a work around for this?

  • Write to spreadsheet adds carriage return

    I am using build array function to put together a number of strings and build an array of strings.  The build array is in a while loop.  A new line is added to the array every loop.  I am using write to spread sheet function to save the spreadsheet t