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.
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.You'd need a program that will test its integrity etc. Maybe DriveDx?
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.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.
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.
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.I've got faith in you.![]()
If it's any consolation I've destroyed HDDs, drive enclosures and RAM chips. Among many other things...
![]()
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.
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!"
It's pitty that GUI is for 10.13 and up.![]()
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.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.
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.)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.![]()
Contrary to the description, F3XSwift does not work on High Sierra - as I've witnessed.
I've tried all my usual tricks but there was no go. Dead parrot.
If these have a PRAM battery, could this cause deadness if it were totally shot?
Yeah read that. Bananas. But if the cell is shorted, maybe that's what is keeping it from booting? Or not, who knows?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.
![]()
MacBook Core Duo PRAM Battery Replacement
The time and date, as well as other settings, are kept by the PRAM battery when your machine is off. If you feel like you're stuck in the movie...www.ifixit.com
I immediately got that reference but for those who didn't...
Do you also remember what sketch followed it?![]()
...and that's okay. 😁"I didn't want to work in a pet-shop. I wanted to be a lumberjack!"
![]()
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.Oooof, I can visualise that transpiring in slow motion and the desperation of attempting to avert the inevitable.![]()