Author Topic: SSD disaster  (Read 4851 times)

0 Members and 1 Guest are viewing this topic.

Offline cgroen

  • Supporter
  • ****
  • Posts: 631
  • Country: dk
    • Carstens personal web
Re: SSD disaster
« Reply #25 on: February 06, 2020, 10:59:49 am »
Get a SSD of same type, move the memory chips from the dropped board to the new one, job done ?
I know, it requires someone with the right equipment, but its still doable if not possible in any other way (which I'm sure it is)
But yeah, "real men don't do backups, they cry"
Hello no  :palm:. Don't move anything, this SSD is easily fixable with bodge wires and preferably new connector if you still intend to use it. You will certainly need to move 2 NAND and controller chip + EEPROM if there is any. Almost any modern SSD have data encrypted and key is within controller. Not to say that even if it's not encrypted, it may have different firmware within it. Recommending moving BGA instead of bodge wires is just lame, not to say risk to screw up the data increases by many times.

You selected NOT to read all what I wrote ?
"lame", thanks  ::)
 

Online wraper

  • Supporter
  • ****
  • Posts: 16958
  • Country: lv
Re: SSD disaster
« Reply #26 on: February 06, 2020, 11:06:46 am »
You selected NOT to read all what I wrote ?
"lame", thanks  ::)
I've read before writing in your later post that bodge wires are OK as well. But even suggesting moving the chips deserves a harsh reprimand. Because you suggested a cumbersome way of easily destroying the data which can be easily recovered with nearly zero risk.
 
The following users thanked this post: tooki, gnavigator1007

Offline cgroen

  • Supporter
  • ****
  • Posts: 631
  • Country: dk
    • Carstens personal web
Re: SSD disaster
« Reply #27 on: February 06, 2020, 11:11:58 am »
You selected NOT to read all what I wrote ?
"lame", thanks  ::)
I've read before writing in your later post that bodge wires are OK as well. But even suggesting moving the chips deserves a harsh reprimand. Because you suggested a cumbersome way of easily destroying the data which can be easily recovered with nearly zero risk.

Totally agree, thats why I put "If NOT possible in any other way"
On a note, it can actually be done, moving the chips and saving your data that way. It wasn't easy, but the guy standing next to my desk in the lab seemed pretty happy about it :)
 

Online wraper

  • Supporter
  • ****
  • Posts: 16958
  • Country: lv
Re: SSD disaster
« Reply #28 on: February 06, 2020, 11:14:19 am »
On a note, it can actually be done, moving the chips and saving your data that way. It wasn't easy, but the guy standing next to my desk in the lab seemed pretty happy about it :)
I can do it myself but risk is there.
 

Offline Howardlong

  • Super Contributor
  • ***
  • Posts: 5323
  • Country: gb
Re: SSD disaster
« Reply #29 on: February 06, 2020, 11:40:51 am »
While the physical connections might be easy enough to repair for a skilled technician with the right tools, if there is FileVault storage encryption (with or without the T2 chip), how recoverable is it if the logic board is toast? I'm not saying it isn't recoverable, I am just interested to know how or if it could be achieved.
« Last Edit: February 06, 2020, 11:42:52 am by Howardlong »
 

Online wraper

  • Supporter
  • ****
  • Posts: 16958
  • Country: lv
Re: SSD disaster
« Reply #30 on: February 06, 2020, 11:51:30 am »
if there is storage encryption (with or without the T2 chip), how recoverable is it if the logic board is toast? I'm not saying it isn't recoverable, I am just interested to know how or if it could be achieved.
If controller holding encryption key is dead, you are screwed. Unless you have access to quantum computer which can brute-force decryption  :).
 

Online tooki

  • Super Contributor
  • ***
  • Posts: 11731
  • Country: ch
Re: SSD disaster
« Reply #31 on: February 06, 2020, 12:17:41 pm »
While the physical connections might be easy enough to repair for a skilled technician with the right tools, if there is FileVault storage encryption (with or without the T2 chip), how recoverable is it if the logic board is toast? I'm not saying it isn't recoverable, I am just interested to know how or if it could be achieved.
100% recoverable in this situation, since FileVault encryption is not tied to a logic board, but simply requires a decryption key, which is accessed via password. (You can use FileVault to encrypt external disks, too, and they simply need a password to mount.) Since the OP knows their login, they can mount the disk on any Mac, or use it to boot any Mac compatible with the OS version installed on the disk.

T2 encryption is separate from FileVault, and is strictly for onboard SSDs which use the T2 as the SSD controller itself. Basically, T2 encryption is the hardware-level encryption, while FileVault is the filesystem-level encryption. (FileVault is aware of the T2 hardware encryption and won't bother layering software encryption on top. Since a T2-based SSD cannot be separated from its logic board except by desoldering the flash chips, there's no ordinary situation in which you'd be attempting to mount it on a Mac other than the one it was written on.)
 

Online Berni

  • Super Contributor
  • ***
  • Posts: 4986
  • Country: si
Re: SSD disaster
« Reply #32 on: February 06, 2020, 12:25:52 pm »
Why would you desolder any of the chips if all you need to do is bodge wire in SATA and power to get it running again.

But yeah Rossman does offer data recovery services and this drive is a pretty easy job for him.
 

Offline Howardlong

  • Super Contributor
  • ***
  • Posts: 5323
  • Country: gb
Re: SSD disaster
« Reply #33 on: February 06, 2020, 01:34:25 pm »
While the physical connections might be easy enough to repair for a skilled technician with the right tools, if there is FileVault storage encryption (with or without the T2 chip), how recoverable is it if the logic board is toast? I'm not saying it isn't recoverable, I am just interested to know how or if it could be achieved.
100% recoverable in this situation, since FileVault encryption is not tied to a logic board, but simply requires a decryption key, which is accessed via password. (You can use FileVault to encrypt external disks, too, and they simply need a password to mount.) Since the OP knows their login, they can mount the disk on any Mac, or use it to boot any Mac compatible with the OS version installed on the disk.

T2 encryption is separate from FileVault, and is strictly for onboard SSDs which use the T2 as the SSD controller itself. Basically, T2 encryption is the hardware-level encryption, while FileVault is the filesystem-level encryption. (FileVault is aware of the T2 hardware encryption and won't bother layering software encryption on top. Since a T2-based SSD cannot be separated from its logic board except by desoldering the flash chips, there's no ordinary situation in which you'd be attempting to mount it on a Mac other than the one it was written on.)

OK thanks for the clarity, the FileVault sounds much like Bitlocker in that respect.

So if I am to understand you correctly, a failure of the T2 chip, practically speaking, renders the unit unrecoverable?

It looks like the T2 chip, as well as for soldered in SSDs, is also used for the new Mac Pro modular (but proprietary) SSD modules, so two points of failure if a T2 failure is also fatal.
« Last Edit: February 06, 2020, 01:47:17 pm by Howardlong »
 

Offline Renate

  • Super Contributor
  • ***
  • Posts: 1460
  • Country: us
Re: SSD disaster
« Reply #34 on: February 06, 2020, 02:05:04 pm »
Data pairs can be easily bodged (if you have a good iron with thin tips) from capacitors.
Yeah, SATA is (usually) capacitively coupled. C1-C4 are it.

If it were mine, I think that I'd just solder blob, suck up C1-4, tombstone big ol' 0805 caps on both pads and connect wires to the top.
 

Offline testpoint1

  • Frequent Contributor
  • **
  • Posts: 374
  • Country: us
Re: SSD disaster
« Reply #35 on: February 06, 2020, 02:47:51 pm »
this is a SM2258XT chip SSD, and the chip, Nand seems is OK, just use a Sata socket solder it, since the pad already strip, please be aware you have at least 10 years soldering tech with microscope, if no, I can help you in free, even replace the SM2258 chip; BTW, for the SM chip, if it failed, just replace a new chip, all data still over there.
 

Online tooki

  • Super Contributor
  • ***
  • Posts: 11731
  • Country: ch
Re: SSD disaster
« Reply #36 on: February 06, 2020, 04:43:07 pm »
While the physical connections might be easy enough to repair for a skilled technician with the right tools, if there is FileVault storage encryption (with or without the T2 chip), how recoverable is it if the logic board is toast? I'm not saying it isn't recoverable, I am just interested to know how or if it could be achieved.
100% recoverable in this situation, since FileVault encryption is not tied to a logic board, but simply requires a decryption key, which is accessed via password. (You can use FileVault to encrypt external disks, too, and they simply need a password to mount.) Since the OP knows their login, they can mount the disk on any Mac, or use it to boot any Mac compatible with the OS version installed on the disk.

T2 encryption is separate from FileVault, and is strictly for onboard SSDs which use the T2 as the SSD controller itself. Basically, T2 encryption is the hardware-level encryption, while FileVault is the filesystem-level encryption. (FileVault is aware of the T2 hardware encryption and won't bother layering software encryption on top. Since a T2-based SSD cannot be separated from its logic board except by desoldering the flash chips, there's no ordinary situation in which you'd be attempting to mount it on a Mac other than the one it was written on.)

OK thanks for the clarity, the FileVault sounds much like Bitlocker in that respect.
I believe so, with the caveat that I'm not much of a Windows expert. (Also, I should mention that what I described is the current version of FileVault, which is FileVault 2. The original FileVault 1 used in very old versions of Mac OS X worked entirely differently, merely moving a user's home folder (user directory) into an encrypted disk image.)

So if I am to understand you correctly, a failure of the T2 chip, practically speaking, renders the unit unrecoverable?
Yes. Exactly the same as in any other SSD with hardware encryption using a long key that's present only in the SSD controller.

It looks like the T2 chip, as well as for soldered in SSDs, is also used for the new Mac Pro modular (but proprietary) SSD modules, so two points of failure if a T2 failure is also fatal.
Oh! I didn't realize the new Mac Pro has modular SSDs! According to this report, the SSD module is married to the T2 on the logic board. It won't even POST without it present. Presumably, Apple has an internal utility to marry replacement parts, as they've had for other models (and iOS devices) for years.

Regardless, I don't see the T2 as being any more or less a point of failure than in any other SSD, since every SSD, by necessity, contains an SSD controller, and it can fail. And if it did, it presumably would take all the data with it.


What I love about Apple's ecosystem is that they REALLY, REALLY got backup and restore down PERFECTLY. Using Time Machine on a Mac means its backups are updated hourly. iCloud sync is usually real-time-ish. iCloud backups of iOS devices are performed daily, and local backups can be done manually. But whether it's a Mac backup from Time Machine or an iOS backup from iCloud or a local backup, when restoring to a new disk or new device, everything gets restored perfectly. Only the very pickiest of copy-protected applications on the Mac may need a license reactivation. I think that the ability to recover from disaster by, in the absolute worst case, going to Apple and purchasing a new device, and be back up and running within a few hours, is an advantage that is not valued nearly enough by most people. So anyway, if one is actually using Time Machine, then a T2 failure would normally mean a loss of no more than 1h of work.
 
The following users thanked this post: fzabkar

Offline sokoloff

  • Super Contributor
  • ***
  • Posts: 1799
  • Country: us
Re: SSD disaster
« Reply #37 on: February 06, 2020, 06:50:08 pm »
So anyway, if one is actually using Time Machine, then a T2 failure would normally mean a loss of no more than 1h of work.
I agree with most everything you say above, but have differences on this point. I’m frequently traveling for days or a week-plus at a time, often with limited or intermittent Internet connectivity and those are windows of exposure where my TimeMachine backups will not cover me against hardware failure within the laptop.
 

Online tooki

  • Super Contributor
  • ***
  • Posts: 11731
  • Country: ch
Re: SSD disaster
« Reply #38 on: February 06, 2020, 11:20:58 pm »
So anyway, if one is actually using Time Machine, then a T2 failure would normally mean a loss of no more than 1h of work.
I agree with most everything you say above, but have differences on this point. I’m frequently traveling for days or a week-plus at a time, often with limited or intermittent Internet connectivity and those are windows of exposure where my TimeMachine backups will not cover me against hardware failure within the laptop.
I travel with my MacBook, and so I bring a backup drive with me. Obviously it won’t protect against the backup drive AND the MacBook getting lost/stolen/damaged, but it will protect against hardware failure, disk corruption, or user error. No, I don’t keep the backup disk connected to it at all times, but even just remembering to do it after any session where I’ve saved lots of data will help. When no backup disk is connected, Time Machine will create hourly local backups (kinda like versioning) to protect against user error or software error, and then when you reconnect the backup disk, the local backups get synced into the backup disk.

Remember, time machine supports using multiple backup disks, so you can have, for example, two separate USB backup disks, and keep one at home only, and the other you take on the road. Or use a NAS for the backup at home, and a USB hard drive for travel/secondary backup. You can encrypt a backup disk with FileVault, so having it with you doesn’t pose much of a security risk.

When more than one backup disk is configured, Time Machine will simply alternate the hourly backup among all the currently-mounted backup disks in a round-robin fashion. On my Mac Pro, I have one internal 10TB backup disk (so always mounted), and one 10TB external USB disk that I connect periodically (for offsite backup). So when both backup disks are mounted, the hourly backups alternate between the two. When the USB disk is not connected, then every hourly backup is made to the internal backup disk.

Also, just to clarify a common misconception: Time Machine is the backup software, and it does NOT require you to use an Apple Time Capsule (network disk)! (Of course, the time capsule is discontinued now anyway.)
 

Offline scooby860110Topic starter

  • Contributor
  • Posts: 11
  • Country: us
Re: SSD disaster
« Reply #39 on: February 07, 2020, 03:27:09 am »
Who on here should i PM to see if they can help ? I got a quote and its $450, as I said i have 3 kids and a wife and $450 is too much.

Plz keep helping me get pointed to the right direction. Thanks yall for your help.


 

Offline drussell

  • Super Contributor
  • ***
  • Posts: 1855
  • Country: ca
  • Hardcore Geek
Re: SSD disaster
« Reply #40 on: February 07, 2020, 03:38:44 am »
That would be a $65-100 job here, (not including a replacement disk to dd the data onto.)

$450 is insane for a temporary connector fix if that's really all it needs.
 

Offline Ed.Kloonk

  • Super Contributor
  • ***
  • Posts: 4000
  • Country: au
  • Cat video aficionado
Re: SSD disaster
« Reply #41 on: February 07, 2020, 03:40:45 am »
$450 sounds a bit exy.

Quotes are negotiable. Did you negotiate?

iratus parum formica
 

Offline scooby860110Topic starter

  • Contributor
  • Posts: 11
  • Country: us
Re: SSD disaster
« Reply #42 on: February 07, 2020, 03:42:07 am »
Dear Testpoint1, Could you email me scooby9261@gmail.com ? I could really use the help and you seem to know much about this SSD.

 

Offline scooby860110Topic starter

  • Contributor
  • Posts: 11
  • Country: us
Re: SSD disaster
« Reply #43 on: February 07, 2020, 11:55:03 pm »
I think I have hope now. Lets see. 40+gb transferred to 320gb SATA laptop drive and ill be in heaven.

THANKS to you everyone, i cant thank you all enough

-Walt
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf