Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I think someone here said that the sn750 does not cause issues with the late 2015 model after the bootrom upgrade. I actually sold my late 2015 and purchased a base 2019 model. I upgraded the ssd blade with sn750 and everything has been work perfectly. I also installed an Evo 860 SSD for windows.

Thanks. I have seen some references to the Samsung now working with the bootrom, but not the sn750.. I'm getting a bit confused!

Dont want to crack it open again on a maybe - it sure didnt work last October when I tried it!! And I may as well upgrade to a 2019 and sell the 2015 and use the sn750 i already have than go and buy the samsung...
 
Can someone with the basic HDD-only 27" iMac 2015 model confirm that the sleep/hibernate issues are GONE with the new 428 firmware version after a blade drive upgrade? (Those of you who have a fusion drive iMac can also execute the below steps.)

Firstly please verify that your iMac originally had no blade drive installed through this website https://appleserialnumberinfo.com/

After that, would you please verify no issue with sleeping in the following scenarios:

1) type in Terminal: sudo pmset -a hibernatemode 25 standby 0 , after that hit sleep, wait 1-2 minutes and try to wake the iMac either by a mouse/keyboard click, or if it doesn't work then by pressing the power button on the back of the iMac.

2) type in Terminal: sudo pmset -a hibernatemode 25 standby 1 , after that hit sleep, wait 1-2 minutes and try to wake the iMac.

3) type in Terminal: sudo pmset -a hibernatemode 0 standby 0 , after that hit sleep, wait 1-2 minutes and try to wake the iMac.

4) type in Terminal: sudo pmset -a hibernatemode 0 standby 1 , after that hit sleep, wait 1-2 minutes and try to wake the iMac.

Please describe how the iMac wakes in the above cases, approx. wake delay and do you see a progress bar when waking, or is it instant? Use the below:

-wakes instantly
-wakes with a progress bar
-crashes with a folder question mark
-crashes with stamp of a problem occurred

Lastly, does anyone know which exactly OS X version brought the new 428 firmware version?
 
Can someone with the basic HDD-only 27" iMac 2015 model confirm that the sleep/hibernate issues are GONE with the new 428 firmware version after a blade drive upgrade? (Those of you who have a fusion drive iMac can also execute the below steps.)

Firstly please verify that your iMac originally had no blade drive installed through this website https://appleserialnumberinfo.com/

After that, would you please verify no issue with sleeping in the following scenarios:

1) type in Terminal: sudo pmset -a hibernatemode 25 standby 0 , after that hit sleep, wait 1-2 minutes and try to wake the iMac either by a mouse/keyboard click, or if it doesn't work then by pressing the power button on the back of the iMac.

2) type in Terminal: sudo pmset -a hibernatemode 25 standby 1 , after that hit sleep, wait 1-2 minutes and try to wake the iMac.

3) type in Terminal: sudo pmset -a hibernatemode 0 standby 0 , after that hit sleep, wait 1-2 minutes and try to wake the iMac.

4) type in Terminal: sudo pmset -a hibernatemode 0 standby 1 , after that hit sleep, wait 1-2 minutes and try to wake the iMac.

Please describe how the iMac wakes in the above cases, approx. wake delay and do you see a progress bar when waking, or is it instant? Use the below:

-wakes instantly
-wakes with a progress bar
-crashes with a folder question mark
-crashes with stamp of a problem occurred

Lastly, does anyone know which exactly OS X version brought the new 428 firmware version?

I have this model, and i tried a sn750 WD blade ssd last year and it failed - had all the crash on wake problems so i pulled it out again and running just a SATA ssd.

I just updated OSX to 10.15.6 today and it successfully updated to Boot ROM Version: 428.0.0.0.0

I am hoping i can put that sn750 back in now!! I also would like this confirmed as working before i crack it open again..
 
I have this model, and i tried a sn750 WD blade ssd last year and it failed - had all the crash on wake problems so i pulled it out again and running just a SATA ssd.

I just updated OSX to 10.15.6 today and it successfully updated to Boot ROM Version: 428.0.0.0.0

I am hoping i can put that sn750 back in now!! I also would like this confirmed as working before i crack it open again..

I can confirm that I am running a Late 2015 iMac 27" with an SN750 without issue.

All sleep/wake/hibernate issues disappeared after upgrading to 10.15.6 which installed BootROM 428.0.0.0.0.
 
I can confirm that I am running a Late 2015 iMac 27" with an SN750 without issue.

All sleep/wake/hibernate issues disappeared after upgrading to 10.15.6 which installed BootROM 428.0.0.0.0.

Fantastic! I was about to sell the 2015 and buy a 2019 to do the upgrade, but this way i can run the 2015 for a couple more years until the new iMacs are released and stable. Now is not the time to spend money on a new intel Mac I think.

Thats a nice cost saving :)
 
I am a bit confused after reading through 20 pages. I thought the first page would have been updated, but I have a feeling our fearless leader @dobrink is waiting for more confirmations on his above question. I recently ordered a i7 6700k, 1tb Sata SSD, and hoping to buy a blade as well. I was going to buy a used SSUBX 256gb on Ebay, but it seems that I may be better off ordering an NVME Samsung 970 Evo Plus or WD SN750 for this upgrade. There was mention on page 1 that "01.2019 released Samsung 970 Evo Plus which is not compatible with any of the adapters." I am assuming that this info is now outdated as there is a new fix with the security update to Boot ROM Version: 428.0.0.0.0.

Can anyone double confirm this?
How much faster is the NVME vs the SSUBX?
Much rather buy new than a used SSD to begin with.

Also, at this point would I install all hardware and go straight to an install of OSX to 10.15.6 through a USB thumb? Instead of installing High Sierra and updating from there? Thank you to everyone and this thread. Extremely helpful and I am excited to open up my imac and give it new life.
 
Hi there and sorry for my English I come from France

I did an upgrade on a iMac 21.5 4k 2017 3.4Ghz with 1TB Fusion Drive
I removed the Fusion Drive and installed a 2TB Sabrent Rocket SSD, this model: https://www.amazon.fr/gp/product/B07MTQTNVR/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1

I have speed around 2.4Gb/s in writing and reading. This is normal I guess because the iMac cannot exploit PCIe M.2 Gen3 x 4.

My concern is that I experienced the deep sleep issue. If I'm not running Amphetamine a software that lets my Mac awake, after several hours, I wake my computer and noticed that it has crashed. I have to log again, I have the macOS message that tells me "your computer had to restart because of a problem".

I didn't copy the crash log but I will add it to this topic next time.
I thought the 2017 iMacs had no problems with deep sleep issues.

That's why I'm sharing my experience.

I'm running the latest Catalina upgrade, on a clean install (I reimported my datas tho with the migration assistant). I do hope that Big Sure will fix the deep sleep issue. I think I made a mistake buying this sabrent rocket. I should have think longer to select an SSD that works well with those Macs.

So maybe I have to run some terminal commands to avoid that problem ?

(I remember that the crash log was mentioning a problem with the nvme controller, again I will post the detailed crash log soon when my iMac crash again...)
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
hello guys, I own a 27inch late 2015. I did cpu and ssd blade upgrade, everything is working fine.
I have just a question for all of you that has the same iMac model.
Basically, when I stop or shutdown it, I hear a "click" coming from inside, after the screen went black and just before the fan stops.
I hear it not always, but let's say, 8 times out of 10.
It sounds like a small spring that acts, but I don't think there are any inside the iMac.
I have always had this sound, even before the upgrade, but I have always thought It was the hard disk that was parking.......but now there is only ssd inside.....
Can you please try it? It is not very loud, so it is necessary absolute silence around.
Thanks a lot
 
@zeratul75 could you quickly test for issues by running those commands, as well as report what your iMac was originally equipped with (HDD, Fusion or SSD drive). After the tests you can easily restore the default settings by going to System Settings -> Energy Saver and tick to restore defaults.
 
1) type in Terminal: sudo pmset -a hibernatemode 25 standby 0 , after that hit sleep, wait 1-2 minutes and try to wake the iMac either by a mouse/keyboard click, or if it doesn't work then by pressing the power button on the back of the iMac.
-> wakes by pressing power button (mouse/keyboard don't awake) with a progress bar (1-2 seconds last)

2) type in Terminal: sudo pmset -a hibernatemode 25 standby 1 , after that hit sleep, wait 1-2 minutes and try to wake the iMac. -> wakes instantly by pressing mouse/keyboard

3) type in Terminal: sudo pmset -a hibernatemode 0 standby 0 , after that hit sleep, wait 1-2 minutes and try to wake the iMac. -> wakes instantly by pressing mouse/keyboard

4) type in Terminal: sudo pmset -a hibernatemode 0 standby 1 , after that hit sleep, wait 1-2 minutes and try to wake the iMac. -> wakes instantly by pressing mouse/keyboard


Post #472 is my report
 
I have late 2015 5K zero issues with Big Sur beta 8 latest firmware and all that good stuff!! You can now use any SSD you want no sleep issues what so ever
 
  • Like
Reactions: Godiexx and mbosse
can anybody with late 2015 27'' report me about the "click" on stop/shutdown I have wrote above in post #483?
thanks a lot
 
I don't know.....it is really strange......that's why I ask someone else to check....
If it was a wire or something else touching the fan I should notice when the iMac is running......but the imac is absolutely silent when running....
It sound like a mechanism that acts only in that moment......sotp/shutdown -> monitor off -> fan is still going and then "click"
maybe an electical relays? but if you guys have the same behaviuor maybe it is ok.......
 
It happens exactly when fan stops. I am sure, because when monitor switch off the fan is still running for 2-3 seconds. I hear it......and suddenly It stops. When it stops I hear that sound. But, as I said, it happens 8 times out of 10, not 100% of times.....and really, to hear it, there must be complete silence in the room, It is not loud. But with complete silence, you can hear it very well if you are in front of the imac.....especially now that I know it :):)
Just curious to know if it is something which is going to fail or it is normal.......if it happens to all of you with the same iMac it is obviously a normal behaviour of that fan......if it is not happening It is my fan which is going to fail.....

I have also tried to force the fan to run into different speeds (by software) and It is runnning very well in all steps.....no strange noises at all......I am sure nothing is touching it and it is running smootly.....

But in all computers I have ever owned, imac or windows, I neved heard that click on fan stop.....
 
Last edited:
So it's been a week since my iMac 21.5 upgraded with the Sabrent Rocket 2to has been awake. So I'm not sure the problem when it crash is a deep sleep issue. It has crash today. This time I copied the crash report. I hope someone could understand what's going on:


panic(cpu 2 caller 0xffffff7f85f3c231): nvme: "Fatal error occurred. CSTS=0x1 US[1]=0x0 US[0]=0xf VID=0x1987 DID=0x5012
. FW Revision=RKT303.3\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-470.100.17/IONVMeController.cpp:5320
Backtrace (CPU 2), Frame : Return Address
0xffffff921c8639e0 : 0xffffff800231a65d
0xffffff921c863a30 : 0xffffff8002454a75
0xffffff921c863a70 : 0xffffff80024465fe
0xffffff921c863ac0 : 0xffffff80022c0a40
0xffffff921c863ae0 : 0xffffff8002319d27
0xffffff921c863be0 : 0xffffff800231a117
0xffffff921c863c30 : 0xffffff8002ac1abc
0xffffff921c863ca0 : 0xffffff7f85f3c231
0xffffff921c863cc0 : 0xffffff7f85f27362
0xffffff921c863e20 : 0xffffff8002a32329
0xffffff921c863e90 : 0xffffff8002a32249
0xffffff921c863ec0 : 0xffffff800235c605
0xffffff921c863f40 : 0xffffff800235c131
0xffffff921c863fa0 : 0xffffff80022c013e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[28183FA3-6A50-3611-BC20-A0717B657AAC]@0xffffff7f85f19000->0xffffff7f85f5bfff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[5922E20B-D148-30DC-ABBA-0E99B3BE6940]@0xffffff7f833fb000
dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f82d31000
dependency: com.apple.driver.AppleEFINVRAM(2.1)[D9C4809C-7B20-3663-A9C8-4DBC261AAD86]@0xffffff7f82f02000
dependency: com.apple.iokit.IOStorageFamily(2.1)[3581A46A-F3F3-3CE7-BA52-7046E8D66C32]@0xffffff7f82f11000
dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7f8312a000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide: 0x0000000002000000
Kernel text base: 0xffffff8002200000
__HIB text base: 0xffffff8002100000
System model name: iMac18,2 (Mac-77F17D7DA9285301)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 557162292516937
last loaded kext at 346969200884552: com.adguard.nfext 27 (addr 0xffffff7f86fd2000, size 184320)
last unloaded kext at 66286794111739: |SCSITaskUserClient 422.120.3 (addr 0xffffff7f87043000, size 28672)
loaded kexts:
com.adguard.nfext 27
com.github.osxfuse.filesystems.osxfuse 3.10.4
com.radiosilenceapp.nke.filter 2.2
>!ATopCaseHIDEventDriver 3430.1
>AudioAUUC 1.70
@fileutil 20.036.15
>AGPM 111.4.4
>!APlatformEnabler 2.7.0d0
>X86PlatformShim 1.0.0
@filesystems.autofs 3.0
>!AUpstreamUserClient 3.6.8
@kext.AMDRadeonServiceManager 3.1.0
@kext.AMDFramebuffer 3.1.0
>!AHDA 283.15
@kext.AMDRadeonX4000 3.1.0
>!A!IPCHPMC 2.0.1
>!AGraphicsDevicePolicy 5.2.6
@AGDCPluginDisplayMetrics 5.2.6
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.6f7
>pmtelemetry 1
>!AGFXHDA 100.1.429
>eficheck 1
@Dont_Steal_Mac_OS_X 7.0.0
>!AMCCSControl 1.14
>!A!IKBLGraphics 14.0.7
@kext.AMD9500!C 3.1.0
>!ASMCLMU 212
>!A!IKBLGraphicsFramebuffer 14.0.7
>!AThunderboltIP 3.1.4
>!A!ISlowAdaptiveClocking 4.0.0
|Broadcom!B20703USBTransport 7.0.6f7
>!AVirtIO 1.0
@filesystems.hfs.kext 522.100.5
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@filesystems.apfs 1412.141.1
|!ABCM5701Ethernet 10.3.5
>!ASDXC 1.7.7
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 341.140.1
@private.KextAudit 1.0
>!AACPIButtons 6.1
>!ARTC 2.0
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
>!AHIDKeyboard 209
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport 3440.8
>!AHS!BDriver 3430.1
>IO!BHIDDriver 7.0.6f7
@kext.triggers 1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
@kext.AMDRadeonX4200HWLibs 1.0
@kext.AMDRadeonX4000HWServices 3.1.0
>!AGraphicsControl 5.2.6
|IOAVB!F 850.1
>!ASMBus!C 1.0.18d1
|IONDRVSupport 576.1
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@kext.AMDSupport 3.1.0
>!ASMBusPCI 1.0.14d1
|IOAccelerator!F2 438.7.3
@plugin.IOgPTPPlugin 840.3
@!AGPUWrangler 5.2.6
@!AGraphicsDeviceControl 5.2.6
|IOSlowAdaptiveClocking!F 1.0.0
|Broadcom!BHost!CUSBTransport 7.0.6f7
|IO!BHost!CUSBTransport 7.0.6f7
|IO!BHost!CTransport 7.0.6f7
|IO!B!F 7.0.6f7
|IO!BPacketLogger 7.0.6f7
>!AHDA!C 283.15
|IOGraphics!F 576.1
|IOHDA!F 283.15
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.11
@filesystems.hfs.encodings.kext 1
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
>!AThunderboltPCIDownAdapter 2.5.4
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssDmac 3.0.60
>!A!ILpssI2C 3.0.60
|IOAHCIBlock!S 316.100.5
|IOEthernetAVB!C 1.1.0
|IO80211!F 1200.12.2b1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IOSkywalk!F 1
|IOAHCI!F 290.0.1
|IONVMe!F 2.1.0
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.1
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
>DiskImages 493.0.0
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 489.120.1
|IOSCSIBlockCommandsDevice 422.120.3
>!ACredentialManager 1.0
>KernelRelayHost 1
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
|IOUSBMass!SDriver 157.140.1
|IOSCSIArchitectureModel!F 422.120.3
|IO!S!F 2.1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
|CoreAnalytics!F 1
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|IOTimeSync!F 840.3
|IONetworking!F 3.4
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
 
I have late 2015 5K zero issues with Big Sur beta 8 latest firmware and all that good stuff!! You can now use any SSD you want no sleep issues what so ever
Any M2 NVME SSD? I know others mentioned they had issues with the Samsung Evo Plus SSD. Is that no longer the case as well?
 
Hey, Guys, just finished blade and Spinning drive upgrade for my iMac with this specifications:

Device: iMac 2017 27" (MNED2LL/A) (3.8Ghz i5-7600, Fusion 2TB HDD+128GB blade)
Blade SSD upgrade: 128GB blade -> 1TB Samsung 970 EVO Plus
SATA SSD upgrade: 2TB HDD -> 1TB Samsung 860 EVO

Speed test: 2900 write, 2900 read for Blade, 500 write/read for SATA SSD
OS: Catalina 10.15.7
Adapter: Sintech NGFF M.2 nVME SSD Adapter Card
Heatsink: EK Water Blocks EK-M.2 NVMe Heatsink

Issues after fresh OS install: None

Everything works super cool, if you wanted to use setup like mine just make sure that you have lastest firmware for 970 EVO Plus and don't forget to enable TRIM on SATA SSD.

Also thanks everyone for really cool guides about this upgrade.
Good luck ;)
 
To those saying they had a successful upgrade with no issues, did you test the microphone? At the first time I've realized the adhesive covered the mic and the second time, even cutting the adhesive in the right place, it doesn't sound as before.

Any ideas?
 
To those saying they had a successful upgrade with no issues, did you test the microphone? At the first time I've realized the adhesive covered the mic and the second time, even cutting the adhesive in the right place, it doesn't sound as before.

Any ideas?
Interesting, did you finally solve this?

Thanks,
Magnus
 
hi guys, I made many tries this week end, and would like to report my data to you.

I have a 970 evo ssd nvme 1tb + ssd sata 860 pro 500 gb.

Installed latest catalina + windows 10 into nvme drive.
Installed big sur beta + windows 10 into sata drive.

Here what happens:

- catalina on nvme -> stop is working fine, no issue at all
- windows 10 on nvme -> suspend crash the system on wake up (windows goes in suspend mode normally). Question mark and need to power down the system with hardware button. That appeared very stranged to me, that's why I decided to go on involving sata ssd

- big sure on ssd -> stop is working fine, no issue at all
- windows 10 on ssd -> suspend is working fine, and waking up the system is working as well. BUT...there is a big BUT....after waking up the system the NVME drive totally desappeared. Try reboot into big sure and nothing, totally gone. It need to power down and power up to appear again (not symply reboot, but a real shutdown).

I think this is the key of the strange behaviour.....basically after a stop I think there is something related to power that doesn't go energy to the nvme drive. That is why appears the ?.....the nvme drive is apparently not present.....I think it is a matter of energy, not driver....because the drive appeared again only after a shutdown/power up and not symply a reboot.

I think there will never be a total solution of the problem....and we must accept a configuration according to everyone needs....
For me, I think I will install final release of big sur (which I am testing and like very much) on NVME drive and windows 10 in the sata ssd.....so that I will have stop/suspend working on both systems and accept the nvme "disappear" problem after suspend/wake up from windows......
 
i know this thread is for the 27inch iMac but has anyone upgraded the 21.5inch iMac 2019, i have the fusion drive version and my warranty comes to an end next month and i'm looking at upgrading the ram to either 16 or 32gb and change the blade drive along with the normal hard drive to a 1tb nvme drive and 1tb ssd. if anyone has upgraded this model could you let me know what parts you used and if there were any problems after the upgrade
 
Hi,

Could someone experienced with this please help me with a sanity check before I go ahead?

I have purchased a 4TB Samsung 860 EVO to install into my late-2015 27" imac (currently configured by Apple with 2TB/128GB fusion drive).

When complete I think I would like to use the 128GB Apple blade SSD as a Windows drive and partition the 4TB SSD with a 3TB Mac OS volume and a 1TB Windows "drive D". My logic is that I use Mac OS for 'life' stuff (many years of photos, videos and documents) so it would be simpler to keep Mac OS on a single large volume retaining default locations for user folders. Whereas in Windows my system and user folders are small. It's only really large games and a bit of storage that would require greater space so it would be much less hassle to move these few things to a D drive. I can't imagine the difference in speed between NVME and SATA being much of a factor, but if anything I guess the Blade SSD's speed would be put to better use on an occasional Windows Game over anything I'm likely to do in Mac OS.

1) From reading this thread I understand that the Samsung 860 EVO contains a temp sensor compatible with the iMac's connector?

2) Do I need to split the fusion drive before swapping the SATA drive? I've read mixed opinions on this. Personally I don't see the point.

3) Are there any quirks that I'm likely to run into? I read that Disk Utility will report an issue (which can be ignored) after a fusion drive split but I think this might now be out-of-date information.

4) Any advice on cloning my current Windows 10 install as easily as possible? I guess I would need to copy it to an external disk and then move it back to the Blade SSD after I've performed the upgrade/fusion split. BUT maybe, before I upgrade the Sata drive I could boot from a clonezilla USB drive, clone the current Bootcamp partition from the HDD to the Blade SSD which would destroy the fusion link in the process, THEN upgrade the HDD to my new Sata SSD. Is this a stupid idea? Would there be any problem in doing it this way?

Thanks for reading my rambling. Sorry if these questions have already been answered. I've tinkered plenty with iMacs in the past but I have never dealt with a Fusion Drive until getting this one last year. For what it's worth, coming from my previous imac with an SSD-only swap, I think the Fusion Drive is fantastic. The 2TB Seagate HDD in this machine is near enough silent, and 128GB SSD is a plentiful cache. Most of the time it just feels almost like a normal SSD. It's just a shame that my Windows partition chugs from the HDD. If I was using Mac OS only I'd probably just leave it as is until I needed more space.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.