![]() ![]() Terminal displays additional data about your drives (volumes).Type diskutil cs list, then press Return.Then enter same command again using the second identifier. If you get a disk unmounting error, enter diskutil unmountDisk identifier, using the first identifier you gathered previously.Then press Return.ĭiskutil cs create Macintosh\ HD identifier1 identifier2Įxample: diskutil cs create Macintosh\ HD disk0 disk1 Type the following command, replacing identifier1 and identifier2 with the identifiers you found in the previous step.One of them should be 128GB or less in size. Usually the identifiers are disk0 and disk1. In the IDENTIFIER column, find the identifier for each of the two internal, physical drives that make up your Fusion Drive. Terminal displays a table of data about your drives.Type diskutil list in the Terminal window, then press Return.When you see the macOS Utilities window, choose Utilities > Terminal from the menu bar.Turn on your Mac, then immediately press and hold Command-R to start up from macOS Recovery. Release the keys you see the Apple logo or spinning globe. ![]() If this is just a Mac you plan on keeping for a while, I would recommend doing something about the HDD, but if this is just to hold you over to see what new Macs will be out over the next year or two, there could be other solutions, like using a second Mac to install Catalina on an external drive.ĭo you have another Mac to work with or could you get access to another Mac? If so, you could use the other Mac to install Catalina to the external drive. You can use software to control the fan speeds, the SATA adapter, or short the pins. Even if you get it working, the failed HDD could cause boot problems like I mentioned above. I am assuming that the HDD is causing problems when doing the Catalina install, probably firmware related. After that, I had booting issue until I was able to boot into my regular drive and wiped the HDD that actually mounted for a couple minutes. I didn't even think it was possible, as I thought the OS files was kept on the SSD portion of the Fusion Drive. Not sure how it even happened, or how it even worked, as the SSD part of the Fusion was decoupled and was wiped. Randomly during a restart, the Mac tried to boot into the HDD. I decoupled the Fusion Drive, wiped the SSD and went on with my life. In a different iMac with a Fusion Drive, the HDD was failing. In retrospect, I should have just replaced it myself after the first time that they said it was fine. It finally worked, and the HDD finally failed the test, so they replaced under warranty. The same Genius that told me at least once before that my HW was fine couldn't get his HW diagnostic tool to boot for over 2 hours. Couldn't boot into recovery, internet recovery, external back up drives, or anything. They would wipe the drive, say everything was fine with the HW, only to have the problem come back.įinally, 12 days before the warranty was over, the drive fully failed. I took it there many times due to the failing drive, and it kept passing their HW diagnostic test. It had a failing HDD portion of the Fusion Drive. Most of which are booting related.Īctually, the Genius at the Apple Store had a lot of trouble getting their HW diagnostic tools to boot on an iMac that I took there under warranty. I have experienced a few different problems with failing HDD portion of Fusion Drives. System uptime in nanoseconds: 729070309698 Panic diags file available: NO (0xe00002bc) System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4) Panic(cpu 0 caller 0xffffff802a013e97): "AppleAHCIDiskQueueManager::setPowerState(0xffffff806656ed80 : 0xffffff7fac8cb5d2, 3 -> 2) timed out after 100689 (CPU 0), Frame : Return AddressīSD process name corresponding to current thread: kernel_taskĭarwin Kernel Version 19.6.0: Thu Jan 13 01:26: root:xnu-6153.141.51~3/RELEASE_X86_64 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |