Tag Info

Hot answers tagged

15

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 backing which can be found in Disk Utility.app by getting info on the drive. (There must be a way to find this ...


12

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


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.


8

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


6

There is a slim chance to repair it with command line (in Terminal) with the terminal utility as described in Apple's support docs, shown below: 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 ...


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


5

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


4

To be able to create a multi-boot environment you have to revert from a CoreStorage partition layout to a standard partition layout. Start to internet recovery mode by pressing altcmdR while booting. Open Terminal.app in the menubar Utilities → Terminal enter diskutil cs revert LVUUID and hit the ⏎ key. (LVUUID is the Logical Volume UUID. You get it by ...


4

Theoretically everything is fine with your Fusion Drive. Fusion Drives look like this. Disk0 is your SSD with 121 GB and disk1 is your HDD with ~1 TB (~1.121 TB summed up). The larger parts of your SSD (disk0s2) and your HDD (disk1s2) are pooled to a CoreStorage LVG (Fusion Drive: disk3) with a size of 967.8 GB. The rest is reserved for EFIs, a Recovery HD ...


4

The original post mentions that SSDs have a 1000-2000 cycle limit, which over-simplifies the problem. Individual cells in an SSD may have such a limit, but the SSD implements many different solutions: from over-provisioning and write-levelling to Sandforce's proprietary collection of de-duplication, compression, and data differencing techniques, which it ...


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

The error message is pretty unclear, but one reason might be that you are not connected to the power outlet. Compacting a disk image might be a long and intensive task, and sometimes the OS denies it when you are running on battery to avoid any risk of data loss. If you are positive that you have enough battery power to complete the task, you may overrun ...


4

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

Testing cabling is more of an empirical exercise. First you disconnect and reseat both ends of the cable. Next, you put in the new cable and if the problem goes away it was the cable. If you suspect the cable on an intermittent problem you replace the cable and leave it in after reseating doesn't reduce the frequency of the issue. I'd start with reseating ...


3

I had a similar problem. I created a 30 GB partition and after deleting it there was unused space. I couldn't manually get the original full partition back because of disk errors. So I booted into Recovery (Command + R), repaired the disk with Disk Utility and then the resize to original was no problem. Rebooted and now back to normal. Had no need to ...


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

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

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

To delete CoreStorage volumes you have to use the CLI: please backup your volume "mainHD" boot to Internet Recovery Mode (hit altcmdR immediately after the start-up chime) open Disk Utility and check/repair mainHD quit Disk Utility , open in the menubar Utilities/Terminal.app and enter diskutil cs deleteVolume LVUUID to delete the Logical Volume in your ...


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.


3

Basically you have a CoreStorage Logical Volume Group without a CoreStorage Logical Volume now. You may delete your Logical Volume Group (-> step 4) or restore a Logical Volume (-> step 7). Requirements: Booted to Recovery Mode Please quit Disk Utility. Open Utilities/Terminal in the menubar Enter diskutil cs list and hit enter. The output will look like ...


2

Boot into Recovery from the USB. Instead of opening Disk Utility, open Terminal instead. Run the command diskutil list to see that your drive is being recognised. It should list two disks, one being your bootable drive, the other your SSD, and provide you with a disk identifier (such as disk0). If it doesn't show up, check that you have installed it ...


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 try booting off a Linux LiveUSB to back up your files. Once that is done, you can reformat your HD and then reinstall OS X. You should also keep an eye on your HD; these types of errors often suggest that your drive is corrupted or damaged.


2

Read out the following S.M.A.R.T attributes of your SSD with an appropriate tool*: 241 - Total LBAs Written: The total number of 512-byte sectors written during the entire lifetime of the device. 242 - Total LBAs Read: The total number of 512-byte sectors read during the entire lifetime of the device. A second set of attributes is: 174 - ...


2

Your Recovery HD doesn't occupy your whole 3 TB drive. It's disk1s3 in the diskutil listing with the common size of 650 MB. Your Logical Volume Family and the Logical Volume vanished though. To rebuild it start to your Recovery HD or to Internet Recovery Mode, open Terminal and enter diskutil cs list. Copy the LVGUUID To recreate the LV enter diskutil cs ...


2

Disk1 is a "virtual device" which resides in disk0s2 (the Apple_CoreStorage Volume Group which actually contains a FileVault volume). You have only one 'physical device' indeed. Disk0s5 is probably an old Bootcamp installation. The clean way (get rid of the 2 Recovery HDs): Make a complete Time Machine backup of Macintosh HD. Start to Internet Recovery ...


2

The problem turned out to be the PMBR. My first attempt was to copy sector 0 off a GPT formatted memory stick. Examined that with fdisk and it had partition of type EE, but start and end cylinders were the same. I edited partition 1 and accepted defaults. fdisk on mac will report "can't get exclusive access to write sector back, reboot required" It ...


2

Things to check for. Some Raid devices are set/Fixed for only one type of Raid 0 or 1. You should check the box and see if this can be used for anything other than Raid 1. Also there maybe software from WD on the drive that will change the Raid for you. If the WD is not hardware locked to be only a Raid 1 and you are unable to find WD software you can try ...


2

Reinstall Windows again using BootCamp, then remove it properly using BootCamp Assistant. It takes time, but solves the problem. Dummy Windows entries are gone forever.



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