Resize a ldom zdisk volume

Hi,
I create a zdisk volume on a T5220 (solaris 11) and installed a solaris10 in a ldom. The zdisk size is 50G.
After some zone migration inside the ldom, my zdisk is a bit short and I want to increase to 60G.
I modified the zdisk size where ldom is installed : zfs set volsize=60G dpool/ldom_sol10
When I check the size on solaris 10 , iostat returns the good new size but the format command see always 50G
[root@t5222_ldom_sol10]:$ iostat -En
c0d0             Soft Errors: 0 Transport Errors: 0 Protocol Errors: 0
Vendor: SUN Product: VDSK Size: 64.42GB <64424509440 bytes>
[root@t5222_ldom_sol10]:$ format
Searching for disks...done
 AVAILABLE DISK SELECTIONS:
        0. c0d0 <SUN-DiskImage-50GB cyl 1420 alt 2 hd 96 sec 768>
           /virtual-devices@100/channel-devices@200/disk@0
Is it possible to resize a zdisk volume where a ldom is installed ?
Thanks in advance.
frbo

R81Z3 wrote:
In my opinion ZFS likes disks, so using partitions is asking for problems, I am no ZFS expert but ZFS loves memory, and if your system does not have much say less then 8gb you are asking for problems. Also most folks who are serious about ZFS will use ECC memory as that provides data integrity as if your memory does errors ZFS can't fix it but assumes it is correct. Like they say garbage in garbage out. I have had ZFS on a BSD system and it works had no issues but it was a complete disk, and had at least 8gb of memory but I made sure I had backups of important files just to avoid the CRC errors that bad memory can give you.
You an add and remove pools but ZFS assumes a pool is a disk, and you have to see the documentation for how to do it properly. But I would just use another disk and solve the problem disks are cheap and honestly ZFS loves disks not partitions.
I have a roughly 2g ram system and I am running into no problems. Not lagging either, I am having better expierence with ZFS than other FS's. To the OP, I have read somewhere about adding another disk and ZFS will expand and include that disk as well, but you would need to look into that. I am no ZFS expert by no means. I just enjoy using it.
Also I have read that ZFS doesn't support seperate partitions for swap, I use a ZFS created swap volume.
Last edited by ndowens04 (2013-09-07 02:16:23)

Similar Messages

  • Partition failed: A problem occurred while resizing Core Storage physical volume structures

    Hi everybody,
    I have just installed Yosemite on my iMac and everything works right.
    iMac 27" late 2012
    3,4 Ghz intel core i7
    32 GB 1600 Mhz DDR3
    3TB Fusion drive.
    Now I need to create a bootable partition to install a copy of Mavericks because some FCPX plugins do not work on Yosemite.
    To create a new partition I use Disc Utility, but each time I try to create it the mac show me this error:
    partition failed A problem occurred while resizing Core Storage physical volume structures
    Why?
    What can I do?
    P.S. FCPX does not work on a virtual machine, so I have to install it on a new partition
    Thanks

    Ditto here.
    Same problem - I have a Apple_Corestorage partition that can't be unlocked.
    You have to do this command to free up the Corestorage partition
    diskutil coreStorage delete logicalGroupUUID
    In your case, it'll be:
    diskutil coreStorage delete E2CDC5FC-DA6E-4F43-B524-8925ABB23883

  • Resizing Time Machine Backup Volume

    As a recent iMac purchaser, I started using Time Machine with an external 1TB FW400 drive about a week ago. All is working well (as far as I know) but I now wish that I had partitioned the external drive e.g., 800GB for Time Machine and 200GB for another volume.
    1) Is there a way for me to resize (make smaller) the TM partition such that I don't lose the TM backup files already on it? Current backupdb is 90GB, free space is roughly 900GB (part of which I'd like to use to create a small partition). If so, how?
    2) Alternatively, if the creation of a second partition from some of the unused space on the existing TM partition will result in loss of data on the TM volume, is there a way for me to first copy the TM data into a folder on my iMac internal hard drive (250GB free)? And, if so, how should I restore the backupdb from the folder back into the TM volume when I'm done repartitioning the external drive?
    I've tried copying the backupdb two ways, with no success. 1) After turning off Time Machine, a "copy" of the database seemed to be working okay but eventually failed with message "The operation can't be completed because the selection contains both backup items and non-backup items." 2) I had also tried a sudo find . -print | cpio -pdmv /Users/somedir in the hope that I force a total copy using Unix utilities, but received plenty of error messages. (I guess there's more to the backupdb than just a collection of files.)
    Since I only recently started using TM, I'm okay with scratching what I have and starting over, but I'd like to determine if there's a way I can solve this problem the hard way... .
    Thanks.
    P.S. If I need to scratch the existing TM volume and start over (after creating two partitions on my external drive), are there any gotchas I need to be aware of before (re)starting TM on the new partition?

    Yes, you can do what you want. I would make a backup of your TM backup as a precaution, but it isn't a necessity. To backup the TM volume you will need another drive large enough for the space used by the TM backup. You must use the Restore option of Disk Utility to essentially clone the volume to another drive.
    To resize the drive do the following:
    1. Open Disk Utility and select the drive entry (mfgr.'s ID and size) from the left side list.
    2. Click on the Partition tab in the DU main window. You should see the graphical sizing window showing the existing partition. A portion will appear as a blue rectangle representing the used space on the drive.
    3. In the lower right corner of the sizing window is a resizing gadget. Select it with the mouse and move the bottom of the rectangle upwards until you have reduced the existing partition enough to create the desired new volume's size. The bottom of the sizing window will appear gray. Click on the Apply button and wait until the process has completed.
    4. Click on the [+] button below the sizing window to add a new partition in the gray space you freed up. Give the new volume a name, if you wish, then click on the Apply button. Wait for the process has completed.
    You should now have a second volume on the drive.

  • Resizing Windows and Mac volumes

    Would anyone please be able to give me some direction as to how to downsize my windows volume in order to give me more space on the Mac volume? Thanks in advance...

    Do not even try to use Partition Magic. If you do an operation on your Windows disk using Partition Magic, Partition Expert or any other such program, you will not be able to boot your Windows!
    when bootcamp creates Windows partition, it sets this partition as active. thus, Windows sees this partition as C drive, and can boot without any problem. But, if you use such a program, It will corrupt the MBR, C: drive will disappear for windows, and it will not boot. This can even make bootcamp unable to run anymore!
    I tried to partition my windows partition like that for installing linux, and it screwed up! I could repartition and install windows+linux (triple boot). But this was really a pain! but right now I am unable to use BootCamp. i manually extract the drivers.
    And you talk about resizing OSX partition via Partition Magic. This can even damage hole system! I just tried to divide Windows partition in 2, and I lost Windows and BootCamp. if you try resizing OSX partition, you will lose everything as your MAC does not use old HD partitioning scheme like PCs do!
    I suggest you to not try that... It is easier to reinstall windows. So the best way is to use BootCamp for deleting Windows, and recreating Windows partition afterwards. Try getting the Image of your Windows partition before erasing it. Maybe after resizing, you can use your old Windows image, so you will not have to install Windows from scratch...
    MacBook Pro 2.16,ibook g4 1.33   Mac OS X (10.4.8)   wireless mighty mouse and 1/2 ipod nano black

  • RAID Utility - Resize Volume?

    Hi,
    I've got a Mac Pro with a hardware RAID0+1, 4 x 500GB disks giving me a maximum of 1TB (ish) of storage.
    Thing is, the last 500GB disk was an addition and now I want to resize the original 500GB volume to use the full 1TB of storage offered by the array. I can't see an easy way to do it in RAID utility. Is it me or is this something that can't be done?
    Cheers,
    Stu

    Usually the drives have to be formatted separately as well as partitioned separately.
    However, I don't quite understand what you are doing. You currently have four 500 GB drives configured as a RAID 0+1 which I would understand to mean two 500 GB drives striped, a second pair striped. That is two 1 TB striped arrays that are then combined into a mirrored array which would be 1TB. Now as I understand you want to resize one 500 GB drive that is already in the array. This I don't get.

  • Is it possible to resize a mac partition from windows?

    Here's what's going on. I originally wanted to use Disk Utility to do this, which is clearly the easy way to do things, but my computer is so slow that Disk Utility immediately becomes unresponsive upon wanting to resize -any- partition. The windows side works fine though, it isn't slow as crap. Is there a way to resize the mac partition from windows (HFS+)? Any possible way? Even crazy ones? I'm open to suggestions.
    Oh yeah, and in case you want to know...my Mac Mini just randomly started getting really, really slow, so slow in fact, that now my old iMac from 1999 is faster (it doesn't even have ANY RAM!). I tried resetting the PRAM/NVRAM, multiple times, booting into safe mode takes forever, but I left it for awhile and it finished. Almost worked, the finder showed up quicker than usual, but then it reverted back to it's slow self again once I opened Disk Utility. I tried booting into single user mode and typing /sbin/fsck -fy, and it's so slow, that it couldn't even do that! It got stuck at checking libraries or something, for hours, and i could type things in still, but it wouldn't recognize any commands (ie fsk - fy). I also cannot replace the RAM because it is an older mac mini and those things are hard as f*** to repair, trust me, i've tried. The weirdest part of all of this has to be that this is the computer that we DON'T download many apps onto, so it most likely isn't bloatware, adware, a virus or something else. We download most stuff to our MacBook, and go to the sketchy websites on it as well (it really should be the other way around, the mac mini would be around 3x less expensive to replace, it's just that it's the family computer). And that's always slow, but this surpassed it (btw, the laptop is a year or so older). I do not have the installation disk.
    Can someone help? Mainly about the first thing...please. The second thing is hopeless, I will need to get a new computer pretty soon, and these macs don't last as long as they used to I guess, we'd most likely get a quality Windows PC to replace it, this has been a disappointment. I'm just trying to get a little more life out of it with Linux, maybe a year or two. That's what i've done with my old iMac. Runs GREAT. Especially for a 13 year old computer. The thing is, my folks don't want me to completely eliminate the mac partition even though it's virtually unusuable.

    I'm not really understanding what the end goal was. But in case anyone else comes across the thread, neither the built-in Windows volume resizing utility nor any 3rd party Windows resizing utility should be used to resize either the Windows partition or the Mac OS partition. Invariably they all manipulate the NTFS volume in such a way that the secondary GPT is corrupt, the primary GPT is rendered invalid, and only correctly alter the MBR. It's a recipe for data loss.
    Conversely, while Disk Utility can resize a Mac OS volume, it cannot resize an NTFS volume. With Lion and Mountain Lion, upon using Boot Camp Assistant there are already four partitions: EFI System, Mac OS, Recovery HD, and Windows. There is no more room for a fifth partition in the MBR partition scheme, and if you try to add one, Disk Utility will apparently let you and render Windows unbootable (because Disk Utility adds the fifth partition to the GPT, but can't add it to the MBR, and instead removes the hybrid MBR needed for Windows support and replaces it with a PMBR.)
    So in effect this is not to be done except with 3rd party utilities.

  • Windows Won't Boot after resizing partition

    I am having problems with Windows not rebooting after I resized partition to reduce Mac side and increase Windows side. I do not see the BootCamp partition labelled as such while running disk utility. Upon startup, the Windows partition shows up when I boot up while pressing the ALT key. However, when I try to run Windows, it says " error loading operatig system".
    I also followed instruction and went through to run gdisk successfully. Results towards the end.
    What can be done? Windows still does not boot and It shows ? Suspicious MBR at sector 0.
    Below is information based on typical questions asked here.....
    diskutil list
    /dev/disk0   #:                       TYPE NAME                    SIZE        IDENTIFIER
       0:              GUID_partition_scheme                        *120.0 GB     disk0
       1:                                           EFI                         209.7 MB     disk0s1
       2:                         Apple_HFS Macintosh HD            78.5 GB     disk0s2
       3:                       Apple_Boot Recovery HD             650.0 MB     disk0s3
       4:                   Microsoft Basic Data                         31.7 GB      disk0s4 
    sudo gpt -r -vv show disk0
    gpt show: disk0: mediasize=120034123776; sectorsize=512; blocks=234441648
    gpt show: disk0: Suspicious MBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 234441647
          start       size            index       contents
              0          1                             MBR
              1          1                             Pri GPT header
              2         32                            Pri GPT table
             34          6       
             40     409600           1            GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  153240016      2            GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      153649656    1269544     3            GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      154919200   17628896       
      172548096   61892608    4            GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      234440704        911       
      234441615         32                       Sec GPT table
      234441647          1                        Sec GPT header
    sudo fdisk /dev/disk0
    Disk: /dev/disk0 geometry: 14593/255/63 [234441648 sectors]Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE    0   0   2 - 1023 254  63 [         1 -  172548095] <Unknown ID>
    *2: 07 1023 254  63 - 1023 254  63 [ 172548096 -   61892608] HPFS/QNX/AUX
    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused    
    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused 
    sudo gdisk /dev/disk0
    GPT fdisk (gdisk) version 0.8.7
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: hybrid
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with hybrid MBR; using GPT.
    Command (? for help): r
    Recovery/transformation command (? for help): h
    WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,
    just hit the Enter key at the below prompt and your MBR partition table will
    be untouched.
    Type from one to three GPT partition numbers, separated by spaces, to be
    added to the hybrid MBR, in sequence: 4
    Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y
    Creating entry for GPT partition #4 (MBR partition #2)
    Enter an MBR hex code (default 07):
    Set the bootable flag? (Y/N): y
    Unused partition space(s) found. Use one to protect more partitions? (Y/N): n
    Recovery/transformation command (? for help): o
    Disk size is 234441648 sectors (111.8 GiB)
    MBR disk identifier: "DELETED INFO"
    MBR partitions:
    Number  Boot  Start Sector   End Sector   Status      Code
       1                               1    172548095   primary     0xEE
       2           *     172548096    234440703   primary     0x07
    Recovery/transformation command (? for help): w
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/disk2.
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Warning: The kernel may continue to use old or deleted partitions.
    You should reboot or remove the drive.
    The operation has completed successfully.

    So here's what I think happened. Upon resizing the OS X volume, a 5th partition was created. When that happens, diskutil removes the hybrid MBR that's needed to activate the EFI firmware CSM (BIOS emulator) which is still presently used for booting Windows on Apple hardware. Upon removing the hybrid MBR, Windows is no longer bootable. So what you probably did was used Disk Utility to reverse what you did by deleting the extra partition. When you do this, diskutil recreates the hybrid MBR but with the wrong partition type code. It sets it to 0x0C, and therefore thinks it's FAT32, whereas it should be 0x07 for NTFS. Disk Utility will then let you run a disk check on what it erroneously thinks is a FAT32 volume, but is in fact NTFS. If any writes are done, which it appears is the case, it corrupts the NTFS file system.
    So this is just yet another Bootcamp data loss story, without any warning in either documentation or Disk Utility whatsoever.
    What version of OS X is this?
    The easiest, but most tedious thing to do is to totally start over with everything: obliterate the entire drive with Disk Utility making 1 partition only, reinstalling OS X and files from backups, use Bootcamp Assistant to resize the OS X volume the way you really want it, reinstall Windows and restore from its backup. All of that can be done in the GUI.
    You might still use the Windows install disk to run Windows startup repair. It might fix the Bootcamp volume. The remaining problem in that case is what to do with the large pile of free space, but I'll make those suggestions later once you get to that point.
    If Windows startup repair can't fix the Bootcamp volume, and you don't have a backup, then you'll need to download and install testdisk, and read how to use it to try and find your data. It's an iterative process. Once that's done, while it probably won't fix it and make it bootable again, you'll have a basic backup of files. The remaining thing to do is use gdisk remove the broken Windows partition, make a new one that also includes free space you presumably wanted Windows to have, and make a new hybrid MBR adding partitions 2 3 4. Then reinstall Windows, your apps, and restore your data from backups.
    So that's the gist. Ask if you have more questions.

  • Can't resize disk partitions after Yosemite install.

    My disk has two partitions. I run Mavericks on the first, and recently installed Yosemite on the second. The OS works fine, but I no way to resize the partitions. I've tried booting into both Yosemite and Mavericks but the partition layout in disk utility appears locked with fixed partition sizes.
    It now appears that I have two options.
    Use the undocumented "resizeVolume" command in diskutil to resize the core storage volume in my Yosemite partition, or
    Use the "revert" command in diskutil to revert from core storage to the default partition type and try my luck.
    Is anyone else facing this issue of not being able to resize your disk partitions after the Yosemite install, and if so, how did you resolve this?
    Thanks in advance.

    None of these worked. I had to resolve this the hard way.
    Make a complete TM backup of the new Yosemite installation.
    Use a bootable install DVD or USB drive, re-partition the disk and do a complete reinstall.
    Recover the applications and data from the TM backup.
    It took me about an hour and a half once I decided on this approach, not counting the hours wasted trying to get it working.
    To give them credit, the TM backup and restore worked flawlessly and all my apps and data were back without a hitch.
    However, reading the other posts in the forum and elsewhere it does appear that Apple has not done a good job with the disk utility in supporting core storage volumes, which is fairly ridiculous since Yosemite defaults to that without giving you a choice.

  • Yosemite "problem resizing Core Storage" upgrade error?

    Not a great amount of luck upgrading from Mavericks to Yosemite here.
    Download and start install, restart, see the progress bar, then the install screen with "about 18 minutes remaining". It moves along, and then boom...
    OS X could not be installed on your computer
    A problem occurred while resizing Core Storage physical volume structures.
    Quit the installer to restart your computer and try again.
    Restarting several times, as well as returning to Mavericks and trying again has so far failed. Live Chat suggestions of verifying and repairing disks and trying in Safe Mode also unsuccessful.
    3TB Fusion Drive has over 450GB free space, just the single "iMac" partition within the Macintosh HD.
    Any help greatly appreciated! Otherwise looks like it's a wait to see if a fix appears...
    iMac 27-inch, Late 2012
    3TB Fusion Drive
    3.4GHz Intel Core i7
    16GB Memory

    http://de.wikipedia.org/wiki/Fusion_Drive
    Fusion Drive is a technology developed by Apple Computer Engineering, with a SSD and a mechanical hard drive be connected to a logical drive. [1]
    Description and function [Edit]
    Fusion Drive called Apple a technique in which an SSD and a mechanical hard disk are transparently connected to a logical drive. The user sees the combination as a single drive. [2] With Fusion Drive is also in large storage volume can be benefited at a moderate price of the speed of the SSD.
    Fusion Drive connects not only two physical drives into one logical, but still used in addition to a technology that tiering is called. When tiering, in German as "staggering", data on frequently accessed, the fastest drive (SSD here) saved, the other to the slower, here on the mechanical drive. What data is stored where, the operating system decides on the basis of a thorough analysis of the data access itself and can not be influenced by the user. Optionally coated the operating system in the background to data. The operating system itself is always on the SSD. [3] [4] tiering is used in mainframe computers for some time, with Fusion Drive this technology now comes for the first time in a personal computer for use.
    Fusion Drive must not be confused with conventional hybrid drives. While in the latter case the SSD part only serves as a data buffer and all data is ultimately always stored on the mechanical disk in Fusion Drive SSD is a full-fledged part of the logical drive (except a small part of 4 GB [3], which also serves as a buffer).
    Fusion Drive is since November 2012 integrated with all new Macs with SSD and mechanical hard drive. [5] The first corresponding Macs were equipped with a 128 GB SSD and a 1 TB or 3 TB of mechanical hard disk. [6] Currently (April 2013 ), Apple provides no utility available with which Fusion Drive install on older Macs could. But this can be done via the terminal, this requirement is OS X 10.8 Lion Mountain. [7]

  • Resize TimeMachine in Lion

    Hi!! I'm using MBP C2D with Lion 10.7.1 and I'm trying to limit the TimeMachine repository that I have in my Western Digital MyBook Live 2TB.
    The TimeMachine Disk is not mounted like a typical resource. TM is mounting the volume when the backups automatically starts (so, all is working fine!!)
    The problem is to limit the size for the backup, because obviusly I want to use my disk not only for TM.
    Looking for a solution, I find resize the volume with hdutil but when I'm trying to apply this instrucion:
    hdiutil resize -size 500g -shrinkonly /Volumes/TimeMachine/blablabla.sparsebundle
    I have this error:
    hdiutil resize failed. not recognized 109
    Now with MobileBackups, is it correct with Lion? The solution is create a new disk instead resize directly?
    I find differents sources to resize the TM volume, that's one for example
    (http://untoro.wordpress.com/2011/06/07/how-to-limit-space-used-by-time-machine/)
    Do you known some third product to better control over TM? It's incredible that TM is still with no limits... (at least, I don't know)
    Thanks in advance,
    Daniel López

    Hi!! Finally I find a solution and I posted it in my blog (step-by-step), exactly in the entry:
    http://geeksandmaks.wordpress.com/2011/08/23/como-limitar-espacio-de-timemachine /
    I hope it will be usefull
    Bye!

  • Limiting Time Machine backup Size with WD MyBookLive and 10.8

    I cannot take credit for the any part of this solution; merely for merging and clarifying how the solutions discovered by 2 Apple Support Communities contributors much smarter than I (namely “Pondini” – Florida and  “himynameismarek”) - worked perfectly for my situation. All cudo’s to these two!
    I have about average or better PC skills, but am an absolute newbie with Apple. This week I got a new iMac. Having a number of home PC’s all sharing files and back up space on a Western Digital MyBookLive (“WD MBL”) 3TB network drive (NAS), naturally I wanted to use it to backup the new Mac rather than rushing out to buy an Apple Time Capsule.
    There are hundreds of threads on limiting size of a Time Machine (“TM”) backup, many of which required entries in “Terminal” or were devised on older versions of OSX. I’m running OSX Mountain Lion 10.8, so was concerned they may not work.
    The issues I wanted to resolve were:
    Time Machine will use up all of the space on my WD MBL if left to it’s own devices.
    The WD MBL is compatible with Mac and PC’s… which is good… but unlike a back up in Windows 7 Pro which will allow you to make backups in a mapped “share” you create yourself, Apple TM Backups will not; they end up in a hidden folder on the NAS (much like PC backups done with WD Smartware)
    At first I thought maybe I could limit the size of a share created in the MBL, but not possible, at least not that I've seen and I have searched for days.
    The solutions:
    First make sure you have the latest firmware for the WD MBL as of today it is MyBookLive 02.11.09-053. From what I’ve read Western Digital fixed the compatibility issues with 10.8 Mountain Lion just recently.
    Next you need to start TM so that it starts to create a back up. You can stop the back up once you see files being copied. Do this before you walk thru the video tutorial by my Marek below. WD MBL will create the hidden folder you need to find for TM Backups. This folder is called “TimeMachine” but it is not visible even in the “MBL_NAME-backup” folder in Finder.
    Open safari and type “ afp://xxx.xxx.x.xxx ” but use your own ip address of your MBL. Mine was 192.168.1.120, yours will be different.
    It will ask how you want to connect. CHOOSE AS A GUEST even if your MBL is protected… I’m not sure why it works but it does. Then a window will come up asking which share you’d like to mount. You will see all of your own shares plus one called software and now one called “TimeMachine”. Choose that one.
    Now in “Finder” you will see a mounted shared item called “YOUR_MBL_NAME-“ (the same as the one that is probably already there but with a dash(-) at the end). You’ll also see a new “device” in the device list called “Time Machine Backups” (If you already have watched the video tutorial by Marek, you’d know you are looking for a file called “YOUR_MACHINE_NAME.sparsebundle”. Well if you browse the folder “Backups.backupdb” in the Time Machine Backups device you won’t find it… again I don’t know why but you won’t. It resides in the hidden folder called “TimeMachine” that is now visible in the thing you just mounted in step 4)
    NOW watch this video tutorial http://youtu.be/Nq7mSizqUSI and follow it step by step.
    Voila... issues resolved. Thank you Pondini and Marek!

    Try Use Terminal to limit Time Machine sparcebundle size on timecapsule,
    should work to limit Time Machine backup size on any NAS or external disk (or not...)
    sudo defaults write /Library/Preferences/com.apple.TimeMachine MaxSize 500000
    to return to ilimited
    sudo defaults delete /Library/Preferences/com.apple.TimeMachine MaxSize
    if you want to reclame deleted files space shrink it use
    hdiutil resize -size 500g -shrinkonly /Volumes/TimeMachineYOURNAME/YOURNAME.sparsebundle/
    Regards

  • Thinkpad T530 Hard Drive Cloning

    Hello,
    I'm looking for best practices, recommendations, lessons learned, etc. for copying the hard drive contents of one T530 to nine other identical T530s recently purchased for software engineering usage.  A current snap shot of our old laptops shows that  we have 214 programs loaded (majority of these programs are not pre-loaded from Lenova), so I'm looking for the most efficient and painless way of getting all the laptops loaded with an identical image.  In the past we have used Norton Ghost but encountered issues with using legacy IBM Thinkpad laptops.  Does the built-in Rescue and Recovery handle this process?  Is a 3rd party product (such as Norton Ghost) recommended?  Any advice would be greatly appreciated.
    Thanks.
    T530 Laptop specs:
    Processor
    Intel Core i7-3720QM Processor (6M Cache, up to 3.60 GHz)
    Operating system
    Genuine Windows 7 Professional (64 bit)
    Operating system language
    Genuine Windows 7 Professional 64 - English
    Windows XP Mode
    Windows 7 XP Mode - English
    Display type
    15.6" HD (1366 x 768) LED Backlit AntiGlare Display, Mobile Broadband Ready
    System graphics
    NVIDIA NVS 5400M Graphics with Optimus Technology, 1GB DDR3 Memory
    Total memory
    4 GB PC3-12800 DDR3 (1 DIMM)
    Keyboard
    Keyboard Backlit - US English
    Pointing device
    UltraNav with Fingerprint Reader
    Camera
    720p HD Camera with Microphone
    Hard drive
    500GB Hard Disk Drive, 7200rpm
    Micro hard drive (mSATA)
    16GB mSATA Solid State Cache Drive
    Optical device
    DVD Recordable
    System expansion slots
    Express Card Slot & 4-in-1 Card Reader
    Battery
    9 Cell Li-Ion TWL 70++
    Power cord
    135W AC Adapter - US (2pin)
    Integrated WiFi wireless LAN adapters
    Intel Centrino Ultimate-N 6300 AGN
    Integrated mobile broadband
    Mobile Broadband upgradable

    +1 for Acronis.  You _can_ also do this with Rescue and Recovery, but it's quite a bit slower in my experience.
    Pull a full drive image onto bootable media, then restore to the other drives when they are installed in the target machines.
    [edit] Or boot Acronis stand-alone on each machine and clone from the original drive in an external enclosure/adapter.  The options re resizing and preservation of volume ID (probably not what you want) are somewhat different when cloning vs restoring.
    Historically, there have been cloning problems with ThinkPads when the target drive wasn't actually installed when it was written.  Something to do with the way BIOS addresses the drives.  This may not be a problem with newer machines, but ti's generally recommended.
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Limiting Time Machine backup size onto external drive

    I have a 6TB RAID LaCie external drive that I would like to use with Time Machine.  My mac has a 1TB HD which is not full.  I do not want Time Machine to fill up my external drive with multiple backups.  Is there some way to limit how much space Time Machine will use on an external drive?  My understanding is that Time Machine will fill up the drive completely, then start overwriting the oldest files.
    I do not think that I could partition the drive.  But I am not sure how to do that, if it works with mac, and if I can do it now without reformating the drives.  I am looking to see if there is a solution on the Time Machine software side. 

    Try Use Terminal to limit Time Machine sparcebundle size on timecapsule,
    should work to limit Time Machine backup size on any NAS or external disk (or not...)
    sudo defaults write /Library/Preferences/com.apple.TimeMachine MaxSize500000
    to return to ilimited
    sudo defaults delete /Library/Preferences/com.apple.TimeMachine MaxSize
    if you want to reclame deleted files space shrink it use
    hdiutil resize -size 500g -shrinkonly /Volumes/TimeMachineYOURNAME/YOURNAME.sparsebundle/
    Regards

  • Do I -need- to install Vista security updates? A few other q's as well..

    I'm just wondering how important security updates are if I don't plan on downloading anything on Vista, and if not having security on Vista will leave me vulnerable even when on OSX?
    Basically, the problem I'm stuck in is that I didn't partition enough space to install ALL the updates while leaving enough room for applications I needed. If security IS important, is there a way to make the partition larger without backuping / erasing and going through the entire process again?
    Also, my last question is: I know macs aren't susceptible to Windows viruses, if I download something that has a virus on OSX, now that I have Vista boot camp does it make it susceptible?

    Security updates for Windows are critical, as the majority of Web attacks "in the wild" target Windows itself. On the Mac OS side, things are a little less "busy", but security is equally as important. Apple tends to issue fixes in big roll-ups (by doing "point releases" such as 10.5.6 or issuing something like "Security Update 2008-008" in between. Further, Apple has taken to a policy of patching only the two most current revisions of the OS (Leopard and Tiger at present). Still, this is one area in which you, the user, should make every effort to stay current.
    That said, Windows malware can't touch the Mac OS, because Windows and Mac OS use different means of executing programs. Mac OS also has other protections that Vista in particular is only now incorporating into itself, such as requesting authorization before running a program. (XP also has this, but to a much more limited degree).
    So, even if you manage to pick up a nasty virus, it will just sit around doing nothing in Mac OS. But, that doesn't mean the virus has no potential to infect a Windows machine. Any mindful Mac user should not send files s/he suspects may be infected, for when a Windows user gets them, it's "game over" should the file be opened.
    You can use TwoCanoes' [Winclone|http://www.twocanoes.com/winclone] to resize the Boot Camp volume if you believe you didn't allocate enough space.
    Nate

  • I am trying to resize disk space on parallels 6 for windows XP under configure Hardrive and I get the error resizing failed unable to resize last volume the file system of this volume might be damaged or not supported?  I am on a Mac using Parallels 6

    I have been trying to increase my disk space for windows xp on my Imac and I am running parallels 6.  before opening windows I go into configure in parallels and open the hard drive and try to move the allotted disk space from 32 gig to 64 or any other increased gig and then apply and I get the error message: resizing failed unable to resize last volume.  The file system of this volume might be damaged or not supported.  How do I increase the size??  I just also did a disk repair utility with Apple on the Apple side of my IMAC.  Please Help!!   I had uninstalled SQL server on the windows side and needed to uncompress files to install this and then I ran short on disk space.

    This sounds to me that your Parallels XP file system is corrupted and not the OSX file system.
    Have you checked the XP file system while running the Parallels XP yet ?
    However, it would be better to ask such question in the Parallels Forum http://forum.parallels.com/
    Stefan

Maybe you are looking for

  • Favorites Delete button in WAD

    Hi, I am using the standard template 0ANALYSIS_Pattern for my queries. In this template, I have the Open and Save As buttons for the favorites. However, where is the "Delete" button in case the user wants to delete a favorite? Thanks for your fast re

  • Photoshop element 1.0 and internet explorer10

    Bonjour, Je possède photoshop element 1.0 surCD avec numérode série. Lors de l'installation sur un nouveau PC, ils'arrête avec le message "ne fonctionne qu'avec internet explorer  > 4.0" alors que je possède internet explorer 10. Comment l'installer

  • Ipod Suffle memory shows 550mb already used before any songs added.

    I just got my new ipod shuffle. When I connected it and started to add songs it showed that 550mb of the memory was already used but did not show what it was used for. I have not added anything to it. I just added songs and although it claims I can a

  • How do i find out?

    How do i find out which generation of i pod i have, i have a pink ipod mini bought 2005.?

  • Explanation of run time error & its process of elimination

    what is the following runtime errors .When does it occur & how can we eliminates these- 1. SYSTEM_NO_SHM_MEMORY 2. RAISE_EXCEPTION 3. UNCAUGHT_EXCEPTION With Regards Amit Singh