The hard drive part of my iMac's fusion drive (SSD + HDD) died recently and I've since replaced the HDD with another SDD and created a new fusion drive. I have a USB-SATA connector. Although I haven't tried plugging it in yet (I don't want to waste any time with the drive powered up due to its condition), I'm assuming it won't mount properly since it was once part of a fusion setup. What would be good software to use to try to recover data from a probably-improperly-formatted-unmountable drive?
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.
Hard drive portion of fusion drive died. Data recovery options?
- Thread starter Surrix
- Start date
- Sort by reaction score
Unless you have a backup, when one portion of the fusion drive fails, there AREN'T ANY "recovery options".
The data... is gone.
Perhaps there are a few "data recovery outfits" that could get -some- of it back.
But I doubt that, even.
The data... is gone.
Perhaps there are a few "data recovery outfits" that could get -some- of it back.
But I doubt that, even.
Isn't there software that can read the raw bits on the drive without mounting it? I remember needing to do something like that with a severely damaged drive maybe 10 years ago in Windows.
I'm not even sure if I lost anything of value, but I was hoping to check.
Edit: EaseUS looks like something like that. Supposedly works with drives that've been formatted. Curious if anyone has experience with this software.
I'm not even sure if I lost anything of value, but I was hoping to check.
Edit: EaseUS looks like something like that. Supposedly works with drives that've been formatted. Curious if anyone has experience with this software.
Forensic recovery like you're suggesting can cost thousands of dollars, so it's certainly not worth it because you're not even sure you lost anything valuable. You can try anything, but Fishrrman is right. Whatever you do, it's unfortunate that you had to learn about the importance of backups the hard way. Going forward, don't be without two (preferably rotated with one kept offsite).
I think it depends on how much it has failed.
I have used a cheap recovery software on a friends failing HDD that wouldn't boot and was able to recover almost everything important, although it took a a few tries, and about a day per try.
The software worked really well, and I tested it with some old HDDs I had sitting around. It recovered stuff that I deleted many years ago.
I think the software cost $80.
I have used a cheap recovery software on a friends failing HDD that wouldn't boot and was able to recover almost everything important, although it took a a few tries, and about a day per try.
The software worked really well, and I tested it with some old HDDs I had sitting around. It recovered stuff that I deleted many years ago.
I think the software cost $80.
HI, I know this is an old post - but I have similar problems.
My Mac died 27 inch late 2014
days with Mac support couldn't reset fusion drive and it often says failure trying to write to the last block etc ... The fusion was split about a year ago - under Apple support guidance - following an email problem.
I have been able to load to High Sierra on the Mac - by booting from an external and loading OS that way,
My issue is that I can't get past High Sierra, it just won't take Mojave or Catalina
I have it booked in locally for a new SSD Drive to be installed - but don't want to do this if the problem is not with the drive
I have tried so many things from so many forums.
I can't restore from time machine back up - I have tried on to external drives that have booted up the Mac and also tried direct to the HDD in the Mac - after erasing it.
Any advice would be greatly appreciated.
Thanks
My Mac died 27 inch late 2014
days with Mac support couldn't reset fusion drive and it often says failure trying to write to the last block etc ... The fusion was split about a year ago - under Apple support guidance - following an email problem.
I have been able to load to High Sierra on the Mac - by booting from an external and loading OS that way,
My issue is that I can't get past High Sierra, it just won't take Mojave or Catalina
I have it booked in locally for a new SSD Drive to be installed - but don't want to do this if the problem is not with the drive
I have tried so many things from so many forums.
I can't restore from time machine back up - I have tried on to external drives that have booted up the Mac and also tried direct to the HDD in the Mac - after erasing it.
Any advice would be greatly appreciated.
Thanks
It does sounds more like a faulty drive, but you haven't said what errors you are getting when install Mojave/Catalina. I have seen it before where you have multiple drives in a system and even if only one of them is faulty, the machine will keep freezing and getting stuck trying to read it.
If you haven't already, try running Apple's hardware diagnostics on it, to make sure nothing else it wrong. But if everything other than drive shows as OK, the best thing to do would be to continue getting the internal drive replaced (make sure they remove the old HDD and SSD).
If you haven't already, try running Apple's hardware diagnostics on it, to make sure nothing else it wrong. But if everything other than drive shows as OK, the best thing to do would be to continue getting the internal drive replaced (make sure they remove the old HDD and SSD).
ohmeo wrote:
"The fusion was split about a year ago - under Apple support guidance - following an email problem."
Important question:
Has it remained "split" ever since?
That is to say, if they are still split, you should have TWO drives on your desktop now:
- one representing the internal SSD portion of the fusion drive
- the other representing the internal HDD portion of the fusion drive.
There was a "bad run" of Seagate drives that got installed into iMacs in the 2013-14 timeframe. I believe most or all of these were 3tb HDD's.
When you boot from an external drive, how many drive icons do you see on your desktop?
Do you get -anything- representing one or both internal drives?
I don't think it's worth having an SSD installed inside (depends on how much you were quoted for this job). The iMac is 6 years old already.
You could do as well to get an EXTERNAL USB3 SSD, and boot and run it that way.
This will give you speeds that will be around 85% of what you'd get from the same drive installed internally, but with less cost and trouble.
Set up the external boot SSD as you would the drive you're booting from now.
You might even use CarbonCopyCloner to just "clone" the current boot drive to the new SSD.
Once you have a good "external boot" drive going, you can attempt to "go to work" on the internal drives to salvage them if possible.
"The fusion was split about a year ago - under Apple support guidance - following an email problem."
Important question:
Has it remained "split" ever since?
That is to say, if they are still split, you should have TWO drives on your desktop now:
- one representing the internal SSD portion of the fusion drive
- the other representing the internal HDD portion of the fusion drive.
There was a "bad run" of Seagate drives that got installed into iMacs in the 2013-14 timeframe. I believe most or all of these were 3tb HDD's.
When you boot from an external drive, how many drive icons do you see on your desktop?
Do you get -anything- representing one or both internal drives?
I don't think it's worth having an SSD installed inside (depends on how much you were quoted for this job). The iMac is 6 years old already.
You could do as well to get an EXTERNAL USB3 SSD, and boot and run it that way.
This will give you speeds that will be around 85% of what you'd get from the same drive installed internally, but with less cost and trouble.
Set up the external boot SSD as you would the drive you're booting from now.
You might even use CarbonCopyCloner to just "clone" the current boot drive to the new SSD.
Once you have a good "external boot" drive going, you can attempt to "go to work" on the internal drives to salvage them if possible.
Last edited:
OK Thanks - this was a 1TB drive
I have attached a screenshot of drive ...
I have erased it a few times and tried to load various OS onto it ...
The price is £100 for drive £80 for install
What I am concerned about is that I can run High Sierra on the current internal drive - but no higher
I can also run these on 3 different external drives I have (not USB3 though) - and no higher (not Mojave or Catalina)
Are you suggesting I can just buy an external SSD drive - 1tb or 2tb and use that as my main drive ? Do you think I will be able to load Catalina onto that if I can't load it onto the current external drives I have ... ?
is that 85% speed of a new SSD internal or 85% speed of the older HHD drive
Thanks for your help
Attachments
Seagate Expansion SSD, 1 TB, Portable External Solid State Drive for PC and Mac, and Three-year Rescue Services (STJD1000400), Black
EXPANSION SSD 1TB 2.5IN USB3.0
www.amazon.co.uk
this kind of thing ?
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Attachments
From the image you posted in reply 9 above, you have the [former] fusion drive "split apart" into it's two components:
- SSD, 128gb
- HDD, can't tell what the size is.
Do these drives currently "show up" on the desktop?
Or, do they remain invisible to the finder?
Or, does only ONE of them show up?
(it looks like the HDD portion named "Macintosh HD" might be mountable)
WHY I'm asking:
If they "show up", then it sounds like you're re-initialized them (erased them) to be "standalone" drives. Be aware that doing this will DESTROY any data that formerly existed on them when they were "fused together".
If they have never shown up since they got "de fused", then the data that was on them might still "be there", but I'm not optimistic about that. The only way to "get at" that data would be to "RE-fuse" them, and I'm wondering if doing so (using the terminal or perhaps disk utility?) would in itself wipe out any previous data.
Didn't you say you also had a tm backup somewhere?
- SSD, 128gb
- HDD, can't tell what the size is.
Do these drives currently "show up" on the desktop?
Or, do they remain invisible to the finder?
Or, does only ONE of them show up?
(it looks like the HDD portion named "Macintosh HD" might be mountable)
WHY I'm asking:
If they "show up", then it sounds like you're re-initialized them (erased them) to be "standalone" drives. Be aware that doing this will DESTROY any data that formerly existed on them when they were "fused together".
If they have never shown up since they got "de fused", then the data that was on them might still "be there", but I'm not optimistic about that. The only way to "get at" that data would be to "RE-fuse" them, and I'm wondering if doing so (using the terminal or perhaps disk utility?) would in itself wipe out any previous data.
Didn't you say you also had a tm backup somewhere?
Thanks for the reply.
I am not worried about the data as I have a fairly recent tm backup
I just need to get the Mac working again and a recent os mounted.
I think I am leaning towards getting an external ssd drive and trying to install my tm back up on that. My only concern is that I have been unable to load Mojave or Catalina onto other externals I have. It seems to load but then gets an error saying Mac had to restart because of an error - press a key - listed in a box in about 6 languages.
the hdd part of the drive does load on desktop so I assume if I can boot system from an external ssd drive I can use the internal hdd as extra storage ?
I did read rather than an external ssd to buy an internal 1tb ssd and use externally - I presume I may need extra cables for this.
do you know of any reason why Mojave or Catalina won’t load on Mac hd or external hard drives ?
I am not worried about the data as I have a fairly recent tm backup
I just need to get the Mac working again and a recent os mounted.
I think I am leaning towards getting an external ssd drive and trying to install my tm back up on that. My only concern is that I have been unable to load Mojave or Catalina onto other externals I have. It seems to load but then gets an error saying Mac had to restart because of an error - press a key - listed in a box in about 6 languages.
the hdd part of the drive does load on desktop so I assume if I can boot system from an external ssd drive I can use the internal hdd as extra storage ?
I did read rather than an external ssd to buy an internal 1tb ssd and use externally - I presume I may need extra cables for this.
do you know of any reason why Mojave or Catalina won’t load on Mac hd or external hard drives ?
"do you know of any reason why Mojave or Catalina won’t load on Mac hd or external hard drives ?"
Not sure what's going on with that.
But...
My advice: don't worry about it right now.
Run with the OS that you have working.
"My only concern is that I have been unable to load Mojave or Catalina onto other externals I have. It seems to load but then gets an error saying Mac had to restart because of an error - press a key - listed in a box in about 6 languages."
That's called a "kernel panic", and I'll guess that it -might- have something to do with the fact that the fusion drive is broken apart and the SSD portion doesn't seem to be mountable.
Have you tried erasing the internal SSD?
If not, I'd suggest you try it.
Click on the "top line" in disk utility to select the drive, then click erase.
Choose "Mac OS extended with journaling enabled, GUID partition format".
Does it erase and mount?
Not sure what's going on with that.
But...
My advice: don't worry about it right now.
Run with the OS that you have working.
"My only concern is that I have been unable to load Mojave or Catalina onto other externals I have. It seems to load but then gets an error saying Mac had to restart because of an error - press a key - listed in a box in about 6 languages."
That's called a "kernel panic", and I'll guess that it -might- have something to do with the fact that the fusion drive is broken apart and the SSD portion doesn't seem to be mountable.
Have you tried erasing the internal SSD?
If not, I'd suggest you try it.
Click on the "top line" in disk utility to select the drive, then click erase.
Choose "Mac OS extended with journaling enabled, GUID partition format".
Does it erase and mount?
Thanks, yes tried that - pretty sure it’s the ssd part that is broken.
is there a way of just forgetting the ssd part and using the hdd part to run Mac
if not external ssd may be the route. What is best - a purpose built ssd external or buy and use internal ssd - presume some wires or conversion kit are needed?
is there a way of just forgetting the ssd part and using the hdd part to run Mac
if not external ssd may be the route. What is best - a purpose built ssd external or buy and use internal ssd - presume some wires or conversion kit are needed?
Attachments
do you know if something like this ...slows the speed much ?
I am thinking of using an internal ssd this way ?
I am thinking of using an internal ssd this way ?
Inateck USB 3.0 to SATA 2-Bay USB 3.0 Hard Drive Docking Station with Offline Clone Function for 2.5 Inch & 3.5 Inch HDD SSD SATA (SATA I/ II/ III) Support 2x 8TB & UASP, Tool-free
HDD/SSD Off-line Duplicator When cloning a hard drive, no PC is required - just plug both hard drives, press "Copy" button for several seconds until the LED will start flashing and the cloning process will begin. Progress indicator with LED: 25% - 50% - 75% - 100%. Support UASP and SATA 6Gbps Ava...
www.amazon.co.uk
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
OP:
Get one of these (they're cheap):
Then get a 2.5" SATA SSD of your choice.
I recommend either Crucial or Sandisk, 1tb in size should be big enough.
Put the SSD into the enclosure and erase it with disk utility.
Use "Mac OS extended with journaling enabled, GUID partition format".
At this point you can install a clean copy of the OS onto it (presuming it will install). Accept whatever version of the OS you can GET onto it.
When the install is done, begin setup ("choose your language").
When asked if you wish to migrate data, connect your backup and "point the way" for setup assistant.
Get the data migrated.
You should also go to the startup disk preference pane and designate the external SSD to be the new boot drive.
Let the INTERNAL SSD be "dead, but in place, unused".
Just "leave it there".
If the internal HDD is good, you might consider using either CarbonCopyCloner or SuperDuper to create a cloned backup of the SSD to the internal HDD.
The internal drive now becomes "your backup" for the SSD.
Get one of these (they're cheap):
SABRENT 2.5 Inch SATA to USB 3.0 Tool Free External Hard Drive Enclosure [Optimized for SSD, Support UASP SATA III] Black (EC-UASP)
SABRENT 2.5 Inch SATA to USB 3.0 Tool Free External Hard Drive Enclosure [Optimized for SSD, Support UASP SATA III] Black (EC-UASP)
tinyurl.com
Then get a 2.5" SATA SSD of your choice.
I recommend either Crucial or Sandisk, 1tb in size should be big enough.
Put the SSD into the enclosure and erase it with disk utility.
Use "Mac OS extended with journaling enabled, GUID partition format".
At this point you can install a clean copy of the OS onto it (presuming it will install). Accept whatever version of the OS you can GET onto it.
When the install is done, begin setup ("choose your language").
When asked if you wish to migrate data, connect your backup and "point the way" for setup assistant.
Get the data migrated.
You should also go to the startup disk preference pane and designate the external SSD to be the new boot drive.
Let the INTERNAL SSD be "dead, but in place, unused".
Just "leave it there".
If the internal HDD is good, you might consider using either CarbonCopyCloner or SuperDuper to create a cloned backup of the SSD to the internal HDD.
The internal drive now becomes "your backup" for the SSD.
OK Thanks,
So I have finally been able to boot the Mac using an external SSD Drive (I was able to load Catalina from Command R)
Everything was looking great - I loaded the welcome screen etc and started to do a transfer from time machine - it then just died - black screen and had the message again in all languages that the computer had to restart because of an error ... press a key.
I was able to see the Problem Details
these are listed below. Does this mean there are further problems with the MAC and not the internal drive ?
I am hoping to just run the Mac from the External SSD drive - which does seem quite quick ...
panic(cpu 0 caller 0xffffff8010812667): "AppleAHCIDiskQueueManager::setPowerState(0xffffff8025124480 : 0xffffff7f919ab5d2, 3 -> 2) timed out after 100642 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.2.2/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffff912502bb40 : 0xffffff801011868d
0xffffff912502bb90 : 0xffffff8010252ab5
0xffffff912502bbd0 : 0xffffff801024463e
0xffffff912502bc20 : 0xffffff80100bea40
0xffffff912502bc40 : 0xffffff8010117d57
0xffffff912502bd40 : 0xffffff8010118147
0xffffff912502bd90 : 0xffffff80108bf2bc
0xffffff912502be00 : 0xffffff8010812667
0xffffff912502be50 : 0xffffff8010811f49
0xffffff912502be60 : 0xffffff80108294de
0xffffff912502bea0 : 0xffffff8010810cf8
0xffffff912502bec0 : 0xffffff801015a645
0xffffff912502bf40 : 0xffffff801015a171
0xffffff912502bfa0 : 0xffffff80100be13e
BSD process name corresponding to current thread: kernel_task
Mac OS version:
19H15
Kernel version:
Darwin Kernel Version 19.6.0: Thu Oct 29 22:56:45 PDT 2020; root:xnu-6153.141.2.2~1/RELEASE_X86_64
Kernel UUID: 9B5A7191-5B84-3990-8710-D9BD9273A8E5
Kernel slide: 0x000000000fe00000
Kernel text base: 0xffffff8010000000
__HIB text base: 0xffffff800ff00000
System model name: iMac15,1 (Mac-42FD25EABCABB274)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
System uptime in nanoseconds: 718088267634
last loaded kext at 18898386325: >DiskImages.SparseDiskImage 493.0.0 (addr 0xffffff7f945f0000, size 16384)
loaded kexts:
>DiskImages.SparseDiskImage 493.0.0
>DiskImages.ReadWriteDiskImage 493.0.0
>DiskImages.CryptoEncoding 493.0.0
>DiskImages.UDIFDiskImage 493.0.0
>DiskImages.HTTPBackingStore 493.0.0
>DiskImages.RAMBackingStore 493.0.0
>DiskImages.FileBackingStore 493.0.0
>!A!BMultitouch 97
>!AUpstreamUserClient 3.6.8
@kext.AMDFramebuffer 3.1.0
>AudioAUUC 1.70
@kext.AMDRadeonX4000 3.1.0
@kext.AMDRadeonServiceManager 3.1.0
>!AGraphicsDevicePolicy 5.2.6
@fileutil 20.036.15
@AGDCPluginDisplayMetrics 5.2.6
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.6f7
>AGPM 111.4.4
>X86PlatformShim 1.0.0
>!APlatformEnabler 2.7.0d0
>pmtelemetry 1
>!AHDAHardwareConfigDriver 283.15
>!AMikeyHIDDriver 131
@Dont_Steal_Mac_OS_X 7.0.0
>AGDCBacklightControl 5.2.6
>!A!IHD5000Graphics 14.0.7
>!AHDA 283.15
>eficheck 1
>!AMikeyDriver 283.15
>ACPI_SMC_PlatformPlugin 1.0.0
>!ABacklight 180.3
>!AThunderboltIP 3.1.4
@kext.AMD7000!C 3.1.0
|!ABCM5701Ethernet 10.3.5
>!ASMCLMU 212
>!ALPC 3.1
>AirPort.BrcmNIC 1400.1.1
>!AFIVRDriver 4.1.0
>!A!ISlowAdaptiveClocking 4.0.0
>!AMCCSControl 1.14
>!A!IFramebufferAzul 14.0.7
@filesystems.autofs 3.0
|IO!BUSBDFU 7.0.6f7
|SCSITaskUserClient 422.120.3
>!U!SCoexistentDriver 489.120.1
>!AFileSystemDriver 3.0.1
>!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
@private.KextAudit 1.0
>!ASDXC 1.7.7
>!AAHCIPort 341.140.1
>!ARTC 2.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
>DiskImages.KernelBacked 493.0.0
>!A!BHIDKeyboard 209
>IO!BHIDDriver 7.0.6f7
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport 3440.8
@kext.AMDRadeonX4030HWLibs 1.0
@kext.AMDRadeonX4000HWServices 3.1.0
>!AGraphicsControl 5.2.6
|IOAVB!F 850.1
@plugin.IOgPTPPlugin 840.3
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>IOPlatformPluginLegacy 1.0.0
@!AGPUWrangler 5.2.6
>!ABacklightExpert 1.1.0
|IONDRVSupport 576.1
@kext.AMDSupport 3.1.0
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOEthernetAVB!C 1.1.0
>!AHIDKeyboard 209
>!ASMBusPCI 1.0.14d1
|IO80211!F 1200.12.2b1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IOSkywalk!F 1
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
>!ASMBus!C 1.0.18d1
>!AThunderboltEDMSink 4.2.3
@!AGraphicsDeviceControl 5.2.6
|IOAccelerator!F2 438.7.3
|IOGraphics!F 576.1
@kext.triggers 1.0
>usb.IOUSBHostHIDDevice 1.2
|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
|IOUSBMass!SClass 4.0.4
>usb.!UHub 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.11
@filesystems.hfs.encodings.kext 1
>!AThunderboltDPOutAdapter 6.2.6
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
>!AThunderboltPCIDownAdapter 2.5.4
>!AXsanScheme 3
|IOAHCIBlock!S 316.100.5
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.1
|IOAHCI!F 290.0.1
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!A!ILpssGspi 3.0.60
>usb.!UHostPacketFilter 1.0
|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
|IOTimeSync!F 840.3
|IONetworking!F 3.4
|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
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 1.0
So I have finally been able to boot the Mac using an external SSD Drive (I was able to load Catalina from Command R)
Everything was looking great - I loaded the welcome screen etc and started to do a transfer from time machine - it then just died - black screen and had the message again in all languages that the computer had to restart because of an error ... press a key.
I was able to see the Problem Details
these are listed below. Does this mean there are further problems with the MAC and not the internal drive ?
I am hoping to just run the Mac from the External SSD drive - which does seem quite quick ...
panic(cpu 0 caller 0xffffff8010812667): "AppleAHCIDiskQueueManager::setPowerState(0xffffff8025124480 : 0xffffff7f919ab5d2, 3 -> 2) timed out after 100642 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.2.2/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffff912502bb40 : 0xffffff801011868d
0xffffff912502bb90 : 0xffffff8010252ab5
0xffffff912502bbd0 : 0xffffff801024463e
0xffffff912502bc20 : 0xffffff80100bea40
0xffffff912502bc40 : 0xffffff8010117d57
0xffffff912502bd40 : 0xffffff8010118147
0xffffff912502bd90 : 0xffffff80108bf2bc
0xffffff912502be00 : 0xffffff8010812667
0xffffff912502be50 : 0xffffff8010811f49
0xffffff912502be60 : 0xffffff80108294de
0xffffff912502bea0 : 0xffffff8010810cf8
0xffffff912502bec0 : 0xffffff801015a645
0xffffff912502bf40 : 0xffffff801015a171
0xffffff912502bfa0 : 0xffffff80100be13e
BSD process name corresponding to current thread: kernel_task
Mac OS version:
19H15
Kernel version:
Darwin Kernel Version 19.6.0: Thu Oct 29 22:56:45 PDT 2020; root:xnu-6153.141.2.2~1/RELEASE_X86_64
Kernel UUID: 9B5A7191-5B84-3990-8710-D9BD9273A8E5
Kernel slide: 0x000000000fe00000
Kernel text base: 0xffffff8010000000
__HIB text base: 0xffffff800ff00000
System model name: iMac15,1 (Mac-42FD25EABCABB274)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
System uptime in nanoseconds: 718088267634
last loaded kext at 18898386325: >DiskImages.SparseDiskImage 493.0.0 (addr 0xffffff7f945f0000, size 16384)
loaded kexts:
>DiskImages.SparseDiskImage 493.0.0
>DiskImages.ReadWriteDiskImage 493.0.0
>DiskImages.CryptoEncoding 493.0.0
>DiskImages.UDIFDiskImage 493.0.0
>DiskImages.HTTPBackingStore 493.0.0
>DiskImages.RAMBackingStore 493.0.0
>DiskImages.FileBackingStore 493.0.0
>!A!BMultitouch 97
>!AUpstreamUserClient 3.6.8
@kext.AMDFramebuffer 3.1.0
>AudioAUUC 1.70
@kext.AMDRadeonX4000 3.1.0
@kext.AMDRadeonServiceManager 3.1.0
>!AGraphicsDevicePolicy 5.2.6
@fileutil 20.036.15
@AGDCPluginDisplayMetrics 5.2.6
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.6f7
>AGPM 111.4.4
>X86PlatformShim 1.0.0
>!APlatformEnabler 2.7.0d0
>pmtelemetry 1
>!AHDAHardwareConfigDriver 283.15
>!AMikeyHIDDriver 131
@Dont_Steal_Mac_OS_X 7.0.0
>AGDCBacklightControl 5.2.6
>!A!IHD5000Graphics 14.0.7
>!AHDA 283.15
>eficheck 1
>!AMikeyDriver 283.15
>ACPI_SMC_PlatformPlugin 1.0.0
>!ABacklight 180.3
>!AThunderboltIP 3.1.4
@kext.AMD7000!C 3.1.0
|!ABCM5701Ethernet 10.3.5
>!ASMCLMU 212
>!ALPC 3.1
>AirPort.BrcmNIC 1400.1.1
>!AFIVRDriver 4.1.0
>!A!ISlowAdaptiveClocking 4.0.0
>!AMCCSControl 1.14
>!A!IFramebufferAzul 14.0.7
@filesystems.autofs 3.0
|IO!BUSBDFU 7.0.6f7
|SCSITaskUserClient 422.120.3
>!U!SCoexistentDriver 489.120.1
>!AFileSystemDriver 3.0.1
>!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
@private.KextAudit 1.0
>!ASDXC 1.7.7
>!AAHCIPort 341.140.1
>!ARTC 2.0
>!AACPIButtons 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
>DiskImages.KernelBacked 493.0.0
>!A!BHIDKeyboard 209
>IO!BHIDDriver 7.0.6f7
>!AMultitouchDriver 3440.1
>!AInputDeviceSupport 3440.8
@kext.AMDRadeonX4030HWLibs 1.0
@kext.AMDRadeonX4000HWServices 3.1.0
>!AGraphicsControl 5.2.6
|IOAVB!F 850.1
@plugin.IOgPTPPlugin 840.3
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>IOPlatformPluginLegacy 1.0.0
@!AGPUWrangler 5.2.6
>!ABacklightExpert 1.1.0
|IONDRVSupport 576.1
@kext.AMDSupport 3.1.0
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOEthernetAVB!C 1.1.0
>!AHIDKeyboard 209
>!ASMBusPCI 1.0.14d1
|IO80211!F 1200.12.2b1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IOSkywalk!F 1
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
>!ASMBus!C 1.0.18d1
>!AThunderboltEDMSink 4.2.3
@!AGraphicsDeviceControl 5.2.6
|IOAccelerator!F2 438.7.3
|IOGraphics!F 576.1
@kext.triggers 1.0
>usb.IOUSBHostHIDDevice 1.2
|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
|IOUSBMass!SClass 4.0.4
>usb.!UHub 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.11
@filesystems.hfs.encodings.kext 1
>!AThunderboltDPOutAdapter 6.2.6
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
>!AThunderboltPCIDownAdapter 2.5.4
>!AXsanScheme 3
|IOAHCIBlock!S 316.100.5
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.1
|IOAHCI!F 290.0.1
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!A!ILpssGspi 3.0.60
>usb.!UHostPacketFilter 1.0
|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
|IOTimeSync!F 840.3
|IONetworking!F 3.4
|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
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 1.0
ohmeo --
Where was the tm "transfer" going to?
To the new external SSD?
Or... to the internal HDD?
I'm wondering what might happen if...
... You got rebooted, then tried to re-install the tm backup to the INTERNAL drive instead?
I suggest you give this a try.
The worst that can happen is that it will crash again...
Where was the tm "transfer" going to?
To the new external SSD?
Or... to the internal HDD?
I'm wondering what might happen if...
... You got rebooted, then tried to re-install the tm backup to the INTERNAL drive instead?
I suggest you give this a try.
The worst that can happen is that it will crash again...
the back up was going to the SSD ...
I have done a lot of research and there appears to be an issue (mainly on laptops - but some iMacs) with the default settings in Energy Saver
discussions.apple.com
Something along these lines ...
anyway, I have now successfully restored from Time Machine
As soon as I revert to factory settings on Energy Saver - it happens again ... so 'turn display off' is currently set to never.
I am just updating catalina again - and will then probably update to Big Sur - to see if that fixes anything ...
I need some form of energy savings set - just need to keep playing I think ...
Thanks for your help.
I have done a lot of research and there appears to be an issue (mainly on laptops - but some iMacs) with the default settings in Energy Saver
SOLUTION to panic(cpu 0 caller 0xffffff80… - Apple Community
Something along these lines ...
anyway, I have now successfully restored from Time Machine
As soon as I revert to factory settings on Energy Saver - it happens again ... so 'turn display off' is currently set to never.
I am just updating catalina again - and will then probably update to Big Sur - to see if that fixes anything ...
I need some form of energy savings set - just need to keep playing I think ...
Thanks for your help.