|
|
Fusion Drive broken?
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
Did the last Catalina update break the fusion drive connection?
We have been remodeling the house. I took my late 2013 27” iMac with a 3TB fusion drive down the street to my mother’s house for the duration.
Last week it started running super slow. I thought it might be due to it trying to use WiFi for iCloud backup. I ran the diagnostic test just to be sure and it said all good. Since we were almost done, I brought it home and plugged it up to the internet via Ethernet with no change.
I decided to do an internet recovery and discovered when I ran disk utility it said the SSD and HDD were no longer one and gave the option to fix it. After it completed I noticed the disk utility was an older version. It formatted the Fusion Drive as Mac OS journaled. When it installed the OS, it installed Mavericks.
I am installing Catalina, it seems to be stuck.
|
45/47
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
Install has completed. Why are there two HDD listed, Macintosh HD and Macintosh HD-Data?
|
45/47
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
|
45/47
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Catalina splits the System folder off to a separate read-only partition. Like in iOS, to prevent tampering. I have philosophical problems with that, another step removing control from the Mac owner. One of several reasons why I don't update to Catalina.
Anyway, your Fusion drive is presumably OK. Sounds like only one device is seen by the OS. "Drive" and "Drive-Data" are separate partitions, which Catalina should pretend is one. Suggest running Disk Utility (Catalina version) on it to fix the flags. Then reboot.
Side note - what does Disk Utility say about the physical hard drive SMART status? A 2013 model HD is about 8 years old now.
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
Originally Posted by reader50
Side note - what does Disk Utility say about the physical hard drive SMART status? A 2013 model HD is about 8 years old now.
HD or HD-Data?
|
45/47
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Those are partitions on the Fusion drive. You're dealing with two levels of abstraction here:
Physical reality: an HD and an SSD.
Fusion converts to a single "device". Which will have a resource code, but not a name.
The fused drive is then partitioned into:
0 (partition map - invisible)
1 Mac HD (contains most of the System folder and not much else)
2 Mac HD-data (contains everything else)
3 (recovery partition - invisible)
Catalina should cause the 2 partitions to appear as one merged volume. I'd think Disk Utility would be able to see the separate physical devices still, for checking health. In DU, go to View -> Show All Devices. That should work, but I don't have a working Catalina install to check with.
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
Running First Aid on “Macintosh HD” (disk4s5)
Verifying the startup volume will cause this computer to stop responding.
Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk4s5
Checking the container superblock.
Checking the fusion superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the Fusion data structures.
Checking volume.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.TimeMachine.2021-05-10-193204.local)
Checking the extent ref tree.
Checking the fsroot tree.
Verifying allocated space.
The volume /dev/rdisk4s5 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.
Operation successful.
|
45/47
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
View all shows Fusion Drive (“Container disk4”)
Running First Aid on “Container disk4”
Verifying the startup volume will cause this computer to stop responding.
Verifying storage system
Using live mode.
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock.
Checking the fusion superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the Fusion data structures.
Checking volume.
Checking the APFS volume superblock.
The volume Macintosh HD - Data was formatted by hfs_convert (1412.141.1) and last modified by apfs_kext (1412.141.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.TimeMachine.2021-05-10-193204.local)
Checking the extent ref tree.
Checking the fsroot tree.
Checking volume.
Checking the APFS volume superblock.
The volume Preboot was formatted by hfs_convert (1412.141.1) and last modified by apfs_kext (1412.141.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the extent ref tree.
Checking the fsroot tree.
Checking volume.
Checking the APFS volume superblock.
The volume Recovery was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the extent ref tree.
Checking the fsroot tree.
Checking volume.
Checking the APFS volume superblock.
The volume VM was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the extent ref tree.
Checking the fsroot tree.
Checking volume.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.TimeMachine.2021-05-10-193204.local)
Checking the extent ref tree.
Checking the fsroot tree.
Verifying allocated space.
warning: MT mapping (0x400000063ac03 -> 0x1c802c, 2, D) is not completely referenced
warning: MT mapping (0x400000063be49 -> 0x1a020c, 3, D) is not completely referenced
warning: MT mapping (0x4000000642cb8 -> 0x1a0448, 1, D) is not completely referenced
warning: MT mapping (0x400000064415c -> 0x1a0527, 2, D) is not completely referenced
warning: MT mapping (0x40000006557ca -> 0x1c82b0, 2, D) is not completely referenced
warning: MT mapping (0x400000067894c -> 0x1c832c, 2, D) is not completely referenced
warning: MT mapping (0x40000008824b6 -> 0x1cadd6, 2, D) is not completely referenced
warning: MT mapping (0x40000008fc0a6 -> 0x1cb53a, 2, D) is not completely referenced
warning: MT mapping (0x400000090a51f -> 0x1cb64e, 2, D) is not completely referenced
warning: MT mapping (0x400000090caab -> 0xb99525, 92, D) is not completely referenced
warning: MT mapping (0x400000091a920 -> 0x1ba002, 2, D) is not completely referenced
warning: MT mapping (0x400000092ba2d -> 0xbb7cac, 7, D) is not completely referenced
warning: MT mapping (0x400000092c6ac -> 0x1bada1, 1, D) is not completely referenced
warning: MT mapping (0x400000092c6b9 -> 0x1badae, 1, D) is not completely referenced
warning: MT mapping (0x400000092e859 -> 0x1bb22a, 1, D) is not completely referenced
warning: MT mapping (0x400000092e85b -> 0x1bb22c, 1, D) is not completely referenced
warning: MT mapping (0x4000000933ad7 -> 0x1bb9c4, 1, D) is not completely referenced
warning: MT mapping (0x4000000933ad9 -> 0x1bb9c6, 1, D) is not completely referenced
warning: MT mapping (0x4000000933af2 -> 0x1bb9cc, 1, D) is not completely referenced
warning: MT mapping (0x40000009481f6 -> 0x1c8388, 2, D) is not completely referenced
warning: MT mapping (0x400000094b2df -> 0x1a0b85, 1, D) is not completely referenced
warning: MT mapping (0x400000094c206 -> 0x1c83d0, 2, D) is not completely referenced
warning: MT mapping (0x4000000950b7e -> 0x1a0c25, 1, D) is not completely referenced
warning: MT mapping (0x4000000952106 -> 0x1c83f8, 2, D) is not completely referenced
warning: MT mapping (0x4000000961254 -> 0x1a0ead, 1, D) is not completely referenced
warning: MT mapping (0x40000009a7f7e -> 0x1c868a, 2, D) is not completely referenced
warning: MT mapping (0x40000009a972d -> 0x1c8694, 2, D) is not completely referenced
warning: MT mapping (0x40000009a9737 -> 0x1c869a, 2, D) is not completely referenced
warning: MT mapping (0x40000009c035c -> 0x1a3aa6, 1, C) is not completely referenced
warning: MT mapping (0x40000009f2bf2 -> 0xbe97f6, 7, D) is not completely referenced
warning: MT mapping (0x4000000a96928 -> 0x1cc5aa, 2, D) is not completely referenced
warning: MT mapping (0x4000000a96f04 -> 0x1cc5b2, 2, D) is not completely referenced
warning: MT mapping (0x4000000aa9e55 -> 0x1cc65c, 2, D) is not completely referenced
warning: MT mapping (0x4000000aaa062 -> 0x1cc666, 2, D) is not completely referenced
warning: MT mapping (0x4000000b1db2f -> 0x1cc9da, 2, D) is not completely referenced
warning: MT mapping (0x4000000b1db60 -> 0x1cc9e2, 2, D) is not completely referenced
warning: MT mapping (0x4000000b3a122 -> 0x98ec6a, 7, D) is not completely referenced
warning: MT mapping (0x4000000b9ca87 -> 0x1cccc2, 2, D) is not completely referenced
warning: MT mapping (0x4000000bc1d43 -> 0x1ccd5e, 2, D) is not completely referenced
warning: MT mapping (0x4000000bc7dde -> 0x1ccd7e, 2, D) is not completely referenced
warning: MT mapping (0x4000000bf7259 -> 0x1a38e0, 1, D) is not completely referenced
warning: MT mapping (0x4000000ce8689 -> 0x1cd1b6, 2, D) is not completely referenced
The volume /dev/disk0s2 appears to be OK.
Storage system check exit code is 0.
Operation successful.
|
45/47
|
|
|
|
|
|
|
|
Administrator
Join Date: Jun 2000
Location: California
Status:
Offline
|
|
Well, I don't know why Catalina isn't hiding the two partitions. But everything looks OK on the functional level. So just ignore, and work as normal.
A reformat and restore from TM would likely fix it. But that's a lot of trouble to fix a cosmetic problem.
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status:
Offline
|
|
Originally Posted by reader50
Well, I don't know why Catalina isn't hiding the two partitions. But everything looks OK on the functional level. So just ignore, and work as normal.
A reformat and restore from TM would likely fix it. But that's a lot of trouble to fix a cosmetic problem.
It reformatted when I reinstalled Mavericks, and again when updated to Catalina. I opened migration assistant band it shows only the last TM update. Online posts state to give time to recognize older updates. I tried a restore by opening TM from the menu bar. I got a pop up saying not formatted for backup.
|
45/47
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|