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

It's simply telling you that the file has been modified, and because it's currently being accessed Disk Utility can't fix the permissions on it. ARDAgent.app is the Apple Remote Desktop agent, and the file shown in the path above is the binary file contained within the app package. This indicates that the app is currently open, and therefore in use. It's ...


6

You can force unmount a drive by running the following Terminal command: diskutil unmountDisk force /Volumes/VOLUMENAME Replace VOLUMENAME with the name of a volume on the disk you are trying to unmount. Following this, attempt to Erase/Partition the drive again in Disk Utility. Using the above command can interrupt file read/writes, which can cause file ...


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


4

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


3

NOTE FOR CASUAL READERS: rm -rf destroys data. Use with caution. rm -rf may appear to go fast, but it is actually recursively going depth-first into each directory and unlinking the files within—the same operation that is used for any file deletion on Unix systems. You can see how rm -rf works by adding the -v flag, e.g. rm -rfv. There's no reason to ...


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

From this blog post: A customized .sparseimage file can be made larger than the total capacity of the physical volume on which it originally resides. While the sparse image volume will seem to make that capacity available, attempting to exceed the physical capacity of the underlying volume will result in a disk error: "ran out of space." A couple of ...


3

In addition to the Unix file permissions, there are old HFS file bits. To unlock your folder try: Terminal > SetFile -a l ~/sites/lockedfolder OR Terminal > chflags nouchg ~/sites/lockedfolder Alternatively, you could do a Get Info in the Finder, and uncheck the "Locked" checkbox from that window.


3

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


3

Don't worry, this is one of the messages that are safe to ignore. For a full list, visit the Apple Knowledge Base article on this topic.


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

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


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

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


2

Yes - OS X offers software RAID functionality on both the Server version and consumer OS. Open Disk Utility and read through the help on RAID. Create a single, large disk from several smaller disks by creating a concatenated disk set, which is also called “Just a Bunch of Disks” (JBOD) or “spanning.” The concatenated disk set acts as one large disk with ...


2

iPartition For all my partitioning, I use and recommend iPartition. It will allow you to resize partitions without deleting any data. It also works for Boot Camp volumes and other PC disks. With iPartition, resizing a partition is as simple as selecting it, grabbing the resize handle and dragging. Not only that, but if you have several operations to ...


2

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


2

I've had the same problem with a 3TB Barracuda and a 3TB Deskstar. The only fix was to delete the logical volume diskutil CS in the terminal. Also running 10.8.4 on a 2009 Mac Pro (upgraded to macpro5,1 firmware).


2

The resizing can be finicky when there is a gap in the space between the partitions. Especially when if not all the logical volumes / partitions are HFS+ format. It's not clear that you will be able to do this without seeing the core storage listing and the normal listing: diskutil list diskutil cs list The first shows how the filesystems are mounted ...


2

This is probably due to an issue with Finder. Relaunch finder with the following command in terminal: killall -HUP Finder


2

I take the following to mean that YES, 7-pass (or 3-pass) may find more bad blocks than a single pass, by the mere fact that some blocks may be, well, "iffy" and need more than one pass to be found and excluded. Please correct me if I am misinterpreting the following: [T]he Zero Out Data option... will trigger the drive's built-in Spare Bad Blocks ...


2

That's basically the only way unless you have one of the older mac pro's with the raid card. if I was you over usb id leave them as stand alone drives.


2

a) You can use the free and open source Mac Linux USB Loader app to make a bootable USB drive. OR b) Follow the instructions for How to create a bootable USB stick on OS X (it has a step to convert ISO files to IMG before writing it to the USB drive).


2

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


2

Download BatChmod, free and very, very handy. When one is done working, correct permissions are easily restored.


2

Yes. Reformat and partition the HD. When you unplugged the drive, you severely damaged the directory information on the 'My Passport' partition, rendering it unusable. If there is nothing of value on the drive, this is your best bet. In addition, make sure to reformat with Mac OS Extended (Journaled) selected.


2

Same problem here. Read and on and I'll tell you what I did to solve this problem: I do Time Machine to an encrypted external Hard Disk. I stored the password to the disk in the default Keychain, and the system mounted the disk automatically after plugging it in. But suddenly, last morning, after I plugged in the disk, it prompted me for a password (it ...


2

Have you tried looking at the kernel log messages? If, as you said earlier, it tried to root from the drive at least once, you can try to find it in the /var/log/system.log, for example: $ grep 'rooting\ via' /var/log/system.log Oct 24 18:01:44 localhost kernel[0]: rooting via boot-uuid from /chosen: 4AB3D289-884F-379C-AF7B-************ Oct 25 11:21:57 ...


2

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



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