Corruption of volume allocation

Hello.
I have a PPC G5 IMac, 10.4.6 w/ all latest updates. Sometimes upon wake-up it freezes. Lately upon startup, I've been having serious issues. In short, no boot. No safe startup. It will get to the gray-apple screen and the pinwheel just goes around forever. The only boot is via CD. Using Techtool Pro 4.1.1. I find that the volume allocation bitmap is bad with a (-90) code. Techtool Pro appears to fix all the problems, and a normal restart occurs with no problems thereafter, until the harddrive sleeps or a shutdown happens, then the startup problems occur again. It wont even boot up from the Techtool E-drive, only the CD.
Ideas?
Thanks
iMac G5 20in LCD   Mac OS X (10.4.6)  

Hi, Sharkin.
1. Run the procedure outlined in my "Resolving Disk, Permission, and Cache Corruption" FAQ. Perform the steps therein in the order specified. In particular, pay attention to Steps 1 and 2.
2. De-selecting "Put the hard disk(s) to sleep when possible" in Energy Saver preferences does not fully prevent hard drive sleep unless you also set Computer sleep to Never. For details as to why, see my "Spinning Beach Ball Of Death (SBBOD)" FAQ, specifically the section entitled "SBBOD spins for 30-35 seconds. You may hear your hard drives spinning up."
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Similar Messages

  • A corrupted CoreStorage volume... what to do next?

    Hi all,
    I got my new computer (MacBook Pro 13-inch Early-2011 purchased from the Apple Online Store) with Lion installed. One of the best features in Lion is the revamped FileVault which uses CoreStorage to encrypt the whole disk.
    Everything was fine until I got back from my vacation and found my computer unable to boot. I have tried everything, resetting from PRAM, etc but to no avail. I booted into single user mode and found several messages stating "CoreStorageFsck: <Bootstrap TXG#5771@1879> : cksum mismatch". When I booted into Recovery HD and tried to use Disk Utility to repair my disk, Disk Utility told me the repair failed, and the corestorage volume was corrupted.
    I do have a backup, but that backup was made over 10 days ago on my old computer running 10.6.8. Since CoreStorage is a new feature in 10.7, my old computer isn't able to read data from the hard disk in my new MacBook Pro as well.
    I am totally frustrated and do not know anything else I could try. I contacted telephone support but they told me to do a "Erase and Install", but I'd appreciate if I could retain the data in the 10 days.
    Help wanted. Does anyone know how to fix the corruption when Disk Utility cannot?
    Regards,
    Kim (qzyyy)

    Hi Kim,
    I'd never trust FileFault without a daily or hourly clone, sorry I can't help with the present situation.

  • 10.5.8 update corrupted the Volume Structure of my MacBook Pro and iMac

    After installing the 10.5.8 update on my Macbook Pro AND my iMac, BOTH computers refuse to boot up. If I boot from a TechTool Deluxe DVD and run the system scan, It fails both the Directory Scan and the Volume Structure test. The only common application on these computers is the Fusion PC emulator. I was reading that the newest update fixed problems with this application. PLEASE HELP!!!

    Some general advice on updating:
    It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
    So before you do anything else:
    If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
    Turn off sleep mode for both screen and hard disk.
    Disconnect all peripherals except your keyboard and mouse.
    1. Repair Permissions (in Disk Utility)
    2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
    At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
    3. Download the correct version of the COMBO update from the Apple download site.
    The Combo updater of Leopard 10.5.8 can be found here:
    http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
    If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
    Full details about the 10.5.8 update here: http://support.apple.com/kb/HT3606
    More information on using Software Updater here:
    http://support.apple.com/kb/TA24901?viewlocale=en_US
    Using the Combo updater ensures that all system files changed since the original 10.5.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.5.7 to 10.5.8. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
    Now proceed as follows:
    4. Close all applications and turn off energy saving and screensaver.
    5. Unplug all peripherals except your keyboard and mouse.
    6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
    7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
    8. Once your Mac is awake, repair permissions again, and you should be good to go!
    If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
    9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 4.
    N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
    Lastly, Apple's own article on the subject of Software Update may also be useful reading:
    http://docs.info.apple.com/article.html?artnum=106695
    If you are updating Safari (or just have):
    Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
    So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari.
    Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party add-on.
    Additional tips on software installation here:
    http://docs.info.apple.com/article.html?artnum=106692
    To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
    Again, the advice is to remove all Input Managers from the following directories:
    • /Library/InputManagers
    • ~/Library/InputManagers
    especially prior to system updates (they can always be added back one-by-one later).

  • LVM Volumes not available after update

    Hi All!
    I haven't updated my system for about two months and today I updated it. Now I have the problem that I cannot boot properly. I have my root partition in an LVM volume and on boot I get the message
    ERROR: device 'UUID=xxx' not found. Skipping fs
    ERROR: Unable to find root device 'UUID=xxx'
    After that I land in the recovery shell. After some research I found, that "lvm lvdisplay" showed that my volumes where not available and I had to reenable them with "lvm vgchange -a y".
    Issuing any lvm command also produced the following warning:
    WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
    Anyway, after issuing the commands and exiting the recovery shell, the system booted again. However, I would prefer being able to boot without manual actions.
    Thanks in advance!
    Further information:
    vgdisplay
    --- Volume group ---
    VG Name ArchLVM
    System ID
    Format lvm2
    Metadata Areas 1
    Metadata Sequence No 3
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 2
    Open LV 1
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 232.69 GiB
    PE Size 4.00 MiB
    Total PE 59568
    Alloc PE / Size 59568 / 232.69 GiB
    Free PE / Size 0 / 0
    VG UUID SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5
    lvdisplay (LV Status was 'not available' right after booting)
    --- Logical volume ---
    LV Path /dev/ArchLVM/Swap
    LV Name Swap
    VG Name ArchLVM
    LV UUID XRYBrz-LojR-k6SD-XIxV-wHnY-f3VG-giKL6V
    LV Write Access read/write
    LV Creation host, time archiso, 2014-05-16 14:43:06 +0200
    LV Status available
    # open 0
    LV Size 8.00 GiB
    Current LE 2048
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:0
    --- Logical volume ---
    LV Path /dev/ArchLVM/Root
    LV Name Root
    VG Name ArchLVM
    LV UUID lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv
    LV Write Access read/write
    LV Creation host, time archiso, 2014-05-16 14:43:27 +0200
    LV Status available
    # open 1
    LV Size 224.69 GiB
    Current LE 57520
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:1
    /etc/fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/mapper/ArchLVM-Root
    UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 / ext4 rw,relatime,data=ordered 0 1
    #/dev/mapper/ArchLVM-Root / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda1
    UUID=72691888-a781-4cdd-a98e-2613d87925d0 /boot ext2 rw,relatime 0 2
    /etc/mkinitcpio.conf
    # 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 last, so it may be used to
    # override the actual binaries included by a given hook
    # 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.
    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 block filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev block filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev block mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev block lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    /boot/grub/grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod lvm
    insmod ext2
    set root='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv' 2db82d1a-47a4-4e30-a819-143e8fb75199
    else
    search --no-floppy --fs-uuid --set=root 2db82d1a-47a4-4e30-a819-143e8fb75199
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    Last edited by Kirodema (2014-07-16 07:31:34)

    use_lvmetad = 0
    lvm2-lvmetad is not enabled or running on my system. Shall I activate it?
    # This is an example configuration file for the LVM2 system.
    # It contains the default settings that would be used if there was no
    # /etc/lvm/lvm.conf file.
    # Refer to 'man lvm.conf' for further information including the file layout.
    # To put this file in a different directory and override /etc/lvm set
    # the environment variable LVM_SYSTEM_DIR before running the tools.
    # N.B. Take care that each setting only appears once if uncommenting
    # example settings in this file.
    # This section allows you to set the way the configuration settings are handled.
    config {
    # If enabled, any LVM2 configuration mismatch is reported.
    # This implies checking that the configuration key is understood
    # by LVM2 and that the value of the key is of a proper type.
    # If disabled, any configuration mismatch is ignored and default
    # value is used instead without any warning (a message about the
    # configuration key not being found is issued in verbose mode only).
    checks = 1
    # If enabled, any configuration mismatch aborts the LVM2 process.
    abort_on_errors = 0
    # Directory where LVM looks for configuration profiles.
    profile_dir = "/etc/lvm/profile"
    # This section allows you to configure which block devices should
    # be used by the LVM system.
    devices {
    # Where do you want your volume groups to appear ?
    dir = "/dev"
    # An array of directories that contain the device nodes you wish
    # to use with LVM2.
    scan = [ "/dev" ]
    # If set, the cache of block device nodes with all associated symlinks
    # will be constructed out of the existing udev database content.
    # This avoids using and opening any inapplicable non-block devices or
    # subdirectories found in the device directory. This setting is applied
    # to udev-managed device directory only, other directories will be scanned
    # fully. LVM2 needs to be compiled with udev support for this setting to
    # take effect. N.B. Any device node or symlink not managed by udev in
    # udev directory will be ignored with this setting on.
    obtain_device_list_from_udev = 1
    # If several entries in the scanned directories correspond to the
    # same block device and the tools need to display a name for device,
    # all the pathnames are matched against each item in the following
    # list of regular expressions in turn and the first match is used.
    preferred_names = [ ]
    # Try to avoid using undescriptive /dev/dm-N names, if present.
    # preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
    # A filter that tells LVM2 to only use a restricted set of devices.
    # The filter consists of an array of regular expressions. These
    # expressions can be delimited by a character of your choice, and
    # prefixed with either an 'a' (for accept) or 'r' (for reject).
    # The first expression found to match a device name determines if
    # the device will be accepted or rejected (ignored). Devices that
    # don't match any patterns are accepted.
    # Be careful if there there are symbolic links or multiple filesystem
    # entries for the same device as each name is checked separately against
    # the list of patterns. The effect is that if the first pattern in the
    # list to match a name is an 'a' pattern for any of the names, the device
    # is accepted; otherwise if the first pattern in the list to match a name
    # is an 'r' pattern for any of the names it is rejected; otherwise it is
    # accepted.
    # Don't have more than one filter line active at once: only one gets used.
    # Run vgscan after you change this parameter to ensure that
    # the cache file gets regenerated (see below).
    # If it doesn't do what you expect, check the output of 'vgscan -vvvv'.
    # If lvmetad is used, then see "A note about device filtering while
    # lvmetad is used" comment that is attached to global/use_lvmetad setting.
    # By default we accept every block device:
    filter = [ "a/.*/" ]
    # Exclude the cdrom drive
    # filter = [ "r|/dev/cdrom|" ]
    # When testing I like to work with just loopback devices:
    # filter = [ "a/loop/", "r/.*/" ]
    # Or maybe all loops and ide drives except hdc:
    # filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
    # Use anchors if you want to be really specific
    # filter = [ "a|^/dev/hda8$|", "r/.*/" ]
    # Since "filter" is often overridden from command line, it is not suitable
    # for system-wide device filtering (udev rules, lvmetad). To hide devices
    # from LVM-specific udev processing and/or from lvmetad, you need to set
    # global_filter. The syntax is the same as for normal "filter"
    # above. Devices that fail the global_filter are not even opened by LVM.
    # global_filter = []
    # The results of the filtering are cached on disk to avoid
    # rescanning dud devices (which can take a very long time).
    # By default this cache is stored in the /etc/lvm/cache directory
    # in a file called '.cache'.
    # It is safe to delete the contents: the tools regenerate it.
    # (The old setting 'cache' is still respected if neither of
    # these new ones is present.)
    # N.B. If obtain_device_list_from_udev is set to 1 the list of
    # devices is instead obtained from udev and any existing .cache
    # file is removed.
    cache_dir = "/etc/lvm/cache"
    cache_file_prefix = ""
    # You can turn off writing this cache file by setting this to 0.
    write_cache_state = 1
    # Advanced settings.
    # List of pairs of additional acceptable block device types found
    # in /proc/devices with maximum (non-zero) number of partitions.
    # types = [ "fd", 16 ]
    # If sysfs is mounted (2.6 kernels) restrict device scanning to
    # the block devices it believes are valid.
    # 1 enables; 0 disables.
    sysfs_scan = 1
    # By default, LVM2 will ignore devices used as component paths
    # of device-mapper multipath devices.
    # 1 enables; 0 disables.
    multipath_component_detection = 1
    # By default, LVM2 will ignore devices used as components of
    # software RAID (md) devices by looking for md superblocks.
    # 1 enables; 0 disables.
    md_component_detection = 1
    # By default, if a PV is placed directly upon an md device, LVM2
    # will align its data blocks with the md device's stripe-width.
    # 1 enables; 0 disables.
    md_chunk_alignment = 1
    # Default alignment of the start of a data area in MB. If set to 0,
    # a value of 64KB will be used. Set to 1 for 1MiB, 2 for 2MiB, etc.
    # default_data_alignment = 1
    # By default, the start of a PV's data area will be a multiple of
    # the 'minimum_io_size' or 'optimal_io_size' exposed in sysfs.
    # - minimum_io_size - the smallest request the device can perform
    # w/o incurring a read-modify-write penalty (e.g. MD's chunk size)
    # - optimal_io_size - the device's preferred unit of receiving I/O
    # (e.g. MD's stripe width)
    # minimum_io_size is used if optimal_io_size is undefined (0).
    # If md_chunk_alignment is enabled, that detects the optimal_io_size.
    # This setting takes precedence over md_chunk_alignment.
    # 1 enables; 0 disables.
    data_alignment_detection = 1
    # Alignment (in KB) of start of data area when creating a new PV.
    # md_chunk_alignment and data_alignment_detection are disabled if set.
    # Set to 0 for the default alignment (see: data_alignment_default)
    # or page size, if larger.
    data_alignment = 0
    # By default, the start of the PV's aligned data area will be shifted by
    # the 'alignment_offset' exposed in sysfs. This offset is often 0 but
    # may be non-zero; e.g.: certain 4KB sector drives that compensate for
    # windows partitioning will have an alignment_offset of 3584 bytes
    # (sector 7 is the lowest aligned logical block, the 4KB sectors start
    # at LBA -1, and consequently sector 63 is aligned on a 4KB boundary).
    # But note that pvcreate --dataalignmentoffset will skip this detection.
    # 1 enables; 0 disables.
    data_alignment_offset_detection = 1
    # If, while scanning the system for PVs, LVM2 encounters a device-mapper
    # device that has its I/O suspended, it waits for it to become accessible.
    # Set this to 1 to skip such devices. This should only be needed
    # in recovery situations.
    ignore_suspended_devices = 0
    # ignore_lvm_mirrors: Introduced in version 2.02.104
    # This setting determines whether logical volumes of "mirror" segment
    # type are scanned for LVM labels. This affects the ability of
    # mirrors to be used as physical volumes. If 'ignore_lvm_mirrors'
    # is set to '1', it becomes impossible to create volume groups on top
    # of mirror logical volumes - i.e. to stack volume groups on mirrors.
    # Allowing mirror logical volumes to be scanned (setting the value to '0')
    # can potentially cause LVM processes and I/O to the mirror to become
    # blocked. This is due to the way that the "mirror" segment type handles
    # failures. In order for the hang to manifest itself, an LVM command must
    # be run just after a failure and before the automatic LVM repair process
    # takes place OR there must be failures in multiple mirrors in the same
    # volume group at the same time with write failures occurring moments
    # before a scan of the mirror's labels.
    # Note that these scanning limitations do not apply to the LVM RAID
    # types, like "raid1". The RAID segment types handle failures in a
    # different way and are not subject to possible process or I/O blocking.
    # It is encouraged that users set 'ignore_lvm_mirrors' to 1 if they
    # are using the "mirror" segment type. Users that require volume group
    # stacking on mirrored logical volumes should consider using the "raid1"
    # segment type. The "raid1" segment type is not available for
    # active/active clustered volume groups.
    # Set to 1 to disallow stacking and thereby avoid a possible deadlock.
    ignore_lvm_mirrors = 1
    # During each LVM operation errors received from each device are counted.
    # If the counter of a particular device exceeds the limit set here, no
    # further I/O is sent to that device for the remainder of the respective
    # operation. Setting the parameter to 0 disables the counters altogether.
    disable_after_error_count = 0
    # Allow use of pvcreate --uuid without requiring --restorefile.
    require_restorefile_with_uuid = 1
    # Minimum size (in KB) of block devices which can be used as PVs.
    # In a clustered environment all nodes must use the same value.
    # Any value smaller than 512KB is ignored.
    # Ignore devices smaller than 2MB such as floppy drives.
    pv_min_size = 2048
    # The original built-in setting was 512 up to and including version 2.02.84.
    # pv_min_size = 512
    # Issue discards to a logical volumes's underlying physical volume(s) when
    # the logical volume is no longer using the physical volumes' space (e.g.
    # lvremove, lvreduce, etc). Discards inform the storage that a region is
    # no longer in use. Storage that supports discards advertise the protocol
    # specific way discards should be issued by the kernel (TRIM, UNMAP, or
    # WRITE SAME with UNMAP bit set). Not all storage will support or benefit
    # from discards but SSDs and thinly provisioned LUNs generally do. If set
    # to 1, discards will only be issued if both the storage and kernel provide
    # support.
    # 1 enables; 0 disables.
    issue_discards = 0
    # This section allows you to configure the way in which LVM selects
    # free space for its Logical Volumes.
    allocation {
    # When searching for free space to extend an LV, the "cling"
    # allocation policy will choose space on the same PVs as the last
    # segment of the existing LV. If there is insufficient space and a
    # list of tags is defined here, it will check whether any of them are
    # attached to the PVs concerned and then seek to match those PV tags
    # between existing extents and new extents.
    # Use the special tag "@*" as a wildcard to match any PV tag.
    # Example: LVs are mirrored between two sites within a single VG.
    # PVs are tagged with either @site1 or @site2 to indicate where
    # they are situated.
    # cling_tag_list = [ "@site1", "@site2" ]
    # cling_tag_list = [ "@*" ]
    # Changes made in version 2.02.85 extended the reach of the 'cling'
    # policies to detect more situations where data can be grouped
    # onto the same disks. Set this to 0 to revert to the previous
    # algorithm.
    maximise_cling = 1
    # Whether to use blkid library instead of native LVM2 code to detect
    # any existing signatures while creating new Physical Volumes and
    # Logical Volumes. LVM2 needs to be compiled with blkid wiping support
    # for this setting to take effect.
    # LVM2 native detection code is currently able to recognize these signatures:
    # - MD device signature
    # - swap signature
    # - LUKS signature
    # To see the list of signatures recognized by blkid, check the output
    # of 'blkid -k' command. The blkid can recognize more signatures than
    # LVM2 native detection code, but due to this higher number of signatures
    # to be recognized, it can take more time to complete the signature scan.
    use_blkid_wiping = 1
    # Set to 1 to wipe any signatures found on newly-created Logical Volumes
    # automatically in addition to zeroing of the first KB on the LV
    # (controlled by the -Z/--zero y option).
    # The command line option -W/--wipesignatures takes precedence over this
    # setting.
    # The default is to wipe signatures when zeroing.
    wipe_signatures_when_zeroing_new_lvs = 1
    # Set to 1 to guarantee that mirror logs will always be placed on
    # different PVs from the mirror images. This was the default
    # until version 2.02.85.
    mirror_logs_require_separate_pvs = 0
    # Set to 1 to guarantee that cache_pool metadata will always be
    # placed on different PVs from the cache_pool data.
    cache_pool_metadata_require_separate_pvs = 0
    # Specify the minimal chunk size (in kiB) for cache pool volumes.
    # Using a chunk_size that is too large can result in wasteful use of
    # the cache, where small reads and writes can cause large sections of
    # an LV to be mapped into the cache. However, choosing a chunk_size
    # that is too small can result in more overhead trying to manage the
    # numerous chunks that become mapped into the cache. The former is
    # more of a problem than the latter in most cases, so we default to
    # a value that is on the smaller end of the spectrum. Supported values
    # range from 32(kiB) to 1048576 in multiples of 32.
    # cache_pool_chunk_size = 64
    # Set to 1 to guarantee that thin pool metadata will always
    # be placed on different PVs from the pool data.
    thin_pool_metadata_require_separate_pvs = 0
    # Specify chunk size calculation policy for thin pool volumes.
    # Possible options are:
    # "generic" - if thin_pool_chunk_size is defined, use it.
    # Otherwise, calculate the chunk size based on
    # estimation and device hints exposed in sysfs:
    # the minimum_io_size. The chunk size is always
    # at least 64KiB.
    # "performance" - if thin_pool_chunk_size is defined, use it.
    # Otherwise, calculate the chunk size for
    # performance based on device hints exposed in
    # sysfs: the optimal_io_size. The chunk size is
    # always at least 512KiB.
    # thin_pool_chunk_size_policy = "generic"
    # Specify the minimal chunk size (in KB) for thin pool volumes.
    # Use of the larger chunk size may improve performance for plain
    # thin volumes, however using them for snapshot volumes is less efficient,
    # as it consumes more space and takes extra time for copying.
    # When unset, lvm tries to estimate chunk size starting from 64KB
    # Supported values are in range from 64 to 1048576.
    # thin_pool_chunk_size = 64
    # Specify discards behaviour of the thin pool volume.
    # Select one of "ignore", "nopassdown", "passdown"
    # thin_pool_discards = "passdown"
    # Set to 0, to disable zeroing of thin pool data chunks before their
    # first use.
    # N.B. zeroing larger thin pool chunk size degrades performance.
    # thin_pool_zero = 1
    # This section that allows you to configure the nature of the
    # information that LVM2 reports.
    log {
    # Controls the messages sent to stdout or stderr.
    # There are three levels of verbosity, 3 being the most verbose.
    verbose = 0
    # Set to 1 to suppress all non-essential messages from stdout.
    # This has the same effect as -qq.
    # When this is set, the following commands still produce output:
    # dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck, pvdisplay,
    # pvs, version, vgcfgrestore -l, vgdisplay, vgs.
    # Non-essential messages are shifted from log level 4 to log level 5
    # for syslog and lvm2_log_fn purposes.
    # Any 'yes' or 'no' questions not overridden by other arguments
    # are suppressed and default to 'no'.
    silent = 0
    # Should we send log messages through syslog?
    # 1 is yes; 0 is no.
    syslog = 1
    # Should we log error and debug messages to a file?
    # By default there is no log file.
    #file = "/var/log/lvm2.log"
    # Should we overwrite the log file each time the program is run?
    # By default we append.
    overwrite = 0
    # What level of log messages should we send to the log file and/or syslog?
    # There are 6 syslog-like log levels currently in use - 2 to 7 inclusive.
    # 7 is the most verbose (LOG_DEBUG).
    level = 0
    # Format of output messages
    # Whether or not (1 or 0) to indent messages according to their severity
    indent = 1
    # Whether or not (1 or 0) to display the command name on each line output
    command_names = 0
    # A prefix to use before the message text (but after the command name,
    # if selected). Default is two spaces, so you can see/grep the severity
    # of each message.
    prefix = " "
    # To make the messages look similar to the original LVM tools use:
    # indent = 0
    # command_names = 1
    # prefix = " -- "
    # Set this if you want log messages during activation.
    # Don't use this in low memory situations (can deadlock).
    # activation = 0
    # Some debugging messages are assigned to a class and only appear
    # in debug output if the class is listed here.
    # Classes currently available:
    # memory, devices, activation, allocation, lvmetad, metadata, cache,
    # locking
    # Use "all" to see everything.
    debug_classes = [ "memory", "devices", "activation", "allocation",
    "lvmetad", "metadata", "cache", "locking" ]
    # Configuration of metadata backups and archiving. In LVM2 when we
    # talk about a 'backup' we mean making a copy of the metadata for the
    # *current* system. The 'archive' contains old metadata configurations.
    # Backups are stored in a human readable text format.
    backup {
    # Should we maintain a backup of the current metadata configuration ?
    # Use 1 for Yes; 0 for No.
    # Think very hard before turning this off!
    backup = 1
    # Where shall we keep it ?
    # Remember to back up this directory regularly!
    backup_dir = "/etc/lvm/backup"
    # Should we maintain an archive of old metadata configurations.
    # Use 1 for Yes; 0 for No.
    # On by default. Think very hard before turning this off.
    archive = 1
    # Where should archived files go ?
    # Remember to back up this directory regularly!
    archive_dir = "/etc/lvm/archive"
    # What is the minimum number of archive files you wish to keep ?
    retain_min = 10
    # What is the minimum time you wish to keep an archive file for ?
    retain_days = 30
    # Settings for the running LVM2 in shell (readline) mode.
    shell {
    # Number of lines of history to store in ~/.lvm_history
    history_size = 100
    # Miscellaneous global LVM2 settings
    global {
    # The file creation mask for any files and directories created.
    # Interpreted as octal if the first digit is zero.
    umask = 077
    # Allow other users to read the files
    #umask = 022
    # Enabling test mode means that no changes to the on disk metadata
    # will be made. Equivalent to having the -t option on every
    # command. Defaults to off.
    test = 0
    # Default value for --units argument
    units = "h"
    # Since version 2.02.54, the tools distinguish between powers of
    # 1024 bytes (e.g. KiB, MiB, GiB) and powers of 1000 bytes (e.g.
    # KB, MB, GB).
    # If you have scripts that depend on the old behaviour, set this to 0
    # temporarily until you update them.
    si_unit_consistency = 1
    # Whether or not to display unit suffix for sizes. This setting has
    # no effect if the units are in human-readable form (global/units="h")
    # in which case the suffix is always displayed.
    suffix = 1
    # Whether or not to communicate with the kernel device-mapper.
    # Set to 0 if you want to use the tools to manipulate LVM metadata
    # without activating any logical volumes.
    # If the device-mapper kernel driver is not present in your kernel
    # setting this to 0 should suppress the error messages.
    activation = 1
    # If we can't communicate with device-mapper, should we try running
    # the LVM1 tools?
    # This option only applies to 2.4 kernels and is provided to help you
    # switch between device-mapper kernels and LVM1 kernels.
    # The LVM1 tools need to be installed with .lvm1 suffices
    # e.g. vgscan.lvm1 and they will stop working after you start using
    # the new lvm2 on-disk metadata format.
    # The default value is set when the tools are built.
    # fallback_to_lvm1 = 0
    # The default metadata format that commands should use - "lvm1" or "lvm2".
    # The command line override is -M1 or -M2.
    # Defaults to "lvm2".
    # format = "lvm2"
    # Location of proc filesystem
    proc = "/proc"
    # Type of locking to use. Defaults to local file-based locking (1).
    # Turn locking off by setting to 0 (dangerous: risks metadata corruption
    # if LVM2 commands get run concurrently).
    # Type 2 uses the external shared library locking_library.
    # Type 3 uses built-in clustered locking.
    # Type 4 uses read-only locking which forbids any operations that might
    # change metadata.
    # N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # is set at the same time, LVM always issues a warning message about this
    # and then it automatically disables lvmetad use.
    locking_type = 1
    # Set to 0 to fail when a lock request cannot be satisfied immediately.
    wait_for_locks = 1
    # If using external locking (type 2) and initialisation fails,
    # with this set to 1 an attempt will be made to use the built-in
    # clustered locking.
    # If you are using a customised locking_library you should set this to 0.
    fallback_to_clustered_locking = 1
    # If an attempt to initialise type 2 or type 3 locking failed, perhaps
    # because cluster components such as clvmd are not running, with this set
    # to 1 an attempt will be made to use local file-based locking (type 1).
    # If this succeeds, only commands against local volume groups will proceed.
    # Volume Groups marked as clustered will be ignored.
    fallback_to_local_locking = 1
    # Local non-LV directory that holds file-based locks while commands are
    # in progress. A directory like /tmp that may get wiped on reboot is OK.
    locking_dir = "/run/lock/lvm"
    # Whenever there are competing read-only and read-write access requests for
    # a volume group's metadata, instead of always granting the read-only
    # requests immediately, delay them to allow the read-write requests to be
    # serviced. Without this setting, write access may be stalled by a high
    # volume of read-only requests.
    # NB. This option only affects locking_type = 1 viz. local file-based
    # locking.
    prioritise_write_locks = 1
    # Other entries can go here to allow you to load shared libraries
    # e.g. if support for LVM1 metadata was compiled as a shared library use
    # format_libraries = "liblvm2format1.so"
    # Full pathnames can be given.
    # Search this directory first for shared libraries.
    # library_dir = "/lib"
    # The external locking library to load if locking_type is set to 2.
    # locking_library = "liblvm2clusterlock.so"
    # Treat any internal errors as fatal errors, aborting the process that
    # encountered the internal error. Please only enable for debugging.
    abort_on_internal_errors = 0
    # Check whether CRC is matching when parsed VG is used multiple times.
    # This is useful to catch unexpected internal cached volume group
    # structure modification. Please only enable for debugging.
    detect_internal_vg_cache_corruption = 0
    # If set to 1, no operations that change on-disk metadata will be permitted.
    # Additionally, read-only commands that encounter metadata in need of repair
    # will still be allowed to proceed exactly as if the repair had been
    # performed (except for the unchanged vg_seqno).
    # Inappropriate use could mess up your system, so seek advice first!
    metadata_read_only = 0
    # 'mirror_segtype_default' defines which segtype will be used when the
    # shorthand '-m' option is used for mirroring. The possible options are:
    # "mirror" - The original RAID1 implementation provided by LVM2/DM. It is
    # characterized by a flexible log solution (core, disk, mirrored)
    # and by the necessity to block I/O while reconfiguring in the
    # event of a failure.
    # There is an inherent race in the dmeventd failure handling
    # logic with snapshots of devices using this type of RAID1 that
    # in the worst case could cause a deadlock.
    # Ref: https://bugzilla.redhat.com/show_bug.cgi?id=817130#c10
    # "raid1" - This implementation leverages MD's RAID1 personality through
    # device-mapper. It is characterized by a lack of log options.
    # (A log is always allocated for every device and they are placed
    # on the same device as the image - no separate devices are
    # required.) This mirror implementation does not require I/O
    # to be blocked in the kernel in the event of a failure.
    # This mirror implementation is not cluster-aware and cannot be
    # used in a shared (active/active) fashion in a cluster.
    # Specify the '--type <mirror|raid1>' option to override this default
    # setting.
    mirror_segtype_default = "raid1"
    # 'raid10_segtype_default' determines the segment types used by default
    # when the '--stripes/-i' and '--mirrors/-m' arguments are both specified
    # during the creation of a logical volume.
    # Possible settings include:
    # "raid10" - This implementation leverages MD's RAID10 personality through
    # device-mapper.
    # "mirror" - LVM will layer the 'mirror' and 'stripe' segment types. It
    # will do this by creating a mirror on top of striped sub-LVs;
    # effectively creating a RAID 0+1 array. This is suboptimal
    # in terms of providing redundancy and performance. Changing to
    # this setting is not advised.
    # Specify the '--type <raid10|mirror>' option to override this default
    # setting.
    raid10_segtype_default = "raid10"
    # The default format for displaying LV names in lvdisplay was changed
    # in version 2.02.89 to show the LV name and path separately.
    # Previously this was always shown as /dev/vgname/lvname even when that
    # was never a valid path in the /dev filesystem.
    # Set to 1 to reinstate the previous format.
    # lvdisplay_shows_full_device_path = 0
    # Whether to use (trust) a running instance of lvmetad. If this is set to
    # 0, all commands fall back to the usual scanning mechanisms. When set to 1
    # *and* when lvmetad is running (automatically instantiated by making use of
    # systemd's socket-based service activation or run as an initscripts service
    # or run manually), the volume group metadata and PV state flags are obtained
    # from the lvmetad instance and no scanning is done by the individual
    # commands. In a setup with lvmetad, lvmetad udev rules *must* be set up for
    # LVM to work correctly. Without proper udev rules, all changes in block
    # device configuration will be *ignored* until a manual 'pvscan --cache'
    # is performed. These rules are installed by default.
    # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped
    # before changing use_lvmetad to 1 and started again afterwards.
    # If using lvmetad, the volume activation is also switched to automatic
    # event-based mode. In this mode, the volumes are activated based on
    # incoming udev events that automatically inform lvmetad about new PVs
    # that appear in the system. Once the VG is complete (all the PVs are
    # present), it is auto-activated. The activation/auto_activation_volume_list
    # setting controls which volumes are auto-activated (all by default).
    # A note about device filtering while lvmetad is used:
    # When lvmetad is updated (either automatically based on udev events
    # or directly by pvscan --cache <device> call), the devices/filter
    # is ignored and all devices are scanned by default. The lvmetad always
    # keeps unfiltered information which is then provided to LVM commands
    # and then each LVM command does the filtering based on devices/filter
    # setting itself.
    # To prevent scanning devices completely, even when using lvmetad,
    # the devices/global_filter must be used.
    # N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # is set at the same time, LVM always issues a warning message about this
    # and then it automatically disables lvmetad use.
    use_lvmetad = 0
    # Full path of the utility called to check that a thin metadata device
    # is in a state that allows it to be used.
    # Each time a thin pool needs to be activated or after it is deactivated
    # this utility is executed. The activation will only proceed if the utility
    # has an exit status of 0.
    # Set to "" to skip this check. (Not recommended.)
    # The thin tools are available as part of the device-mapper-persistent-data
    # package from https://github.com/jthornber/thin-provisioning-tools.
    # thin_check_executable = "/usr/bin/thin_check"
    # Array of string options passed with thin_check command. By default,
    # option "-q" is for quiet output.
    # With thin_check version 2.1 or newer you can add "--ignore-non-fatal-errors"
    # to let it pass through ignorable errors and fix them later.
    # thin_check_options = [ "-q" ]
    # Full path of the utility called to repair a thin metadata device
    # is in a state that allows it to be used.
    # Each time a thin pool needs repair this utility is executed.
    # See thin_check_executable how to obtain binaries.
    # thin_repair_executable = "/usr/bin/thin_repair"
    # Array of extra string options passed with thin_repair command.
    # thin_repair_options = [ "" ]
    # Full path of the utility called to dump thin metadata content.
    # See thin_check_executable how to obtain binaries.
    # thin_dump_executable = "/usr/bin/thin_dump"
    # If set, given features are not used by thin driver.
    # This can be helpful not just for testing, but i.e. allows to avoid
    # using problematic implementation of some thin feature.
    # Features:
    # block_size
    # discards
    # discards_non_power_2
    # external_origin
    # metadata_resize
    # external_origin_extend
    # thin_disabled_features = [ "discards", "block_size" ]
    activation {
    # Set to 1 to perform internal checks on the operations issued to
    # libdevmapper. Useful for debugging problems with activation.
    # Some of the checks may be expensive, so it's best to use this
    # only when there seems to be a problem.
    checks = 0
    # Set to 0 to disable udev synchronisation (if compiled into the binaries).
    # Processes will not wait for notification from udev.
    # They will continue irrespective of any possible udev processing
    # in the background. You should only use this if udev is not running
    # or has rules that ignore the devices LVM2 creates.
    # The command line argument --nodevsync takes precedence over this setting.
    # If set to 1 when udev is not running, and there are LVM2 processes
    # waiting for udev, run 'dmsetup udevcomplete_all' manually to wake them up.
    udev_sync = 1
    # Set to 0 to disable the udev rules installed by LVM2 (if built with
    # --enable-udev_rules). LVM2 will then manage the /dev nodes and symlinks
    # for active logical volumes directly itself.
    # N.B. Manual intervention may be required if this setting is changed
    # while any logical volumes are active.
    udev_rules = 1
    # Set to 1 for LVM2 to verify operations performed by udev. This turns on
    # additional checks (and if necessary, repairs) on entries in the device
    # directory after udev has completed processing its events.
    # Useful for diagnosing problems with LVM2/udev interactions.
    verify_udev_operations = 0
    # If set to 1 and if deactivation of an LV fails, perhaps because
    # a process run from a quick udev rule temporarily opened the device,
    # retry the operation for a few seconds before failing.
    retry_deactivation = 1
    # How to fill in missing stripes if activating an incomplete volume.
    # Using "error" will make inaccessible parts of the device return
    # I/O errors on access. You can instead use a device path, in which
    # case, that device will be used to in place of missing stripes.
    # But note that using anything other than "error" with mirrored
    # or snapshotted volumes is likely to result in data corruption.
    missing_stripe_filler = "error"
    # The linear target is an optimised version of the striped target
    # that only handles a single stripe. Set this to 0 to disable this
    # optimisation and always use the striped target.
    use_linear_target = 1
    # How much stack (in KB) to reserve for use while devices suspended
    # Prior to version 2.02.89 this used to be set to 256KB
    reserved_stack = 64
    # How much memory (in KB) to reserve for use while devices suspended
    reserved_memory = 8192
    # Nice value used while devices suspended
    process_priority = -18
    # If volume_list is defined, each LV is only activated if there is a
    # match against the list.
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # If any host tags exist but volume_list is not defined, a default
    # single-entry list containing "@*" is assumed.
    # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # If auto_activation_volume_list is defined, each LV that is to be
    # activated with the autoactivation option (--activate ay/-a ay) is
    # first checked against the list. There are two scenarios in which
    # the autoactivation option is used:
    # - automatic activation of volumes based on incoming PVs. If all the
    # PVs making up a VG are present in the system, the autoactivation
    # is triggered. This requires lvmetad (global/use_lvmetad=1) and udev
    # to be running. In this case, "pvscan --cache -aay" is called
    # automatically without any user intervention while processing
    # udev events. Please, make sure you define auto_activation_volume_list
    # properly so only the volumes you want and expect are autoactivated.
    # - direct activation on command line with the autoactivation option.
    # In this case, the user calls "vgchange --activate ay/-a ay" or
    # "lvchange --activate ay/-a ay" directly.
    # By default, the auto_activation_volume_list is not defined and all
    # volumes will be activated either automatically or by using --activate ay/-a ay.
    # N.B. The "activation/volume_list" is still honoured in all cases so even
    # if the VG/LV passes the auto_activation_volume_list, it still needs to
    # pass the volume_list for it to be activated in the end.
    # If auto_activation_volume_list is defined but empty, no volumes will be
    # activated automatically and --activate ay/-a ay will do nothing.
    # auto_activation_volume_list = []
    # If auto_activation_volume_list is defined and it's not empty, only matching
    # volumes will be activated either automatically or by using --activate ay/-a ay.
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # If read_only_volume_list is defined, each LV that is to be activated
    # is checked against the list, and if it matches, it as activated
    # in read-only mode. (This overrides '--permission rw' stored in the
    # metadata.)
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # Each LV can have an 'activation skip' flag stored persistently against it.
    # During activation, this flag is used to decide whether such an LV is skipped.
    # The 'activation skip' flag can be set during LV creation and by default it
    # is automatically set for thin snapshot LVs. The 'auto_set_activation_skip'
    # enables or disables this automatic setting of the flag while LVs are created.
    # auto_set_activation_skip = 1
    # For RAID or 'mirror' segment types, 'raid_region_size' is the
    # size (in KiB) of each:
    # - synchronization operation when initializing
    # - each copy operation when performing a 'pvmove' (using 'mirror' segtype)
    # This setting has replaced 'mirror_region_size' since version 2.02.99
    raid_region_size = 512
    # Setting to use when there is no readahead value stored in the metadata.
    # "none" - Disable readahead.
    # "auto" - Use default value chosen by kernel.
    readahead = "auto"
    # 'raid_fault_policy' defines how a device failure in a RAID logical
    # volume is handled. This includes logical volumes that have the following
    # segment types: raid1, raid4, raid5*, and raid6*.
    # In the event of a failure, the following policies will determine what
    # actions are performed during the automated response to failures (when
    # dmeventd is monitoring the RAID logical volume) and when 'lvconvert' is
    # called manually with the options '--repair' and '--use-policies'.
    # "warn" - Use the system log to warn the user that a device in the RAID
    # logical volume has failed. It is left to the user to run
    # 'lvconvert --repair' manually to remove or replace the failed
    # device. As long as the number of failed devices does not
    # exceed the redundancy of the logical volume (1 device for
    # raid4/5, 2 for raid6, etc) the logical volume will remain
    # usable.
    # "allocate" - Attempt to use any extra physical volumes in the volume
    # group as spares and replace faulty devices.
    raid_fault_policy = "warn"
    # 'mirror_image_fault_policy' and 'mirror_log_fault_policy' define
    # how a device failure affecting a mirror (of "mirror" segment type) is
    # handled. A mirror is composed of mirror images (copies) and a log.
    # A disk log ensures that a mirror does not need to be re-synced
    # (all copies made the same) every time a machine reboots or crashes.
    # In the event of a failure, the specified policy will be used to determine
    # what happens. This applies to automatic repairs (when the mirror is being
    # monitored by dmeventd) and to manual lvconvert --repair when
    # --use-policies is given.
    # "remove" - Simply remove the faulty device and run without it. If
    # the log device fails, the mirror would convert to using
    # an in-memory log. This means the mirror will not
    # remember its sync status across crashes/reboots and
    # the entire mirror will be re-synced. If a
    # mirror image fails, the mirror will convert to a
    # non-mirrored device if there is only one remaining good
    # copy.
    # "allocate" - Remove the faulty device and try to allocate space on
    # a new device to be a replacement for the failed device.
    # Using this policy for the log is fast and maintains the
    # ability to remember sync state through crashes/reboots.
    # Using this policy for a mirror device is slow, as it
    # requires the mirror to resynchronize the devices, but it
    # will preserve the mirror characteristic of the device.
    # This policy acts like "remove" if no suitable device and
    # space can be allocated for the replacement.
    # "allocate_anywhere" - Not yet implemented. Useful to place the log device
    # temporarily on same physical volume as one of the mirror
    # images. This policy is not recommended for mirror devices
    # since it would break the redundant nature of the mirror. This
    # policy acts like "remove" if no suitable device and space can
    # be allocated for the replacement.
    mirror_log_fault_policy = "allocate"
    mirror_image_fault_policy = "remove"
    # 'snapshot_autoextend_threshold' and 'snapshot_autoextend_percent' define
    # how to handle automatic snapshot extension. The former defines when the
    # snapshot should be extended: when its space usage exceeds this many
    # percent. The latter defines how much extra space should be allocated for
    # the snapshot, in percent of its current size.
    # For example, if you set snapshot_autoextend_threshold to 70 and
    # snapshot_autoextend_percent to 20, whenever a snapshot exceeds 70% usage,
    # it will be extended by another 20%. For a 1G snapshot, using up 700M will
    # trigger a resize to 1.2G. When the usage exceeds 840M, the snapshot will
    # be extended to 1.44G, and so on.
    # Setting snapshot_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).
    snapshot_autoextend_threshold = 100
    snapshot_autoextend_percent = 20
    # 'thin_pool_autoextend_threshold' and 'thin_pool_autoextend_percent' define
    # how to handle automatic pool extension. The former defines when the
    # pool should be extended: when its space usage exceeds this many
    # percent. The latter defines how much extra space should be allocated for
    # the pool, in percent of its current size.
    # For example, if you set thin_pool_autoextend_threshold to 70 and
    # thin_pool_autoextend_percent to 20, whenever a pool exceeds 70% usage,
    # it will be extended by another 20%. For a 1G pool, using up 700M will
    # trigger a resize to 1.2G. When the usage exceeds 840M, the pool will
    # be extended to 1.44G, and so on.
    # Setting thin_pool_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).
    thin_pool_autoextend_threshold = 100
    thin_pool_autoextend_percent = 20
    # While activating devices, I/O to devices being (re)configured is
    # suspended, and as a precaution against deadlocks, LVM2 needs to pin
    # any memory it is using so it is not paged out. Groups of pages that
    # are known not to be accessed during activation need not be pinned
    # into memory. Each string listed in this setting is compared against
    # each line in /proc/self/maps, and the pages corresponding to any
    # lines that match are not pinned. On some systems locale-archive was
    # found to make up over 80% of the memory used by the process.
    # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
    # Set to 1 to revert to the default behaviour prior to version 2.02.62
    # which used mlockall() to pin the whole process's memory while activating
    # devices.
    use_mlockall = 0
    # Monitoring is enabled by default when activating logical volumes.
    # Set to 0 to disable monitoring or use the --ignoremonitoring option.
    monitoring = 1
    # When pvmove or lvconvert must wait for the kernel to finish
    # synchronising or merging data, they check and report progress
    # at intervals of this number of seconds. The default is 15 seconds.
    # If this is set to 0 and there is only one thing to wait for, there
    # are no progress reports, but the process is awoken immediately the
    # operation is complete.
    polling_interval = 15
    # Report settings.
    # report {
    # Align columns on report output.
    # aligned=1
    # When buffered reporting is used, the report's content is appended
    # incrementally to include each object being reported until the report
    # is flushed to output which normally happens at the end of command
    # execution. Otherwise, if buffering is not used, each object is
    # reported as soon as its processing is finished.
    # buffered=1
    # Show headings for columns on report.
    # headings=1
    # A separator to use on report after each field.
    # separator=" "
    # Use a field name prefix for each field reported.
    # prefixes=0
    # Quote field values when using field name prefixes.
    # quoted=1
    # Output each column as a row. If set, this also implies report/prefixes=1.
    # colums_as_rows=0
    # Comma separated list of columns to sort by when reporting 'lvm devtypes' command.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_sort="devtype_name"
    # Comma separated list of columns to report for 'lvm devtypes' command.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_cols="devtype_name,devtype_max_partitions,devtype_description"
    # Comma separated list of columns to report for 'lvm devtypes' command in verbose mode.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_cols_verbose="devtype_name,devtype_max_partitions,devtype_description"
    # Comma separated list of columns to sort by when reporting 'lvs' command.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_sort="vg_name,lv_name"
    # Comma separated list of columns to report for 'lvs' command.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_cols="lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,move_pv,mirror_log,copy_percent,convert_lv"
    # Comma separated list of columns to report for 'lvs' command in verbose mode.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_cols_verbose="lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert
    # Comma separated list of columns to sort by when reporting 'vgs' command.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_sort="vg_name"
    # Comma separated list of columns to report for 'vgs' command.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_cols="vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
    # Comma separated list of columns to report for 'vgs' command in verbose mode.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_cols_verbose="vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
    # Comma separated list of columns to sort by when reporting 'pvs' command.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_sort="pv_name"
    # Comma separated list of columns to report for 'pvs' command.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
    # Comma separated list of columns to report for 'pvs' command in verbose mode.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
    # Comma separated list of columns to sort by when reporting 'lvs --segments' command.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_sort="vg_name,lv_name,seg_start"
    # Comma separated list of columns to report for 'lvs --segments' command.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_cols="lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
    # Comma separated list of columns to report for 'lvs --segments' command in verbose mode.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_cols_verbose="lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_sort="pv_name,pvseg_start"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command in verbose mode.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
    # Advanced section #
    # Metadata settings
    # metadata {
    # Default number of copies of metadata to hold on each PV. 0, 1 or 2.
    # You might want to override it from the command line with 0
    # when running pvcreate on new PVs which are to be added to large VGs.
    # pvmetadatacopies = 1
    # Default number of copies of metadata to maintain for each VG.
    # If set to a non-zero value, LVM automatically chooses which of
    # the available metadata areas to use to achieve the requested
    # number of copies of the VG metadata. If you set a value larger
    # than the the total number of metadata areas available then
    # metadata is stored in them all.
    # The default value of 0 ("unmanaged") disables this automatic
    # management and allows you to control which metadata areas
    # are used at the individual PV level using 'pvchange
    # --metadataignore y/n'.
    # vgmetadatacopies = 0
    # Approximate default size of on-disk metadata areas in sectors.
    # You should increase this if you have large volume groups or
    # you want to retain a large on-disk history of your metadata changes.
    # pvmetadatasize = 255
    # List of directories holding live copies of text format metadata.
    # These directories must not be on logical volumes!
    # It's possible to use LVM2 with a couple of directories here,
    # preferably on different (non-LV) filesystems, and with no other
    # on-disk metadata (pvmetadatacopies = 0). Or this can be in
    # addition to on-disk metadata areas.
    # The feature was originally added to simplify testing and is not
    # supported under low memory situations - the machine could lock up.
    # Never edit any files in these directories by hand unless you
    # you are absolutely sure you know what you are doing! Use
    # the supplied toolset to make changes (e.g. vgcfgrestore).
    # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
    # Event daemon
    dmeventd {
    # mirror_library is the library used when monitoring a mirror device.
    # "libdevmapper-event-lvm2mirror.so" attempts to recover from
    # failures. It removes failed devices from a volume group and
    # reconfigures a mirror as necessary. If no mirror library is
    # provided, mirrors are not monitored through dmeventd.
    mirror_library = "libdevmapper-event-lvm2mirror.so"
    # snapshot_library is the library used when monitoring a snapshot device.
    # "libdevmapper-event-lvm2snapshot.so" monitors the filling of
    # snapshots and emits a warning through syslog when the use of
    # the snapshot exceeds 80%. The warning is repeated when 85%, 90% and
    # 95% of the snapshot is filled.
    snapshot_library = "libdevmapper-event-lvm2snapshot.so"
    # thin_library is the library used when monitoring a thin device.
    # "libdevmapper-event-lvm2thin.so" monitors the filling of
    # pool and emits a warning through syslog when the use of
    # the pool exceeds 80%. The warning is repeated when 85%, 90% and
    # 95% of the pool is filled.
    thin_library = "libdevmapper-event-lvm2thin.so"
    # Full path of the dmeventd binary.
    # executable = "/usr/sbin/dmeventd"

  • Time Machine IS killing or corrupting disks

    To all those " This is just coincidence" guys.
    I have heard about several people being unable to mount their harddrives,
    I had a email traffic with a couple of them and told them to to a manual fsck
    everyone of these guys has a corrupted super block...
    I work with harddrives for about 10 years now, as i do with unix.
    Time Machine IS corrupting, at least, some hard drives.
    I have seen TM corrupting the volume headers and super blocks on 3 brand new external hard drives and one internal harddrive
    Extended read/write tests on this HD's don't show any errors
    Reformating to HFS+, fire up TM and boom, corrupted hard disk
    They had the same issues with TM over Airport, and now they turned it off
    but... it happens to wired hard drives too.
    Apple, fix this!
    Message was edited by: ruebezahl
    Message was edited by: ruebezahl

    The volume structure on an HFS+ volume that is comparable to the superblock of a UFS volume is the volume header, or volume information block (VIB).
    Apple has a detailed description of the HFS+ Volume format:
    http://developer.apple.com/technotes/tn/tn1150.html
    Micromat posted in the MacFixIt Forums some instructions for viewing the text representation of the volume header, using the free utility hfsdebug:
    Use hfsdebug to view volume header:
    syntax given on page 1494 of “Mac OS X Internals” by Amit Singh.
    Using your browser, go to http://www.osxbook.com/software/hfsdebug/ . Download hfsdebug from the link at the bottom of the page. After the download is complete, double-click the .dmg file you downloaded. When this disk image mounts, you see a free utility named hfsdebug. Copy the hfsdebug file to your desktop.
    Open Terminal, located in /Applications/Utilities. Type the following three commands, each on its own line, and press the Return key at the end of each line:
    cd ~/Desktop
    chmod u+x hfsdebug
    sudo ./hfsdebug -d /dev/rdisk1s10 -v
    Enter your administrative password at the prompt.
    Here is a sample of the output:
    MMT3s-Computer:~ MMT3$ cd ~/Desktop
    MMT3s-Computer:~/Desktop MMT3$ chmod u+x hfsdebug
    MMT3s-Computer:~/Desktop MMT3$ sudo ./hfsdebug -d /dev/rdisk1s10 -v
    Password:
    # HFS Plus Volume
    Volume size = 9699188 KB/9471.86 MB/9.25 GB
    # HFS Plus Volume Header
    signature = 0x482b (H+)
    version = 0x4
    lastMountedVersion = 0x4846534a (HFSJ)
    attributes = 00000000000000000010000100000000
    . kHFSVolumeUnmounted (volume was successfully unmounted)
    . kHFSVolumeJournaled (volume has a journal)
    journalInfoBlock = 0x1993a3
    createDate = Tue Oct 11 20:35:24 2005
    modifyDate = Wed Oct 11 21:23:41 2006
    backupDate = Fri Jan 1 00:00:00 1904
    checkedDate = Tue Oct 11 20:35:24 2005
    fileCount = 178583
    folderCount = 47879 /* not including the root folder */
    blockSize = 4096
    totalBlocks = 2424797
    freeBlocks = 693970
    nextAllocation = 2343707
    rsrcClumpSize = 65536
    dataClumpSize = 65536
    nextCatalogID = 265932
    writeCount = 8163599
    encodingsBitmap = 00000000000000000000000000000000
    00000010000000000000000000001111
    # Finder Info
    # Bootable system blessed folder ID
    finderInfo[0] = 0x1f7ca (LaCie_Boot:/System/Library/CoreServices)
    # Parent folder ID of the startup application
    finderInfo[1] = 0
    # Open folder ID
    finderInfo[2] = 0
    # Mac OS 9 blessed folder ID
    finderInfo[3] = 0
    # Reserved
    finderInfo[4] = 0
    # Mac OS X blessed folder ID
    finderInfo[5] = 0x1f7ca (LaCie_Boot:/System/Library/CoreServices)
    # VSDB volume identifier (64-bit)
    finderInfo[6] = 0xcd566ff7
    finderInfo[7] = 0x351c415f
    # File System Boot UUID
    UUID = 38178E0C-3CC2-37E3-8E87-B5C2662DCF95
    # Allocation Bitmap File
    logicalSize = 659456 bytes
    totalBlocks = 161
    fork temperature = /* Metadata Zone */
    clumpSize = 356352 bytes
    extents = startBlock blockCount % of file
    0x74b86 0xa1 100.00 %
    161 allocation blocks in 1 extents total.
    161.00 allocation blocks per extent on an average.
    # Extents Overflow File
    logicalSize = 5242880 bytes
    totalBlocks = 1280
    fork temperature = /* Metadata Zone */
    clumpSize = 5242880 bytes
    extents = startBlock blockCount % of file
    0xa98c9 0x500 100.00 %
    1280 allocation blocks in 1 extents total.
    1280.00 allocation blocks per extent on an average.
    # Catalog File
    logicalSize = 92274688 bytes
    totalBlocks = 22528
    fork temperature = /* Metadata Zone */
    clumpSize = 11534336 bytes
    extents = startBlock blockCount % of file
    0x148dde 0x5800 100.00 %
    22528 allocation blocks in 1 extents total.
    22528.00 allocation blocks per extent on an average.
    # Attributes File
    logicalSize = 0 bytes
    # Startup File
    logicalSize = 0 bytes

  • Why is the Log Area size much smaller than the log volume

    I have been following up on an Early Watch report that has been generated for our production SCM 5.0 system running liveCache 7.6.02 Build 14.  The alert says "The LOG volumes size in your system is too small. Recommendation: Configure LOG Volumes to at least 2 GB".  There are two interesting things about this.
    1) I have spent the last couple of days reading all the OSS Notes, and MaxDB documentation I could find, and this does not seem to be documented as a recommendation anywhere.  Does this seem like a realistic recommendation without taking into account the level of change actifity?
    2)  There is a single log volume allocated with size 2,097,160 KB.  In production LC10 and DBMGUI report this to be correct size under volume details, but only list the total log area size as 1,706,328 (81% of the volume size).  We have a non-production environment with exactly the same size log volume, but it reports that the log area size is 2,032,008 KB (97% of the volume).  What leads to these different amounts of wasted space, and is there any way of getting the database to start using it?
    Thanks,
    Mark

    Hi Natalia,
    I did read 869267, several times.  It does not answer my questions which is why I posted here.
    DBMGUI version = 7.6.00.25
    DBMCLI commands for PL1 (Production)
    > xinstinfo PL1
    IndepData           : /sapdb/data
    IndepPrograms       : /sapdb/programs
    InstallationPath    : /sapdb/PL1/db
    Kernelversion       : KERNEL    7.6.02   BUILD 014-123-152-175
    Rundirectory        : /sapdb/data/wrk/PL1
    > dbmcli -d PL1 -u control,control
    dbmcli on PL1>db_state
    OK
    State
    ONLINE
    dbmcli on PL1>info log
    OK
    END    
    Name                            | Value
    Log Mirrored                    = NO
    Log Writing                     = ON
    Log Automatic Overwrite         = OFF
    Max. Size (KB)                  = 1706328
    Backup Segment Size (KB)        = 699048
    Used Size (KB)                  = 104640
    Used Size (%)                   = 6
    Not Saved (KB)                  = 104640
    Not Saved (%)                   = 6
    Log Since Last Data Backup (KB) = 0
    Savepoints                      = 5210
    Checkpoints                     = 0
    Physical Reads                  = 2469115
    Physical Writes                 = 15655616
    Queue Size (KB)                 = 48000
    Queue Overflows                 = 646
    Group Commits                   = 98205
    Waits for Logwriter             = 10957511
    Max. Waits                      = 10
    Average Waits                   = 0
    OMS Log Used Pages              = 0
    OMS Min. Free Pages             = 0
    dbmcli on PL1>param_getvolsall
    OK
    LOG_MIRRORED                     NO
    MAXLOGVOLUMES                    2
    MAXDATAVOLUMES                   14
    LOG_VOLUME_NAME_001              262145     F  /sapdb/PL1/saplog/DISKL001
    DATA_VOLUME_NAME_0001            524289     F  /sapdb/PL1/sapdata/DISKD0001
    DATA_VOLUME_NAME_0002            524289     F  /sapdb/PL1/sapdata/DISKD0002
    DATA_VOLUME_NAME_0003            524289     F  /sapdb/PL1/sapdata/DISKD0003
    DATA_VOLUME_NAME_0004            524289     F  /sapdb/PL1/sapdata/DISKD0004
    DATA_VOLUME_NAME_0005            524289     F  /sapdb/PL1/sapdata/DISKD0005
    DATA_VOLUME_NAME_0006            524289     F  /sapdb/PL1/sapdata/DISKD0006
    DATA_VOLUME_NAME_0007            524289     F  /sapdb/PL1/sapdata/DISKD0007
    DATA_VOLUME_NAME_0008            524289     F  /sapdb/PL1/sapdata/DISKD0008
    DATA_VOLUME_NAME_0009            1048577    F  /sapdb/PL1/sapdata/DISKD0009
    DATA_VOLUME_NAME_0010            1048577    F  /sapdb/PL1/sapdata/DISKD0010
    DATA_VOLUME_NAME_0011            1048577    F  /sapdb/PL1/sapdata/DISKD0011
    DATA_VOLUME_NAME_0012            1048577    F  /sapdb/PL1/sapdata/DISKD0012
    dbmcli on PL1>param_directget MAXCPU
    OK
    MAXCPU  12
    dbmcli on PL1>param_directget MAX_LOG_QUEUE_COUNT
    OK
    MAX_LOG_QUEUE_COUNT     0
    dbmcli on PL1>param_directget LOG_IO_QUEUE
    OK
    LOG_IO_QUEUE    6000
    > xinstinfo SL1
    IndepData           : /sapdb/data
    IndepPrograms       : /sapdb/programs
    InstallationPath    : /sapdb/SL1/db
    Kernelversion       : KERNEL    7.6.02   BUILD 014-123-152-175
    Rundirectory        : /sapdb/data/wrk/SL1
    dbmcli on SL1>db_state
    OK
    State
    ONLINE
    dbmcli on SL1>info log
    OK
    END    
    Name                            | Value
    Log Mirrored                    = NO
    Log Writing                     = ON
    Log Automatic Overwrite         = OFF
    Max. Size (KB)                  = 2032008
    Backup Segment Size (KB)        = 699048
    Used Size (KB)                  = 3824
    Used Size (%)                   = 0
    Not Saved (KB)                  = 3824
    Not Saved (%)                   = 0
    Log Since Last Data Backup (KB) = 0
    Savepoints                      = 1256
    Checkpoints                     = 0
    Physical Reads                  = 2178269
    Physical Writes                 = 4969914
    Queue Size (KB)                 = 16000
    Queue Overflows                 = 21201
    Group Commits                   = 643
    Waits for Logwriter             = 751336
    Max. Waits                      = 4
    Average Waits                   = 0
    OMS Log Used Pages              = 0
    OMS Min. Free Pages             = 0
    dbmcli on SL1>param_getvolsall
    OK
    LOG_MIRRORED                     NO
    MAXLOGVOLUMES                    2
    MAXDATAVOLUMES                   10
    LOG_VOLUME_NAME_001              262145     F  /sapdb/SL1/saplog/DISKL001
    DATA_VOLUME_NAME_0001            262145     F  /sapdb/SL1/sapdata1/DISKD0001
    DATA_VOLUME_NAME_0002            262145     F  /sapdb/SL1/sapdata2/DISKD0002
    DATA_VOLUME_NAME_0003            1048577    F  /sapdb/SL1/sapdata3/DISKD0003
    DATA_VOLUME_NAME_0004            1048577    F  /sapdb/SL1/sapdata4/DISKD0004
    DATA_VOLUME_NAME_0005            783501     F  /sapdb/SL1/sapdata1/DISKD0005
    DATA_VOLUME_NAME_0006            783501     F  /sapdb/SL1/sapdata2/DISKD0006
    dbmcli on SL1>param_directget MAXCPU
    OK
    MAXCPU  4
    dbmcli on SL1>param_directget MAX_LOG_QUEUE_COUNT
    OK
    MAX_LOG_QUEUE_COUNT     0
    dbmcli on SL1>param_directget LOG_IO_QUEUE
    OK
    LOG_IO_QUEUE    2000
    Thanks for the explaination of the reserved space for the Log Queue pages.  This does explain why there is the difference between the two.  I think we probably have our log segment size too large.  As you can see we do get occasional log queue overflows.  Do you suggest we increase the size of our log IO queue higher, and allocate more log volume space to compensate?
    select * from SYSINFO.LOGSTATISTICS (on PL1)
    1706328;334176;19;334176;19;1879;20305192;64109066;7806480;182151514;12;48000
    DBMGUI Log Area Usage
    Total Size: 2048.01 MB
    Free Log Area: 1330.38 MB
    Used Log Area: 335.96 MB
    Unsaved Log Area: 335.96
    Log since Last Data Backup: 0.00 MB
    Thanks,
    Mark

  • Open and work on FCP project file located at xsan volume

    It is recommended by apple to *open and work on FCP project file located at xsan volume*
    or we should open , work and save our FCP project file from local drive only .
    Is there is risk of corrupting xsan volume if we open FCP project file placed in xsan volume .
    where should be the location of FCP project files ??????
    Mac pro 2.66 , FCP 6.01, xsan 1.4

    Opening a file twice is a indeed a problem. To prevent this, and for numerous other reasons, we use Open Directory. In OD you can configure that a user can login just once (concurrently).
    In old versions of xsan it was not recommended to put project files on xsan, but nowadays it works fine.
    Putting projectfiles on a san has the advantage that a user can work on any client. If this is not important in your environment these files can be stored locally.

  • Simultaneous volume failing

    Hi, I have 2 Seagate FreeAgent GoFlex 1.5TBs. Recently, one of the partitions on one (I'll refer to it as the first one) won't show up in Finder, but still would show up in Disk Utility (although grayed out). Therefore, I hit "Repair Disk", and it shows, "Disk Utility can't repair this disk. Backup as many of your files as possible, reformat the disk and restore your backed-up files.", and somehow opens it in Finder. So I moved the content of that partition to a partition in disk #2. In the process, I saw a virus alert (Sophos) for some variant of the Blackhole exploit kit (I don't remember the exact name. That was one of the files I've backed up from a Windows computer.), and I removed it. (I don't know whether or not this is relevant.)  Then, I formatted the failed partition, created a new partiton, and replaced all of my files.
    A few days later, I went to use the mentioned partition on disk #1, and saw that the same thing happened. So therefore I went to use the mentioned partition in disk #2. It has also failed. Keep in mind that I've forgot to clean off the files from the partition on disk#1 that were on the partition on disk#2. I have the feeling that it is because of a file from disk#1 that perhaps corrupted the disk, but I don't know
    Does anyone here have any guess to why, and how I can fix both of the partitions?

    Sounds to me like that drive is failing, which will destroy both partitions at the same time. If you have any data on that drive that isn't backed up anywhere else, get it off there ASAP!
    This is definitely not related to that Blackhole file. Blackhole is currently not able to infect an up-to-date Mac system, and a file can't corrupt a volume simply by being copied to it.

  • AWS Hana one Volume usage - Amazon charging

    Hi All,
    Currently I am having a HANA One AWS instance which I have started 2 weeks back. However when I see my account activity I found amazon is asking a high amount for the storage volume usage. Obviously they allow 30GB free per month but my volume allocation is more than 560GB which is waste as almost nothing is there.
    Can anyone suggest me what I should do to avoid being charged so much by amazon? Please advise ASAP.
    Regards,
    TD

    Hi Swapan,
    Thanks a lot for responding to my queries. However being on AWS with a pre-configured instance and provision to use it even for personal training is the most useful thing that SAP gave us but this should be categorized in my opinion.
    I totally understand the AWS Hana instance is meant primarily for production usage hence the cluster configuration is made like that but this is not at all useful to the guys who use it for training / personal development. The current configuration is using 520GB of storage which is good enough for production usage - or sort of but totally overkill for the training use. The extra cost of this is not mentioned anywhere in SAP(as I see, pardon if I missed anywhere) and should be clearly mentioned in the system. No SAP Video from SAPHANA Academy says the same.
    Yes, I am using my Hana instance for my personal usage/training so the cost that extra storage is bothering me - moreover didn't saw this mentioned anywhere.
    I would request SAP to let people know how to optimized their storage utilization and save money in instances - meant for training purposes. Further I feel if SAP should consider providing two separate class of SAP HANA One instances - PRD usage/Training Usage and both with diff utilization. (Might be asking too much but I pretty feel there are many guys out in this web forest to utilize this HANA One for personal development)That would be a most effective way and will optimize resource utilization throughout. (A guy blocking 520GB storage for his training is quite overkill and waste of AWS resources)
    Please check if you can guide us with this optimization.
    Regards,
    TD

  • Hard drive error - Corrupt files - Archive and Install?

    Hi
    I have been using Onyx for a while and last week it asked me to reinstall the Snow Leopard disc.  I verified this in Disk Utility first and that also advised I had corrupt files.  I installed the disc and all seemed fine when i checked again in Disk Utility.  But now a week later I have the same problem and not sure whether it is a problem with 0SX or my hard drive.  My mac pro is still under Applecare and they advised tonight that I should do another archive and install and if does not fix then to take the machine into my local Apple store.
    Red part of Error message is - Invalid volume file count - it should be 362310 instead of 362313 and Invalid volume directory count - it should be 99776 instead of 99773. 
    The volume Macintosh HD was found corrupt and needs to be repaired.  - Error: This disk needs to be repaired etc.
    Has anyone else experienced the same problem.  I use Aperture 3 & Final Cut Express and until recently had problems getting the two to work together until Applecare helped.
    Many thanks
    Matt

    Other people have certainly experienced a corrupt HFS volume header, which is what you have, or did have. It should be a very rare occurrence. If it happens frequently, then your drive is probably failing and should be replaced.

  • HP Mini 210-4000 Blue Screen of Death PAGE_FAULT_IN_NONPAGED_AREA error

    I've been up and down the Forums here with no specific luck, unfortunately, so I'm going to ask even if this has been queried and solved in another part of the site which I may have missed.
    I am trying to sort out a friend's HP Mini Notebook, model HP Mini 210-4125sa. The machine started up well enough until a week ago, when it suddenly decided to blue screen.
    The specific error message text displayed within the BSOD reads as follows:
    PAGE_FAULT_IN_NONPAGED_AREA
    TECHNICAL INFORMATION:
    *** STOP: 0x00000050 (0x87E40000, 0x00000000, 0x92442B13, 0x00000000)
    I can not boot past the Windows 7 loading screen - the load bar makes it two fifths up and that's it.
    I had thought to try and recover the operating system, if at all possible, from what is apparently a recovery partition that is created on the HD ( i haven't worked with these machines before unfortunately), although i cannot figure how to get at this partition before the error hits.
    Also, having attempted to download a piece of software from the HP USB Recovery Flash Disk Utility, i realise that it seems necessary to actually use this from the notebook itself, which is not possible.
    Having started running the various onboard tests from the BIOS menu, the Hard Disk Test has just apparently failed (specifically the Hard Disk Optimized DST portion of the test), with failure ID GGBXXV-66A75U-MFPX0J-61VV03 (i'm not certain if this information is of value but am including it nonetheless).HP have not unfortunately been an awful lot of help as they wil only offer a one-off technician support call for forty quid, or to take the notebook away for repair, the cost of which is practically as much as the original cost of the hardware. I would of course prefer to try and sort this out myself but have hit a bit of a wall at the moment. Any suggestions would be fantastic, at this point.
    This question was solved.
    View Solution.

    That hardware test for the hard disk is a dead giveaway of a failed item. A failed hard disk  is a show stopper.
    Hard Disk Optimized DST portion of the test), with failure ID GGBXXV-66A75U-MFPX0J-61VV03 (i'm not certain if this information is of value but am including it nonetheless) It is important information. 
    A corrupted NTFS volume (the hard disk) can also generate the " PAGE_FAULT_IN_NONPAGED_AREA error"  stop message.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • Windows 7 Blue Screen Issues With Alt-tabbing From WoW

    As the title says, lately I've been having blue screens which are mostly caused by wow.
    Previously I've had the occasional bsod (once a month or so) when alt tabbing, but it was pretty rare. However recently, I've had something more like 1 a day, usually caused by alt tabbing out of wow. It seems the longer I'm alt tabbed the more likely it
    is to happen. I haven't experienced the same problem with any other game, although the occasional monthly ones usually happen when I'm changing my music as I alt tab out of League of Legends.
    I downloaded bluescreenview and it appears the cause is some combination of win32k.sys as well as ntoskrnl.exe             Based off the fact that it is happening more with a more demanding game, I'm guessing the problem is
    most likely due to a bad stick of ram, but I'd like a second opinion.
    I'll attach a few of the most recent dump files (the one today is slightly different than the ones last week which seems slightly odd).
    http://puu.sh/8lVuH     http://puu.sh/8lVtT      http://puu.sh/8lVse
    Thanks in advance for any help, and I hope image files are okay :)

    Thanks, and it's not, no. You can't exactly debug pictures :')
    We have two consistent bug checks:
    SYSTEM_SERVICE_EXCEPTION (3b)
    This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
    BugCheck 3B, {c0000005, fffff80002e5301e, fffff88008945c70, 0}
    0: kd> ln fffff80002e5301e
    (fffff800`02e52ff8) nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26 | (fffff800`02e53040) nt!PsIsProtectedProcess
    ^^ The exception occurred in nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe. This is a routine that first enters a critical region, and then acquires the specified fast mutex for the calling thread.
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    This indicates that invalid system memory has been referenced.
    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
    Another common cause is the installation of a faulty system service.
    Antivirus software can also trigger this error, as can a corrupted NTFS volume.
    BugCheck 50, {fffff900c25efcf0, 0, fffff9600032c69d, 0}
    ^^ Address fffff900c25efcf0 was written to by the instruction at address
    fffff9600032c69d.
    1: kd> r cr2
    Last set context:
    cr2=fffff900c25efcf0
    ^^ The 1st parameter address was stored in cr2 prior to calling the page fault handler.
    1: kd> !pte fffff900c25efcf0
    VA fffff900c25efcf0
    PXE at FFFFF6FB7DBEDF90 PPE at FFFFF6FB7DBF2018 PDE at FFFFF6FB7E403090 PTE at FFFFF6FC80612F78
    Unable to get PXE FFFFF6FB7DBEDF90
    ^^ Can't see whether or not it's valid/non-valid.
    1: kd> .trap fffff880`073858e0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c376ae40
    rdx=00000000701215e6 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff9600032c69d rsp=fffff88007385a70 rbp=0000000000000001
    r8=0000000000000000 r9=0000000000000410 r10=fffff80002e4e000
    r11=0000000000000022 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d:
    fffff960`0032c69d 488b4f20 mov rcx,qword ptr [rdi+20h] ds:00000000`00000020=??????????
    ^^ On the instruction we failed on, address fffff960`0032c69d deferenced
    rdi+20h where rdi is 0000000000000000. All of this would result in a memory write to the address
    00000000`00000020.
    1: kd> dd 00000000`00000020
    00000000`00000020 ???????? ???????? ???????? ????????
    00000000`00000030 ???????? ???????? ???????? ????????
    00000000`00000040 ???????? ???????? ???????? ????????
    00000000`00000050 ???????? ???????? ???????? ????????
    00000000`00000060 ???????? ???????? ???????? ????????
    00000000`00000070 ???????? ???????? ???????? ????????
    00000000`00000080 ???????? ???????? ???????? ????????
    00000000`00000090 ???????? ???????? ???????? ????????
    Right, so the code wanted to write to 00000000`00000020 which as we can see above is a completely invalid address. The 1st parameter and cr2 however note we failed writing to address
    fffff900c25efcf0. This does not make sense, and is essentially not logically possible.
    The hardware was told to write to 00000000`00000020, and the hardware came back and said 'I cannot write to
    fffff900c25efcf0'. Another way to think about it is if you kindly asked the waiter of your table for more water, he writes it down, but comes back and says 'I'm sorry, but we're all out of coffee'.
    1. Uninstall any/all installed Asus bloatware, I for example see Asus PC Probe, and AI Suite.
    2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:
    avast! removal -
    http://www.avast.com/uninstall-utility
    MSE - 
    http://windows.microsoft.com/en-us/windows/security-essentials-download
    3. If the above fails, you have faulty RAM.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Kernel panic every time I try to backup

    I am running Mac OS X 10.8.4. I bought the newly released 3TB Airport Time Capsule two days ago.
    After installing Parallels, my disk became corrupted and using the Option key during start up to access the disk repair utility was not successful - the utility was unable to restore the disk. As such, I formatted and reinstalled Mac OS X 10.8. I note the fact it should be a fresh copy with no compatability issues.
    The only thing I have touched is a 32GB RAM aftermarket upgrade which was done 2 months ago.
    Every time I try to run the Time Machine backup to the Airport Time Capsule - it starts the backup process but around 1-2 hours later I find the computer has rebooted and there is an error report. The error report is reproduced below.
    How can I fix the problem?
    nterval Since Last Panic Report:  8253 sec
    Panics Since Last Report:          3
    Wed Jul 10 22:56:56 2013
    panic(cpu 0 caller 0xffffff80232444fe): "a freed zone element has been modified in zone: kalloc.256"@/SourceCache/xnu/xnu-2050.24.15/osfmk/kern/zalloc.c:219
    Backtrace (CPU 0), Frame : Return Address
    0xffffff83b07eb160 : 0xffffff802321d626
    0xffffff83b07eb1d0 : 0xffffff80232444fe
    0xffffff83b07eb210 : 0xffffff8023243d42
    0xffffff83b07eb2f0 : 0xffffff802322463d
    0xffffff83b07eb320 : 0xffffff802355ae90
    0xffffff83b07eb350 : 0xffffff7fa5f34be3
    0xffffff83b07eb410 : 0xffffff8023597fba
    0xffffff83b07eb500 : 0xffffff80235b056e
    0xffffff83b07eb5b0 : 0xffffff7fa5f5b74b
    0xffffff83b07eb6d0 : 0xffffff7fa5f5ba2e
    0xffffff83b07eb740 : 0xffffff7fa5f5d8de
    0xffffff83b07eb860 : 0xffffff7fa5f55c35
    0xffffff83b07eb900 : 0xffffff7fa5f57606
    0xffffff83b07eb990 : 0xffffff80233138ee
    0xffffff83b07eb9c0 : 0xffffff80232e248f
    0xffffff83b07ebb00 : 0xffffff80232e8915
    0xffffff83b07ebba0 : 0xffffff80232e823a
    0xffffff83b07ebce0 : 0xffffff80232e7cc0
    0xffffff83b07ebd50 : 0xffffff7fa5f746ab
    0xffffff83b07ebda0 : 0xffffff8023311b26
    0xffffff83b07ebde0 : 0xffffff80233091cf
    0xffffff83b07ebe10 : 0xffffff8023308365
    0xffffff83b07ebe60 : 0xffffff802354c60c
    0xffffff83b07ebed0 : 0xffffff8023548c0c
    0xffffff83b07ebf20 : 0xffffff802354b000
    0xffffff83b07ebf50 : 0xffffff80235e16aa
    0xffffff83b07ebfb0 : 0xffffff80232ce9c3
         Kernel Extensions in backtrace:
            com.apple.nke.asp_tcp(7.1)[4EFDAEBD-2C9A-3112-9B71-76F9F251299F]@0xffffff7fa5f3 1000->0xffffff7fa5f3dfff
            com.apple.filesystems.afpfs(10.0)[DD13DBB8-D221-3E34-A783-F89A7D6CB026]@0xfffff f7fa5f4f000->0xffffff7fa5fa3fff
               dependency: com.apple.security.SecureRemotePassword(1.0)[F63E4A18-4AEE-36EE-9881-0F4F437DE8 FE]@0xffffff7fa5f3e000
    BSD process name corresponding to current thread: diskimages-helpe
    Mac OS version:
    12E55
    Kernel version:
    Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
    Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
    Kernel slide:     0x0000000023000000
    Kernel text base: 0xffffff8023200000
    System model name: iMac12,2 (Mac-942B59F58194171B)
    System uptime in nanoseconds: 2350416633032
    last loaded kext at 600142330867: com.apple.filesystems.afpfs          10.0 (addr 0xffffff7fa5f4f000, size 348160)
    last unloaded kext at 306293948736: com.apple.filesystems.msdosfs          1.8.1 (addr 0xffffff7fa5f23000, size 57344)
    loaded kexts:
    com.apple.filesystems.afpfs          10.0
    com.apple.nke.asp_tcp          7.1.0
    com.apple.driver.AppleBluetoothMultitouch          75.19
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AudioAUUC          1.60
    com.apple.iokit.IOBluetoothSerialManager          4.1.4f2
    com.apple.driver.AGPM          100.12.87
    com.apple.driver.AppleMikeyHIDDriver          122
    com.apple.driver.AppleHDA          2.3.7fc4
    com.apple.driver.AppleUpstreamUserClient          3.5.10
    com.apple.kext.AMDFramebuffer          8.1.2
    com.apple.driver.AppleMikeyDriver          2.3.7fc4
    com.apple.AMDRadeonAccelerator          1.0.8
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.AppleIntelHD3000Graphics          8.1.2
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.4f2
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleBacklight          170.2.5
    com.apple.driver.AppleMCCSControl          1.1.11
    com.apple.driver.AppleSMCLMU          2.0.3d0
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.driver.AppleIntelSNBGraphicsFB          8.1.2
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.4.5
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleUSBCardReader          3.1.7
    com.apple.driver.AppleIRController          320.15
    com.apple.iokit.SCSITaskUserClient          3.5.5
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.3.1
    com.apple.driver.AppleUSBHub          5.5.5
    com.apple.iokit.AppleBCM5701Ethernet          3.6.1b4
    com.apple.driver.AirPort.Atheros40          600.72.2
    com.apple.driver.AppleFWOHCI          4.9.6
    com.apple.driver.AppleAHCIPort          2.5.2
    com.apple.driver.AppleUSBEHCI          5.5.0
    com.apple.driver.AppleEFINVRAM          1.7
    com.apple.driver.AppleACPIButtons          1.7
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.7
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2.1
    com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
    com.apple.security.SecureRemotePassword          1.0
    com.apple.driver.AppleBluetoothHIDKeyboard          170.2
    com.apple.driver.AppleHIDKeyboard          170.2
    com.apple.driver.IOBluetoothHIDDriver          4.1.4f2
    com.apple.driver.AppleMultitouchDriver          235.29
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.driver.DspFuncLib          2.3.7fc4
    com.apple.iokit.IOAudioFamily          1.8.9fc11
    com.apple.kext.OSvKernDSPLib          1.6
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.iokit.IOAcceleratorFamily          74.5.1
    com.apple.driver.AppleSMBusPCI          1.0.11d0
    com.apple.driver.AppleHDAController          2.3.7fc4
    com.apple.iokit.IOHDAFamily          2.3.7fc4
    com.apple.driver.AppleThunderboltEDMSink          1.1.8
    com.apple.driver.AppleThunderboltEDMSource          1.1.8
    com.apple.kext.AMD6000Controller          8.1.2
    com.apple.kext.AMDSupport          8.1.2
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.4f2
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleSMBusController          1.0.11d0
    com.apple.iokit.IOSurface          86.0.4
    com.apple.iokit.IOBluetoothFamily          4.1.4f2
    com.apple.driver.AppleGraphicsControl          3.4.5
    com.apple.iokit.IONDRVSupport          2.3.7
    com.apple.iokit.IOGraphicsFamily          2.3.7
    com.apple.driver.AppleSMC          3.1.4d2
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.IOPlatformPluginFamily          5.3.0d51
    com.apple.driver.AppleThunderboltDPOutAdapter          1.8.9
    com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.5
    com.apple.iokit.IOUSBMassStorageClass          3.5.1
    com.apple.iokit.IOUSBHIDDriver          5.2.5
    com.apple.driver.AppleUSBMergeNub          5.5.5
    com.apple.driver.AppleUSBComposite          5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.5
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
    com.apple.driver.AppleThunderboltNHI          1.7.8
    com.apple.iokit.IOThunderboltFamily          2.4.0
    com.apple.iokit.IOUSBUserClient          5.5.5
    com.apple.iokit.IOEthernetAVBController          1.0.2b1
    com.apple.iokit.IO80211Family          530.4
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOAHCIFamily          2.3.1
    com.apple.iokit.IOUSBFamily          5.6.0
    com.apple.driver.AppleEFIRuntime          1.7
    com.apple.iokit.IOHIDFamily          1.8.1
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220.3
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          345
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.7
    com.apple.iokit.IOPCIFamily          2.7.3
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    Model: iMac12,2, BootROM IM121.0047.B1F, 4 processors, Intel Core i7, 3.4 GHz, 32 GB, SMC 1.72f2
    Graphics: AMD Radeon HD 6970M, AMD Radeon HD 6970M, PCIe, 2048 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x85F7, 0x483634314755363746393333334700000000
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x85F7, 0x483634314755363746393333334700000000
    Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1333 MHz, 0x85F7, 0x483634314755363746393333334700000000
    Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1333 MHz, 0x85F7, 0x483634314755363746393333334700000000
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.72.0-P2P
    Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Serial ATA Device: Hitachi HDS722020ALA330, 2 TB
    Serial ATA Device: APPLE SSD TS256C, 251 GB
    Serial ATA Device: OPTIARC DVD RW AD-5690H
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x850b, 0xfa200000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 2
    USB Device: hp LaserJet 1300, 0x03f0  (Hewlett Packard), 0x1017, 0xfa130000 / 5
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 6
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfd100000 / 2
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4
    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfd110000 / 3

    You hsve a fault in a memory stick or (less likely) in some other internal component. You also have a corrupt boot volume, which may or may not be due to the same hardware fault.
    Remove the memory upgrade and reinstall the original RAM.
    Then, to repeat, back up all data to a USB or FireWire hard drive, not to the Time Capsule.
    You're going to have to erase the internal hard drive, which means that you need at least two backups of everything on it. One backup is not enough. You can try again to back up to the TC after replacing the RAM. If it still doesn't work, you'll need a second USB or FireWire drive to back up to.
    Boot into Recovery mode, launch Disk Utility, and erase the startup volume. This operation will destroy all data on the volume, so you had be better be sure of your backups. Quit Disk Utility and install OS X. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.
    When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For a walkthrough, see here:
    Using Setup Assistant
    Don't transfer the Guest account, if it was enabled on the old system.
    If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it.

  • Setting up a new network - How does this look?

    Hello,
    Current layout of network - http://i30.tinypic.com/fkywav.jpg
    We currently use this way of setting up our network and we may be moving to a new office so i'm looking at the best way of setting up the new network while we have a relatively clean slate. All wiring is done via CAT5e ethernet.
    We run OS X Server 10.5 and use the following services within the building. File sharing, email, internet. We backup all machines individually with external drives but i'm looking at getting a large storage device to enable everyone to backup to one location using Time Machine Server.
    I'd like to know if the way our network is currently set up is the correct way for what we need. In the near future i'd like to start using iCal sharing, and hosting websites internally for web development.
    Regards
    James

    What you have will work; it's fairly typical network.
    The physical plant, and the plans for expansion, and the current speeds and feeds are also key details when designing a network.
    Cat5e? Don't skimp. Go Cat6 or better. Wiring is always around and in use for far longer than any of us want, and the cost of installation is comparatively vastly higher than the cost of the wire itself; retrofitting is to be avoided.
    As part of avoiding unnecessary retrofitting, run extra Cat6 or better wiring in parallel, too. Prepare to segment your network based on business organization or on physical organization, or both. The extra runs can provide physical redundancy, and bandwidth. The incremental cost of building out with extra (spare) wire is negligible. The cost of not having a wiring run where you need it is higher.
    Without knowledge of the physical plant, I'd also look at the establishment of wiring closets and such; you'll usually have a star at the core of the network in a smaller configuration, then stars at the wiring closet(s) (if any) and out at the desktop. This may be a plan now, and you have the wiring in place for the main runs to retrofit a server closet as you need it. Long wire runs out from the core are a pain. In a moderate or larger network, you'll be using the backhaul connections to the network cores; runs between server closets. (And if you may add server closets, remember the need for cooling can arise.)
    Depending on your plans and your network activities, I might (also) establish higher-bandwidth wiring between the wiring closets; what amount to backhaul connections. Either used up front, or in the closets should you need to place switches further out.
    Also look for corner cases, such as a business and operational environment where you'll be running a dozen or two client netboot operations at exactly 8:01 each and every morning as each staffer arrives and boots up the workstation; these cases can play havoc with aggregate bandwidth and server requirements.
    You may want to consider a parallel network (whether WiFi or wired) for guest access; a conference room or conference center network. You'll almost certainly want 11G and 11N WiFi for your own internal use, too.
    Yes, I usually overbuild these things. Planning and wiring are (comparatively) cheap. Installation isn't.
    Backing up to a Mac OS X Server disk or a TC disk via TM is part of what you need. If you get corrupted archival volume(s) or if your RAID array is somehow damaged or lost or stolen, you're in deep sneakers. I've had a couple of TC archives corrupted; stuff happens. Plan for off-site archives.

  • Mac Pro - 50% of the time, it does not turn on properly.

    Hello all,
    I got my 8-core Mac Pro in september - very new - very happy - and all the rest of it!
    Two days ago however, my Mac starts playing up... It now boots with a car-like rev and roughly 50%-70% of the time I switch on the Mac it thinks for about 3mins, my screen flashes lots and (occasionally) it will load the desktop which seems at first to be normal... Until I try clicking anything or using my keyboard which are completely inactive, and my USB devices aren't receiving their power.
    the other 50%-30% of the time it loads perfectly (although still with the car rev!)
    This is a brand new very expensive Mac... What. On. Earth!?
    Thanks in advance to replies to this,
    Matt

    You are familiar with some of the basic system maintenance I hope:
    Clone your system with SuperDuper
    Run Disk Warrior on the clone
    Boot from there
    Repair your main hard drive
    Keep an emergency boot drive handy
    USB cables and hubs can be buggy. Apple keyboard has its own EFI firmware. Basic troubleshooting to unplug all but stock basics.
    Did this start with 10.6.5? before making OS updates, clone the system so you still have a clone of your working system you can fall back on. And do repair your system before updates. Boot from another hard drive with a mini Apple OS.
    The long boot sounds like it could be looking for network or for a boot volume or a corrupt boot volume. Like after a freeze. Zapping PRAM will clear path to boot OS also so you need to go to Start Disk to reset preference.
    Try resetting the SMC to see if that helps with fans, otherwise run Apple Hardware Test and then, consider schedule and trip to have it looked into.
    http://www.apple.com/support/macpro

Maybe you are looking for