What does disk utility really do ?

I downloaded a lion 10.8 dmg from internet and wanted to make a installation portable disk.
And when I loaded the dmg, and used the 'disk utility' to restore installation files to one of my disk partitions, it just failed. And what is real annoying is that I got my disk partitions after the partition lost. And I can't get my important files back.
Maybe the 'disk utility' want to change the partition to be bootable and made the partition tables damaged.
Hope someone can help me to repair the disk and make the disk utility more secure !

varjak paw wrote:
There is no DMG of Lion, at least not anything legal. From where did you get this file?
Well there is a DMG of both Lion and Mt Lion. But it is included in the Lion/Mt Lion OS X Install.app package files and can be copied out.
But that is Not the Operating System. It is the Install files for the operating system. Restoring that DMG would, supposedly, give you bootable media for installing the OS on a drive.
To the OP I have found that the Restore feature/function in Disk Utility doesn't always work as expected. Best thing to do is use this program for creating a Dual Layer DVD or USB thumb of the Mt Lion install files. It works every time.
Make the USB thumb as most of the, Not So, Superdrives can't really write to Dual Layer DVDs. You will be very lucky if you have a Superdrive that will actually write to Dual Layer DVDs.

Similar Messages

  • What does Disk Utility mean by saying the back up disk cannot be unmounted?

    Disk utility has been giving me that error and I get about the same message when Time Machine attempts to do a back up as well. What does it mean?

    Hi! When you try to do a repair on a disk it "unmounts" (removes it from the desktop) (which locks the directory) so it can be repaired. Unmounting also is required for an erase. Time Machine shouldn't be trying to unmount it for a backup in fact it could write to it if it unmounts. Tom

  • Does disk utility repair delete any files on external hard drive?

    Does disk utility repair disk delete any files on the external hard drive?

    diskutil list
    Last login: Sun Dec 21 16:07:46 on console
    Justins-MacBook-Pro:~ justinmontoya$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *750.2 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:          Apple_CoreStorage                         749.3 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Macintosh HD           *748.9 GB   disk1
                                     Logical Volume on disk0s2
                                     4A646B29-3794-4A34-AC98-C0FB505D402B
                                     Unlocked Encrypted
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     FDisk_partition_scheme                        *500.1 GB   disk2
       1:                 DOS_FAT_32 500HDD WD               500.1 GB   disk2s1
    Justins-MacBook-Pro:~ justinmontoya$

  • How does disk utility decide which optical drive to use for burn?

    This is a somewhat daft question and purely out of interest.
    How does disk utility decide which optical drive bay to open for burning?
    I have two drives in a MacPro and both have the same capabilities (DVD-RW). Why does it sometimes open the lower one, and sometimes the top one?

    Grant Bennet-Alder wrote:
    The estimate is based on how long it already took to do how many blocks, and how many blocks are left to do. If you told it to overwrite 35 times, it will be a long, long time before it completes.
    The estimate is made grossly large by the presence of Bad Blocks that need to be Read during the test (not the case with Erase and Write Zeroes).
    Each Block is written with some redundancy bits, so that small errors can be corrected on reading. A Bad Block causes the drive to re-read. and re-read, and re-read, in hopes of getting correctable data the next time. This should NOT be an issue in writing. But if the drive stops responding (which can and does happen with a bad drive) the Erase function will just sit there, thinking it is making progress, and stretching out the time.
    Thanks, Grant.
    If I read your reply correctly, Erase and Zero Out free space shouldn't elongate the process, because there's no read occurring.
    The drive will not be Mounted while Disk Utility works on it, so it will not be on the Desktop. But ask Apple System Profiler \[ About this Mac > More Info > Serial ATA ] if the drive is still THERE . If it cannot be seen, you have your answer -- the drive dropped out of sight while being tested -- Bad Drive.
    Well, now I am confused. It's a FW800 drive. It's on the Desktop. And it appears under FireWire in System Profiler. AND Disk Utility shows a mount point. But the Unmount and Eject buttons are grayed out.
    Will the drive be mounted if it fails to respond to Disk Utility? That doesn't seem to make sense.
    How do I determine its status? It appears to be stuck at "1 day, 5 hours" but it'll take an hour for that to change. I think it's been that long since I first noticed the time.
    Harv

  • What is disk utility, what is used for?

    What is disk utlity, & what it used for?

    It is used for a variety of things, including disk repair (if the data structures that keep track of data on the disk get corrupted), repair of permissions on the system files if they get messed up, erasing and partitioning disks, etc.  As Linc points out, Disk Utility's help can give you all the details.  Note that some things cannot be done to the system drive unless you start up from a different drive.
    Also, note that if you're asking because you're deleting apps that you don't use, you really shouldn't do that with the preinstalled Apple apps, even if you think you don't have a use for them.  Sometimes deleting them can have unexpected side effects, and you never know when you might need such an app.

  • What is Disk Utility parameter : 'Owners Enabled' about?

    There is a parameter in the Disk Utility dialogue window , bottom left corner that says (on mine) Owners Enabled: No.  What does that signify and how, where or why is it set?

    That parameter can be set manually in the getInfo window of the drive itself (in Finder, not inside Disk Utility). See if this adds any insight:
    PH10670- OS X Mountain Lion: If you don’t have permission to use a disk

  • Why Does Disk Utility Say "This Partition Can Not Be Modified"

    I've got an external drive with three partitions. I want to expand the first partition. (It's a backup of my internal drive and it isn't big enough anymore.)
    All partitions are Journaled. All verify okay. The disk's partition map is GUID.
    Disk utility will change the size of the 2nd and 3rd partition, but when I click on the first partition, the one I want to expand, it says "This partition can not be modified."
    I've tried making another partition smaller, but that doesn't help.
    Does anyone know why? Or what I can do about it? (Can I delete that partition, make another one smaller and then create a new bigger one?)
    Many thanks in advance.
    Steve

    Thanks, guys.
    I ended up taking one of the existing partitions, making it smaller and then adding a partition of the size I needed -- created out of the space freed up. I also erased the original partition that I couldn't change and Disk Utility now says I can make it smaller, but not bigger.
    Bottom line in my case -- all partitions except the first could be made smaller. But none could be made larger. (Maybe the first one couldn't be made smaller because it was full?). That caveat -- 'you can make 'em smaller but not larger' -- is not mentioned in the help file, but that's what I saw.
    Make sense?
    Thanks again,
    Steve

  • Why does Disk Utility keep breaking my partition table?

    I have two drives in my Mac Mini - the original drive it came with, and a SSD drive.  I dual boot from the SSD drive and it is fine.  On my original drive, I still have the original Lion install, but I would like to add a NTFS partition for use by windows.  The problem is that every single time I have Disk Utility try to do something to it, like delete a partion, it breaks the partition table.  It does delete the partition, but then it goes and sets all the partition types to 07 (Microsoft BAsic) instead of AF (Apple HFS).  Then Disk utility will claim the disk is broken and can't mount the partitions anymore.  I have to go in with gdisk to set the partition type back to AF and it will start working again.  BTW, gdisk claims the partition table type is hybrid MBR, even though windows is not installed on it.  Diskutil thinks it is GUID.  I did create a partition on it from the windows side once if that means anything.
    Now what I want to do is resize the HFS partition, but I am deathly afraid that DU will break something that isn't as easy to fix.

    I repaired permissions because I reinstalled Epson drivers, and reinstalling Epson drivers has  given me a permissions problems in the past which was cured by running permission repair. As it is an easy prophylactic step to take, I did it again.
    It may not be needed, but that is not the issue, which is why, when the permissions are indicated as repaired, are they not.
    Other previous posts on this issue suggest that these indications of permissions not being repaired should be ignored, so the report made by Disk Utility is simply a programming error.
    Disk Utility needs some work if it is going to respond to usage by a typical average user this way.

  • How does Disk Utility estimate completion time?

    I'm sending an external drive back to the vendor for troubleshooting, and want to make it more difficult for a curious tech to examine the data there. So I told Disk Utility to Zero Out Data and Erase Free Space. The drive was just initialized, so it's all free space. Did I mention it's a 2 TB FW800 drive?
    Anyway, when I started this yesterday, the time estimate was 14 hours. (No hissing please.) Sleep is only enabled for the display: computer and HDs are set to "Never" sleep.
    When I checked this afternoon (about 24 hours later) the estimate was "1 day, 5 hours."
    How is this estimate calculated?
    Thanks,
    harv47

    Grant Bennet-Alder wrote:
    The estimate is based on how long it already took to do how many blocks, and how many blocks are left to do. If you told it to overwrite 35 times, it will be a long, long time before it completes.
    The estimate is made grossly large by the presence of Bad Blocks that need to be Read during the test (not the case with Erase and Write Zeroes).
    Each Block is written with some redundancy bits, so that small errors can be corrected on reading. A Bad Block causes the drive to re-read. and re-read, and re-read, in hopes of getting correctable data the next time. This should NOT be an issue in writing. But if the drive stops responding (which can and does happen with a bad drive) the Erase function will just sit there, thinking it is making progress, and stretching out the time.
    Thanks, Grant.
    If I read your reply correctly, Erase and Zero Out free space shouldn't elongate the process, because there's no read occurring.
    The drive will not be Mounted while Disk Utility works on it, so it will not be on the Desktop. But ask Apple System Profiler \[ About this Mac > More Info > Serial ATA ] if the drive is still THERE . If it cannot be seen, you have your answer -- the drive dropped out of sight while being tested -- Bad Drive.
    Well, now I am confused. It's a FW800 drive. It's on the Desktop. And it appears under FireWire in System Profiler. AND Disk Utility shows a mount point. But the Unmount and Eject buttons are grayed out.
    Will the drive be mounted if it fails to respond to Disk Utility? That doesn't seem to make sense.
    How do I determine its status? It appears to be stuck at "1 day, 5 hours" but it'll take an hour for that to change. I think it's been that long since I first noticed the time.
    Harv

  • Disk Utility really doesn't repair disk

    When repairing permissions disk utility finds and repairs permissions that are not correct.However,when the repair permissions utility is ran again it finds the same errors and says it fixes them again and again and again.What gives? Thanks.

    Have you visited [Disk Utility's Repair Disk Permissions messages that you can safely ignore|http://support.apple.com/kb/TS1448]?
    And, why are you repairing permissions? Do you have file access problems? Are applications reporting that they can't find or open some files?

  • What is disk utility for?

    what is the function of disk utility under application? can someone tell me how to use it?

    The hatter wrote:
    It is used to format drives, repair permission, and has some ability to repair disk errors, though most go with Disk Warrior.
    I think thats a very brief summary of what DU can do, and I'd advise you to check the OSX Help for more DU usages. I'd write that DU can also: repair start-up disk, get info on a disk or volume, create a RAID HD array, SMART-based diagnostic for HD failure, transfer or back-up data as a disk image, burn a CD or DVD, protect info on removable media, see contents on disk image, erase and secure erase a disk/volume... etc
    I don't think most Mac users head straight to DW either. I may be guessing but I reckon most simply let their Macs run and run using Leopard with no care at all for file system maintenance. Nonetheless DW is useful third-party utility for some forms of file system repair, though many only bother with it if DU or other means of OS X trouble shooting haven't sorted out the issue first.

  • OSX 10.5.6 doesn't see Fibre Channel Disk array, neither does Disk Utility

    My system is a Power Mac G5 Quad, 6gb Ram, 1Tb internal hard drives, 1Tb external and several portable drives as needed.
    The Drive array in question is a Fujitsu GR710 which contains 12 Seagate Cheeta ST336605FC drives which are around 35gb each.
    OK, I have been given a Fibre Channel system, that at one time worked with OSX. I had to move it and now it doesn't show up on Disk Utility anymore. I can totally reformat it if possible, but I have to be able to see it first.
    System Profiler sees the setup as:
    Fibre Channel Domain 0:
    Vendor: LSILogic
    Product: LSI7202EP
    Revision: Firmware 1.2.18.0, Fcode 1.00.37
    Bus: PCI
    Slot: SLOT-2
    Initiator Identifier: 126
    Node World Wide Name: 20:00:00:06:2B:12:C4:C4
    Port World Wide Name: 10:00:00:06:2B:12:C4:C4
    Address Identifier: 00:00:E8
    Description: Port 0
    Speed: Automatic (1 Gigabit)
    Topology: Automatic (Arbitrated Loop)
    Status: Link Established
    Cable Type: Fiber Optic
    SCSI Target Device @ 0:
    Node World Wide Name: 20:00:00:E0:00:41:04:6D
    Port World Wide Name: 21:00:00:E0:00:41:04:6D
    Address Identifier: 00:00:EF
    SCSI Target Identifier: 0
    SCSI Peripheral Device Type: 0
    Manufacturer: FUJITSU
    Model: GR710
    Revision: 0000
    SCSI Logical Unit @ 0:
    SCSI Logical Unit Number: 0
    Manufacturer: FUJITSU
    Model: GR710
    Revision: 0000
    Fiber Channel Preferences shows that a link is established.
    Hardware RAID says that there is no hardware present.
    I am using the Apple MA900A/G Fibre Channel Card to hook into the Drive array. It is hooked up with both ethernet and fiber optic cables.
    I have used an IP scanner to search for the IP of the array and only find one that I can't identify at 224.0.0.251 another scan reports an IP of 0.0.0.0, neither worked when I tried to use Safari to access it.
    I have tried several programs to try and get into this array and nothing sees it. All my experts tell me that I will need to use the Terminal program and use command lines to access the drives, but I can't find any information about what to do there. I've been told I need the driver for the array, naturally there isn't a driver for Mac to be had, but there are drivers for solaris, Unix, and windows. The last expert said to use the Unix driver, but I don't know where to put it in the system.
    So I need help, Terminal commands to talk to the drive and revive it hopefully, or a system program that will do something similar. None of my diagnostic programs sees the array. The Card came with no software or instructions. Neither did the array. I haven't been able to find any hardware information about the drive from FuJitsu at all, it's too old for them to bother with anymore.
    Any help would be greatly appreciated!
    Thanks
    Doc

    I have to go with William on this one - if it's shows up over fibre then it should be okay. Have you gotten the admin module to see the device over ether? I have a feeling that is you can get the software to see it you might be able to configure the device into something the computer could mount.
    The Promise that way - you can configure the device entire from the web interface and you don't need fibre communication working for any of the configuration of what RAID you want and which disks are attached with what set etc. Once the RAIDs are configured into volumes then the Xserve sees they exist and you can use Disk Utility to format them. If you don't need fibre communication I don't see how SCSI drivers would matter over ethernet. But maybe the box is a strange beast - odder things have been made.
    Barring that - can you attach the device to an older machine with the drivers and configure the device into raw volumes and then an HFS+ (or whatever you want) system? If you did that and then switched the box back to Xserve it should be able to pick up the configured volumes drivers or no.
    My $.02,
    =Tod

  • Does disk utility damage the Hybrid MBR

    I have a dual boot system for Mac X 10.8 and Windows 8 and there are 5 partitions on my internal HD (EFI, Mac OS X, HD Recovery, Mac HFS Data, NTFS Windows 8). I created a custom Hybrid MBR that allows dual boot to partitions 2 and 5 and protects the remaining partitions. The MBR shows 4 partitions (max allowed) so it does not precisely agree with the GPT. This all worked fine in conjuction with rEFIt for booting.
    Recently after using Disk Utility to check and repair my internal HD the custom MBR was apparently compromised because I was unable to boot into Windows. My question is then, "Can Disk Utility damage the MBR that I carefullly customised?" I could rebuild the MBR using gdisk in terminal but I don't want to have to repeat this unnecessarily. If not Disk Utility, do other programs mess with this area of the disk? I also use Carbon Copy Cloner to make a periodic clone of my start-up partition.

    diskutil list
    Last login: Sun Dec 21 16:07:46 on console
    Justins-MacBook-Pro:~ justinmontoya$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *750.2 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:          Apple_CoreStorage                         749.3 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Macintosh HD           *748.9 GB   disk1
                                     Logical Volume on disk0s2
                                     4A646B29-3794-4A34-AC98-C0FB505D402B
                                     Unlocked Encrypted
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     FDisk_partition_scheme                        *500.1 GB   disk2
       1:                 DOS_FAT_32 500HDD WD               500.1 GB   disk2s1
    Justins-MacBook-Pro:~ justinmontoya$

  • Where does Disk Utility define NFS mounts?

    Hi, I used to use Disk Utility to define a NFS mount point for my Drobo, but then I sold the Drobo and deleted the mount point from Disk Utility.  However, my system.log file shows that rpc.statd is trying to find the Drobo once every hour still.  I double checked and there is nothing listed in auto_master, so the only place I can think of that Disk Utility defines the mounts within is Directory Services but I can't find where.  Does anyone know where Disk Utility defines NFS mounts and how I can clear it out?

    Mountain Lion NFS Mounts Missing In...: Apple Support Communities

  • Does Disk Utility defragment files during clone?

    Scenario:
    Boot from OS X (10.6) install disc > run Disk Utility > format a second drive (internal SATA) using HFS+ (Journaled) > Restore tab > Erase and Restore function
    Question:
    Does the above procedure actually defragment file clusters or just remove fragmented free space during the 'clone' process?
    Thanks in advance for knowledge.
    Note - this question was prompted by a post regarding fragmented Aperture library databases but I realized this is probably a better place to raise the question.

    No. When you clone to a freshly formatted drive the result is by definition defragmented. That is because the destination's sector blocks are sequential. Fragmentation only occurs when a file is changed and requires more space than was used by the previous version. If there isn't a contiguous block of space available then the OS uses any available block elsewhere. This results in the file not being saved in a contiguous block of space - hence fragmentation.
    Therefore, when you clone a drive to a newly formatted drive the result is a fully defragmented drive. This is the fastest and safest way to defragment a drive: clone it to a newly formatted drive, erase the fragmented drive, then clone back.
    Fragmentation is unlikely to occur unless files over 20 MBs are being frequently changed and re-written to a drive that hasn't enough free space to continuously change large files that are growing. These files can no longer be saved into a contiguous block of space - hence they become fragmented. Otherwise OS X automatically defragments files under 20 MBs on the fly. Typically rapid drive fragmentation is more a problem from small files than very large ones.

Maybe you are looking for