Tag Info

Hot answers tagged

10

The HDD is formatted using FAT32 which has a known limitation of 4GB file size. You need to format it using exFAT which is supported by OS X and Windows.


7

If I understand your question correctly you are trying to resize the volume group or actually one of the volumes within a group. From what I could gather your disk was converted to a CoreStorage Volume. Could you please verify that by issuing the following command in a terminal and check if you get a similar output to the one in the picture: diskutil ...


5

I recently had the same question and found a command line tool www.smartmontools.org which can be installed via brew: brew install smartmontools you can then run it smartctl -a disk0s3 for the full report where disk0s3 is the disks physical baking which can be found in Disk Utility.app by getting info on the drive. (There must be a way to find this ...


5

If you are facing a healthy file system at the level of its structure and want to find files which have disk faulty blocks, here is how I would proceed: Make a full backup of your disk with Time Machine or Carbon Copy Cloner Check this backup. Run the following heavy and risky (in case you do have bad blocks outside of your filesystem structure) command: ...


4

Reboot in single user mode by holding the Command + S during boot. When you see a prompt (should look like root # or something similar), type fsck -f and press Return. This is Mac's built-in filesystem consistency check tool and allows you to find and repair errors with the startup file system. Run this command until you don't see **The volume [volume name] ...


4

If your partition turned into Logical Volume Group (you can't resize or delete Yosemite partition), you can revert partition type with few command line. Open Terminal type "diskutil corestorage list" Find Yosemite partition UUID string. type "diskutil corestorage revert " Your Yosemite partition is now revert to default partition type. Now, you can resize ...


4

I had the same problem after converting a disk. There was a message displayed by diskutil cs convert: Couldn't unmount disk0s4; converted volume won't appear until it's unmounted I solved the problem by unmounting the disk and repairing it : diskutil unmount force disk0s4 diskutil repairVolume disk0s4


3

I also have this issue... MacPro, 3TB drive (Seagate). I have to use the terminal: diskutil list diskutil unmount /dev/disk22 diskutil eraseDisk HFS+ "Macintosh HD" /dev/disk22 etc etc to utilize this drive correctly. (Sorry for all the commands. Posting them just in case it helps someone. Though anyone using those commands better know what they do ...


3

Apple's bespoke command line utility to do disk cloning is asr. It is tailored to the specifics of OS X needs to perform file by file as well as block based imaging and deals with differences in partition sizes, allows network streaming (and even multicast streaming) as well as copying between disks that are locally connected. Unlike dd, it knows about ...


3

I've struggled for some days with the same problem but now it is solved. The problem was a faulty SATA cable. I've replaced it with a new one and now everything works as expected.


3

The process is UnmountAssistantAgent, therefore can be killed using: killall UnmountAssistantAgent


3

Your partition table does not know about the larger hard drive yet. While Disk Utility also queries the hard disk size and lets you request it to enlarge your partition, it will fail when finally changing the partition size (after doing a file system check). This can be solved on different ways: One is to destroy the GPT (partition table) and recreate it ...


3

None of the HFS flavors will offer any performance benefit that's measurable. I have seen encryption slow down some storage medium such as slow USB flash and I would expect journaling there to also be more of a slowdown than on storage with fast cache or more responsive write service times. I suppose journaling could in some rare circumstances (bizarre edge ...


3

The apparent issues seems related to FileVault. The following steps seem to be the cure: Go to “System Preferences” – “Security and Privacy”, click on “FileVault” tab, click the lock icon on the bottom left to unlock, then click on “Turn Off FileVault”. The decryption process will take a while (hours). When the decryption is done, reboot into Recovery HD. ...


3

You can use diskutil cs list to show the core storage view of things. Once you have the logical volume UUID for the disk in question, you can use diskutil cs deleteVolume to clean up the reserved space that was allocated to the encrypted data and filesystems. That would allow you to surgically remove the core storage. You could also unmount the filesystems ...


3

The Disk Utility Repair Permissions command is just a front end for the repair_packages program. Use this: /usr/libexec/repair_packages --repair --standard-pkgs


3

I highly recommend completely backing up the machine before attempting this, either using TM with no exclusions set, or better yet, cloning the whole drive using a program like Carbon Copy Cloner. Unmount the Logical Volume: sudo diskutil unmount force /dev/disk1 Remove the Logical Volume Group and all of its contents: sudo diskutil cs deleteLVG ...


3

You do know that RAID 0 is only striping and not only provides no redundancy, but increases the risk of data loss as the failure of any single drive can mean the loss of the entire storage pool? RAID 0 is only for increasing read and write speeds, for example for video editing. You need at least RAID 1 or 5 for redundancy. That being said, if you're losing ...


3

There is a slim chance to repair it with command line (in Terminal) fsck Option 3 (advanced): Use the command line and the fsck_hfs -l command. Start up your computer and log in as an administrator. Open Terminal (/Applications/Utilities). At the prompt, type the following command and then press Return to determine your filesytem ID: df -hl Look for ...


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 ...


3

You cannot erase the currently-running volume. Shut the computer down, restart while holding the option key, and choose the Recovery HD. Find Disk Utility in the menus and you will now be able to erase your internal storage.


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 ...


2

You could setup a Mac OS X Server and boot from the network, however you will need to have a third Mac, which might be costly unless you have an old one. You can purchase the Server from the AppStore for $20. However, booting your Mac from your server requires a moderate internet connection as well as a quick bandwidth (at the place where the server is and ...


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 ...


2

You're using Apple's RAID which means you need a device which just hosts the discs and then your new laptop will see them and use the existing RAID structure. This rules out NAS. AS these are existing RAID arrays you can't simple merge them together to create a single new RAID. At least, you can't while keeping the data on them. Essentially, in one device ...


2

Yes! First get the UUID of the partition you want to prevent from mounting... You can get this in Disk Utility "Get Info". Now open your /etc/fstab file for editing: sudo pico /etc/fstab In this file add the following line (use your own UUID naturally): UUID=[your UUID] none hfs rw,noauto 0 0 And save the file. Restart for the change to take ...


2

One thing to try that is perhaps extreme is to place the drive in a few layers of freezer bags and cool it in the freezer, and then try to get it to mount, and copy off what data you can until it fails again, and then repeat this process. Its absurd, but it has worked for me and there is a lot of anacdotal evidence that this can help recover data, regardless ...


2

I would highly recommend DiskWarrior for rebuilding disk catalogs and for scanning for potentially damaged files. During the catalog rebuild, it can also let you know if it experiences a delay because of disk malfunction.


2

Before trashing it try this: In disk utility Under the Volume Scheme heading set the number of partitions from the drop down menu to one. 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. ...


2

There is a app on your drive already. The Migration Assistant.app in /Applications/Utilities Try it.



Only top voted, non community-wiki answers of a minimum length are eligible