Reallocating partitions

I have a Sun v215 currently running Solaris 10 and I had a question about re-partitioning the disks.
The v215 that I bought has two 70Gb disks. Disk 0 (c1t0d0) is allocated as the boot disc and has solaris installed. Disk 1 (c1t1d0) is allocated with 1 partition (not used currently). This is all part of the standard delivery of the box. The issue I have is that Disk 0 has an insufficient root partition size given the application I need to run. So I need to repartition that first disk to have a larger root partition and I'm looking for the best way to do this.
My first thought is (not sure if this is possible) partition Disk 1 with the correct root partition size I need. I would then install solaris on disk 1 and switch the book disk to be disk1. I could then go in and reformat Disc 0 and repartition it for say /export/home or something.
Is there a better way to handling this problem? Any other links/advice out there that could help.
I'm new to admining a SUN/Solaris box, so any help is appreciated.

Several options, though depending on your knowledge, might not be of much use.
You can use a flash archive, load it back out with the new partition scheme.
You can partition the new disk, then ufsdump/restore in single user mode to the new disk, then swap the disks physically.
You can create extra slices on the second disk and dump selective directories over. ie if you don't have a /usr or /opt and they're going to be the big ones from your root, you can copy/ufsdump just the data from those over to the slices on the second disk, then add entries to /etc/vfstab as appropriate.

Similar Messages

  • CSCul50066 - Upgrade fails due to lack of disk space in the /common partition

    I noticed this has only 1 and 2 star ratings after bumping into this issue myself, so I figured I would help out the original poster and others who are experiencing this issue.
    Presumably, the original poster is intending to advise that we read the CUCM 10.0(1) Upgrade Guide, and view the Pre-Upgrade Tasks therein.  These (the bullet points below) seem to be the salient options contained in that section.  I used the "Free Common Space COP file" option to resolve my disk space issue and allow my upgrade.  I found the .cop file in the following download area on CCO:
    Downloads Home
    Products
    Unified Communications
    Call Control
    Unified Communications Manager (CallManager)
    Unified Communications Manager Version 10.0
    Unified Communications Manager / CallManager / Cisco Unity Connection Utilities-COP-Files
    It is called:  "VMware Disk Size Reallocation COP file: This COP file allows UCM VMs to increase the size of their vDisk(s) without requiring a system rebuild. 
    ciscocm.free_common_space_v1.1.cop.sgn "
    • Use the Cisco Log Partition Monitoring Tool to adjust the low and high watermarks to reduce the traces
    and remove unnecessary log files. Cisco recommends that you adjust the low watermark value to 30,
    and the high watermark value to 40. After the upgrade, you must restore the high and low watermarks
    to their original values in order to avoid premature purging of traces. The default value for the high
    watermark is 85. The default value for the low watermark is 80. For more information about using the
    Cisco Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration
    Guide.
    • Use the Disk Expansion COP file (ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn) to
    expand the vDisk size if your virtual environment has additional available disk space. Ensure that you
    review the Readme file that supports this COP file before you proceed.
    • Use the Free Common Space COP file (ciscocm.free_common_space_v<latest_version>.cop.sgn). This
    COP file removes the inactive side in the common partition to increase available disk space without
    requiring a system rebuild. Ensure that you review the Readme file that supports this COP file before
    you proceed.
    • Manually remove outdated or unused firmware files from the TFTP directory. You can remove these
    files using the TFTP File Management page in the OS Administration interface, or you can use the file
    list tftp and file delete tftp commands from the command line interface.

    I noticed this has only 1 and 2 star ratings after bumping into this issue myself, so I figured I would help out the original poster and others who are experiencing this issue.
    Presumably, the original poster is intending to advise that we read the CUCM 10.0(1) Upgrade Guide, and view the Pre-Upgrade Tasks therein.  These (the bullet points below) seem to be the salient options contained in that section.  I used the "Free Common Space COP file" option to resolve my disk space issue and allow my upgrade.  I found the .cop file in the following download area on CCO:
    Downloads Home
    Products
    Unified Communications
    Call Control
    Unified Communications Manager (CallManager)
    Unified Communications Manager Version 10.0
    Unified Communications Manager / CallManager / Cisco Unity Connection Utilities-COP-Files
    It is called:  "VMware Disk Size Reallocation COP file: This COP file allows UCM VMs to increase the size of their vDisk(s) without requiring a system rebuild. 
    ciscocm.free_common_space_v1.1.cop.sgn "
    • Use the Cisco Log Partition Monitoring Tool to adjust the low and high watermarks to reduce the traces
    and remove unnecessary log files. Cisco recommends that you adjust the low watermark value to 30,
    and the high watermark value to 40. After the upgrade, you must restore the high and low watermarks
    to their original values in order to avoid premature purging of traces. The default value for the high
    watermark is 85. The default value for the low watermark is 80. For more information about using the
    Cisco Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration
    Guide.
    • Use the Disk Expansion COP file (ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn) to
    expand the vDisk size if your virtual environment has additional available disk space. Ensure that you
    review the Readme file that supports this COP file before you proceed.
    • Use the Free Common Space COP file (ciscocm.free_common_space_v<latest_version>.cop.sgn). This
    COP file removes the inactive side in the common partition to increase available disk space without
    requiring a system rebuild. Ensure that you review the Readme file that supports this COP file before
    you proceed.
    • Manually remove outdated or unused firmware files from the TFTP directory. You can remove these
    files using the TFTP File Management page in the OS Administration interface, or you can use the file
    list tftp and file delete tftp commands from the command line interface.

  • MD randomly dropping partition from array

    Hello, folks! I am having some trouble with MD randomly removing a partition from one of my RAID-1 arrays. So far this has happened three times over the past couple weeks, but it only happens on boot.
    I have two 3TB WD SATA hard disks containing two RAID-1 volumes set up as follows:
    /dev/sda1 FAT32 EFI System Partition (250MiB)
    /dev/sdb1 Reserved Space (250MiB)
    /dev/sda2 Disk 0 of /dev/md0 with v0.90 metadata (250MiB)
    /dev/sdb2 Disk 1 of /dev/md0 with v0.90 metadata (250MiB)
    /dev/sda3 swap partition 0 encrypted with dm-crypt mapped to /dev/mapper/swapA (8GiB)
    /dev/sdb3 swap partition 1 encrypted with dm-crypt mapped to /dev/mapper/swapB (8GiB)
    /dev/sda4 Disk 0 of /dev/md1 with v1.2 metadata (2750GiB)
    /dev/sdb4 Disk 1 of /dev/md1 with v1.2 metadata (2750GiB)
    /dev/md1 is encrypted with LUKS and mapped to /dev/mapper/root
    /dev/mapper/root is the only volume in the LVM volume group rootvg
    the volume group rootvg currently has three logical volumes
    logical volume root is mapped to /dev/mapper/rootvg-root and is the file system root
    logical volume home is mapped to /dev/mapper/rootvg-home and is mounted /home
    logical volume var is mapped to /dev/mapper/rootvg-var and is mounted /var
    I also wrote this initcpio hook (I call it 'secdec'), with a bit of help from the Arch Wiki, which decrypts /dev/mapper/root, optionally with a openssl encrypted key file on a USB memory stick:
    run_hook ()
    local keyCopyDec keyCopyEnc keyMountPoint maxTries retryDelay \
    shutdownOnFail
    # customizable ############################################################
    keyCopyDec="/crypto_keyfile.bin" # temp storage for decrypted key data
    keyCopyEnc="/crypto_keyfile.enc" # temp storage for encrypted key data
    keyMountPoint="/ckey" # key storage device mount point
    maxTries=3 # max number of decrypt attempts
    retryDelay=2 # delay in seconds between retries
    shutdownOnFail=0 # shut down computer if decrypt fails
    #+0=yes, 1=no
    # /customizable ###########################################################
    local abortMsg passPromptKey passPromptVol passWrong secdecFormat \
    shutdownMsg
    local E_NOFILE
    local KEY NOKEY SSLKEY
    local CSQUIET OIFS
    local cryptDev cryptName keyDev keyFile keyFs keyType pass passPrompt \
    success tries
    abortMsg="Aborting..."
    passPromptKey="Key passphrase: "
    passPromptVol="LUKS passphrase: "
    passWrong="Invalid passphrase."
    secdecFormat="secdec=cryptdev:dmname:keydev:keyfs:keyfile"
    shutdownMsg="Shutting down computer. You may try again later."
    E_NOFILE=66
    KEY=1
    NOKEY=0
    SSLKEY=2
    OIFS=$IFS
    [ "$(echo "${quiet}" | awk '{print tolower($0)}')" == "y" ] && \
    CSQUIET=">/dev/null 2>&1"
    askForBooleanInput ()
    # Ask the user for boolean input.
    # $1: The question to pose.
    # $2: A string containing single characters, separated by spaces, which are
    #+keys pressed that would return boolean true (0).
    # $3: A string containing single characters, separated by spaces, which are
    #+keys pressed that would return a boolean false (1).
    # Returns 0 if the user presses a key that generates a character found in
    #+$2.
    # Returns 1 if the user presses a key that generates a character found in
    #+$3.
    # Returns 2 if an incorrect number of parameters was provided.
    local keyin
    [ ${#} -ne 3 ] && return 2
    echo -n "$1"
    while true; do
    read -sn1 keyin
    case "$keyin" in
    [$2]) echo "$keyin"; keyin=0; break;;
    [$3]) echo "$keyin"; keyin=1; break;;
    *) echo -n -e "\a";;
    esac
    done
    return $keyin
    askForPass ()
    # Ask the user to enter a pass{word|phrase}.
    # $1: The prompt to display.
    # $2: The name of the variable to assign the input pass{word|phrase} to.
    #+For example, to assign to $pass, $2 should be "pass".
    # Returns 0 on success or 1 if there is a parameter error.
    [ ${#} -ne 2 ] || [ -z "${1}" ] || [ -z "${2}" ] && return 1
    read -rsp "$1" "$2"
    echo
    isSsl ()
    # Examine a file for indications that it is SSL encrypted.
    # $1: Path to the key file to examine.
    # Returns 0 if the file appears to be SSL encrypted, 1 if the file does not
    #+appear to be SSL encrypted and $E_NOFILE if $1 is not a regular file.
    [ ! -f "${1}" ] && return $E_NOFILE
    [ "$(dd if="${1}" bs=1 count=8 2>/dev/null | \
    awk '{print tolower($0)}')" == "salted__" ]
    getKey ()
    # Attempt to find and copy a key from $keyDev to $keyCopyEnc.
    # $1: Path to the device containing the key data.
    # $2: Name of file system containing the key file.
    # $3: Path to the key file, relative to $4.
    # $4: Mount point of partition containing key file.
    # $5: Path to temporary copy of key file.
    # $6: Boolean value indicating whether to allow user the opportunity to
    #+switch key devices before attempting to find a key. This is useful if
    #+a key has already been tried and failed. The user could switch memory
    #+devices before trying again. 0=true, 1=false; default is false.
    # Returns one of $KEY, $NOKEY or $SSLKEY depending on what was found.
    local result wait
    if [ -z "${6}" ] || [ ${6} -eq 1 ]; then wait=1; else wait=0; fi
    mkdir -p "$4" >/dev/null 2>&1
    while true; do
    if [ ${wait} -eq 0 ]; then
    askForBooleanInput \
    "(S)earch for key or (R)evert to LUKS passphrase? " "s S" "r R"
    if [ ${?} -eq 0 ]; then result=$KEY; else result=$NOKEY; fi
    wait=1
    else
    result=$KEY
    fi
    if [ ${result} -eq ${KEY} ]; then
    if poll_device "${1}" ${rootdelay}; then
    mount -r -t "$2" "$1" "$4" >/dev/null 2>&1
    dd if="$4/$3" of="$5" >/dev/null 2>&1
    umount "$4" >/dev/null 2>&1
    if [ -f "${5}" ]; then
    isSsl "${5}" && result=$SSLKEY
    else
    err "Key $3 not found."
    unset result
    wait=0
    fi
    else
    err "Key device $1 not found."
    unset result
    wait=0
    fi
    fi
    [ -n "${result}" ] && break
    done
    return $result
    # If the secdec kernel parameter was not specified, inform the user, but
    #+allow init to continue in case another hook will work.
    if [ -z "${secdec}" ]; then
    echo "Missing parameter: $secdecFormat"
    return 0
    fi
    # Make sure required kernel modules are available.
    if ! /sbin/modprobe -a -q dm-crypt >/dev/null 2>&1 || \
    [ ! -e "/sys/class/misc/device-mapper" ]; then
    err "Required kernel modules not available."
    err "$abortMsg"
    exit 1
    fi
    if [ ! -e "/dev/mapper/control" ]; then
    mkdir -p "/dev/mapper" >/dev/null 2>&1
    mknod "/dev/mapper/control" c \
    $(cat /sys/class/misc/device-mapper/dev | sed 's|:| |') >/dev/null 2>&1
    fi
    # Parse the secdec kernel parameter, check it's format, make sure $cryptDev
    #+is available, and that it contains a LUKS volume.
    IFS=:
    read cryptDev cryptName keyDev keyFs keyFile <<EOF
    $secdec
    EOF
    IFS=$OIFS
    if [ $(echo "${secdec}" | awk -F: '{print NF}') -ne 5 ] || \
    [ -z "${cryptDev}" ] || [ -z "${cryptName}" ]; then
    err "Verify parameter format: $secdecFormat"
    err "$abortMsg"
    exit 1
    fi
    if ! poll_device "${cryptDev}" ${rootdelay}; then
    err "Device $cryptDev not available."
    err "$abortMsg"
    exit 1
    fi
    # Inform the user that $cryptDev doesn't contain a LUKS volume, but allow
    #+init to continue, in case another hook can handle this.
    if ! /sbin/cryptsetup isLuks "${cryptDev}" >/dev/null 2>&1; then
    echo "Device $cryptDev does not contain a LUKS volume."
    return 0
    fi
    # Attempt to open the LUKS volume.
    tries=0
    unset keyType
    while true; do
    success=1
    # Attempt to copy a decryption key.
    if [ -z ${keyType} ]; then
    getKey "$keyDev" "$keyFs" "$keyFile" "$keyMountPoint" \
    "$keyCopyEnc" 1
    keyType=$?
    elif [ ${keyType} -eq ${KEY} ]; then
    getKey "$keyDev" "$keyFs" "$keyFile" "$keyMountPoint" \
    "$keyCopyEnc" 0
    keyType=$?
    elif [ ${keyType} -eq ${SSLKEY} ]; then
    if askForBooleanInput "(U)se a different key or (T)ry again? " \
    "u U" "t T"; then
    getKey "$keyDev" "$keyFs" "$keyFile" "$keyMountPoint" \
    "$keyCopyEnc" 0
    keyType=$?
    fi
    fi
    # Open the LUKS volume.
    if [ ${keyType} -eq ${NOKEY} ]; then
    askForPass "$passPromptVol" "pass"
    /sbin/cryptsetup luksOpen "$cryptDev" "$cryptName" "$CSQUIET" <<EOF
    $pass
    EOF
    success=$?
    [ ${success} -ne 0 ] && err "$passWrong"
    else
    if [ ${keyType} -eq ${SSLKEY} ]; then
    askForPass "$passPromptKey" "pass"
    /sbin/openssl aes256 -pass pass:"$pass" -d -in "$keyCopyEnc" \
    -out "$keyCopyDec" >/dev/null 2>&1
    if [ ${?} -ne 0 ]; then
    rm -f "$keyCopyDec" >/dev/null 2>&1
    err "$passWrong"
    fi
    else
    mv "$keyCopyEnc" "$keyCopyDec" >/dev/null 2>&1
    fi
    if [ -f "${keyCopyDec}" ]; then
    /sbin/cryptsetup --key-file "$keyCopyDec" \
    luksOpen "$cryptDev" "$cryptName" "$CSQUIET"
    success=$?
    fi
    fi
    [ ${success} -ne 0 ] && err "Failed to open LUKS volume."
    tries=$(( $tries + 1 ))
    [ ${tries} -ge ${maxTries} ] || [ ${success} -eq 0 ] && break
    sleep "$retryDelay"
    done
    if [ ${success} -eq 0 ]; then
    if [ ! -e "/dev/mapper/${cryptName}" ]; then
    err "LUKS volume was opened, but failed to map to $cryptName."
    err "$abortMsg"
    exit 1
    fi
    echo "LUKS volume opened."
    else
    if [ ${shutdownOnFail} -eq 0 ]; then
    echo "shutdownMsg"
    poweroff -f
    fi
    exit 1
    fi
    The failing array is /dev/md1 and mdadm is reporting the following:
    mdadm --detail /dev/md1
    /dev/md1:
    Version : 1.2
    Creation Time : Wed May 30 18:50:05 2012
    Raid Level : raid1
    Array Size : 2921467179 (2786.13 GiB 2991.58 GB)
    Used Dev Size : 2921467179 (2786.13 GiB 2991.58 GB)
    Raid Devices : 2
    Total Devices : 1
    Persistence : Superblock is persistent
    Update Time : Wed Sep 12 03:34:52 2012
    State : clean, degraded
    Active Devices : 1
    Working Devices : 1
    Failed Devices : 0
    Spare Devices : 0
    Name : archiso:1
    UUID : 8ad37e84:f7261906:da3d317e:24080362
    Events : 44661
    Number Major Minor RaidDevice State
    0 8 4 0 active sync /dev/sda4
    1 0 0 1 removed
    mdadm --examine /dev/sda4
    /dev/sda4:
    Magic : a92b4efc
    Version : 1.2
    Feature Map : 0x0
    Array UUID : 8ad37e84:f7261906:da3d317e:24080362
    Name : archiso:1
    Creation Time : Wed May 30 18:50:05 2012
    Raid Level : raid1
    Raid Devices : 2
    Avail Dev Size : 5842934631 (2786.13 GiB 2991.58 GB)
    Array Size : 2921467179 (2786.13 GiB 2991.58 GB)
    Used Dev Size : 5842934358 (2786.13 GiB 2991.58 GB)
    Data Offset : 2048 sectors
    Super Offset : 8 sectors
    State : clean
    Device UUID : abba1dc3:3fadf7a7:be452bb5:b8bbe97b
    Update Time : Wed Sep 12 03:37:48 2012
    Checksum : aad3e44b - correct
    Events : 44729
    Device Role : Active device 0
    Array State : A. ('A' == active, '.' == missing)
    mdadm --examine /dev/sdb4/dev/sdb4:
    Magic : a92b4efc
    Version : 1.2
    Feature Map : 0x0
    Array UUID : 8ad37e84:f7261906:da3d317e:24080362
    Name : archiso:1
    Creation Time : Wed May 30 18:50:05 2012
    Raid Level : raid1
    Raid Devices : 2
    Avail Dev Size : 5842934631 (2786.13 GiB 2991.58 GB)
    Array Size : 2921467179 (2786.13 GiB 2991.58 GB)
    Used Dev Size : 5842934358 (2786.13 GiB 2991.58 GB)
    Data Offset : 2048 sectors
    Super Offset : 8 sectors
    State : clean
    Device UUID : 09a09f49:b329feaa:3341111b:47b484fe
    Update Time : Wed Sep 12 01:50:34 2012
    Checksum : 1cdc19c0 - correct
    Events : 42869
    Device Role : Active device 1
    Array State : AA ('A' == active, '.' == missing)
    cat /proc/mdstat
    Personalities : [raid1]
    md0 : active raid1 sda2[0] sdb2[1]
    204736 blocks [2/2] [UU]
    md1 : active raid1 sda4[0]
    2921467179 blocks super 1.2 [2/1] [U_]
    unused devices: <none>
    This is md log info of the first reboot after my first recovery:
    Sep 9 20:18:03 localhost kernel: [ 1.784225] md: raid1 personality registered for level 1
    Sep 9 20:18:03 localhost kernel: [ 2.552971] md: md1 stopped.
    Sep 9 20:18:03 localhost kernel: [ 2.553418] md: bind<sdb4>
    Sep 9 20:18:03 localhost kernel: [ 2.553574] md: bind<sda4>
    Sep 9 20:18:03 localhost kernel: [ 2.554080] md/raid1:md1: active with 2 out of 2 mirrors
    Sep 9 20:18:03 localhost kernel: [ 2.554093] md1: detected capacity change from 0 to 2991582391296
    Sep 9 20:18:03 localhost kernel: [ 2.566266] md1: unknown partition table
    Sep 9 20:18:03 localhost kernel: [ 2.617922] md: md0 stopped.
    Sep 9 20:18:03 localhost kernel: [ 2.618382] md: bind<sdb2>
    Sep 9 20:18:03 localhost kernel: [ 2.618525] md: bind<sda2>
    Sep 9 20:18:03 localhost kernel: [ 2.619175] md/raid1:md0: active with 2 out of 2 mirrors
    Sep 9 20:18:03 localhost kernel: [ 2.619203] md0: detected capacity change from 0 to 209649664
    Sep 9 20:18:03 localhost kernel: [ 10.933334] md0: unknown partition table
    And this is the next time I rebooted:
    Sep 10 19:59:07 localhost kernel: [ 1.780481] md: raid1 personality registered for level 1
    Sep 10 19:59:07 localhost kernel: [ 2.806037] md: md1 stopped.
    Sep 10 19:59:07 localhost kernel: [ 2.806345] md: bind<sda4>
    Sep 10 19:59:07 localhost kernel: [ 2.806888] md/raid1:md1: active with 1 out of 2 mirrors
    Sep 10 19:59:07 localhost kernel: [ 2.806898] md1: detected capacity change from 0 to 2991582391296
    Sep 10 19:59:07 localhost kernel: [ 2.820308] md1: unknown partition table
    Sep 10 19:59:07 localhost kernel: [ 2.956599] md: md0 stopped.
    Sep 10 19:59:07 localhost kernel: [ 2.957149] md: bind<sdb2>
    Sep 10 19:59:07 localhost kernel: [ 2.957269] md: bind<sda2>
    Sep 10 19:59:07 localhost kernel: [ 2.958086] md/raid1:md0: active with 2 out of 2 mirrors
    Sep 10 19:59:07 localhost kernel: [ 2.958100] md0: detected capacity change from 0 to 209649664
    Sep 10 19:59:07 localhost kernel: [ 11.742281] md0: unknown partition table
    In between these two boots there are no reports of md failures. For some reason, its just dropping the second partition.
    I just did a restoration earlier today and on the very next boot, md refuses to use /dev/sdb4. Once I booted, I checked update times (not the ones listed) and /dev/sda4 and /dev/sdb4 were about 4 minutes apart. Since it takes only about a minute for Arch to reboot, including me typing my openssl key password, Arch was running for about 3 minutes without updating. I'm assuming this is of some significance since /dev/md0 reports perfect synchronization.
    All of this has been working very well for me for about 6 months now. Both hard drives, which I bought at the same time, are about 9 months old. I checked both drives using smartctl, and both report SMART enabled and passed. SMART attribute data doesn't make a lot of sense to me and I haven't looked up the format, but the reallocation event value is the same as the day I bought the drives, so I'm kind of assuming things are ok there, or at least bad sectors aren't being created.
    I hope I've provided all required details here. Any help would be appreciated.
    Last edited by cng1024 (2012-09-13 00:02:43)

    It would seem that nobody has any ideas about why this may be happening. I've done a complete diagnostic of both hard disks and both passed. I then downloaded the latest iso, formatted and reinstalled, but that failed after one reboot.
    I have a theory as to why it may be happening, but I haven't tested it yet. Perhaps someone can tell me if I may be on the right track here. I got to wondering what happens during shutdown. The root fs remounts ro during shutdown, but it does remain mounted which means everything under that, my logical volumes, LUKS and RAID are all still open when the system halts. I saved my original configs before I reformatted and it turns out I forgot to add the shutdown hook to the initcpio image which means my RAID wasn't being stopped before halt.
    I'm going to try a few experiments to see if adding the shutdown hook makes a difference. Hopefully I'm right, and I'll update either way, but I'd still appreciate it if someone with a bit more experience could weigh in on this.

  • RAID1 Partitions disappeared when one of the mirrored HDD is used as an external drive for data rescue.

    Hi, I have mirrored build of two identical 1TB HDD in my Xserve Late 2006 (RAID 1) in Bay 2 and Bay3. When I took one HDD out and connected it as an external drive to my MacBook Pro, only the first partition appeared. That is, for instance, I have RAID partition A1, A2, A3 in Xserve but only A1 appears when the drive is connected to MacBook Pro as an external drive. Is there any way to let partition A2, A3 appear too? Thanks.

    Oh, I didn't realise you were using the hardware RAID card for this. In that case, yes, that makes sense, you won't see the other partitions because they're handled by the RAID card. I admit I'd never tried it with a RAID 1 mirror where you might expect to - I've only used RAID 5 on the hardware cards where there's no expectation, of course, to pull a drive to relocate the data.
    So you may ask why not just use a single partition for my RAID1 design. The reason is that I prefer to partition HDD because it is good for HDD lifespan. I don't like to design my parition schema to be just a single big parition with 1T Hard Drive since all data are going to be stored scattered and hence, taking longer for spindle reading.
    I don't agree with most of this statement. I've not seen anything that indicates partitioning improves lifespan - for any given data, the disk spins the exact same number of times, and the heads move the same number of times, regardless of the partitioning - partitioning is only a logical, not a physical, construct.
    As for the data being scattered and spindle latency, that's nowhere near the problem it used to be in the past thanks to faster spindles and larger caches. In addition, Mac OS X uses a dynamic reallocation/fragmentation system that automatically (re)allocates files as they're used, meaning you don't have the level of fragmentation that you used to have.
    The primary benefit of partitioning is to restrict file system sizes so that you don't get a runaway proceess filling up the entire disk. Even that is less of a problem - when an 8GB drive was large it didn't take much to fill it, but you'd have to have a pretty rampant process to fill up a 1TB drive before alarms started ringing.

  • My macbook pro hard disk showing S.M.A.R.T failure, but the partitions inside are okay

    My macbook pro had been facing booting problems intitially. Getting stuck at Apple logo and showing a progress bar. On reaching end of the progress bar, the system shutsdown. I'm able to log in to Recovery HD/Single user login mode. Backed up all data to an external drive. Then cloned the Macintosh HD image to one partition. The cloned image is also showing the same problems - Cannot Verify/Repair. After backing up data, I've erased the Macintosh HD partition, which is blank now and has no errors. But the parent node (disk0) is showing S.M.A.R.T failure.
    A week back, I was having problems with Google Chrome and Safari getting stuck and not responding issues repeatedly.
    Welcoming expert opinions to get thru this.
    Thank you.
    Regards
    Naveen

    It's nothing like that. You have suggested very good steps for all my queries in fact.
    But I'm a bit reluctant to accept that the HDD has failed physically. Even if the SMART error shows reallocated sector count problem, this could again be Hard and Soft error i suppose. Since the data is not critical to me, I want to experiment other ways before disposing.
    Also, as of now I'm able to use my Laptop as it used to be before. It could very well fail shortly.
    99% threads suggest to throw away the HDD at the earliest. And so, there is nothing wrong in believing you.
    Hope you get me.
    Still I have one question to you. If I erase the whole internal drive using erasedisk command in terminal, would I be able to boot in from the external usb installation which I have. I wanted to know if some data required for boot menu and all will get erased as well.
    Thanks
    Naveen

  • Active and Inactive partitions - need expert knowledge

    We are out of space on CCM ver 8.5.1 and we are about to do what Cisco says is needed.  We are going to run an iso and re-install 8.5.1, which will formet the drive and all existing data gets overwritten.  Then we will restore the current backup.
    Our inactive partition has ver 6.something.  Can we make that partition the active one, install 8.5.1 over it, then restore the backup to there?  My goal is to preserve our current active 8.5.1 in case anything goes wrong and we will have a place to go back to.  We've asked the Cisco tech every which way and don't think he is understanding what we are asking.

    That would be just futile, if the common partition is full, you'll probably face the same issue when you try to upgrade to 8.5, the common partition won't clean up and free space just because you switch to the previous version.
    You have a few options here:
    A) Use RTMT to clean as much log files and any other unnecessary files as possible
    B) Use the ciscocm.free_common_space_v1.1.cop.sgn and lose the ability to switch back at that point
    From README
    Important Note: This COP file does not install anything on the node. It just runs a script that
    removes the inactive side in the common partition to free up the disk space so that upgrade is
    successfully completed. You will not be able to switch back to the inactive version after installing this patch.
    C) If this is on ESXi, use the ciscocm.vmware-disk-size-reallocation COP file to increase the disk size and then try the upgrade.
    D) DRS restore on a fresh install as they instructed.

  • X220 backup partition removal

    First let me say I LOVE my new x220.  It represents the perfect compromise between portability and performance.
    But I have heartburn about one thing.  Is the recovery partion needed????  It takes 8 GB that I would rather allocate somewhere else.
    In my circumstances I think I don't need it and it is being a pain.  I ordered the machine with a 320GB hard drive.  After installing the first round of applications, I did a clone of the drive using Acronis software supplied by Kingston onto a a 256GB SSD.  
    For whatever reason, the Kingston/Acronis package took the Q space on the drive, renamed it "D" and gave it exactly the amount of space it occupied.  This had two effects.  First the laptop starting giving drive space warnings about the D partition.  So I was able to allocate it 200 MB more space and that took care of the nanny warnings.
    But why do I need this partition at all?  I have a fully ready standby drive all loaded and ready to go.  And I can fully back up the C partition (for whatever reason my Windows Home Server does not want to back up the D partition).
    So--any harm in simply removing the D partition and reallocating it to C???????
    And it seems that if I want to copy the D partition to a disk first, I need a CD ROM and not DVD?  Is that right???
    Appreciate some expert advice here.  Machine runs great--like a rocket in fact.  But I hate wasting a full 8 GB for nothing.

    While you are waiting on expert advice, I can give you non expert advice.
    I used the recovery disks to load my SSD (120GB) and than deleted that partition since you only can create the recovery disks once.  I recall that it was very easy to do.  In fact I think the factory image is set up to do it automatically.
    Now an expert could tell you how, I just can say that I googled removing it and did what was recommended and it was about a 2 step operation with no outside software needed.
    Perry
    Perry
    W520, I7 2720QM, M4 512 GB SSD OS/Program Disk, C300 256 GB Data Disk in Ultrabay Caddy; X220, I7 2620, Samsung 256 GB SSD, Intel 310 mSata Drv, T61, ancient but working, Asus MoBo, I7 2600k overclocked

  • RE-PARTITION

    I have an external disk with 4 partitions.  I would like to eliminate 2 of the partitions and add the extra storage to the other 2 partions.  Is it possible? I am using OS X Maverick.

    Open the Disk Utility in the /Applications/Utilities/ folder, select the whole drive, choose the Partition tab, delete those two partitions, and allocate the space to the partition immediately above them. If one of those partitions is at the top of the list, the space it uses can't be reallocated to an existing partition.
    (107962)

  • Losing disk partition after choosing startup disk

    Hi,
    I'm using MB Pro retina 2012, I have 3 disk partitions. 1 for Mac osx, 1 for windows (bothcamp) and 1 for data (ExFAT). I using it normally until I change startup disk to Windows. After that, data drive is not show anymore. I have more than 100GB important data on this drive. What happend? How to restore them? I cant repair disk, it doesnt work for me. It show like this on disk utility.
    I've tried to mount it, repair, verify but not successful. This is the log:
    2013-07-18 15:39:32 +0700: Disk Utility started.
    2013-07-18 15:44:53 +0700: Verifying partition map for “APPLE SSD SM512E Media”
    2013-07-18 15:44:53 +0700: Starting verification tool:
    2013-07-18 15:44:53 +0700: Checking prerequisites
    2013-07-18 15:44:53 +0700: Checking the partition list
    2013-07-18 15:44:53 +0700: Checking for an EFI system partition
    2013-07-18 15:44:53 +0700: Checking the EFI system partition’s size
    2013-07-18 15:44:53 +0700: Checking the EFI system partition’s file system
    2013-07-18 15:44:53 +0700: Checking all HFS data partition loader spaces
    2013-07-18 15:44:53 +0700: Checking Core Storage Physical Volume partitions
    2013-07-18 15:44:53 +0700: The partition map appears to be OK
    2013-07-18 15:44:53 +0700:
    2013-07-18 15:44:53 +0700:
    2013-07-18 15:44:55 +0700: Verifying and repairing partition map for “APPLE SSD SM512E Media”
    2013-07-18 15:44:55 +0700: Starting repair tool:
    2013-07-18 15:44:55 +0700: Checking prerequisites
    2013-07-18 15:44:55 +0700: Checking the partition list
    2013-07-18 15:44:55 +0700: Adjusting partition map to fit whole disk as required
    2013-07-18 15:44:55 +0700: Checking for an EFI system partition
    2013-07-18 15:44:55 +0700: Checking the EFI system partition’s size
    2013-07-18 15:44:55 +0700: Checking the EFI system partition’s file system
    2013-07-18 15:44:55 +0700: Checking all HFS data partition loader spaces
    2013-07-18 15:44:55 +0700: Reviewing boot support loaders
    2013-07-18 15:44:55 +0700: Checking Core Storage Physical Volume partitions
    2013-07-18 15:44:55 +0700: Updating Windows boot.ini files as required
    2013-07-18 15:44:55 +0700: The partition map appears to be OK
    2013-07-18 15:44:55 +0700:
    2013-07-18 15:44:55 +0700:
    2013-07-18 15:51:33 +0700: Disk Utility started.
    2013-07-18 15:59:19 +0700: Disk Utility started.
    2013-07-18 15:59:36 +0700: Preparing to remove partition from disk: “APPLE SSD SM512E Media”
    2013-07-18 15:59:36 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 15:59:36 +0700:           1 partition will be removed
    2013-07-18 15:59:36 +0700:           1 partition will not be changed
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:36 +0700:           Partition 1
    2013-07-18 15:59:36 +0700:                     Name                    : “Mac”
    2013-07-18 15:59:36 +0700:                     Size                    : 101.93 GB
    2013-07-18 15:59:36 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 15:59:36 +0700:                     Do not erase contents
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:36 +0700:           Partition 2
    2013-07-18 15:59:36 +0700:                     Size                    : 398 GB
    2013-07-18 15:59:36 +0700:                     File system          : Free Space
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:36 +0700: Beginning partition operations
    2013-07-18 15:59:36 +0700: Unmounting disk
    2013-07-18 15:59:36 +0700: Finishing partition modifications
    2013-07-18 15:59:36 +0700: Waiting for the disks to reappear
    2013-07-18 15:59:36 +0700: Partition complete.
    2013-07-18 15:59:36 +0700:
    2013-07-18 15:59:42 +0700: Preparing to partition disk: “APPLE SSD SM512E Media”
    2013-07-18 15:59:42 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 15:59:42 +0700:           1 partition will be created
    2013-07-18 15:59:42 +0700:
    2013-07-18 15:59:42 +0700:           Partition 1
    2013-07-18 15:59:42 +0700:                     Name                    : “Mac”
    2013-07-18 15:59:42 +0700:                     Size                    : 499.93 GB
    2013-07-18 15:59:42 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 15:59:42 +0700:                     Do not erase contents
    2013-07-18 15:59:42 +0700:
    2013-07-18 15:59:42 +0700: Beginning partition operations
    2013-07-18 15:59:42 +0700: Verifying the disk
    2013-07-18 15:59:42 +0700: Checking file system
    2013-07-18 15:59:42 +0700: Performing live verification.
    2013-07-18 15:59:42 +0700: Checking Journaled HFS Plus volume.
    2013-07-18 15:59:42 +0700: Checking extents overflow file.
    2013-07-18 15:59:42 +0700: Checking catalog file.
    2013-07-18 15:59:53 +0700: Checking multi-linked files.
    2013-07-18 15:59:53 +0700: Checking catalog hierarchy.
    2013-07-18 15:59:53 +0700: Checking extended attributes file.
    2013-07-18 15:59:53 +0700: Checking volume bitmap.
    2013-07-18 15:59:53 +0700: Checking volume information.
    2013-07-18 15:59:53 +0700: The volume Mac appears to be OK.
    2013-07-18 15:59:53 +0700: Unmounting disk
    2013-07-18 15:59:53 +0700: Finishing partition modifications
    2013-07-18 15:59:53 +0700: Waiting for the disks to reappear
    2013-07-18 15:59:53 +0700: Growing disk
    2013-07-18 15:59:54 +0700: Partition complete.
    2013-07-18 15:59:54 +0700:
    2013-07-18 16:36:53 +0700: Disk Utility started.
    2013-07-18 16:37:07 +0700: Preparing to partition disk: “APPLE SSD SM512E Media”
    2013-07-18 16:37:07 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 16:37:07 +0700:           3 partitions will be created
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700:           Partition 1
    2013-07-18 16:37:07 +0700:                     Name                    : “Mac”
    2013-07-18 16:37:07 +0700:                     Size                    : 100 GB
    2013-07-18 16:37:07 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 16:37:07 +0700:                     Do not erase contents
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700:           Partition 2
    2013-07-18 16:37:07 +0700:                     Name                    : “Mac 2”
    2013-07-18 16:37:07 +0700:                     Size                    : 298.93 GB
    2013-07-18 16:37:07 +0700:                     File system          : Mac OS Extended (Journaled)
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700:           Partition 3
    2013-07-18 16:37:07 +0700:                     Name                    : “BOOTCAMP”
    2013-07-18 16:37:07 +0700:                     Size                    : 101 GB
    2013-07-18 16:37:07 +0700:                     File system          : Windows NT File System (NTFS)
    2013-07-18 16:37:07 +0700:                     Do not erase contents
    2013-07-18 16:37:07 +0700:
    2013-07-18 16:37:07 +0700: Beginning partition operations
    2013-07-18 16:37:07 +0700: Verifying the disk
    2013-07-18 16:37:07 +0700: Checking file system
    2013-07-18 16:37:07 +0700: Performing live verification.
    2013-07-18 16:37:07 +0700: Checking Journaled HFS Plus volume.
    2013-07-18 16:37:07 +0700: Checking extents overflow file.
    2013-07-18 16:37:18 +0700: Checking catalog file.
    2013-07-18 16:37:19 +0700: Checking multi-linked files.
    2013-07-18 16:37:19 +0700: Checking catalog hierarchy.
    2013-07-18 16:37:19 +0700: Checking extended attributes file.
    2013-07-18 16:37:19 +0700: Checking volume bitmap.
    2013-07-18 16:37:19 +0700: Checking volume information.
    2013-07-18 16:37:19 +0700: The volume Mac appears to be OK.
    2013-07-18 16:37:19 +0700: Shrinking the disk
    2013-07-18 16:37:19 +0700: Unmounting disk
    2013-07-18 16:37:19 +0700: Finishing partition modifications
    2013-07-18 16:37:19 +0700: Waiting for the disks to reappear
    2013-07-18 16:37:20 +0700: Formatting disk0s5 as Mac OS Extended (Journaled) with name Mac 2
    2013-07-18 16:37:21 +0700: Initialized /dev/rdisk0s5 as a 278 GB HFS Plus volume with a 24576k journal
    2013-07-18 16:37:21 +0700: Mounting disk
    2013-07-18 16:37:21 +0700: Partition complete.
    2013-07-18 16:37:21 +0700:
    2013-07-18 16:37:35 +0700: Preparing to erase : “Data”
    2013-07-18 16:37:35 +0700:           Partition Scheme: GUID Partition Table
    2013-07-18 16:37:35 +0700:           1 volume will be erased
    2013-07-18 16:37:35 +0700:                     Name                    : “Data”
    2013-07-18 16:37:35 +0700:                     Size                    : 298.8 GB
    2013-07-18 16:37:35 +0700:                     File system          : ExFAT
    2013-07-18 16:37:35 +0700: Unmounting disk
    2013-07-18 16:37:35 +0700: Erasing
    2013-07-18 16:37:35 +0700: Volume name      : Data
    Partition offset : 195984280 sectors (100343951360 bytes)
    Volume size      : 583593064 sectors (298799648768 bytes)
    Bytes per sector : 512
    Bytes per cluster: 131072
    FAT offset       : 2048 sectors (1048576 bytes)
    # FAT sectors    : 18432
    Number of FATs   : 1
    Cluster offset   : 20480 sectors (10485760 bytes)
    # Clusters       : 2279580
    Volume Serial #  : 51e7b75f
    Bitmap start     : 2
    Bitmap file size : 284948
    Upcase start     : 5
    Upcase file size : 5836
    Root start       : 6
    2013-07-18 16:37:35 +0700: Mounting disk
    2013-07-18 16:37:35 +0700: Erase complete.
    2013-07-18 16:37:35 +0700:
    2013-11-07 13:52:44 +0700: Disk Utility started.
    2013-11-07 14:04:32 +0700:
              Name :           disk0s3
              Type :           Partition
              Disk Identifier :           disk0s3
              Mount Point :           Not mounted
              File System :           MS-DOS (FAT)
              Connection Bus :           SATA
              Device Tree :           IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0
              Writable :           Yes
              Capacity :           298.8 GB (298,799,648,768 Bytes)
              Owners Enabled :           No
              Can Turn Owners Off :           No
              Can Be Formatted :           Yes
              Bootable :           No
              Supports Journaling :           No
              Journaled :           No
              Disk Number :           0
              Partition Number :           3
    2013-11-07 14:26:36 +0700: Disk Utility started.
    2013-11-07 14:26:47 +0700: Verify and Repair volume “disk0s3”
    2013-11-07 14:26:47 +0700: Starting repair tool:
    2013-11-07 14:26:47 +0700: Checking file system2013-11-07 14:26:47 +0700: ** /dev/disk0s3
    2013-11-07 14:26:47 +0700: Invalid sector size: 0
    2013-11-07 14:26:47 +0700: Volume repair complete.2013-11-07 14:26:47 +0700: Updating boot support partitions for the volume as required.2013-11-07 14:26:47 +0700: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 14:26:47 +0700:
    2013-11-07 14:26:47 +0700: Disk Utility stopped repairing “disk0s3”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    2013-11-07 14:26:47 +0700:
    2013-11-07 14:27:21 +0700: Verifying volume “disk0s3”
    2013-11-07 14:27:21 +0700: Starting verification tool:
    2013-11-07 14:27:21 +0700: Checking file system2013-11-07 14:27:21 +0700: ** /dev/disk0s3
    2013-11-07 14:27:21 +0700: Invalid sector size: 0
    2013-11-07 14:27:21 +0700: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 14:27:21 +0700:
    2013-11-07 14:27:21 +0700: Disk Utility stopped verifying “disk0s3”: This disk needs to be repaired. Click Repair Disk.
    2013-11-07 14:27:21 +0700:
    2013-11-07 14:27:30 +0700: Verify and Repair volume “disk0s3”
    2013-11-07 14:27:30 +0700: Starting repair tool:
    2013-11-07 14:27:30 +0700: Checking file system2013-11-07 14:27:30 +0700: ** /dev/disk0s3
    2013-11-07 14:27:30 +0700: Invalid sector size: 0
    2013-11-07 14:27:30 +0700: Volume repair complete.2013-11-07 14:27:30 +0700: Updating boot support partitions for the volume as required.2013-11-07 14:27:30 +0700: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 14:27:30 +0700:
    2013-11-07 14:27:30 +0700: Disk Utility stopped repairing “disk0s3”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    2013-11-07 14:27:30 +0700:
    2013-11-07 14:32:17 +0700:
              Name :           APPLE SSD SM512E Media
              Type :           Disk
              Partition Map Scheme :           GUID Partition Table
              Disk Identifier :           disk0
              Media Name :           APPLE SSD SM512E Media
              Media Type :           Generic
              Connection Bus :           SATA
              Device Tree :           IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0
              Writable :           Yes
              Ejectable :           No
              Location :           Internal
              Solid State Disk :           Yes
              Total Capacity :           500.28 GB (500,277,790,720 Bytes)
              Disk Number :           0
              Partition Number :           0
              S.M.A.R.T. Status :           Verified
              Raw Read Error :           000000000000
              Reallocated Sector Count :           000000000000
              Power On Hours :           0000000003B2
              Power Cycle :           000000000DD0
              Temperature :           004F00040027
              UDMA CRC Error (PATA only) :           000000000000
    2013-11-07 14:39:58 +0700:
              Name :           disk0s3
              Type :           Partition
              Disk Identifier :           disk0s3
              Mount Point :           Not mounted
              File System :           MS-DOS (FAT)
              Connection Bus :           SATA
              Device Tree :           IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0
              Writable :           Yes
              Capacity :           298.8 GB (298,799,648,768 Bytes)
              Owners Enabled :           No
              Can Turn Owners Off :           No
              Can Be Formatted :           Yes
              Bootable :           No
              Supports Journaling :           No
              Journaled :           No
              Disk Number :           0
              Partition Number :           3
    2013-11-07 14:43:11 +0700: Disk Utility started.
    Thanks for help

    You CAN'T have 3 partitions on your Mac and have the Windows install work. Windows only allows 4 Primary partitions on any one physical hard drive. Since you created a exFAT partition you have past that Windows limit.
    One partition for OS X, one for Windows, one for the OS X Recovery HD and the forth for the EFI. Now that you have created a so called Data partition windows will no longer boot.
    You are basically TOAST and might need to start over with a total wipe, Re-Partitioning, of the drive then reinstall OS X and you programs and files then reinstall Windows program and files and then do not try fooling with the partitions again, any of them on the OS X or Windows side, because if you do Windows again will not boot.

  • Format and partition external drive if you want dual use Mac / PC

    I had purchased from the Apple store in France a portable hard drive Iomega eGO USB 2.0/FireWire ov 250 Go capacity (P/N 31713900; Model: RPHD-C; S/N: FEAJ02011V)
    Originally formatted HFS+, it would mount on any of my Mac desktops with Firewire, easily on the iMac using USB and with great difficulty on the iBook with the two USB plugs (together). It did not mount on any windows PC I had used for tests (so reformatting it FAT(32) or NTFS was *not an option).
    I had reformatted it FAT32 using the iMac under mac OS 10.5 for use on multiple computers including Windows PC's. The drive would now accept to:
    Mount on the iMac and iBook using Firewire
    Mount on the iMac using USB, but it will NOT:
    1 - Mount on the iBook using USB, nor
    2 - Mount on any Windows PC using USB
    The solution was found at the office with our IT helpdesk.
    Whether I format it FAT 32 or NTFS (using the Paragon NTFS for mac OS X 10.5) on my iMac under OS 10.5, including when I do the same on another external drive than the Iomega, the PC would not recognise it while it would always mount on a Mac and it was even impossible on the PC to reformat it. The solution is (at least in windows world), you need to (1) format the drive, AND (2) partition the drive, even if this involves creating a single partition. Using Disk Utility of the Mac, I had only formatted the drive and not partitioned it into a single partition and Disk utility did not request that from me. The drive as prepared was perfectly usable on any Mac anyway.
    The cure was to go back to the imac which had formatted it, mount it (it mounts), (1) reformat and (2) partition, using a single partition.
    Then, the drive would instantly be recognised on the PC as a F drive, whether under FAT 32 or under NTFS.
    The blame is in me and on the Apple Drive utility which did not help me (trust it would have been worse in windows world, but this is a bad mark on disk utility)
    My suggestion to Apple would be that Disk Utilisty should tell us, once we have formatted a drive (HFS+, FAT 32 or NTFS using Parangon) that we are not done yet and still must create the partition(s), even if we only need one partition.
    HTH

    Hi Michel-Ange
    You are talking to other user like yourself here and not Apple. If you wish to make a suggestion to Apple, I suggest you do it at this site - http://www.apple.com/feedback/macosx.html
    Allan

  • Data Recovery from Partitioned and formatted Bit Locker Encrypted Drive

    Recently because of some issues in windows 7 installation from windows 8 installed OS. it was giving as the disc is dynamic windows can not be installed on it. so at last after struggling hard no other solution i partitioned and formatted my whole
    drive so all data gone included the drive which was encrypted by bit lockers.
    For recovery i used many software such as ontrack easy recover, get data back, recovery my files professional edition but still i couldnt able to recover my data from that drive. then i found some suggestion Using CMD to decrypt my data first 
    http://technet.microsoft.com/en-us/library/ee523219(WS.10).aspx
    where it shows it successfully decrypt my data at that moment my drives were in RAW format excluding on which windows is installed and then in CMD i check Chdsk which also shows no problem found. but now problem is still i coudnt able to recover
    my data then i format the drive D and again tried to recover data using above software after decryption still no result. 
    Now i need assistance how i can recover my encrypted drive as it was partitioned and also formatted but decrypted also as i have its recovery key too. thanks

    Hi ,
    I am afraid that we cannot get the data back if the drive has been formatted even if use the
    BitLocker Repair Tool.
    You’d better contact your local data recovery center to try to get data back.
    Tracy Cai
    TechNet Community Support

  • HT201250 Can I partition my external hard drive and use one partion for time machine and the other one for data that i may want to use in different computers?

    I have this doubt. I've just bought an external drive, especifically a Seagate GoFlex Desk 3 tb.
    I want to know if it is recomendable to make a partion exclusively for time machine and let another one so I can put there music, photos, videos, etc that I should need to use or copy to another computer.
    May half and half, 1.5 tb for time machine and 1.5 tb for data.
    I have an internal hard drive of 500 GB (499.25 GB) in my macbook pro.
    Any recommendation?

    As I said, yes. Be sure your Time Machine partition has at least 1 TB for backups.
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to two (2). Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.

  • Using a partition to share files among multiple computers?

    I have a small business with just a few employees and we currently share all of our business files which are hosted on my Macbook Pro.  These files include an Aperture library, an iPhoto library, and a bunch of just plain old files, including a fairly large Filemaker database. I like having these files on my computer so that I can access them quickly (without lag), and this is particularly important for the database and the photo libraries.  And since I am often working 'after hours' its easy for me to be on the move (even if its just a move to my couch!) and still have quick and easy access to the work files.
    However, we're having some major problems with file permissions. Sometimes (and seemingly randomly) employees can't open files because they don't have permission' and often I need to reset the permissions on files my employees create in order to open them myself.  iPhoto needs to "repair" the photo library just about any time a different user opens it up.  It looks like we just lost a couple hours worth of work yyesterday tagging photos in iPhoto since they mysterously dissapeared when I opened iPhoto this morning.
    So we need a solution that will get us around this permissions nightmare.  I read one suggestion about putting iPhoto/Aperture libraries on an external HD and sharing them that way, however, totting a hard drive around might get akward, especially if I am working after hours, and I Don't know that it solves our issue with the rest of our work files.  At this point I would be willing to invest in a Mac Mini server if that would solve some problems, but that would probably leave me with slower access to the files than I currently enjoy.
    So the thought came to me, why don't I partition my hard drive and use half of it for all the work files?  Could I set it up so permissions are ignored on that partitions as is reccommened for the external HD solution?  Are there other solutions, or pitfalls with this solution that I'm not considering?

    ArisaemaDracontium wrote:
    I'd like to use the method described in the following link.  Can I do this with a partition instead of an external drive?:
    Yes.  
    Can I partition my drive without whiping it entirely and then having to restore everything?
    Probably.  See #3 in Using Disk Utility.
    Also, the "Alternative Method" mentions using a disk image.  My experience with disk images is limited to those temporary "disks" used when installing new software that are erased when put in the trash or the computer restarts.  Is there such thing as a perminent disk image?
    Yes.  You can create and keep them anywhere.  They're kind of like a disk-within-a-disk.  They have their own format, directories, etc.  For example, some folks use encrypted disk images for their sensitive files.
    There are a few considerations:
    Only one user can access it at a time, so if you use Fast User Switching and one user has it open, others won't be able to use it.
    You'll need to put it in each user's Login Items so it will be mounted at login, per the article.
    The contents will not be backed-up while it's mounted.
    (But, in many cases the iPhoto Library won't be backed-up by Time Machine while the iPhoto app is open, no matter where it is.)

  • How to delete "Other" partition in yellow color that appears when I connect my devices to the laptop, it's a giant one (4 GB)

    Hello, I would like to know how to delete the yellow partition named "Other" (in italian "Altro") that appears when I connect all my devices to the laptop. This partition in Ipad comes with 4 Gb that for an instrument of 16 seems a bit too also because it far exceeds anything else. So far not been able to find useful information and is a very common problem. Thank you.

    Thank you very much, but it's not so simple. I read somewhere in this same forum that:
    I quote: "That large of "other" is corrupt data. Try restoring your phone from backup first, followed by syncing your content back to the phone. If restoring from backup does not fix things, you will have to restore as a new device to get rid of it. There is no way to directly delete it, other than restoring your phone."
    First of all it's terrible, (but we know that itunes is very far to work properly, it's a store) and how many times a day we should make a restoring? and if it does not have we to buy another device? I cannot believe that there aren't other solutions.

  • Another hard drive swap question - re: 8GB partition for OSX in iMac 266

    I have a Tangerine iMac 266 that I am setting up for a neighbor's son. The original 6GB hard drive was toast, so I swapped in an old 10GB drive that had previously been removed from an iMacDV 400. The 10GB "new" drive had OSX 10.3.1 and OS 9.1 on a single partition. I am aware that these early iMacs need OSX in a first partition of less than 8GB, so I expected that I would need to partition the "new" drive. However, while I was loading an install CD after powering up, the iMac booted fine into OSX, despite it NOT being located in a first partition of less than 8GB (and has continued operating well - booting multiple times in OS X and 9, surfing the net, etc...the only weirdness is a refusal of Word X to run).
    I thought this was impossible, and in researching this I found that the Apple support site says that, for this computer, "Mac OS X must be installed on a volume that is contained entirely within the first 8 GB of its ATA hard disk." see http://docs.info.apple.com/article.html?artnum=106235
    My Questions:
    Is the 8GB limit only related to iINSTALLING OSX on these machines (and not RUNNING OSX)?
    Will the machine run into problems later if a portion of the OS (i.e., during an update) gets installed outside of the first 8GB of the disk?
    One of the log files says that the driver is out of date for the RageproC, and Classic applications that require more than 4MB of VRAM say that I don't have enough VRAM to run, yet the iMac has 6MB of VRAM (2 on MB and 4 in slot as listing by the system profiler) - do I need to (or should I) reinstall the system software (I already tried loading the latest ATI drivers, but it did't help)?
    P.S. - to add more data points on the subject of RAM upgrades in these iMacs, my iMac 266 would not accept a 256MB PC-100 SO-DIMM that worked fine in an iBook and in the upper slot of a Rev. A iMac 233. Well, it accepted it, but only recognized the first 128MB.

    I believe Duane is correct. Even with Mac OS 9, you can run fine as long as all OS components used during startup are within the first 8GB of space. However, (even with Mac OS 9) as soon as something used during startup ends up beyond that limit, you will get open firmware or a gray screen at startup. The Mac OS X does not allow the installation target to exceed the limit as a preventative measure, not because it won't work at all.
    The best "non-technical" explanation I have heard as to why, is this... The IDE hardware (and its driver) can only "see" the first 8GB of space during the initial start up process before the OS is loaded. Once start up completes, control is handed to the OS, which can see the entire drive. Therefore, apps have no problem running from beyond the limit. Only components needed before the hand-off is constrained to the 8GB limit.
    FYI - On my iMac and 120GB drive, 7.78 GB (as shown in a Finder window) is the precise point where the Mac OS X Installer allows the volume to be the install target. "Precise" to with a few hundred MB's.

Maybe you are looking for

  • Use of external LDAP server in Weblogic Commerce Server

    I'm using the following software: Iplanet Directory Server v5 Weblogic Application Server v6 Weblogic Commerce v3.5 I need to configure Weblogic Commerce Server to use Iplanet Directory Server directory services. How do I do that? I have a couple of

  • Problem with virtual guitarist with my logic

    Impossible pour logic pro 9.1.8 de reconnaitre virtual guitarist and bassist malgres l'install et VST au adaptator acheté, je suis sous snow ...ca marché avant et plus maintenant je suis deseperee de l'aide svp je viens de m'acheter un mac pro et je

  • How do I get back to default screen display after clicking View/Full Screen Display?

    After I click View/Full Screen on the Firefox menu bar, I lose the main FF Menu bar. When I hit the esc key, the screen remains locked in full screen view mode. Then I have to reboot my computer to get back to the default FF menu and display mode. Wh

  • CD Covers on my 5th G iPod mixed up

    On iTunes the imported cd covers are all correctly shon and assigned to the related title/album. When playing the iPod the covers are often mixed up and not correctly assigned to the related title/album anymore. Any help ?

  • Insert million records

    Hi Guys, I have a web application that has an upload feature. Records from the file that has been uploaded will be inserted to the database (I'm using TimesTen as of now). Assuming that the file contains million of records, it will, for sure, make th