Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Recovered.

My first attempt last night was restoring the disk image to the new SSD. That didn't work, so I went with plan B.

Plan B was downloading Super Duper and cloning the disk image to the APFS container on the SSD. Of course, I can't boot from that because no EFI partition. But that's where reinstalling the OS came in.

Booted from my USB stick and reinstalled Sonoma to the SSD. That gave me an EFI boot partition and I ran through the rest of the post install steps.

A few stumbles here and there because at certain points things didn't want to boot up. But I got there.

Dropbox was really the only problem. Didn't want to start, so I had to redownload and install it. Also had to redo the source drive on my backups under CCC. The app thought I was backing up back to the source, probably a residual from using the disk image to restore my data.

I have a few minor things I'm going to implement for the restore part of this if I have to do it again. Namely, a dedicated USB drive. I've ordered a new enclosure and will drop in one of my spare drives for that. The MBA does not have enough internal space to accept a drive image from the NAS so I had to disconnect the USB drive from my MP and use that with the MBA. I should probably also pick up another one of those SATA/USB adapters as well.

No idea what I'm going to do with the Zheino. Connecting it to the MBA has the drive come right up as if nothing happened. But I don't trust it.

Anyway, typing this on the Mac Pro. 7 hours of usage on the new SSD.
 
Last edited:
You'd need a program that will test its integrity etc. Maybe DriveDx?
Yeah, I have DriveDx but I hesitate to connect that drive right now. I've only connected it to the MBA so far and didn't play around with it much. It's not critical. I have more drive space than I know what to do with and about 8 hard drives of 1, 3 and 6TB sizes that are all just spares, plus two laptop drives.

I'll probably connect it to one of the Mac Minis when I bring those back online later, or perhaps the 2008 MBP. We'll see. I'm just curious what the SMART status will say, but not THAT curious right now.

I did learn something though. DriveDX did tell me there were three errors on the Zheino. No idea how long those were there but I found out a few weeks ago. But it was showing 98% of drive life left so I ignored it. Won't make that mistake with an SSD again.

EDIT: LOL, have to update my signature now. Apparently I've been updated to 14.6.1. :D
 
Last edited:
I've got faith in you. :)

If it's any consolation I've destroyed HDDs, drive enclosures and RAM chips. Among many other things...

4194ea6e-b6f7-43d7-8eec-ee63bed5a118_text.gif
I knocked over one of my 17" Studio Displays at one point. Tried to catch it, didn't work, the cable stripped itself on the desk edge and the display cracked when it landed.

@Raging Dufus can attest "That's why it's called it an accident, Erik!"
 
You could run it through its paces using f3. It fills the entire drive and checks if the data reads correctly. Any errors mean goodbye to the thing.

It's pitty that GUI is for 10.13 and up. :(
CLI f3 tools at packages.macports are available for every system beginning with 10.6
 
  • Like
Reactions: Amethyst1
I knocked over one of my 17" Studio Displays at one point. Tried to catch it, didn't work, the cable stripped itself on the desk edge and the display cracked when it landed.

@Raging Dufus can attest "That's why it's called it an accident, Erik!"

Oooof, I can visualise that transpiring in slow motion and the desperation of attempting to avert the inevitable. :(

It's pitty that GUI is for 10.13 and up. :(

Contrary to the description, F3XSwift does not work on High Sierra - as I've witnessed.
 
installed macOS 15 Sequoia on the 2014 Mac mini added some widgets and was playing the original FINAL FANTASY III not VI on the Super Nintendo but the pixel remastered version of the new original via wine
 

Attachments

  • Screenshot 2024-09-19 at 1.07.57 PM.png
    Screenshot 2024-09-19 at 1.07.57 PM.png
    1.2 MB · Views: 52
  • Like
Reactions: MacFoxG4
I did learn something though. DriveDX did tell me there were three errors on the Zheino. No idea how long those were there but I found out a few weeks ago. But it was showing 98% of drive life left so I ignored it. Won't make that mistake with an SSD again.
I suspect the life left -indication is a summary of calculations or statistics based on how many times has been written to the cells on the SSD. I guess other errors can occur and can kill a drive which are not related to the usage statistics. Like cells can die even if they are relatively new and/or unused and of course the controller board can have many kind of more or less severe component faults. Low quality or decaying caps, transistors or memory chips could cause weird behavior and lost or corrupted data. I am speculating but sounds logical to me.
 
  • Like
Reactions: eyoungren
Yeah, I have DriveDx but I hesitate to connect that drive right now. I've only connected it to the MBA so far and didn't play around with it much. It's not critical. I have more drive space than I know what to do with and about 8 hard drives of 1, 3 and 6TB sizes that are all just spares, plus two laptop drives.

I'll probably connect it to one of the Mac Minis when I bring those back online later, or perhaps the 2008 MBP. We'll see. I'm just curious what the SMART status will say, but not THAT curious right now.

I did learn something though. DriveDX did tell me there were three errors on the Zheino. No idea how long those were there but I found out a few weeks ago. But it was showing 98% of drive life left so I ignored it. Won't make that mistake with an SSD again.

EDIT: LOL, have to update my signature now. Apparently I've been updated to 14.6.1. :D
My go-to drive utilities: DriveDx (so I can tell if the thing is screwed at the hardware level), DiskWarrior5 (basically does the Disk Utility "Repair" function's job better, HFS only, and you'll have to get rid of the auto-startup doohickey it likes to put into logon items), CarbonCopyCloner5 (always better than SuperDuper, and copies the Recovery Partition), GetBackupPro3 (best cloning procedure: CCC5 first pass, start into drive to see in Activity Monitor if memory usage is correct, if not, then second pass with GPP3 and CCC5 again), EaseUSRecovery (deleted files/partition recovery), and ddrescue (command-line linux; used to sector-clone drives near death. On at least two occasions, a ddrescue successfully cloned a drive that then died permanently on the next start-up. Has the ability to skip bad-blocks on a first-pass, then try them again after all good blocks are recovered.)
 
A1181 Macbook, dead.
Symptoms:
No display, internal or external.
ODD sounds.
Beeps without RAM.
Charging working OK after cleaning magsafe port.
Tried SMC, PRAM etc, just in case.
Any starting points would be much appreciated!
If these have a PRAM battery, could this cause deadness if it were totally shot?
 
If these have a PRAM battery, could this cause deadness if it were totally shot?

It varies. There are A1181s which do have a replaceable PRAM battery whilst there are others that do not.

Have a look at the iFixit guide and judge whether you want to have a go as it's pretty intensive and annoying that Apple made this such a laborious task whereas with other manufacturers it's five minutes of work to access the CMOS battery.

 
  • Like
Reactions: DCBassman
It varies. There are A1181s which do have a replaceable PRAM battery whilst there are others that do not.

Have a look at the iFixit guide and judge whether you want to have a go as it's pretty intensive and annoying that Apple made this such a laborious task whereas with other manufacturers it's five minutes of work to access the CMOS battery.

Yeah read that. Bananas. But if the cell is shorted, maybe that's what is keeping it from booting? Or not, who knows?
 
  • Like
Reactions: TheShortTimer
Oooof, I can visualise that transpiring in slow motion and the desperation of attempting to avert the inevitable. :(
It was something more akin to fast forwarding. And since my hands were positioning another monitor at the time, making a quick grab would have meant letting go of the one I was working with. I'd bumped the Studio Display with my elbow.

OTOH, that incident marked the end of my attempts to stay consistent with the G4 period and put money down on the acrylic displays. That's when I started the hunt for the aluminum displays. Currently, I'm still a couple displays short (of the larger ones).
 
  • Like
Reactions: TheShortTimer
It just occurred to me that I have a spare parts MBP 15" 2011 with the high res antiglare -display and the newly acquired MBP 15" 2010 with the standard display.

I am wondering if I could transplant the better display to the older machine. Both years came with same spec display options.

So, are the displays between these two years compatible?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.