Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
APFS and Fusion Drives
- Thread starter ryxn
- Start date
- Sort by reaction score
I think that was just the "beta" version of APFS that you could try in Sierra. Considering they still sell Fusion drives I would think APFS would have to work with the public release version.
Definitely make a backup first! But I would think it would work since it is giving you the option.
Some are supported :
- Unsupported configurations in this seed release:
• HDD-only Macs currently are not converted to APFS by default.
• Some iMacs with 3TB Fusion drives and BootCamp may be unsupported for use with APFS.
• APFS support for Mid 2012 Mac Pro will be included in an upcoming seed.
Wanted to report back to you all on my beta install.
So, with the option checked, I was unable to install it. Some users on the forum have already made note with screenshots, but if you have a fusion drive and have the option to upgrade to APFS, DO NOT DO IT! Leave it unchecked and proceed with the install.
So, with the option checked, I was unable to install it. Some users on the forum have already made note with screenshots, but if you have a fusion drive and have the option to upgrade to APFS, DO NOT DO IT! Leave it unchecked and proceed with the install.
You can.
[doublepost=1496750195][/doublepost]
I'd say that with the first Developer Preview it's especially important to test APFS. I've installed on 2 different MacBook Airs and converted those to APFS without a problem. They are, of course, just test machines without anything critical on them. I'll test a Fusion drive computer later today.
I've got a custom Fusion Drive in my 2011 MacBook Pro, and it converted it just fine, but the actual OS install failed.
now the system is deadly slow, and can no longer wake up after sleep
How can I fall back?
How can I fall back?
I faced the same in the begining, while able to complete Installation in recovery mode.
I checked the box for my 2011 Mini with custom built Fusion. Custom because Fusion officially came about in the 2012 model I believe. Anyhow, a 240GB SSD combined with the stock 500GB spinning drive.
I checked the box because I wanted APFS. It took about 2.5 hours to run the update. At one point I thought it was stuck because it just sat and sat with no time estimate. Eventually it moved on. So far no issues with running and to be honest forgot about the Fusion drive issues from last year until after the update.
My MBP (self built FD) is running very slow with after 10.13 installation and conversion to APFS... Have u had the same problem?
No. In fact, it runs as well or better than before. Not that it says anything but for the first time I can watch full resolution, full screen 4k video without any issue. In the past the fan would run full speed and it would stutter. Now, at 2160 fullscreen it looks great. Maybe I just had an issue before but for my use this 2011 machine is all I need.
I am also using a DIY fusion drive.. after converting into APFS, seems like it is now behaving like JBOD (Just a bunch of Disks) than FD.
As there are a lot of reading / writing to the HDD
When it was a HFS+ FD, most read/write happens in the SSD.
Last edited:
I'm using a 1.12 Tb fusion drive, I wasn't given an option to install high sierra with APFS, initially. Because I was curious i did a reinstall and managed to install the system on an APFS partition. The strange thing was that after using the mac for a few hours it became very slow, so i decided to do a restart.
To my surprise after the restart the screen remained black, saying installing the system, and it dis a reinstall to a HFS+ partition. So now I have a working high sierra on a HFS partition, waiting for a few betas to try again the APFS.
To my surprise after the restart the screen remained black, saying installing the system, and it dis a reinstall to a HFS+ partition. So now I have a working high sierra on a HFS partition, waiting for a few betas to try again the APFS.
Unless I'm missing something, there's no mention of anything like automated tiered storage in the 2017-06-05 edition of the Apple File System Guide.
The manual page for diskutil(8) is more informative:
> … more than one device, a Fusion Container is created, with the performance roles assigned automatically (preferred) unless you use the -main and -secondary options, in which case, the secondary disk is assumed by APFS's performance algorithms to be on "slower" hardware. …
@gsmornot @MichaelDT @Billyla please let us have output from:
diskutil APFS list
APFS disk0s2 is my SSD, disk1s2 is my HDD --> seems like APFS recognize it is a FD, as the container reference is remarked "Fusion".
Below is the output.
APFS Container (1 found)
|
+-- Container disk2 072666EE-5E0E-462A-BCB0-9BDBB785B4B7
====================================================
APFS Container Reference: disk2 (Fusion)
Capacity Ceiling (Size): 376891113472 B (376.9 GB)
Capacity In Use By Volumes: 220355485696 B (220.4 GB) (58.5% used)
Capacity Available: 156535627776 B (156.5 GB) (41.5% free)
|
+-< Physical Store disk0s2 D0960504-4BBB-4A4B-9D40-E655BCE418AE
| -----------------------------------------------------------
| APFS Physical Store Disk: disk0s2
| Size: 127691702272 B (127.7 GB)
|
+-< Physical Store disk1s2 36BCF4E7-BFBC-4117-948A-160714D68FCA
| -----------------------------------------------------------
| APFS Physical Store Disk: disk1s2
| Size: 249199411200 B (249.2 GB)
|
+-> Volume disk2s1 0227BCD1-B1E9-3847-BBA8-5A6400EF31D0
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s1 (No specific role)
| Name: Macintosh
| Mount Point: /
| Capacity Consumed: 205692260352 B (205.7 GB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s2 9ADF7FC3-16B7-4CA8-A810-606076FDC573
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s2 (Preboot)
| Name: Preboot
| Mount Point: Not Mounted
| Capacity Consumed: 19652608 B (19.7 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s3 A491BB0C-6A22-4FEC-A413-F0E1AD48DB03
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s3 (Recovery)
| Name: Recovery
| Mount Point: Not Mounted
| Capacity Consumed: 518934528 B (518.9 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s4 4FC10908-8AC4-4DCF-8035-0D950E62F97D
---------------------------------------------------
APFS Volume Disk (Role): disk2s4 (VM)
Name: VM
Mount Point: /private/var/vm
Capacity Consumed: 5368762368 B (5.4 GB)
Capacity Reserve: None
Capacity Quota: None
Encrypted: No
[doublepost=1497084918][/doublepost]I allowed it idle for 5 hours and there were a lot of mds activities.
Now its speed almost resumed (still have a noticable difference), and the HDD activities is still more frequent than I was with Sierra HFS+
However, boot / shutdown time is still very long, and it cannot wake up after closing the lid.
It has started to speed up a bit, perhaps it was indexing or checksumming. It could be the programming isn't finished as well. I.e. it knows it's a fusion drive but doesn't do anything special yet.
APFS Container (1 found)
|
+-- Container disk2 1E034718-E726-40C1-8173-C22F58EDB47D
====================================================
APFS Container Reference: disk2 (Fusion)
Capacity Ceiling (Size): 3255449649152 B (3.3 TB)
Capacity In Use By Volumes: 1784905375744 B (1.8 TB) (54.8% used)
Capacity Available: 1470544273408 B (1.5 TB) (45.2% free)
|
+-< Physical Store disk0s2 187ADBD1-8840-40FB-A016-08A0AF9AA18F
| -----------------------------------------------------------
| APFS Physical Store Disk: disk0s2
| Size: 255716540416 B (255.7 GB)
|
+-< Physical Store disk1s2 7C6FE268-F6C3-42C3-8DDB-B59445AF173A
| -----------------------------------------------------------
| APFS Physical Store Disk: disk1s2
| Size: 2999733108736 B (3.0 TB)
|
+-> Volume disk2s1 1EA7D8AA-6B8B-3BD1-A79A-EEFD1B936DEC
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s1 (No specific role)
| Name: Macintosh HD
| Mount Point: /
| Capacity Consumed: 1774885416960 B (1.8 TB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s2 93BA10D0-162F-43B0-BDD9-330D9F37C61B
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s2 (Preboot)
| Name: Preboot
| Mount Point: Not Mounted
| Capacity Consumed: 18755584 B (18.8 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s3 2B0C4FF8-2420-475B-8335-61771154534A
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s3 (Recovery)
| Name: Recovery
| Mount Point: Not Mounted
| Capacity Consumed: 518926336 B (518.9 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s4 FBDD57D6-A546-47D3-9C0C-8E87A0E9CE99
---------------------------------------------------
APFS Volume Disk (Role): disk2s4 (VM)
Name: VM
Mount Point: /private/var/vm
Capacity Consumed: 446169088 B (446.2 MB)
Capacity Reserve: None
Capacity Quota: None
Encrypted: No
APFS Container (1 found)
|
+-- Container disk2 1E034718-E726-40C1-8173-C22F58EDB47D
====================================================
APFS Container Reference: disk2 (Fusion)
Capacity Ceiling (Size): 3255449649152 B (3.3 TB)
Capacity In Use By Volumes: 1784905375744 B (1.8 TB) (54.8% used)
Capacity Available: 1470544273408 B (1.5 TB) (45.2% free)
|
+-< Physical Store disk0s2 187ADBD1-8840-40FB-A016-08A0AF9AA18F
| -----------------------------------------------------------
| APFS Physical Store Disk: disk0s2
| Size: 255716540416 B (255.7 GB)
|
+-< Physical Store disk1s2 7C6FE268-F6C3-42C3-8DDB-B59445AF173A
| -----------------------------------------------------------
| APFS Physical Store Disk: disk1s2
| Size: 2999733108736 B (3.0 TB)
|
+-> Volume disk2s1 1EA7D8AA-6B8B-3BD1-A79A-EEFD1B936DEC
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s1 (No specific role)
| Name: Macintosh HD
| Mount Point: /
| Capacity Consumed: 1774885416960 B (1.8 TB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s2 93BA10D0-162F-43B0-BDD9-330D9F37C61B
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s2 (Preboot)
| Name: Preboot
| Mount Point: Not Mounted
| Capacity Consumed: 18755584 B (18.8 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s3 2B0C4FF8-2420-475B-8335-61771154534A
| ---------------------------------------------------
| APFS Volume Disk (Role): disk2s3 (Recovery)
| Name: Recovery
| Mount Point: Not Mounted
| Capacity Consumed: 518926336 B (518.9 MB)
| Capacity Reserve: None
| Capacity Quota: None
| Encrypted: No
|
+-> Volume disk2s4 FBDD57D6-A546-47D3-9C0C-8E87A0E9CE99
---------------------------------------------------
APFS Volume Disk (Role): disk2s4 (VM)
Name: VM
Mount Point: /private/var/vm
Capacity Consumed: 446169088 B (446.2 MB)
Capacity Reserve: None
Capacity Quota: None
Encrypted: No
I too had the option to check (iMac 27 retina i5 late 2014, Fusion Drive). The install process was too slow, too slow to use (opening apps, web browsing etc), 2 or 3 Kernel Panics. In the end, impossible to use. I am a bold user. Have been using betas (even the first releases of each one) since 2010 as the only system on the macs I had and never had the amount of freak problems I had with this one. First time I had to come back to the past!! (my God, so many "hads"...)