Tag Info

New answers tagged

1

I am not an expert in OSX partitions but I suspect Carbon Copy Cloner mucks up the partition table somewhat so that start and end cylinders are not correct, or something like that. I may leave my new SSD as it is exactly the way you did it, or try Mike's (Bombich) suggestions to manually create the partition. By the way, they have released version 4 of ...


0

IN DISK UTILITY SELECTED PARTITION THEN MADE 1 PARTITION ADDED A NAME FOR THIS SSD PARTITION AND APPLIED. THIS DID THE TRICK. NOW I CAN SEE NEW SSD IN FINDER AND CAN LOAD INDIVIDUAL FILES AND ALSO SEE IN CARBON COPY CLONER FOR FULL CLONE BACK UP.


0

Before you can clone your hard drive with CarbonCopyCloner, you need to create a partition on the drive and format it appropriately for use with your Mac. Most external drives come pre-formatted for use with Windows machines. You can use Disk Utility for this purpose. You'll find Disk Utility under /Applications/Utilities/Disk Utility on your machine. In ...


-1


0

As of Nov. 2. 2014 there is a report regrading that problem. http://www.larryjordan.biz/caution-ssd-drives-and-yosemite/ If you own a 3rd-party SSD (Solid State Drive) unit and plan to upgrade to Yosemite – you NEED to read this. The issue revolves around Trim utility software used by the SSD drive. For possible fix read here. ...


0

This cannot be done in Disk Utility, or even while running the OS in the active partition. I normally backup the partition to an external HD, then restore to the Mac. This is easier if you have another OS, but you should be able to do it from the Recovery mode. Another option is to remove the HD, and do it on another Mac. There may be 3rd party utilities ...


0

I am currently going through the same thing myself. The SSD is not likely toast as some suggest. For my situation, I have installed a second 1TB SSD on my Mac Mini 2012. I tried with a 500GB one with no problems (except a defect in the drive), so I decided to upgrade to a 1TB. After installation, I could see the drive on Disk Utility but not format it for ...


1

With the encryption process included in Yosemite there is a duplicate drive created in the space after the drive that was encrypted. If I'm entirely honest I don't know how that works or what its purpose is I just know that every encrypted machine in this situation has it. That being said you can see using diskutil that your ssd does have a recovery drive on ...


0

The reason is probably that you have local snapshots of time machine backups (http://support.apple.com/en-us/ht4878). The difference is that the Finder calculates the free space you can use (the backups would be deleted if necessary). They are stored at /.MobileBackups (at least that's what it has been in Mavericks iirc) if you want to have a look and verify ...


0

For a start, you can go to "Startup Disk" under system preferences to start up into your old OS X from Yosemite. From there maybe you will be able to partition/fix however you like.


1

Plus 1's for everyone as far as I'm concerned. A good question and two good answers. I'd like, however, to emphasize the following quote from Bob O: Steer clear of any tool that tells you it's going to take a bad sector and "repair" it. There's no such thing. That's a dishonest marketing trick that has it's roots back in the 1980's when drives were ...


2

Klanomath's procedures are 100% correct if it's a hard drive. I use a tool named Scannerz to evaluate drives and it's extremely conservative. If you find bad blocks their procedures are pretty much exactly what Klanomath described, except it will be quite evident how extensive the damage is during testing. SMART technology only finds bad sectors if a write ...


1

According to wikipedia 3 levels of formatting are common: Low-level formatting (i.e., closest to the hardware) marks the surfaces of the disks with markers indicating the start of a recording block (typically today called sector markers) and other information like block CRC to be used later, in normal operations, by the disk controller to read or ...


0

I've solved this way... https://beshoy.girgis.us/2013/11/solved-error-disk-utility-cant-repair-disk-backup-many-files-possible/ Tried multiple times to repair the disk...


-1

The volume of the disk is damaged and you should repair the disk.


0

Your volume Macintosh HD is a Core Storage Logical Volume and part of a Core Storage volume group and thus can't be modified by iPartition or Disk Utility. You have to boot from an external disk, a thumb drive or in the Internet Recovery Mode to be able to modify the volume with some Terminal commands. The following diskutil cs resizeStack command is ...


1

Ha, found it! It was a corrupted ".Trashes" folder in the root of the SSD. It occupied me than 100GB of data (see screenshot). I managed to make these files visible by running GrandPerspective from the command line: sudo GrandPerspective.app/Contents/MacOS/GrandPerspective That will show the files but still it is not possible to delete them. Even sudo ...


0

I rebooted the iMac and replugged the WD Time Machine 3 times --it would not mount and "could not be found". Wondering if it simply might be the cable connection I twisted the cable so I could insert the plug into its reverse position. It immediately mounted as it should as the lighting bolt plugs are reversible. Perhaps it was just a bad connection on a ...


-1

I find many times it relates to disc space. reboot holding down CMD + S (safe mode ) once on the command line, issue a df -h command to view disc usage. if low on disc you may issue another command for finding big files and deleting some: sudo find / -size +500000 -print (will display files bigger than 500 MB) this might take some time so sit back for a ...


3

The following diskutil cs resizeStack command is vastly undocumented and as such potentially destructive. There might be an easy way outlined first and a long winding, time consuming hard way. Please backup your Mac OS X before proceeding. The not-as-long-as-expected way: A 2nd computer or an iPhone with the stackexchange credentials to enter the site ...


0

So if I understand you correctly, all you want to do is wipe your disk and reinstall OS X. Boot into recovery mode Choose "Utilities" in the Menu bar Select "Disk Utility" Select the disk Click on "Erase" and select "Mac OS Extended (Journaled)" Then you should be able to do a fresh install of OS X.


2

The phenomenon derives from a faulty Apple Script mounting a Time Machine sparsebundle image from a smb-share serving as a Time Machine backup volume to /Volumes. The mounted image interferes with (maybe any) other mounted volume(s) there The faulty Apple Script: try mount volume "smb://someserver/DATA" end try do shell script "/usr/bin/perl -Ue ...


0

I found this in my own search.. hope it helps. http://crucialsecurityblog.harris.com/2011/03/30/4/ "Crack and Image a FileVault Sparsebundle"


0

I've figured it out! Though still appears that converting a dmg file to an encrypted one using Disk Utility is still broken as of OS X 10.10 (Yosemite), I've figured out a way to do it via terminal using this: hdiutil convert /PATH/TO/FILE -format UDZO -encryption AES-256 -o /OUTPUT/FILE This converts a dmg using AES-256 encryption and uses zlib ...


1

There are at least two approaches to solve your problem: One is potentially destructive, vastly undocumented and i don't know if it works (1) and the other one is for sure destructive (2). So please backup your Mac OS X and your Ubuntu partition if necessary. Requirements: USB thumb drive with a full working Mac OS X and iPartition installed or a Linux ...


0

You might lose them. According to this thread on Adobe's forums, other users experienced issues with restoring an entire drive from Time Machine. It looks like, from some cursory research, that the plist files or FlexNet folders don't get restored (even if they are present in the backup), and that Adobe's recommendations are to delicense before restoring and ...


0

When you plugin a damaged Apple_HFS disk into Mavericks/Yosemite it runs fsck_hfs on its own. You can see the output (in Terminal): tail -f /var/log/fsck_hfs.log Wait for it to finish before running repair yourself. Also repair needs to be run repeatedly to repair some errors. I recently needed to launch it 7 times but it repaired the disk successfully ...


1

A clean install is not necessary, you simply need to reconfigure your NVRAM (nvram boot-args=kext-dev-mode=1) to disable the kext signing requirement for OS X. (After which, you can remove your TRIM enabler and reverse this change or leave it until the next time your NVRAM is changed/resets) A very clear explanation of OS X 10.10 Yosemite's new policy ...


1

I did fix this by resizing (making it a bit smaller) the Partition1. After doing this I was able to delete/resize all the other partitions. Well, I have no idea why this happened, so this is not a real solution but probably a bug of diskutil.


0

You can blow away a corestorage disk partition by booting in Single User Mode... then use this command: WARNING: THIS WILL RUIN ALL DATA ON THE DISK!!! dd in:/dev/zero out:/dev/disk0 After a moment you will see an error that the corestorage volume has come offline unexpectedly (that is because you have destroyed it). You can now type Ctrl-C to stop ...


0

1 TB? I presume that's a Fusion drive. Fusion drive can at most have 2 partitions.


0

It is completely possible that the SSD is toast. It is also possible that Disk Utility just can't fix it. There are other disk repair utilities out there like DiskWarrior, Drive Genius and the like. If you don't have one, you should. you won't use it often but will be glad you have it when stuff like this happens. Failing that and assuming that you already ...



Top 50 recent answers are included